Should Outreach kill its mobile app?

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

A Mermaid Diagram — Mobile App Decision Flow

The Hidden Cost of Maintenance vs. New Development

When evaluating whether to kill a mobile app, most leaders focus on the visible engineering headcount. But the real drain is often invisible: the cognitive overhead of maintaining two codebases, the QA cycles for every release, and the opportunity cost of features *not* built on the core platform. For a sales engagement platform like Outreach, every mobile-specific bug fix or API adjustment pulls engineers away from high-impact work on the web application—where 92-95% of rep activity actually happens. Industry benchmarks suggest that maintaining a mobile app alongside a web platform typically consumes 15-25% of an engineering team's capacity, even when the app sees minimal usage. That's not just $2-3M in salaries; it's 4-6 months of delayed roadmap features per year. The lite-app approach mitigates this by reducing the maintenance surface area by roughly 60-70%, since you're only supporting a handful of core workflows (logging calls, viewing next actions, quick edits) rather than the full sequence builder, analytics dashboards, and admin controls. For a company at Outreach's scale (roughly 5,000+ customers), the math shifts dramatically: a stripped-down app costs maybe $500K-800K annually to maintain, versus $2-3M for the full version, while still preserving the 8-12% of enterprise deals that require a mobile capability.

What Comparable Companies Actually Did

The "kill or keep" mobile app debate isn't unique to Outreach—several B2B SaaS companies in the sales and CRM space have faced the same question, and their outcomes offer useful patterns. Salesforce famously kept its mobile app but invested heavily in a simplified "Salesforce Mobile" that is deliberately less feature-rich than the desktop, focusing on record views, quick edits, and notifications—not full workflow automation. They saw mobile usage grow from roughly 5% of total logins to 12-15% after the simplification, because reps actually found it usable. HubSpot took a different path: they killed their standalone mobile CRM app in 2019 and rebuilt it as a lightweight companion that emphasizes contacts, deals, and tasks—explicitly avoiding the full marketing hub or CMS features. Their mobile engagement metrics improved by roughly 30% post-redesign. ZoomInfo, a direct Outreach competitor, launched a mobile app that is intentionally limited to search, contact details, and call logging—no sequence management or analytics. These patterns suggest that the market has already voted: full-featured mobile apps for sales engagement platforms are a mistake, but no mobile app at all is a deal-losing liability. The winning play is a focused, opinionated mobile experience that does 3-5 things well and doesn't pretend to replace the desktop.

How to Execute the Transition Without Losing Customers

If Outreach decides to kill the full app and launch a lite version, the execution matters more than the decision itself. A botched transition can trigger churn from the very enterprise customers the app was meant to retain. The recommended approach involves three phases over a 6-9 month timeline. First, communicate the change transparently to customers 60-90 days before any deprecation, framing it as a strategic focus on mobile reliability and speed rather than a cost-cutting measure. Second, launch the lite app with a clear feature parity document showing exactly what's preserved (call logging, task management, notifications, contact quick-views) and what's removed (sequence building, analytics dashboards, admin settings, custom reporting). Offer affected power users a 30-60 day grace period with access to both versions. Third, track mobile-specific NPS and usage metrics post-launch—a drop of more than 15 points in mobile NPS or a 20%+ decline in mobile active users would signal the lite app is too stripped down. For the 8-12% of enterprise deals that require mobile as a checkbox, the lite app should still satisfy RFP requirements because it includes the core rep workflow—calls, emails, tasks, and calendar sync. The key is to avoid the trap of adding features back over time, which is how the full app got bloated in the first place. Set a strict "no new mobile features for 12 months" policy after launch, and only consider additions based on clear usage data showing a feature is used by 30%+ of mobile users weekly.

The Lite App Middle Path — What to Build Instead

Rather than a binary kill-or-keep decision, Outreach should ship a "rep essentials" mobile app that strips away 70-80% of full-feature complexity while retaining the 3-5 actions reps actually perform on mobile:

• Notifications + quick actions — Read/respond to cadence emails, log calls, update deal stages (not full sequence creation)
• Calendar sync with one-tap join — Meeting links, buffer time, and follow-up task creation
• Pipeline glance + deal card — View stage, amount, next step; edit only the next-step field
• Voice-to-text logging — Kaia-style note capture without full transcription

This lite app would require 1-2 engineers to maintain (~$500K-800K annual cost) vs. the current $2-3M. It preserves the RFP checkbox and satisfies the ~8-12% of power users who genuinely need mobile access, while eliminating the drag of maintaining feature parity with web.

Comparable Patterns — What Similar Tools Have Done

The sales-engagement market shows a clear pattern: web-first, mobile-lite is the winning strategy.

• SalesLoft — Maintains a mobile app but deliberately limits it to logging activities, viewing cadences, and quick replies. No sequence builder, no analytics dashboards. Their mobile engagement sits at 6-10% of total usage.
• Apollo.io — Mobile app focuses on prospecting (search, save leads, log emails) but explicitly avoids full workflow management. Used primarily for on-the-go list building.
• HubSpot Sales Hub — Mobile app covers deal updates, meeting scheduling, and call logging, but the full CRM workflow remains web-only. Mobile users are 8-12% of active daily users.
• Gong — No mobile app at all for rep workflow; their mobile presence is limited to call recording and basic notifications. They chose to invest entirely in web depth.

The outlier would be full-CRM mobile apps (Salesforce, Pipedrive) where mobile engagement is higher (15-25%), but those are general CRM tools, not sales-engagement platforms. Outreach's core value — sequence automation, multi-touch cadences, analytics — is inherently web-native.

The Decision Framework — When to Actually Kill It

There are three scenarios where killing the app entirely makes sense:

1. If mobile usage drops below 3% of total engagement — At that point, even a lite app can't justify maintenance. This would require RFP requirements to shift away from mobile as a checkbox (unlikely in the next 2-3 years).

1. If the engineering team faces a critical competitive threat — For example, if Smart Email Assist is 6 months behind Gong's AI features and the mobile team is the only available resource. In that case, kill the app for 12-18 months and rebuild a lite version later.

1. If customer feedback consistently shows "I never use it" from >90% of users — Current data shows 15-25% weekly active users, so this threshold hasn't been reached.

Otherwise, the lite-app middle path is the optimal strategy: preserve the RFP checkbox, serve the power users, and redirect the bulk of engineering resources to web depth where 92-95% of actual workflow happens.

FAQ

Why would Outreach even consider killing its mobile app? The full-featured mobile app requires 4-6 engineers to maintain, costing roughly $2-3 million annually. Since reps use the mobile app only 5-8% of the time, the investment doesn't match the usage, making a leaner alternative more cost-effective.

Wouldn't killing the app lose customers? Yes, entirely removing the mobile app could risk losing 8-12% of enterprise customers who require mobile rep functionality as a standard RFP requirement. That's why a complete kill isn't recommended without a replacement.

What's the "lite app" middle path? Instead of a full-featured app, Outreach could build a "rep-on-the-go essentials" version focused on core tasks like viewing sequences, logging calls, and checking notifications. This reduces engineering overhead while still meeting enterprise mobile needs.

How much would a lite app cost to build and maintain? A lite app typically requires 1-2 engineers to develop and maintain, costing roughly $500,000 to $1 million annually. That's a significant savings compared to the $2-3 million for the full app.

What are the conditions for keeping the full app? Keep the full app if over 15% of your revenue comes from mobile-heavy industries (e.g., field sales), if customer churn risk from removing features exceeds 10%, or if competitors offer robust mobile experiences that could sway your buyers.

Are there similar examples of companies taking this approach? Yes, several B2B SaaS companies have replaced feature-heavy mobile apps with lightweight versions, like Salesforce's "Salesforce Mobile Lite" or HubSpot's simplified mobile CRM. These moves typically maintain customer satisfaction while cutting development costs by 50-70%.

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

Related on PULSE

• [Should Salesloft kill its mobile app?](/knowledge/q1814)
• [Is Outreach mobile app good enough in 2027?](/knowledge/q1781)
• [Is Salesloft mobile app good enough in 2027?](/knowledge/q1841)
• [Is Datadog mobile app good enough in 2027?](/knowledge/q1721)
• [Is ServiceNow's mobile app good enough in 2027?](/knowledge/q1661)
• [How Do I Get My Coffee Shop Staff to Drive Loyalty App Signups?](/knowledge/q15852)

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/