Should Salesloft kill its mobile app?

Direct Answer

Yes — Salesloft should ship lite mobile (10-12 essential workflows) under Vista discipline, NOT full-featured. Vista's R&D budget constraints make full mobile parity impractical: 4-6 engineers + ~$2-3M/yr cost for ~5-8% rep engagement = bad ROI. The lite path saves $1.5-2M/yr that goes to AI Cadence v2 + Drift integration.

The four conditions for keep/kill + lite-mobile design + Vista-portfolio comparable patterns. RFP table-stakes (~30-40% enterprise RFPs require mobile) prevent full kill; lite-mobile preserves checkbox while freeing Vista capital.

The Hard Numbers — Salesloft Mobile Usage

• Estimated weekly active users on mobile: ~12-20% of total seats
• Estimated time spent in mobile: ~5-8% of total Salesloft engagement
• Engineering investment under Vista: ~3-5 engineers + ~$1.5-2.5M annual cost
• Feature parity gap with web: ~30-40% of web features missing on mobile
• App Store rating: 3.5-4.0 stars (mid-tier sales tooling)
• Enterprise RFP requirement: ~30-40% of enterprise RFPs ask "do you have a mobile app?"

The 4 Reasons To KILL Outright

• Reason 1: Low usage relative to engineering cost — 5-8% engagement vs $1.5-2.5M annual investment = poor ROI
• Reason 2: Feature parity is impossible economically — Sales-engagement workflow is too complex for mobile-first
• Reason 3: Engineering opportunity cost — engineers could ship AI Cadence v2 OR Drift integration faster
• Reason 4: Outreach + Apollo mobile equally underused — category-wide pattern

The 4 Reasons To KEEP (At Least Lite)

• Reason 1: Enterprise RFP table-stakes — 30-40% of enterprise RFPs require mobile; killing loses 8-12% of enterprise deal flow
• Reason 2: Field sales motion still exists — industrial, manufacturing, healthcare reps in field need mobile call-logging
• Reason 3: Brand signal — mobile app says "we're a real platform"
• Reason 4: CSM + executive coaching mobility — managers reviewing rep activity on mobile during commute

The Lite-Mobile Design (Recommendation)

• Strip mobile app to ~10-12 essential workflows: call logging, sequence pause/resume, deal status check, manager dashboards, push notifications, basic prospect notes
• Reduce engineering investment from 3-5 to 1-2 engineers (~$500K-1M annual cost)
• Maintain App Store presence + RFP checkbox + brand signal
• Reallocate 2-3 engineers to AI Cadence v2 + Drift orchestration + Pipeline AI
• Acceptable feature parity: 80% of "essentials" workflows; explicit web-required for everything else

Why Vista Aligns With Lite-Mobile

• Capital efficiency mandate: Vista wants every R&D dollar to drive FCF + exit value
• Mobile ROI weakness: 5-8% engagement = bad signal to Vista
• Lite-mobile saves $1.5-2M/yr: redirects to higher-leverage AI investment
• Preserves RFP eligibility: keeps enterprise sales motion intact
• Net: Vista approves lite-mobile path; would push back on full mobile investment

Comparable Mobile App Decisions

• Outreach: lite-mobile per q1755 (~5-8% engagement, similar pattern)
• Apollo: lite-medium, ~10-15% engagement (data-first use case fits mobile better)
• Salesforce Sales Cloud Mobile: full-featured (massive enterprise demand drives investment)
• HubSpot Mobile: full-featured (PLG motion drives mobile signups)
• Drift Mobile: killed in 2022 to refocus
• Pattern: vertical-platform tools (Salesloft, Outreach) get away with lite mobile; horizontal-platform tools need full

What Lite-Mobile MUST Do Well

• Push notifications: real-time signal alerts (prospect engagement, deal milestone)
• Call logging: in-field rep logs call outcome quickly
• Sequence pause/resume: rep stops sequence on vacation; resumes back
• Manager dashboards: VPs review team activity on commute
• Quick prospect notes: rep adds notes between meetings

What Lite-Mobile DOESN'T Need To Do

• Sequence builder — keep web-only; complex UX
• Drift conversation marketing — keep web-only; complex chat workflow
• Deep reporting — keep web-only; data-dense
• Strategic Account workflow — keep web-only; multi-stakeholder complexity

A Markdown Table — Mobile Strategy Trade-Offs FY27

A Mermaid Diagram — Salesloft Mobile Decision FY27

Bottom Line

Salesloft should ship lite mobile (10-12 essential workflows, 1-2 engineers, $500K-1M/yr) and reallocate 2-3 engineers to AI Cadence v2 + Drift orchestration. Vista's capital efficiency mandate makes the call simpler than Outreach's. Honest call: full-featured mobile is bad ROI ($1.5-2.5M cost for 5-8% usage); killing entirely costs $20-40M ARR in lost enterprise RFPs.

Lite-mobile path captures 80% of value at 30% of cost. Decision deadline: Q1 2026 to free engineers for AI Cadence v2 timeline. (See also: q1789, q1797, q1808, Outreach q1755)

Tags

Salesloft, mobile-app, product-portfolio, rep-mobility, engineering-allocation, opportunity-cost, fy27-roadmap, kill-decisions, mobile-vs-web, enterprise-buyer

FAQ

Should Salesloft kill its mobile app entirely or ship a lite version? Salesloft should ship a lite mobile app of 10-12 essential workflows rather than killing it or maintaining full parity. Full-featured mobile costs $1.5-2.5M a year for only 5-8% engagement, which is poor ROI, while killing it outright loses 8-12% of enterprise RFP deal flow.

The lite path captures roughly 80% of the value at 30% of the cost.

What are the actual usage numbers behind the mobile decision? Weekly active users on mobile are about 12-20% of seats, time spent is about 5-8% of total engagement, and the feature parity gap with web is 30-40%. The app holds a 3.5-4.0 star rating, and 30-40% of enterprise RFPs ask whether a mobile app exists.

Low usage plus RFP table-stakes is what argues for lite rather than kill.

Which workflows should the lite mobile app keep? The lite app should keep call logging, sequence pause and resume, deal status checks, manager dashboards, push notifications, and basic prospect notes. It should drop the sequence builder, Drift conversation marketing, deep reporting, and Strategic Account workflows, all kept web-only for complexity reasons.

Push notifications and in-field call logging are the must-do-well features.

How much money does the lite path save and where does it go? Lite mobile cuts engineering from 3-5 down to 1-2 engineers, lowering cost from $1.5-2.5M to $500K-1M a year. The freed 2-3 engineers move to AI Cadence v2, Drift orchestration, and Pipeline AI. The net saving of roughly $1.5-2M redirects to higher-leverage AI investment.

Why does the lite-mobile call align with Vista's mandate? Vista wants every R&D dollar to drive free cash flow and exit value, and 5-8% mobile engagement is a bad ROI signal, so Vista would push back on full mobile but approve lite. Lite preserves the RFP checkbox and brand signal while freeing capital.

The decision deadline is Q1 2026 to free engineers for the AI Cadence v2 timeline.

Sources

• Https://www.salesloft.com/about
• Https://apps.apple.com/us/app/salesloft/id1080635954
• Https://play.google.com/store/apps/details?id=com.salesloft.connect
• Https://www.salesforce.com/products/sales-cloud-mobile/
• Https://news.salesloft.com/news-releases/news-release-details/salesloft-vista-equity-acquisition
• Https://www.bvp.com/atlas/state-of-the-cloud-2026
• Https://openviewpartners.com/saas-benchmarks/