Define what 100,000 users actually means
Before discussing value, label the number and its measurement window. A hundred thousand lifetime downloads could include abandoned installs, replacement devices, or people who never opened the app. A hundred thousand monthly active users describes a current audience. A hundred thousand paying subscribers describes a different revenue base again.
Record the action that makes someone “active.” Opening a notification is not necessarily the same as completing a lesson, making a booking, or purchasing a subscription. Use a consistent definition over time and reconcile analytics with billing and store records.
| Metric | What it establishes | What it leaves unanswered |
|---|---|---|
| Lifetime installs | Distribution so far | Whether people still use the app |
| Registered accounts | People who signed up | Activation, duplication, and current engagement |
| Monthly active users | Usage within a defined month | Retention and willingness to pay |
| Paying customers | Monetization | Profit, refunds, churn, and acquisition cost |
Flippa’s discussion of app acquisitions highlights financial performance, active usage, growth, and category as factors buyers consider. The practical lesson is to document the business behind the audience rather than attach an arbitrary dollar amount to each download.
Build the revenue and profit picture first
For a subscription app, start with paying subscribers multiplied by average monthly revenue per subscriber. Account for discounts, refunds, failed payments, and annual plans rather than treating the sticker price as cash collected every month. For an ad-supported app, use actual ad statements; geography, format, and engagement affect revenue. For a marketplace, distinguish transaction volume from the fees your business keeps.
Then subtract the ongoing costs required to operate the business: store and payment fees, infrastructure, support, maintenance, content, and customer acquisition. Include a realistic cost for work the founder does without a salary. Removing that work from the spreadsheet does not remove the need for someone to do it after a sale.
Use a trailing twelve-month view where available and show month-by-month trends. One unusually successful launch month is weaker evidence than recurring cash flow. If the app is young, make the limited history explicit.
Compare three hypothetical 100,000-user apps
The following examples all assume 100,000 monthly active users, purely to make the scenarios comparable. The conversion rates, revenue, costs, and valuation multiple are invented teaching inputs. They are not observed sales, forecasts, or benchmark conversion rates.
| Scenario | Monthly economics | Illustrative value |
|---|---|---|
| No monetization yet | $0 revenue; ongoing operating costs | User count alone cannot establish a price |
| Subscription app A | 1,000 payers × $10 = $10,000 revenue; $5,000 costs; $5,000 profit | $5,000 × 12 × assumed 3 = $180,000 |
| Subscription app B | 3,000 payers × $10 = $30,000 revenue; $12,000 costs; $18,000 profit | $18,000 × 12 × assumed 3 = $648,000 |
App A assumes 1% of monthly active users pay; app B assumes 3%. Both use the same annual profit multiple so you can see the effect of different economics. A buyer might choose a different multiple or decline either business entirely after reviewing its risks.
For app A, an assumed 2× annual profit multiple gives $120,000, while 4× gives $240,000. That is a sensitivity exercise around the same $60,000 annual profit, not a promised valuation range. Always state whether a multiple applies to monthly or annual profit and whether the underlying figure is revenue, earnings, or cash flow.
A loss-making app is not automatically worthless. Its technology, audience, contracts, or strategic fit may interest a buyer. Establishing that value requires evidence and a buyer-specific assessment; multiplying losses by a profit multiple does not answer the question.
Explain what makes the earnings durable
A buyer needs to know how much of today’s performance can survive a transfer. Prepare evidence for these questions:
- Retention: Do acquisition cohorts keep returning, or does paid advertising replace departing users every month?
- Acquisition: Which channels bring useful customers, and what happens when the ad budget stops?
- Revenue concentration: Is income spread across customers and products, or dependent on one partnership or campaign?
- Operating effort: How much weekly work does the founder do, and can someone else perform it from documentation?
- Technical condition: Are builds reproducible, dependencies maintained, and critical flows tested?
- Transferability: Can the buyer receive the relevant code, store presence, licenses, and contracts under applicable terms?
Retention and monetization matter together. Raising prices can improve short-term revenue while increasing churn. Track the longer-term effect before treating a higher month’s profit as permanent.
Distinguish a sale price from a fundraising valuation
A buyer acquiring an app may focus on transferable earnings and operational risk. An investor funding a growing company may weigh future growth, market opportunity, and financing terms differently. A funding valuation is not cash a founder could necessarily receive by selling the app today. Development cost is also not a floor under the sale price: money spent building features does not guarantee demand.
Acquire.com’s guide to valuation multiples discusses profit and revenue approaches in the context of SaaS acquisitions. Use relevant completed transactions and a consistent earnings definition when choosing comparable businesses. SaaS multiples should not be copied onto a consumer mobile app without examining the differences.
For a real sale or investment decision, have a qualified valuation adviser or broker assess your records and comparable transactions. This guide teaches a calculation framework; it is not an appraisal of your app.
Make the next release improve the evidence
Prepare a diligence folder with monthly financials, analytics definitions, retention cohorts, acquisition costs, store reports, ownership records, and a technical handover. Share access securely with appropriate reviewers rather than exporting personal user data into an unrestricted sales document.
If you are still building, instrument the main user journey and billing events early. Choose the next release around an observed problem: a broken onboarding step, an unreliable purchase flow, or a reason existing users stop returning. That gives you more useful evidence than buying downloads to reach a round number.
Our development cost guide helps budget that work, and our MVP development service can help scope a focused release. We build the product; a transaction valuation should come from its business evidence and the people evaluating the deal.