Try “ad networks with no minimum”, “paid newsletter”, “Mediavine” · Esc to close

Case study

Overcast: Marco Arment's podcast app that published its own $164K first-year sales

Marco Arment shipped Overcast, an iOS podcast player, on July 16, 2014, and did something almost no other indie app developer did at the time: nine months…

23 September 2026 · 3 min read · figures for 2014

Property
Overcast
Type
Mobile app
Niche
Tech & SaaS
Audience
318,996 monthly users
Revenue
$164,134 in in-app purchase revenue in 2014 (first partial year), after Apple's cut
Year
2014

Visit Overcast ↗ Source ↗

Overcast: Marco Arment's podcast app that published its own $164K first-year sales
Photo by Sanket Mishra on Pexels

Marco Arment shipped Overcast, an iOS podcast player, on July 16, 2014, and did something almost no other indie app developer did at the time: nine months later he published the exact sales numbers on his blog, marco.org. No range, no "six figures" hand-wave — actual dollars, actual unit counts, actual expenses.

The numbers

Overcast is free to download, with a single non-consumable in-app purchase called "Unlock Everything," priced at Apple's $5 tier. In its first partial year:

  • 318,996 downloads, about 200,000 of which created an account
  • 46,940 in-app purchases, a 14.7% conversion rate across the year (16.3% in the months after the launch spike settled)
  • $164,134 in revenue after Apple's cut
  • Apple itself collected $70,343 from that one app in 2014 — the 30% platform tax on every one of those unlocks
  • A first-month launch spike of $85,715, settling to a monthly average of about $15,684 for the rest of the year
  • Running costs were tiny next to that: roughly $750 a month in server and hosting costs, plus a one-time ~$12,000 trademark-coexistence agreement to keep the Overcast name

That's the entire monetization method in one line: a single in-app purchase, sold once per user, with Apple as the only payment processor and the only toll collector. There was no ad network, no sponsorship deck, no email list to build first — the app itself was the storefront.

The revenue mix

Overcast's mix is deliberately narrow, which is part of what makes it a clean case study. Almost all of it runs through in-app purchases and app subscriptions — Apple's StoreKit handled the transaction, the receipt validation and the payout, and Arment never had to touch a card number. For an indie developer with no support team and no billing infrastructure, that's the appeal: you accept Apple's 30% instead of building or renting a payments stack.

RevenueCat 🧰 PlatformFreemium

In-app subscription infrastructure for iOS, Android and web: paywalls, entitlements, analytics; free up to $2,500 MTR.

#2.1k web rank

8.7 Visit ↗

That RevenueCat listing is what most indie iOS developers would reach for today to do what Arment built by hand in 2014 — wrapping StoreKit receipt validation, renewal tracking and paywall experiments into one SDK instead of writing it from scratch. Arment shipped before that category existed in its current form; a founder running the same playbook now would spend far less engineering time getting to the same $15k/month run rate.

Why it worked

Three things made this work as a business, not just a hobby project:

  1. A single price point, decided once. No tiers, no trial-then-nag funnel, no metered paywall. One purchase, one unlock, sold to people who already loved the free version enough to want more.
  2. Distribution was free. Overcast rode the App Store's own discovery — podcast enthusiasts searching for podcast apps — instead of paying for installs. The 14-16% conversion from download to purchase is unusually high because the audience was pre-qualified: people who install a niche podcast player are already invested in podcasts.
  3. Radical transparency became its own marketing. Publishing real numbers turned a routine blog post into a widely-linked industry data point (it hit Techmeme and Six Colors within a day), which is free publicity that a growth-hacked launch post can't buy.

What to take from it

If you're building a utility app rather than a content property, in-app purchases are still the simplest monetization model on this site to reason about: no ad network approval, no rate card, just a price and Apple's cut. The trade-off is the one Arment's own numbers expose — Apple took $70,343 of the $234,477 the app actually generated, a fixed 30% regardless of your margins. Model that tax into your price before you launch, not after. And if you want the same transparency-as-marketing effect Arment got, publish your first real numbers once you have a full year of them, not a cherry-picked best month.

Methods in this case study

In-App Purchases & App Subscriptions Medium

Sell upgrades, consumables and subscriptions inside an iOS or Android app through the store's billing, at a 15-30% store cut.

💰 $20-150 per 1,000 monthly users; 2-5% of users pay · ⏱ 1-3 months · 👣 1k/mo

8.0 Guide →

Networks and platforms mentioned

RevenueCat 🧰 PlatformFreemium

In-app subscription infrastructure for iOS, Android and web: paywalls, entitlements, analytics; free up to $2,500 MTR.

#2.1k web rank

8.7 Visit ↗

What could your property earn?

Pick what you have, your monthly traffic, niche and audience location, and see what every method would typically pay and which networks accept you.

Open the earnings calculator

More case studies