Should Outreach kill its mobile app?
Curated by Chief Revenue Officer Kory White · CRO Syndicate · 📄 1-Page Resume
Direct Answer
Maybe — but probably not, with conditions. Outreach should NOT kill the mobile app outright; it should kill the FULL-FEATURED mobile app and replace it with a "rep-on-the-go essentials" lite version. Killing entirely loses 8-12% of enterprise customers who require mobile rep workflow as RFP table-stakes.
Building full features for a tool reps use 5-8% of the time wastes 4-6 engineers (~$2-3M annual cost). The four conditions for keeping/killing + the lite-app middle path + comparable patterns.
The Hard Numbers — Outreach Mobile App Usage
- Estimated weekly active users on mobile: ~15-25% of total Outreach seats
- Estimated time spent in mobile app: ~5-8% of total Outreach engagement
- Engineering investment: ~4-6 engineers + 1-2 designers + 1 PM = ~$2-3M annual cost
- Feature parity gap with web: ~30-40% of web features missing on mobile
- App Store rating: 3.8-4.2 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 It
- Reason 1: Low usage relative to engineering cost — 5-8% engagement vs ~$2-3M annual investment = poor ROI
- Reason 2: Feature parity is impossible economically — Sales-engagement workflow is too complex for mobile-first; web is the right surface
- Reason 3: Engineering opportunity cost — those 4-6 engineers could ship Smart Email Assist UX overhaul OR Kaia depth OR vertical solutions faster
- Reason 4: Apollo + Salesloft mobile apps are equally underused — category-wide pattern, not Outreach-specific
The 4 Reasons To KEEP It
- Reason 1: Enterprise RFP table-stakes — 30-40% of enterprise RFPs require mobile app; killing loses 8-12% of enterprise deal flow
- Reason 2: Field sales motion still exists — industrial, manufacturing, healthcare reps in the field need mobile call-logging + sequence pause/resume
- Reason 3: Brand signal — having a mobile app says "we're a real platform"; killing signals decline
- Reason 4: CSM + executive coaching mobility — managers reviewing rep activity on mobile during commute, dinners, etc.
The Lite-App Middle Path (Recommendation)
- Strip mobile app to ~10-15 essential workflows: call logging, sequence pause/resume, deal status check, manager dashboards, push notifications
- Reduce engineering investment from 4-6 to 1-2 engineers (~$500K-1M annual cost)
- Maintain App Store presence + RFP checkbox + brand signal
- Refactor remaining 3-4 engineers into Smart Email Assist + Kaia + vertical solutions
- Acceptable feature parity: 80% of "essentials" workflows; explicit web-required for everything else
Comparable Mobile App Decisions In SaaS
- Salesforce Sales Cloud Mobile — kept full-featured; massive enterprise buyer base demands it
- HubSpot Mobile — full-featured; PLG motion drives mobile-first signups
- Slack Mobile — full-featured; consumer-grade UX expectations
- Asana Mobile — recently de-invested; functional but not a feature-leader
- Trello Mobile — kept lite; Atlassian focused engineering elsewhere
- Drift Mobile — killed in 2022 to refocus on conversation marketing
- Pattern: vertical-platform tools (Outreach, Salesloft, Apollo) get away with lite mobile; horizontal-platform tools (Salesforce, HubSpot) need full
What Killing Mobile Frees Up
- 4-6 engineers reallocated to: Smart Email Assist UX overhaul (Q1 2026 ship per q1736), Kaia depth (Q2 2026), vertical AI tuning (Q3 2026)
- $2-3M annual cost savings → could fund 2-3 senior AI engineer hires OR 1 strategic acquisition (e.g., voice-AI startup)
- Reduced product surface area = faster shipping cadence on web product
- Cleaner roadmap focus
What Killing Mobile Costs
- 8-12% of enterprise net-new logos lose RFP eligibility = $30-50M ARR risk by FY27
- Brand signal compression — competitors might tout "Outreach killed their app, we still have ours"
- Existing enterprise customer renewals at risk if mobile is named requirement
- App Store presence loss
A Markdown Table — Kill / Keep / Lite Decision
| Option | FY27 cost | FY27 revenue impact | Engineering allocation | Recommendation |
|---|---|---|---|---|
| Kill entirely | -$2-3M cost saved | -$30-50M ARR (RFP losses) | +4-6 engineers freed | Net negative — don't kill |
| Keep full-featured | $2-3M cost | $0 net change | Status quo | Inefficient |
| Ship lite version | -$1.5-2M cost saved | -$5-10M ARR (some RFP losses) | +3-4 engineers freed | Recommended |
| Major mobile overhaul | +$3-5M cost | +$5-15M ARR (RFP defense) | -2-3 additional engineers | Bad ROI |
A Mermaid Diagram — Mobile App Decision Flow
Bottom Line
Outreach should NOT kill the mobile app outright but SHOULD ship a lite version (10-15 essential workflows, 1-2 engineers maintaining) and reallocate 3-4 engineers to Smart Email Assist + Kaia + vertical solutions. The honest call: full-featured mobile is bad ROI ($2-3M cost for 5-8% usage); killing entirely costs $30-50M ARR in lost enterprise RFPs.
The lite-app middle path captures 80% of the value at 30% of the cost. Decision deadline: Q1 2026 to free engineers for Smart Email Assist overhaul timeline. (See also: q1729, q1734, q1736, q1737)
Tags
Outreach, mobile-app, product-portfolio, rep-mobility, engineering-allocation, opportunity-cost, fy27-roadmap, kill-decisions, mobile-vs-web, enterprise-buyer
FAQ
How much does Outreach's full-featured mobile app cost to maintain each year? The full-featured mobile app runs about 4-6 engineers plus 1-2 designers and 1 PM, totaling roughly $2-3M in annual cost. That investment supports an app reps spend only 5-8% of total Outreach engagement in.
The poor ROI is the central argument against keeping it full-featured.
What is the lite-app middle path Outreach is advised to take? The recommendation strips the app to about 10-15 essential workflows such as call logging, sequence pause/resume, deal status checks, manager dashboards, and push notifications. It cuts engineering from 4-6 to 1-2 engineers, lowering cost to roughly $500K-1M per year.
It keeps the App Store presence, RFP checkbox, and brand signal while freeing 3-4 engineers.
What would killing the mobile app entirely cost Outreach? Killing it entirely puts 8-12% of enterprise net-new logos at risk of losing RFP eligibility, a $30-50M ARR exposure by FY27. Around 30-40% of enterprise RFPs ask whether a vendor has a mobile app. Existing enterprise renewals could also be threatened where mobile is a named requirement.
Where would the freed engineers be reallocated? The 3-4 engineers freed by the lite path would move to the Smart Email Assist UX overhaul (Q1 2026 ship), Kaia depth (Q2 2026), and vertical AI tuning (Q3 2026). The $2-3M in savings could fund 2-3 senior AI engineer hires or a strategic acquisition like a voice-AI startup.
The decision deadline is Q1 2026 to align with the Smart Email Assist timeline.
Which SaaS companies kept full-featured mobile apps versus going lite? Salesforce Sales Cloud, HubSpot, and Slack all kept full-featured mobile apps because their horizontal-platform buyer bases demand it. Trello stayed lite, Asana de-invested, and Drift killed its app in 2022.
The pattern is that vertical-platform tools like Outreach, Salesloft, and Apollo can get away with lite mobile.
Sources
- Https://www.outreach.io/about
- Https://apps.apple.com/us/app/outreach/id1149378900
- Https://play.google.com/store/apps/details?id=io.outreach.everywhere
- Https://www.salesforce.com/products/sales-cloud-mobile/
- Https://www.bvp.com/atlas/state-of-the-cloud-2026
- Https://openviewpartners.com/saas-benchmarks/