TL;DR: Day 60 of my indie iOS experiment. The "MRR is the only metric that matters" advice is repeated everywhere. After looking at real Adapty 2026 data + my own funnel signals, here's why I think it's bad advice for cold-start indies.
The advice I kept hearing
For 60 days, every indie hacker podcast I listened to and every Twitter thread I read on indie monetization said variants of:
- "MRR is the only metric that matters"
- "Don't ship a product that isn't subscription-priced"
- "If you're not building toward $10k MRR, you're not serious"
- "VCs only care about MRR; you should too"
This sounds reasonable. SaaS economics are well-understood. Recurring revenue compounds. MRR is the metric you can put in a pitch deck.
But here's what nobody mentions: the data on which monetization model converts.
The Adapty 2026 benchmark
Adapty publishes annual benchmark reports across thousands of indie iOS subscription apps. Their 2026 report (the largest indie sample I've seen for benchmark conversion data) shows:
- Hard paywall apps (must-pay-to-use): 12.11% conversion
- Freemium subscription apps (free with subscription upsell): 2.18% conversion
That's not a tiny gap. That's 5.5×. For every 100 visitors:
- Hard paywall converts ~12 paying users
- Freemium subscription converts ~2 paying users
If your goal is paying customers per visitor, the data points hard at one-time pricing or hard paywall. The MRR-or-nothing advice ignores this.
Why the advice persists despite data
Three reasons:
1. Survivorship bias
The visible indie successes (Notion, Linear, Figma, Superhuman) all use subscription pricing. We see the winners. We don't see the 95% of indie subscriptions that died at <100 paying customers because conversion was 2%.
2. VC alignment
The advice optimizes for raising money, not for actually getting paid. VCs prefer MRR because it's what they understand. If you're not raising, this misalignment costs you.
3. The advice is from people who already won
Founders who hit subscription product-market fit retroactively justify subscription pricing. They forget the 12 months of zero traction before the model worked. New indies copy the advice without the timeline.
What the data actually suggests for cold-start indies
Looking at the same Adapty report + my own 60-day data:
For cold-start indie iOS (no existing audience, no paid acquisition budget):
- One-time IAP at $1.99-9.99 → 12% conversion likely
- One-time IAP at $19-49 → 4-6% conversion likely
- One-time IAP at $99-499 → 1-2% conversion likely
- Subscription (any price) → 1-3% conversion likely
The cross-over point: one-time IAP up to ~$30 dominates subscription on absolute conversion. Above that, subscription's compounding starts to matter — but only IF you can sustain the audience and not churn.
For my AutoApp portfolio: 4 apps × $1.99 IAP. Per Adapty math: each app needs ~8 visitors to convert 1 paying user. That's a tractable customer acquisition equation.
If the same apps were $4.99/month subscription: each app needs ~46 visitors to convert 1 paying user. AND the per-user revenue arrives in chunks, not upfront. The math gets harder.
My 60-day data
Real numbers, not extrapolated:
- iOS apps: 4, all awaiting Apple Review (no live revenue data)
- Gumroad SKUs: 5 LIVE, all one-time pricing
- B2B funnel: 600 unique visitors, 47 email captures (7.8%)
- Substack: 4 issues, ~10 cumulative subscribers (cold start)
- dev.to: 9 articles, 1247 top view (cold start)
The signal so far: hard paywall (Gumroad SKU buy) converts at industry standards. The Substack/dev.to followers (the "MRR-shaped" audience) compound slowly — 60 days for 10 subscribers is fine but not "VC traction."
If I'd built subscription apps from Day 1, I'd have:
- 4 subscription apps with 0 paying users (apps not approved yet)
- Same Substack subscribers (~10)
- Worse Gumroad data (subscription Gumroad doesn't fit the audience)
The MRR-first path costs option value. One-time pricing keeps options open.
The hidden cost of MRR-first thinking
Beyond the conversion math, MRR-first thinking creates these traps:
1. Support load explodes
Every paying subscription user is a recurring support customer. Refund requests, billing disputes, downgrade flows. For solo indies, this is the bottleneck — not the code.
2. Churn obsession
Once you have MRR, you spend half your time on retention. That's strategic for VC-backed SaaS. For indie scale, it's a distraction from shipping new products.
3. Cost of failure rises
Subscription failure = a year of users canceling and demanding refunds. One-time pricing failure = the product just stops selling. Recovery is faster.
4. Audience must be sustained
Subscription pricing requires a continuous audience to feed renewals. One-time pricing lets you ship-and-move-on.
What I actually recommend
For cold-start indie iOS / digital products:
- Default to one-time pricing unless you have specific reasons against it
- Write content that builds audience (dev.to, Substack, Twitter)
- Set up affiliate program at Day 1 so audience can earn from sharing
- Track conversion rate, not MRR, for the first 6-12 months
- Revisit subscription pricing only when you have real audience momentum
The MRR-or-nothing advice optimizes for a different game. If you're not playing that game, ignore it.
Source
Adapty 2026 benchmark report (private link, redistribute via Adapty's permission). My 60-day data: transparency dashboard.
Full reasoning on iOS one-time pricing decision: Why I Picked One-Time IAP over Subscription After Shipping 4 iOS Apps.
Want the full 60-day playbook with one-time pricing strategy + ASC checklist + B2B funnel? iOS Indie Launch Playbook ($19) — real data, 50pp PDF, 30-day refund.
