How ElevenLabs' mobile app reached $1M ARR in 16 days
A lean mobile team at an AI audio company shipped two revenue-generating apps across iOS, Android, and web, unified a hybrid mix of subscriptions, credits, and content purchases, and reached $1M ARR with the flagship mobile app in 16 days — without diverting engineers into payments plumbing.
A lean team building AI audio for mobile
ElevenLabs is known for text-to-speech, voice agents, and an API used by creators building with voice AI. Its mobile work is strategic rather than peripheral: creators often begin and end workflows on phones, and the boundary between creator and consumer is narrowing. Over roughly a year and a half, the mobile team shipped the ElevenLabs app and the ElevenReader app across iOS, Android, and web. The team operated as a small, autonomous unit — fewer than 10 people for much of the year — where every engineering choice had to protect speed, reliability, and momentum.
Why the team did not build payments itself
Building payments in-house was rejected for a practical reason: assigning multiple engineers for months to payments infrastructure would have pulled focus from shipping product and improving the user experience, while introducing ongoing maintenance and bug risk. The decision rule for a small team is therefore simple — if a capability does not differentiate the product, buy or adopt it rather than building and maintaining it. That freed capacity for strategic work instead of maintaining monetization pipes.
The complexity of hybrid monetization across platforms
This was not a single subscription behind a single paywall. Alongside subscriptions, users could buy credit packs for usage-based consumption and purchase content directly, such as audiobooks and ebooks. All of it had to function across the App Store, Google Play, and Stripe on the web, and stay aligned with broader billing structures and customer records. The hard parts were not just setting up SKUs: entitlement logic, credit allocation, usage tracking, and consistent customer state across devices and platforms all interact. Trials and introductory offers multiply the edge cases further, because each change to a product or offer ripples across every platform.
Unifying monetization so engineers can ship product
The team chose {{OWNER_SUBSCRIPTION_PLATFORM}} to unify monetization across iOS, Android, and web. In practice that meant connecting SKUs across platforms, synchronizing entitlement and customer state, and keeping usage-based credit allocation and access rules consistent as pricing and offers changed. The operational benefit was focus: engineers could spend most of their time on new interactions and experiences instead of connecting payment systems together.
Analytics: warehouse events plus mobile-native reporting
On the growth side, the platform became a source of truth the team could act on quickly. Payment events were streamed into BigQuery via webhooks to maintain a complete log for deeper BI analysis. Built-in reporting supplied mobile-native views on trials, renewals, and churn — the kind of opinionated layer that is difficult to rebuild accurately from raw events alone, because mobile subscription nuances are easy to get wrong. Use both layers deliberately: warehouse events for heavy analysis, and purpose-built subscription reporting for fast, high-confidence answers.
Outcome and a checklist for similar teams
With monetization handled, the app reached $1M ARR in 16 days. The wider strategy is to build where creators are, grow with consumers, move fast with small teams, and keep engineers on work that differentiates the product rather than infrastructure that slows it down. For any small mobile team, the transferable checklist is: map every payment model and platform before choosing tooling; verify entitlement and credit sync across devices; test trials and intro offers as edge cases; stream events to your warehouse; and confirm you can answer trial, renewal, and churn questions without a bespoke rebuild.
| Payment model | What it covers | Platforms involved |
|---|---|---|
| Subscriptions | Recurring access to the product | App Store, Google Play, Stripe on web |
| Credit packs | Usage-based consumption | App Store, Google Play, Stripe on web |
| Direct content purchases | Audiobooks and ebooks | App Store, Google Play, Stripe on web |
Captured case-study description; confirm current product and pricing details with the owner before publication.
| Outcome | Captured result |
|---|---|
| Apps shipped | Two fully revenue-generating apps in a matter of weeks |
| ElevenLabs mobile app | $1M ARR in 16 days |
| Engineering focus | Capacity unlocked for strategic work instead of maintaining monetization pipes |
Unverified captured case-study claims; requires {{OWNER_CASE_STUDY_CONFIRMATION}} before publication as fact.
Frequently asked questions
How quickly did the ElevenLabs mobile app reach $1M ARR?
The mobile app reached $1M ARR in 16 days.
What monetization models had to work together?
Subscriptions, credit packs for usage-based consumption, and direct content purchases such as audiobooks and ebooks, operating across the App Store, Google Play, and Stripe on the web.
Why not build the payments infrastructure in-house?
A small mobile team — fewer than 10 people for much of the year, described as a lean team of 10 developers — chose not to build payments infrastructure in-house because that would have diverted engineers from product work and added maintenance and bug risk.
How was subscription data used for analysis?
Events were streamed into BigQuery via webhooks for a complete payments-event log and deeper BI analysis, while built-in mobile reporting provided views on trials, renewals, and churn.