AppStock
How AppStock values mobile apps and SaaS businesses
A transparent framework for estimating the fair-market value of mobile apps and SaaS businesses, calibrated to current marketplace transactions, private M&A benchmarks, and public SaaS market data.
// Contents
- Purpose & scope
- The valuation approach
- Core financial metrics
- Category baselines
- Size tiers & multiples
- Revenue quality adjustments
- Retention & churn
- Growth rate adjustments
- Platform & monetization adjustments
- Risk discounts
- Computing the valuation
- Worked examples
- Honest limitations
- Sources & data
- Changelog & feedback
// 01Purpose & scope
This document is the foundation of AppStock’s valuation tool. It explains exactly how we estimate the fair sale price of mobile apps and SaaS businesses, what data we use, how we adjust for quality factors, and where our framework is most and least confident.
We publish this methodology because we believe valuation references should be transparent and contestable, not black boxes. If you disagree with how we weight retention, or you have better category data than we do, we want to know. The methodology will improve through use, debate, and incoming data.
Version 1.1 reflects the latest completed-quarter market data available at review. Software Equity Group reported a 3.2x median public SaaS EV/TTM revenue multiple in 2Q26 and a 4.0x median multiple across disclosed SaaS M&A, while Acquire.com reported a 3.9x median profit multiple for closed SaaS deals in both 2024 and 2025. The market remains active, but buyers are more selective about retention, profitability, workflow embedment, proprietary data, and AI defensibility.
What this methodology covers
- Mobile apps — iOS, Android, and cross-platform apps generating revenue through subscriptions, in-app purchases, advertising, or one-time sales
- SaaS businesses — web-based subscription software with recurring revenue, including B2B and B2C tools
- Hybrid mobile + web products — apps with both a mobile interface and a complementary web platform
- Deal sizes from $5K to $50M — primarily focused on the $25K–$5M range where most public comp data exists
What this methodology does not cover
- Pre-revenue apps (no consistent valuation method exists; multiples need revenue to apply)
- Mobile games (different economics; game-specific multiples and retention curves apply)
- Marketplaces and platforms with two-sided network effects (require different valuation lens)
- Hardware-dependent or service-heavy businesses
- Strategic acquisitions where synergy value dominates pricing
AppStock valuations are fair-market estimates for arms-length sales between informed parties. Strategic acquirers may pay more for synergy reasons, and motivated sellers may accept less for liquidity reasons. Our outputs are starting points for negotiation, not definitive prices.
// 02The valuation approach
We use a multiple-based valuation method, the standard approach used by every major broker and acquirer in the app and SaaS space. The basic formula:
The valuation metric depends on business size, operating structure, profitability, and growth:
- Owner-operated profitable SaaS and apps: Use SDE (Seller’s Discretionary Earnings — profit + owner compensation + legitimate discretionary or non-recurring add-backs). Flippa’s 2026 guidance places many smaller SaaS transactions around 2.5x–4.5x SDE.
- Team-operated, established software businesses: Use EBITDA when owner compensation is no longer the right proxy for normalized operating earnings. Flippa cites roughly 3.5x–6.0x EBITDA for mid-market SaaS, depending on growth, margins, and retention.
- High-growth SaaS reinvesting for scale: ARR may be the better anchor when current profit understates economic value. Marketplace guidance commonly places ordinary revenue-based SaaS around 2.0x–3.5x ARR, with higher outcomes requiring stronger-than-normal evidence.
- Mobile apps: Use SDE for profitable owner-operated apps and annualized recurring revenue for subscription apps when retention and recurring-revenue quality are the primary value drivers.
The adjusted multiple starts with the appropriate baseline and then applies a single net quality adjustment for revenue quality, retention, growth, platform concentration, owner dependence, acquisition durability, age, technical risk, and other factors in sections 6–10. Version 1.1 no longer compounds every percentage sequentially because that can exaggerate otherwise modest strengths.
Multiples-based valuation is what every disciplined buyer uses because it’s the only way to compare deals across different sizes and categories. As one acquirer put it: “If you’re not disciplined on multiples, you’ll overpay, which makes succeeding that much harder.” AppStock follows the industry consensus rather than inventing alternative frameworks.
// 03Core financial metrics
Every valuation requires accurate input metrics. We use these definitions consistently throughout the methodology:
| Metric | Definition | Used For |
|---|---|---|
| MRR | Monthly Recurring Revenue. Subscribers × ARPU, recurring portion only. | Subscription apps, SaaS |
| ARR | MRR × 12. Annual recurring revenue. | SaaS valuation, growth metrics |
| SDE | Net profit + owner salary + discretionary expenses + non-recurring costs. | Sub-$5M businesses |
| EBITDA | Earnings before interest, taxes, depreciation, amortization. | $5M+ businesses, mature SaaS |
| NRR | Net Revenue Retention. (Starting MRR + expansion − churn − contraction) / starting MRR. | SaaS retention quality |
| D30 retention | % of users still active 30 days after install. | Mobile app stickiness |
| Churn rate | % of paying users canceling per month or year. | All subscription businesses |
| LTV/CAC | Lifetime value divided by customer acquisition cost. | Acquisition channel quality |
| Gross margin | Revenue minus direct cost of revenue, as % of revenue. | SaaS valuation premium |
// 04Category baselines
Different business models trade at different multiples because recurring revenue, retention, profitability, transferability, and buyer demand differ. Version 1.1 treats these as working calibration bands, not universal market percentiles. The SaaS bands are anchored to Acquire.com’s 2025 closed-deal data, Flippa’s 2026 valuation guidance, SEG’s 2Q26 public/private market data, and AppStock’s comparable-sale review.
SaaS baseline multiples
| Profile | SDE / Profit Multiple | Revenue Multiple (ARR) | Typical Characteristics |
|---|---|---|---|
| Lower-quality / higher-risk | 2.5x | 1.8x | High churn, owner-dependent, concentrated acquisition, weak growth |
| Market-center | 3.9x | 2.6x | Profitable, understandable economics, acceptable retention and transferability |
| Premium | 5.0x | 4.0x | Durable growth, strong retention, defensible workflow/data, low owner dependence |
Acquire.com reported a 3.9x median profit multiple for closed SaaS deals in 2025. SEG reported a 4.0x median EV/TTM revenue multiple for disclosed SaaS M&A in 2Q26, while its public SaaS Index median compressed to 3.2x. These are reference points, not interchangeable valuation rules: profit multiples and revenue multiples measure different business profiles.
Mobile app baseline multiples (subscription apps)
| Profile | SDE Multiple | Annualized Recurring Revenue Multiple | Typical Characteristics |
|---|---|---|---|
| Lower-quality / higher-risk | 1.8x | 1.5x | Weak retention, single-platform exposure, paid-acquisition dependence |
| Market-center | 3.0x | 2.5x | Stable subscription revenue, acceptable retention, transferable operations |
| Premium | 5.0x | 4.0x | Strong retention, organic acquisition, cross-platform reach, durable product moat |
Mobile app baseline (non-subscription: ad-supported, IAP, paid downloads)
Apps without recurring revenue generally receive lower baseline multiples because future revenue is harder to forecast and buyer underwriting depends more heavily on user durability, traffic sources, platform exposure, and monetization stability.
| Profile | SDE Multiple | Typical Characteristics |
|---|---|---|
| Lower-quality / declining | 1.2x | Ad-heavy, declining users, concentrated traffic or platform risk |
| Market-center | 2.2x | Stable users, mixed monetization, transferable operations |
| Premium | 3.5x | Growing usage, durable organic acquisition, strong IAP or diversified monetization |
AppStock’s baselines are calibration starting points. The actual sale price can diverge materially because of diligence findings, deal structure, buyer competition, strategic fit, intellectual property, concentration risk, and the quality of the specific comparable sales available for the business.
// 05Size, operating structure & valuation metric
Size matters, but version 1.1 does not apply a mechanical “size premium” from deal price alone. The more important question is which earnings or revenue metric a rational buyer would underwrite for the business at its current stage.
| Business Profile | Primary Metric | Current Working Range | How AppStock Uses It |
|---|---|---|---|
| Owner-operated profitable software / app | SDE | 2.5x–4.5x | Primary small-business cash-flow lane; current Flippa SaaS guidance |
| Established team-operated SaaS | EBITDA | 3.5x–6.0x | Used when normalized team economics matter more than owner add-backs |
| High-growth SaaS reinvesting for scale | ARR | 2.0x–3.5x | Starting market lane; premium outcomes need superior growth/retention evidence |
| Larger or strategically important software | ARR / EBITDA + comps | Case-specific | Cross-check against current private M&A and public-company multiples |
For Q3 2026, the latest completed-quarter cross-check is especially important: SEG’s public SaaS median was 3.2x EV/TTM revenue in 2Q26, down sharply from 5.7x a year earlier, while disclosed private SaaS M&A held near a 4.0x median revenue multiple. That divergence is why AppStock does not simply copy a public-market multiple onto a private founder-owned business.
// 06Revenue quality adjustments
Not all revenue is equally predictable. Version 1.1 narrows these adjustments so revenue quality can influence the baseline without overwhelming verified profitability, retention, and comparable-sale evidence.
| Revenue Type | Multiple Adjustment | Rationale |
|---|---|---|
| Annual subscription (B2B) | +15% | High predictability and lower renewal frequency |
| Monthly subscription (B2B) | +10% | Recurring with more frequent churn exposure |
| Annual subscription (consumer) | +5% | Recurring and prepaid, but consumer churn remains meaningful |
| Monthly subscription (consumer) | baseline | Reference point for recurring consumer revenue |
| In-app purchases (recurring use) | −10% | Repeatable but less contractually predictable than subscription revenue |
| One-time IAP / paid download | −20% | Requires continued new-user acquisition |
| Ad revenue (primary) | −25% | More exposed to traffic, platform, privacy, and ad-market volatility |
| Mixed (subscription + ads) | −10% to baseline | Depends on how much gross profit comes from recurring subscription revenue |
// 07Retention & churn
Retention remains one of the strongest indicators of revenue quality and future growth. SaaS Capital’s valuation framework explicitly uses ARR growth and NRR as company-specific valuation inputs, while current M&A research continues to emphasize durable retention and embedded workflows as buyer priorities.
SaaS / subscription retention adjustments
| Net Revenue Retention | Multiple Adjustment |
|---|---|
| Below 80% | −30% |
| 80% – 95% | −15% |
| 95% – 105% | baseline |
| 105% – 120% | +15% |
| Above 120% | +30% |
Mobile app retention adjustments
| Day-30 Retention | Multiple Adjustment |
|---|---|
| Below 5% | −25% |
| 5% – 15% | −10% |
| 15% – 25% | baseline |
| 25% – 40% | +15% |
| Above 40% | +25% |
NRR is appropriate for recurring SaaS revenue where expansion, contraction, and churn can be measured consistently. Day-30 retention is more useful for consumer apps, but it should be interpreted alongside paid conversion, renewal behavior, cohort maturity, and the app’s actual monetization model.
// 08Growth rate adjustments
Growth matters, but 2026 buyers are placing a higher bar on the quality and durability of growth. Version 1.1 reduces the growth premium and requires high-growth claims to be supported by enough history to distinguish sustainable expansion from a short-term spike.
| YoY Revenue Growth | Multiple Adjustment | Notes |
|---|---|---|
| Declining (−10% or worse) | −30% | Material deterioration; buyer must underwrite further downside |
| Declining (0% to −10%) | −15% | Moderate decline |
| Flat (0% – 10%) | baseline | Acceptable for a mature, profitable business |
| Moderate (10% – 30%) | +10% | Healthy growth when retention and margins are stable |
| Strong (30% – 60%) | +20% | Premium only when supported by durable cohorts and economics |
| Hyper (60%+) | +30% | Requires verification and a sustainability review |
We require at least 12 months of credible revenue history before applying the full high-growth premium. Shorter histories can still be valued, but AppStock reduces confidence and may apply an age or execution-risk discount.
Rule of 40
For SaaS, the Rule of 40 remains a useful cross-check: (YoY revenue growth %) + (EBITDA margin %). It is not a standalone valuation formula. In v1.1, passing the Rule of 40 supports a premium only when retention, gross margin, customer concentration, and product defensibility are also consistent with a high-quality business.
// 09Platform & monetization adjustments
Platform diversification can reduce concentration risk, but version 1.1 deliberately gives it less weight than retention, profit quality, and acquisition durability. A second platform is valuable only when it contributes real users, revenue, or transferability.
| Platform Coverage | Multiple Adjustment |
|---|---|
| iOS only | baseline |
| Android only | −5% |
| iOS + Android | +5% |
| iOS + Android + meaningful web revenue | +10% |
| Web only (SaaS) | baseline |
Platform exposure is also evaluated qualitatively. App-store policy dependence, account-transfer restrictions, fragile third-party APIs, or a platform that controls most acquisition can justify a separate risk discount even when the app is technically available on multiple platforms.
Monetization quality
| Pricing Power Signal | Multiple Adjustment |
|---|---|
| Raised prices in past 24 months without material churn impact | +5% |
| Multiple pricing tiers / verified expansion revenue | +10% |
| Single price point, no expansion | baseline |
| Heavy discounting / promo dependency | −10% |
// 10Risk discounts & defensibility premiums
Buyers are more selective in 2026. In addition to traditional concentration and transferability risks, v1.1 explicitly evaluates whether a software product is vulnerable to being replicated or displaced by general-purpose AI.
| Risk Factor | Multiple Discount | Threshold / Evidence |
|---|---|---|
| Owner-dependent operations | −10% to −25% | >20 hrs/week of essential owner time |
| Single-channel acquisition | −15% | >70% of new customers/users from one source |
| Customer concentration | −15% to −35% | >20% of revenue from one customer |
| Heavy paid-acquisition dependency | −15% to −25% | >50% of acquisition from paid channels with limited organic demand |
| Platform / policy concentration | −10% to −20% | A single policy, account, API, or platform can materially impair revenue |
| Trademark / IP issues | −20% to −30% | Unresolved ownership or infringement risk |
| Recent significant churn event | −15% to −25% | Material customer/user loss in past 6 months |
| Technical debt / unmaintained codebase | −10% to −20% | Outdated frameworks, security issues, difficult transfer or maintenance |
| Business age < 12 months | −15% to −25% | Insufficient operating history |
| AI substitution risk | −15% to −30% | Core value can be replicated cheaply by general-purpose AI with little proprietary data, workflow lock-in, or distribution moat |
Quality and defensibility premiums
| Quality Factor | Multiple Premium |
|---|---|
| Operates with <5 owner hours/week | +10% |
| Diversified acquisition (3+ meaningful channels) | +10% |
| Strong organic acquisition (SEO, ASO, referrals, community, viral) | +10% |
| Documented SOPs, clean financials, easy transfer | +5% |
| 3+ years of operating history | +5% |
| Strong app-store reputation with meaningful review volume | +5% |
| Mission-critical workflow embedment / proprietary data | +10% to +15% |
| AI capability with verified monetization or defensible data advantage | +5% to +15% |
SEG’s 2026 research shows buyers increasingly care about credible AI strategy, proprietary data, and embedded workflows. AppStock does not award a premium merely because a product uses an AI API or markets itself as “AI-powered.” The premium requires evidence of durable customer value, monetization, switching cost, proprietary data, distribution, or workflow advantage.
// 11Computing the valuation
Version 1.1 uses an additive adjustment model with guardrails. This removes the order effect created by multiplying every premium and discount sequentially.
Step 2: Select the category baseline multiple
Step 3: Score revenue quality, retention, growth, platform, risk, and defensibility
Step 4: Sum the applicable percentage adjustments into one net adjustment
Step 5: Apply default guardrail: −50% ≤ net adjustment ≤ +50%
Step 6: Adjusted multiple = baseline multiple × (1 + net adjustment)
Step 7: Estimated value = annualized SDE / EBITDA / ARR × adjusted multiple
Step 8: Cross-check against current comparable sales and market benchmarks
Step 9: Output a valuation range, normally ±25% around fair value
A model output that sits materially above current private M&A and public-market benchmarks is not automatically wrong, but it requires stronger evidence. AppStock flags unusually high revenue multiples for manual review of retention, growth durability, strategic fit, proprietary data, customer concentration, and comparable transactions before treating them as fair value.
The output is always a range
We output valuation ranges rather than a false-precision point estimate. Buyer competition, diligence findings, financing, deal structure, transition requirements, and presentation quality can all move the final price.
Standard output format: Low estimate · Fair value · High estimate. The default range is ±25% around the modeled fair value unless the quality of comparable-sale evidence supports a narrower or wider interval.
// 12Worked examples
Example 1: Subscription mobile app
An iOS + Android subscription productivity app, 18 months old, $4,500 MRR, $54K ARR, 22% Day-30 retention, 30% YoY growth, owner spends 8 hours/week, with meaningful organic acquisition through ASO and content.
| Step | Adjustment | Result |
|---|---|---|
| Baseline (market-center subscription app) | 2.5x ARR | 2.50x |
| Revenue quality (monthly consumer subscription) | 0% | baseline |
| Retention (D30 of 22%) | 0% | baseline |
| Growth (30% YoY) | +10% | healthy growth |
| Platform (iOS + Android) | +5% | reduced platform concentration |
| Organic acquisition | +10% | durable acquisition signal |
| Age / owner involvement | 0% | no additional premium or discount |
| Net adjustment | +25% | 3.13x ARR |
Fair value: $54,000 ARR × 3.125 = $168,750
Range: approximately $127K (low) – $169K (fair) – $211K (high)
Example 2: B2B SaaS
Web-based B2B SaaS, 4 years old, $24K MRR, $288K ARR, 110% NRR, 25% YoY growth, 75% gross margin, 15 hrs/week owner involvement, with diversified acquisition across SEO, content, and outbound.
| Step | Adjustment | Result |
|---|---|---|
| Baseline (market-center SaaS) | 2.6x ARR | 2.60x |
| Revenue quality (monthly B2B subscription) | +10% | recurring B2B revenue |
| Retention (NRR 110%) | +15% | positive expansion / retention profile |
| Growth (25% YoY) | +10% | healthy growth |
| Diversified acquisition | +10% | lower channel concentration |
| 3+ years operating history | +5% | longer track record |
| Net adjustment | +50% | 3.90x ARR |
Fair value: $288,000 ARR × 3.90 = $1,123,200
Range: approximately $842K (low) – $1.12M (fair) – $1.40M (high)
This second example intentionally lands near the latest disclosed private SaaS M&A market median rather than mechanically compounding several good metrics into a much higher multiple. A stronger result is still possible, but v1.1 requires verified premium evidence to support it.
// 13Honest limitations
This methodology has real limitations that should be visible to anyone using the output.
Public deal data is incomplete
Most app and SaaS sales do not disclose every financial and operational detail. Public marketplaces provide useful transaction evidence, while advisor reports often publish aggregate M&A data, but private deals can remain confidential. AppStock therefore treats comparable-sale quality as a confidence input rather than pretending every category has a complete market dataset.
Marketplace populations differ
Acquire.com, Flippa, broker-managed transactions, lower-middle-market M&A, and public SaaS companies do not represent identical businesses. A 3.9x profit multiple on a profitable founder-owned SaaS business is not directly comparable to a 3.2x public-company revenue multiple. Version 1.1 uses each source as a lane-specific cross-check instead of blending them into one universal number.
Multiples are time-sensitive
The current calibration reflects the latest completed-quarter data available at the August 10, 2026 review. SEG reported that its public SaaS median EV/TTM revenue multiple fell to 3.2x in 2Q26 from 5.7x in 2Q25, while disclosed private SaaS M&A held near 4.0x. That public/private divergence is unusually important in the current AI-driven repricing cycle. Valuations should be re-checked against current market data when this methodology is more than one quarter old.
Strategic vs. financial buyers
AppStock estimates fair-market value for a rational financial buyer using the economics and evidence available. A strategic buyer may pay materially more when the target provides unique product fit, proprietary data, distribution, customer access, workflow embedment, or competitive advantage. Conversely, a weak diligence process or urgent seller can produce a lower outcome.
AI-native and AI-exposed categories are still developing
AI-native software has a short exit history compared with mature SaaS categories. At the same time, general-purpose AI is changing the perceived defensibility of some traditional point solutions. Version 1.1 adds an explicit AI substitution/defensibility review, but confidence remains lower where there are few relevant completed transactions.
If you have better information than the model — a credible acquisition offer, a recent directly comparable transaction, verified strategic buyer interest, or diligence information that materially changes risk — that evidence should outweigh a generic model adjustment.
// 14Sources & data
Version 1.1 prioritizes current primary market sources and uses each source for the type of business it actually represents.
Current marketplace & M&A calibration
- Software Equity Group — 2Q26 Quarterly SaaS Report — public SaaS valuation reset, disclosed SaaS M&A multiples, transaction volume, buyer selectivity, vertical activity, and AI/workflow defensibility.
- Acquire.com — 2026 Acquisition Multiples Report — verified 2025 closed SaaS transactions; 3.9x median profit multiple and low-to-mid 4x average profit multiple range.
- Flippa — How to Value a SaaS Company in 2026 — small SaaS SDE, EBITDA, and ARR valuation lanes and buyer-quality factors.
- Flippa — 2025 Market Insights & 2026 Outlook — marketplace transaction activity, professional-buyer participation, profitability, and defensibility trends.
Public SaaS & valuation framework
- SaaS Capital Index — current public B2B SaaS market reference, updated monthly; data page reviewed with July 31, 2026 index data.
- SaaS Capital — What’s Your SaaS Company Worth? — data-driven private SaaS framework emphasizing public-market appetite, ARR growth, and NRR.
- Software Equity Group — 2026 Annual SaaS Report — 2025 public SaaS fundamentals and approximately 2,700 SaaS M&A transactions.
- Aventis Advisors — SaaS Valuation Multiples 2015–2026 — longer-term public software valuation context.
AppStock comparable sales
- AppStock Comparable Sales — transaction-level reference set used to test model outputs against more directly comparable app and SaaS sales.
- Submit a Comparable Sale — first-party transaction submissions are reviewed before they are used in public market data or calibration.
No single external source “powers” the calculator. AppStock uses current market research to establish valuation lanes and then cross-checks the modeled result against the closest available comparable transactions.
// 15Changelog & feedback
Version history
| Version | Date | Changes |
|---|---|---|
| 1.1 | August 10, 2026 | Q3 review: recalibrated SaaS baselines to current 2026 marketplace/M&A data; replaced sequential compounding with additive net adjustments and ±50% guardrails; reduced retention/growth/platform premiums; added AI substitution and defensibility factors; rebuilt worked examples; refreshed sources and market sanity checks. |
| 1.0 | April 28, 2026 | Initial publication |
How to give feedback
This methodology should improve as better transactions and objections arrive. If you disagree with a weight, have stronger category data, or identify an error, AppStock wants the evidence behind the disagreement.
- Methodology corrections: Email methodology@appstock.com with the section number, proposed correction, and supporting data.
- Comparable sales submissions: Use /comps/submit/ for completed app or SaaS transactions that can improve the comparable-sales database.
- Broker / marketplace data partnerships: Email partnerships@appstock.com.
Update cadence
This methodology is reviewed quarterly. The next scheduled review is Q4 2026. AppStock may update sooner if market multiples, buyer behavior, platform economics, or AI-related software risk change enough to make the current calibration materially stale.
Retention changes both recurring revenue and buyer confidence. Use the Churn Impact Calculator to model how churn improvements can affect revenue durability before applying the valuation framework.