ASOhack
Back to Blog
Methodology

Mobile App Cost of Goods Sold (COGS): Economics for Indie Devs (2026)

Understanding the real cost of running a mobile app per user — server costs, AI API calls, payment processing, customer support. The framework for healthy unit economics.

ASOhack TeamMay 19, 20266 min read

Indie devs often think of revenue and don't think about COGS (Cost of Goods Sold). The result: surprises later when scale exposes margin issues.

This is the working framework for understanding the real per-user cost of running a mobile app.

What COGS includes for mobile apps

Infrastructure

  • Cloud hosting (Vercel, Netlify, Fly, AWS).
  • CDN bandwidth.
  • Database storage.
  • Backup storage.

Backend services

  • Authentication service.
  • Email delivery.
  • Push notifications.
  • Analytics service.

Third-party APIs

  • OpenAI / AI model API calls.
  • Image processing APIs.
  • Maps / location services.
  • Payment gateway fees.

Customer support

  • Support tool subscriptions.
  • Time of support staff (or you).

Refund / chargeback

  • Direct cost of refunds.
  • Indirect cost of disputes.

Apple / Google commission

  • 30% standard.
  • 15% for Small Business / Year 2+ subscriptions.

Examples by category

Simple utility app

  • Hosting: $0-$50/month.
  • Backend: $0-$20/month.
  • Support: $0-$50/month.
  • COGS per user: $0.01-$0.10/month.
  • Net margin: very high (80-90%+).

AI-powered app

  • Hosting: $20-$200/month.
  • AI API calls: $0.01-$0.10 per generation.
  • Support: $50+/month.
  • COGS per user: $0.50-$5.00/month (depends on usage).
  • Net margin: variable (40-70% typical).

Streaming / heavy bandwidth app

  • Hosting + CDN: $200-$2,000+/month.
  • Bandwidth scaling.
  • COGS per user: $1-$10/month.
  • Net margin: moderate (50-70%).

Subscription app with cloud sync

  • Hosting + database: $50-$500/month.
  • Backup storage.
  • COGS per user: $0.10-$1.00/month.
  • Net margin: high (70-85%).

The per-user cost analysis

For a typical $9.99/month subscription app:

Gross revenue: $9.99
Apple's 30% (year 1): -$3.00
Apple's 15% (year 2+): -$1.50
Stripe (if web-paid): -$0.30

Year 1 net: ~$6.99/month
Year 2+ net: ~$8.49/month

Minus your COGS per user:

If COGS is $0.50/user/month:
Year 1 margin: $6.49 / user / month
Year 2+ margin: $7.99 / user / month

This is your gross profit per user. Healthy.

COGS at scale

Most COGS components scale sub-linearly:

  • Hosting: doubles less than 2× per 10× user growth.
  • Support: scales linearly with user count.
  • AI APIs: scales with feature usage.
  • Apple commission: linear with revenue.

Implication: margins improve at scale. Indie devs at $1M MRR have better margins than at $10k MRR.

Calculating your COGS

Per-user model

Monthly COGS = (Fixed costs + Variable costs per user × User count) / User count

Per-user COGS = Fixed costs / User count + Variable per user

For most indie apps:

At 100 users: COGS may be $1+/user/month (fixed costs dominate)
At 10,000 users: COGS may be $0.20/user/month (variable dominates)
At 100,000 users: COGS may be $0.10/user/month (operational efficiency)

Hidden COGS

Beyond obvious costs:

Customer support

If you handle 1 ticket per 100 users per month, at $20/ticket of your time:

COGS per user: $20 × 0.01 = $0.20/month

Often forgotten.

Engineering time

Bug fixes + maintenance. If your hourly cost is $100 and you spend 10 hours/week on maintenance:

Monthly: ~$4,000 maintenance cost
At 10k users: $0.40/user/month maintenance

Not strictly COGS but worth tracking.

Refund costs

If refund rate is 5%:

Average subscription: $9.99 (year 1)
Refunds at 5%: $0.50 per subscription on average

Failed payments

Subscription apps see 5-15% involuntary churn (failed payments):

  • Card declined.
  • Card expired.

You retry; some recover. Lost revenue.

When COGS hurts margins

AI-heavy apps

If each user generates $5/month in AI API costs and you charge $9.99:

  • Net revenue: $6.99 (year 1).
  • COGS (AI): $5.
  • Margin: $1.99.

Tight.

Mitigations:

  • Cap free tier generations.
  • Tier pricing for heavy users.
  • Optimize AI usage (smaller models, caching).

Heavy bandwidth apps

Streaming or asset-heavy apps:

  • Each user costs $2/month in bandwidth.
  • Subscription $9.99 → $7 net → $5 margin.

Mitigations:

  • CDN caching.
  • Bandwidth-aware features.
  • Premium tier for high-usage.

Customer support heavy

Apps with complex workflows:

  • 10% of users contact support monthly.
  • Each ticket = $5 of time.
  • COGS per user: $0.50/month.

Mitigations:

  • Better in-app help.
  • Self-service.
  • FAQ + documentation.

The healthy margins target

For most mobile subscription apps:

  • Gross margin (after Apple cut): 70%+.
  • Operating margin (after COGS): 50%+.
  • Net margin (after fixed costs): 30%+.

If you're below these, fix COGS before scaling.

When margins are tight

Diagnose

Calculate per-user COGS. Identify biggest contributors.

Optimize

For each contributor:

  • Hosting: move to cheaper providers, optimize queries.
  • AI calls: cache, batch, use smaller models.
  • Support: improve documentation, automate.

Pricing

If margins are stuck, consider pricing increase. Test.

Feature decisions

Some features are COGS heavy. Decide if their value justifies cost.

Premium tier pricing for high-COGS features

For features that cost real money per use (AI, bandwidth, etc.):

  • Basic tier: limited usage (basic features).
  • Pro tier: unlimited (higher price).
  • Premium tier: power users (highest price).

Match price to usage. Otherwise margins collapse at high usage.

Track these metrics monthly

  • COGS per active user.
  • COGS per paying user.
  • Gross margin (after Apple cut + COGS).
  • Customer support tickets per active user.
  • AI / API calls per user (if applicable).

These tell you when margins are healthy vs deteriorating.

What kills indie margins

Mistake 1: AI app at fixed price

Heavy AI usage destroys margin.

Mistake 2: free tier without limits

Power users on free tier cost you money.

Mistake 3: too aggressive customer service

Slack tickets per user explodes COGS.

Mistake 4: ignoring refund / chargeback rate

5%+ refund rate often signals trust issues.

Mistake 5: over-engineering features

Some features cost more per user than they generate.

When to raise prices

Signals you should consider:

  • Margin tight.
  • Competition shows higher prices.
  • LTV stable or growing.
  • Users tolerate well in surveys.

How to raise:

  • Test on new users first.
  • Grandfather existing.
  • Announce changes clearly.

See pricing psychology.

Common mistakes

  • Not calculating COGS. Surprised at low margin.
  • Free tier without limits. Loss on heavy users.
  • AI pricing without usage tiers. Margin collapses.
  • Skipping support automation. COGS explodes.
  • Ignoring refund / chargeback rate. Trust issue + cost.

Run an audit

Healthy margins start with healthy retention. Bad retention → high acquisition needs → COGS dominated by acquisition. Run free ASO audit to ensure listing converts retention-worthy users.

Try the tools

Ready to Optimize Your App Store Listing?

Try our free ASO tools — no signup required.