How much is my app worth? A self-estimate framework for software owners

Why an app is harder to value than a website

If you build software — a mobile app, a desktop utility, a browser extension, a documentation or productivity tool — the value question lands the same way it does for site owners: how much is this thing actually worth? The honest answer is that you can produce a credible self-estimate in an afternoon, but only if you resist the urge to skip straight to a number. An app's value is a function of its earnings and its risk, and apps carry risks a plain content site never has to think about.

A website lives on infrastructure you control. An app usually lives on someone else's platform. The App Store, Google Play, a browser extension store, or a marketplace can change fee structures, review policies, or ranking rules at any time, and your earnings move with them. That platform dependence is the single biggest reason app multiples are quoted more cautiously than equivalent SaaS or content multiples.

Two things sit outside your control and shape your margin directly: the store's cut and the store's rules. Both stores publish them. Google lays out its tiered service fees in the Play Console Help, and the approval rules that can pull or block a release live in Apple's App Review Guidelines.

Read both as a buyer would. Every percentage point the platform takes is profit a buyer never sees, and every rule that could delist you is a line in someone's risk model. That is why an app earning the same profit as a self-hosted product still tends to price lower.

This piece is the app-specific spoke of our SaaS valuation work. For the full software methodology and multiple ranges, read the pillar: how to value a SaaS business. If you are working on a tiny solo product, micro-SaaS valuation goes deeper on the single-developer case.

Step 1 — Normalize earnings across every revenue line

Buyers pay for profit, not revenue, so the first job is to convert your messy income into one clean number. Most apps earn across more than one model at once: a subscription tier, a one-time unlock, in-app purchases, and ad revenue can all land in the same month. Pull twelve trailing months and separate each line, because each behaves differently and a buyer will discount them differently.

Once the lines are separated, subtract real operating costs — store commissions, hosting and API bills, support tooling, and any contractor time. What remains is your seller's discretionary earnings (SDE): owner profit before your own salary.

For a recurring-heavy app you may anchor on MRR instead; for a profit-heavy one-time app, SDE is the cleaner base. The distinction between profit definitions matters enough that we wrote it up separately in SDE vs EBITDA for website valuation.

Avoid the most common self-estimate error: annualizing one good month. A launch spike, a holiday in-app-purchase bump, or a single press hit will inflate your base and produce a range you cannot defend. Use the trailing twelve months, and if revenue is trending hard in either direction, note it as a separate adjustment rather than baking it into the base.

Walk through a quick illustration so the mechanics are concrete. Say your app pulls a trailing-twelve-month gross of $120,000 across all lines. Strip out the store commission, hosting, the analytics and support tools you actually pay for, and the contractor who handles your release builds — call it $42,000 of real cost.

You are left with roughly $78,000 of owner profit. That is your SDE base, not the $120,000 headline. These are illustrative, not a broker quote — plug in your own numbers and the method holds.

If most of that $78,000 comes from recurring subscriptions, you weight it as durable. If most of it is one-time unlocks or ad CPMs that reset to zero each month, you weight it lower and let that flow into your multiple in Step 2. Same profit, different quality — and quality is what the multiple actually prices.

Step 2 — Pick a defensible multiple band

With a clean earnings base, you multiply by a band, not a single figure. Small software assets trade in ranges that depend heavily on revenue quality. A subscription app with low churn earns a higher multiple than an ad-supported app with the same headline profit, because the buyer is really pricing the predictability of the cash flow, not last year's total.

Start from the multiple range in the SaaS pillar, then place your app inside it conservatively. The defensible move is to assume the middle-to-low end unless you have evidence that justifies the top. Each piece of evidence — long operating history, low churn, diversified revenue — earns you a step up. Each risk earns a step down.

Step 3 — Adjust for the app-specific factors

Now apply the adjustments that a generic website calculator never asks about. These are the factors that separate two apps with identical profit into very different value ranges, and being honest about them is what keeps your self-estimate credible rather than wishful.

• Platform and fee dependence. What share of revenue routes through one store, and what happens to your profit if that store raises its cut or changes review rules?
• Churn and retention. For subscription apps, monthly churn is the heartbeat. Low, stable churn is the strongest single argument for the top of your band.
• Ratings and install-base quality. A large but stale install base of one-time downloaders is worth less than a smaller base of engaged, recurring users.
• Single-developer risk. If you are the only person who can ship a fix or pass an app review, the asset is concentrated on you. A buyer discounts that, and you should too.
• Monetization durability. Ad-funded and novelty apps decay faster than tools people open every workday — think developer utilities, documentation, or productivity apps that sit in a daily workflow.

Productivity and documentation apps are a useful illustration of why durability matters. A tool embedded in someone's daily workflow tends to retain users and survive platform shifts better than an entertainment app riding a trend. That stickiness is exactly the signal a buyer pays a higher multiple for, so weight it deliberately when you place your band.

Step 4 — Widen to a range and attach confidence

A single number is the wrong output for any asset, and it is especially wrong for an app, where earnings are noisier than a content site's. Multiply your normalized earnings by the low end of your adjusted band, then by the high end, and present the result as a range. Then ask how much you trust your own inputs and convert that into a confidence level.

Confidence should be low when your data is thin: a short history, lumpy in-app revenue, a single dominant traffic source, or earnings that swing month to month. Confidence rises when you have twelve-plus clean months, low churn, diversified revenue, and a base that does not depend on a single launch spike. A wide range with honest low confidence is more useful than a tight range you cannot defend.

Two apps can show the same $78,000 of owner profit and land in very different ranges. The recurring, low-churn one might sit near the top of your band with a tight spread and higher confidence. The ad-heavy, single-developer one earns the low end and a wide spread, because more of its inputs are uncertain. The table above is the logic, not a price — illustrative, not a broker quote.

This is the same discipline our engine uses on the website side. If you want to see the full step-by-step logic applied to sites, the website valuation complete guide walks through earnings normalization, multiple selection, and ranging in detail, and most of it transfers cleanly to software.

Sanity-check against comps, then re-read the result

The final step is to pressure-test your range against real comparable sales. If your self-estimate lands far above what similar apps with similar profit actually changed hands for, the gap is usually in your multiple or in an over-counted revenue line — not in the market being wrong. Comps are the reality check that keeps the framework honest.

Browse comparable web and software asset sales to see where real ranges sit, then compare them to your own figure: explore web asset comps. If your range survives that comparison, you have a defensible self-estimate. If it does not, walk back to Step 2 and place your multiple more conservatively.

Public marketplaces are useful for calibration too. Acquisition platforms like Acquire.com list app and SaaS businesses with asking prices and revenue figures attached, so you can eyeball the multiples real sellers are quoting in your size range. Treat asking prices as ceilings, not settled values — deals close below the ask far more often than above it — and weight closed comps over open listings whenever you can find them.

Read the final number for what it is: an informed range to guide your own thinking, not a price a buyer has promised. Apps move on platform decisions and retention curves that no estimate can fully predict, so treat the range as a starting point for diligence rather than a finish line. It is a self-estimate, illustrative, not a broker quote — and never financial advice on whether or when to sell.