How to Price Your Indie App (Without Leaving Money on the Table)
I keep seeing the same pattern: a developer spends six months building an app, then picks a price in about ten minutes. Usually by looking at what competitors charge and going slightly lower. That's like spending a year designing a house and then flipping a coin on the foundation. Pricing is the single highest-leverage decision you'll make, and it deserves real thought.
The math that should keep you up at night
Say you have 1,000 paying users at $4.99/month. That's about $60,000 a year. Now imagine you had charged $6.99 instead. Same number of users, same product, same effort. That's $84,000. You just left $24,000 on the table by picking the wrong number.
In practice it's not that clean. A higher price might mean fewer conversions. But the relationship isn't linear. Most indie devs assume raising the price by 40% will lose 40% of customers. The actual number is usually closer to 5-15%, depending on the category. The math almost always favors a higher price than your gut says.
Patrick Campbell (ProfitWell founder) spent a decade studying SaaS pricing and found that companies who actively worked on pricing grew 2-4x faster than those who set it once and forgot about it. There's no reason to think apps are different.
Stop racing to the bottom
The App Store trains developers to think small. $0.99 apps. Free with ads. “Nobody will pay $10 for an app.” That was maybe true in 2012. The market has matured. People pay $7/month for Duolingo. $13/month for YouTube Premium. $80/year for a weather app (Hello Weather). The ceiling is higher than you think.
Here's the problem with pricing low: you attract price-sensitive users. These are, on average, the hardest customers to please and the quickest to leave a one-star review. Raise your price and you filter for people who actually value what you built. Your support load goes down, your review quality goes up, and you have more money to reinvest in the product.
I'm not saying charge $50/month for a to-do list. I'm saying the right price is probably 30-50% higher than whatever number just popped into your head.
How to actually find your price point
Forget cost-plus pricing. Your costs are irrelevant to the user. Nobody cares that your server bill is $200/month. They care about the value they get.
1. Figure out what you replace
Every app replaces something. A time tracker replaces a spreadsheet (free) or a freelancer's lost billing hours ($$$). A meal planner replaces food waste and takeout spending. A sleep tracker replaces... well, nothing, but it taps into health anxiety, which people spend freely on.
Your price should be a fraction of the value you create. If your expense tracker helps someone save $200/month on wasted subscriptions, charging $4.99/month is an easy yes. That's a 40x return. Even $9.99 is still 20x.
2. Study your category, not just your competitors
Open the App Store and look at the top 20 apps in your category. Not your direct competitors. The whole category. What's the price range? Where do the successful indie apps cluster?
In Productivity, subscriptions from $2-$8/month are standard. In Health & Fitness, $5-$15/month is normal. In Photo & Video, one-time purchases from $5-$30 still work well. Utilities tend toward one-time purchases or very cheap subscriptions. Know the norms, then decide if you want to work within them or break them (and have a reason for breaking them).
3. Pick a number and then raise it
Whatever price feels right, add 20%. Seriously. Most indie devs dramatically undervalue their work. If $4.99/month felt right, try $5.99. If $29.99/year felt right, try $34.99. You can always lower it later. Raising a price on existing users is much harder.
The free tier question
Should your app have a free tier? Almost certainly yes, unless you're in a niche with strong buyer intent (professional tools, B2B utilities). The question isn't whether to have a free tier. It's where to draw the line.
Too generous: you never convert anyone
If your free tier does 90% of what people need, they'll never pay. This is the most common mistake. You built a great free app with a donation box that nobody uses. The free tier should give users enough to understand the value and want more. Not enough to be satisfied.
Too stingy: nobody sticks around to upgrade
If the free tier is so limited that people can't get any value from it, they leave before they see what they'd be paying for. A 3-day free trial with no real functionality isn't a free tier. It's a demo that nobody finishes. The paywall itself matters too — when and how you present it shapes whether anyone sticks around long enough to convert.
Where the line usually works
The best free tiers I've seen follow one of these patterns:
- Usage limits: Free for 5 projects, pay for unlimited. Works because users hit the wall exactly when they're most invested.
- Feature gates: Core features free, advanced features paid. Works when the advanced features are genuinely advanced (not basic features held hostage).
- Time-limited full access: 7-14 day trial of everything, then downgrade. Works because users get used to the full experience and feel the loss.
Structured, the daily planner, does this well: the free tier lets you use the app fully, but limits you to basic templates. The paid tier ($12/year) unlocks everything. By the time you care about templates, you already love the app.
Price anchoring: the psychology that actually works
Anchoring is one of the few psychological pricing tactics that works reliably. The idea is simple: people judge prices relative to other prices they've seen, not in absolute terms.
If you offer two plans at $4.99/month and $9.99/month, most people pick $4.99. But if you add a $19.99/month plan (even if nobody buys it), the $9.99 plan suddenly looks like the smart middle option. This is well-documented. It's why every SaaS company has three pricing tiers.
For indie apps with simpler pricing, you can anchor differently:
- Show the monthly price first, then the annual price as a discount. “$7.99/month or $49.99/year (save 48%)” anchors on $96/year, making $50 feel like a deal.
- Compare to what users currently spend. “Less than one coffee per month” is cliche, but the framing works. Be more specific: “Less than a single Uber Eats delivery fee.”
- If you're replacing an expensive competitor, say so. “Toggl charges $9/user/month. We're $4.99 for everything.”
Regional pricing: free money most devs ignore
Apple and Google both let you set different prices per country. Most indie devs don't bother, which means someone in Brazil or India sees the same $9.99/month as someone in the US. Adjusted for purchasing power, that's like charging $40/month. Those users just leave.
Setting regional pricing takes about 30 minutes and can increase your total revenue 15-30%, depending on your user base. The App Store has predefined price tiers per country. Google Play lets you set arbitrary prices per region. Use both.
If you're targeting Asian markets specifically, localized pricing is even more critical. Our localization guide for Asian markets covers the payment method and pricing nuances for Japan, Taiwan, and Korea.
The Geo Arbitrage scanner can help you find markets where your competitors haven't bothered with localized pricing, giving you an opening.
Annual vs monthly: the tradeoffs nobody talks about
Conventional wisdom says push annual plans because they reduce churn. That's true. But there are tradeoffs.
Monthly plans let users try your app with low commitment. If your app has a learning curve or takes time to show value (habit trackers, fitness apps), monthly makes the first conversion easier. You can always upsell annual later, once they're hooked.
Annual plans lock in revenue but create a cliff. Users who auto-renew annually might not notice the first renewal. But when they do, they often cancel outright instead of downgrading. Monthly churners sometimes come back. Annual cancellers rarely do.
What works: offer both. Default to showing annual (with the savings highlighted). Let users switch to monthly if they want. Most will pick annual anyway. The ones who pick monthly are users you would've lost entirely if annual was the only option.
When subscriptions backfire
Not everything should be a subscription. This might be heresy in 2026, but some apps are better off with one-time pricing.
Users can smell when a subscription doesn't make sense. A QR code scanner with a $4.99/month subscription? A unit converter that charges weekly? These apps get destroyed in reviews. The subscription model works when there's ongoing value: cloud sync, fresh content, continuous updates, server costs. It doesn't work when the app does one thing and doesn't change.
For a deeper look at which model fits which category, see our breakdown of indie app revenue models. The short version: if users would reasonably expect your app to work forever after paying once, a subscription will frustrate them. Consider a one-time purchase with optional paid upgrades for major new features.
If you do go the subscription route, expect churn. It's unavoidable. What matters is understanding which churn is preventable and which is just the cost of doing business.
How to test pricing when you have a small user base
Enterprise SaaS companies run A/B tests on pricing pages with millions of visitors. You have maybe 500 monthly visitors and a handful of trial users. Different game.
Here's what actually works at indie scale:
- Sequential testing: Run one price for 2-4 weeks, switch, run another for 2-4 weeks, compare. Not statistically rigorous, but better than guessing. Track conversion rate and total revenue, not just one of them.
- Ask users directly: The Van Westendorp method works: ask “At what price would this be too cheap to trust? A bargain? Getting expensive? Too expensive?” Plot the curves. The intersection tells you the acceptable range. You can do this with 20-30 responses.
- Watch competitor reviews: Go to your competitors' App Store pages and search reviews for “expensive,” “price,” “cost,” and “worth.” You'll learn what price points trigger complaints and which feel acceptable. Our guide to reading App Store reviews covers this technique in detail.
- Launch high, discount down: Start at your high-end estimate and offer a limited “launch price.” This lets you test the higher price while still converting users. If the launch price converts well, your “regular” price might work too. If it doesn't, you keep the launch price and nobody feels burned.
Pricing mistakes that cost real money
Pricing by competitor, not by value
“My competitor charges $4.99, so I'll charge $3.99.” This assumes your competitor priced correctly. They probably didn't. They probably did the same thing you're doing now, looking at someone else and going a dollar lower. It's underpricing all the way down.
Price based on the value you deliver. If your app is meaningfully better than the competition, charge more, not less. A lower price signals lower quality. In the Downgrade Rage scanner, you can see apps where users are furious about declining quality. A better alternative at a higher price is exactly what those users want.
The $0.99 trap
After Apple's 30% cut and taxes, you keep about $0.50 from a $0.99 purchase. You need 10,000 sales to make $5,000. At $4.99, you need about 1,500 sales for the same revenue. And those 1,500 buyers will be better customers on average. Unless you're building a viral game that needs millions of downloads, the $0.99 tier is a trap.
Changing prices without a plan
Some developers panic-change their price every few weeks when downloads dip. This is noise. You need at least 2-4 weeks of data at a given price to draw any conclusions. Track conversion rate (App Store impressions to downloads), not just absolute download counts. Downloads fluctuate for dozens of reasons that have nothing to do with price.
Ignoring lifetime value
If your average user stays subscribed for 8 months at $4.99/month, your LTV is about $40. If you could increase retention by one month (through better onboarding, not price changes), that's another $5 per user. Sometimes the best pricing move isn't changing the price. It's making users stay longer.
What tends to work by category
Based on what I've seen across hundreds of indie apps in our scanner data:
- Productivity: $3-$7/month or $25-$50/year. Subscriptions work because users rely on these daily. Cloud sync is the natural paywall.
- Health & Fitness: $5-$12/month. Users are buying motivation and accountability, which makes them less price-sensitive than you'd expect. Annual plans work well here because fitness is aspirational.
- Photo & Video: $5-$30 one-time or $3-$8/month. Creative tools can go either way. One-time works for single-purpose editors. Subscriptions work when there are ongoing filter packs or cloud features.
- Utilities: $2-$10 one-time. Subscription fatigue is strongest here. People don't want to rent a calculator. Keep it simple.
- Education: $5-$15/month. Parents will pay more than they would for themselves. Family plans and per-child pricing work well.
These aren't rules, just patterns. The best indie apps sometimes break category norms deliberately. A one-time-purchase productivity app at $29.99 can work if you position against subscription fatigue (see: Cardhop, Fantastical's old model, many of the apps covered in our successful clones case study).
Pricing is easier when the market is right
The hardest pricing situation is a crowded market where every competitor is racing to zero. The easiest is a market where demand is high and alternatives are poor. In the second scenario, you can charge a premium and users are happy to pay because nothing else solves their problem well.
This is why market selection matters as much as pricing strategy. If you haven't chosen what to build yet, our guide to finding profitable app ideas covers how to identify markets where pricing power is strong. The Rising Niche scanner is specifically designed to find categories with growing demand and weak competition.
Even if you've already built something, validating that real demand exists will give you confidence to price higher. See our validation guide for the framework.
Practical first steps
If you're about to launch and need to pick a price this week:
- Scan the top 20 apps in your App Store category. Note the price range. Ignore the free apps backed by venture capital. Focus on what independent apps charge.
- Estimate the value you create. Be specific. Time saved, money saved, frustration avoided. Your price should be 5-20% of that value.
- Pick a price at the higher end of your comfort zone. Start there. You can offer a limited launch discount, but don't start at the bottom.
- Set up analytics to track conversion rate at the paywall. Not just downloads. Actual conversion. If you don't measure this, you're flying blind.
- Plan to revisit pricing in 30 days with data. Not feelings. Data. What's the trial-to-paid conversion rate? What's the LTV? What are people saying in reviews about the price?
If you're already live and want to optimize, our ASO guide covers how to track and improve conversion rates on your App Store listing, which directly affects the value you extract from any price point.
The uncomfortable truth
Most indie developers underprice because they're afraid of rejection. Charging more feels presumptuous. What if nobody pays? What if people are angry?
But here's the thing: a higher price with fewer users usually means more revenue, better reviews, lower support load, and a more sustainable business. The developers who charge $0.99 or give everything away for free aren't more virtuous. They're just more likely to burn out and abandon their app in a year.
Price for sustainability. Your future self will thank you. If you're getting close to the point where your app could replace your salary, our guide to going full-time walks through the numbers and timing.
Find markets where users will pay
AppOpportunity scans the App Store across 5 countries to find categories where demand is high and alternatives are poor. Better markets mean easier pricing decisions.
See Pricing →