TL;DR: To find out how much an app is worth, define whether you mean market value, asking price, replacement cost, or buyer value, then build the estimate from revenue, profit, costs, retention, growth, founder dependence, and risk. For a small app, a rough, risk-adjusted range is usually more useful than a fake-precise number.

Start by defining what “worth” means for the app

Before you do any math, decide which number you actually need. App value can mean market value, asking price, replacement cost, or what a specific buyer would pay. Those are related, but not the same.

Market value is the most useful number for a sale. Asking price is what you hope to get, which is not a valuation method. Replacement cost asks what it would take to rebuild the app from scratch, which matters when the codebase is the main asset. Buyer value is the number a particular buyer sees after weighing upside, remaining work, and risk.

The right method depends on the situation. Selling a profitable indie app is not the same as pricing a side project, and neither is the same as estimating what the code is worth to a developer who wants to acquire it and move on.

Gather the inputs that actually drive app value

Start with the unglamorous details, because they usually decide the price.

Collect these first:

  • Revenue, if the app makes money.
  • Profit, not just revenue, because expenses matter.
  • Costs, including hosting, support, subscriptions, maintenance, and contractor work.
  • User base, but only as context.
  • Retention, because users who vanish quickly are a weak asset.
  • Growth trend, whether the app is rising, flat, or declining.
  • Dependency on the founder, because a business that only works when one person is around is harder to transfer.
  • Risks around platform policy or IP, because those can reduce what a buyer will pay.

For iOS apps, review and policy risk matters too. Apple’s App Store Review Guidelines exist for a reason, and a buyer will usually discount anything that looks likely to be blocked, delayed, or repeatedly revised. If the app depends on fragile permissions, shaky claims, or a naming issue, that is not just a launch problem. It is a value problem.

Use a simple valuation approach that fits a small app

For a small app, a simple profit-based or revenue-based approach is usually more useful than building a spreadsheet cathedral around vanity metrics.

If the app earns profit, start there. Ask what a reasonable buyer would pay for a business that produces that amount, then adjust for risk, founder dependence, and whether growth is stable or lumpy. If the app does not profit yet but has clear revenue, use revenue carefully and discount harder for costs and uncertainty.

The key idea is simple: value should come from what the app produces, not from download counts or a polished dashboard. Downloads can be nice. They are not rent.

For a small app, a rough range is often better than a precise number. A buyer is dealing with uncertainty, not balancing a moon mission budget. A range keeps you honest and avoids pretending the math is more exact than it is.

Worked example: estimate the value of a small iOS app

Picture a typical indie iOS app. It has a small paying user base, steady monthly revenue, and a handful of recurring costs. The founder handles support, updates, and the occasional fire drill.

Now walk through the inputs:

  1. Revenue and profit: If the app brings in money but most of it disappears into hosting, tools, refunds, and support time, the buyer cares more about what remains than the top-line number.
  2. Retention: If users stick around, the revenue feels sturdier. If they churn fast, the income is more fragile than it first appears.
  3. Growth trend: A flat app can still be valuable, but a steadily growing one usually supports a stronger estimate. A declining app gets a haircut.
  4. Founder dependency: If the app only survives because the founder knows every corner of the codebase and every odd customer issue, transfer risk goes up. That lowers value.
  5. Policy and IP risk: If the app’s name, content, permissions, or distribution setup might trigger review or legal trouble, a buyer will usually price that uncertainty in.

At the end of that pass, the estimate may move a lot. A stable app with decent profit, low maintenance, and little founder dependence can justify a much better number than a similar app that looks fine on the surface but is held together with hope and one developer’s memory.

So the process is simple enough to repeat on your own app:

  • Write down the actual monthly profit.
  • Note whether revenue is stable, growing, or shrinking.
  • Score how much work only the founder can do.
  • Flag any policy, IP, or naming issues.
  • Turn that into a range, not a magic number.

If naming or trademark risk could affect transferability, How do I legally choose an app name? is useful because a clean name can make the app easier for a buyer to take over.

Check whether the number changes for App Store review prep

Yes, it changes. A lot.

A rejected or incomplete app is harder to value because the buyer cannot rely on it being shippable, let alone transferable. If the app has unresolved review issues, missing metadata, broken flows, or policy-sensitive behavior, the estimate should come down. Not because the app is worthless, but because the buyer is buying uncertainty, and uncertainty comes with a discount.

That is why review readiness matters to worth. An app that is approved, complete, and policy-safe is much easier to present as an asset. An app that is still in limbo is closer to a project than a product.

Apple’s own review and guideline framework is part of that picture. If the app is likely to run into those rules, the risk is not abstract. It affects saleability, timeline, and confidence.

Final check before you trust the estimate

Before you believe your number, do three sanity checks.

First, compare it with comparable real-world offers if you can find them. Not internet fantasy pricing, actual offers or acquisitions, if available.

Second, discount for risk. If the app depends heavily on one person, a fragile third-party service, or anything policy-sensitive, the cleaner number is probably too optimistic.

Third, do not treat any single formula as definitive. Small app valuation is a judgment call wrapped around some math. The math helps, but the judgment is doing a lot of the heavy lifting.

If the estimate feels high, ask what would make a buyer hesitate. If it feels low, ask what is actually transferable. Somewhere between those two questions is usually the number that makes sense.