A cash-flowing mobile game is worth what its revenue survives verification, not its install count. Verify revenue at the console level, treat mediated ad revenue as a single dependent stream, and price platform and transition risk through structure rather than by cutting the headline number. Below is how that works, and how Kautilya bought a real game at ~1.1x with the downside engineered through structure.
Search for how to value a mobile game and you’ll mostly find calculators estimating what it costs to build one, or advice for developers picking a game idea. Almost nobody writes the buyer’s playbook: how to value a small, cash-flowing game you want to acquire, and how to protect yourself doing it.
That’s the gap this engagement fills. Kautilya sourced, valued and structured the acquisition of Dino Games, a cash-flow-positive dinosaur-simulation title with about 8M Android installs, carved out from a nine-title studio portfolio. It closed at $39K, roughly 1.1x revenue, in a deal where the buyer’s downside was engineered through structure rather than a low price, and where the real work was refusing to take the seller’s numbers at face value.
What actually drives a mobile game’s acquisition value
Value is verified, durable cash flow, not installs and not dashboard revenue. Installs are a vanity metric without retained monetisation behind them; what matters is whether the game reliably converts usage into cash, how dependent that cash is on a third-party platform, and how much survives once the seller is gone.
Kautilya underwrote Dino Games on cash-flow-positive operations, roughly $3,000 a month of net profit on $3,000 to $4,000 of ad spend, at a 1.1x revenue multiple, not on its 8M install count. It sustained 40–50% net margins despite modest retention (sub-10% 30-day, ~4% 7-day) and no major updates for over two years, because its value is realised early in each user’s life through short, ad-dense sessions, a front-loaded LTV model. Recognising that is what justified the price.
Step 1, Verify revenue at the console, not the dashboard
Seller summaries smooth over currency, timing and platform gaps. Insist on console-level access to every revenue and user-acquisition surface, and walk each number back to its source before treating any of it as bankable. Historical opacity isn’t a footnote, it changes what the revenue is worth.
The seller wanted to work from summaries. The team refused.
Kautilya demanded console-level access across Google Ads, AdMob and Play Console, which forced the seller to acknowledge historical reporting gaps and abandon the story of one clean revenue source. Cross-checking spend against revenue against in-app-purchase receipts surfaced concrete discrepancies, including a ~$182 Play Console mismatch the seller wrote off as a data-entry error. Once historical opacity was on the table, the revenue became probabilistic rather than bankable, and the risk premium rose accordingly.
Step 2, Treat mediated ad revenue as one dependent stream
Ad revenue appearing across several dashboards can look like diversification when it’s really a single mediated stack. If one network mediates the others, that’s one source of truth and one point of failure, and it deserves a risk premium, not a blended average that implies resilience the business doesn’t have.
The seller’s revenue appeared on both AppLovin and Google, until they confirmed AdMob was running inside AppLovin mediation. That made post-cutoff revenue a single mediated stream, not independent sources. The team disallowed blended averages, fixed AppLovin as the sole post-cutoff source of truth, and the seller’s diversification narrative, and the premium it implied, collapsed. Growth claims were reframed as optimization upside, not proven history.
Step 3, Price platform and transition risk through structure
Rather than compressing valuation to offset transition risk, engineer the risk out through payment timing and controls. Defer part of the consideration and tie it to stability rather than speculative performance; use escrow and an inspection period to keep leverage until the asset is verifiably transferred; and remove embedded liabilities before close so you never inherit them.
The deal closed at $39K, about 1.1x revenue and 1.2x normalized profit, with ~56% paid at close (~$22K) and 44% deferred over twelve months against transition stability. Kautilya held the line on escrow despite seller pressure for off-escrow splits over jurisdictional limitations, structuring it through a US LLC workaround with a signed APA, an inspection period and milestone releases. Technical diligence was sequenced as a hard gate, buyer-selected reviewer first, no asset release until scope was met, turning diligence timing into leverage. And a 70%-off lifetime IAP promotion was shut off before close, so the buyer never inherited that perpetual, loss-making obligation.
The effect was decisive: the headline price was preserved, no bruising renegotiation, while the buyer’s real exposure at close was materially reduced. Upfront capital of ~$22K against ~$3K a month of net profit implied a payback measured in months. That is what disciplined structuring buys a buyer, and it’s the discipline Kautilya brings to acquisitions where the revenue sits on someone else’s platform.
The same underwrite-conservative, structure-the-rest approach is what makes a young business financeable in the first place, see how it plays out on a $110K acquisition closed with $20K down.
Frequently asked
How do you value a mobile game acquisition?
On verified, durable cash flow, not installs or dashboard revenue. Confirm revenue at the console level, understand what it depends on (platform, ad mediation, geography), and recognise the monetisation model, an ad-led, front-loaded-LTV game can be sound even with weak retention. Cash-flowing games sourced off-market often trade near 1x revenue.
How do you verify a mobile game’s revenue before buying?
Work from console and platform payout data, Google Ads, AdMob, Play Console, not the seller’s dashboard. Reconcile ad spend, ad revenue and in-app-purchase receipts against each other, and if ad revenue is mediated through one network, treat it as a single dependent stream rather than diversified income.
What multiple do cash-flowing mobile games sell for?
It varies with revenue durability and platform risk, but cash-flowing games sourced off-market can change hands close to 1x revenue, as this one did at about 1.1x. Platform and operator dependency are the biggest discount factors, which is why they belong in the structure as well as the price.
How do you protect yourself buying a mobile app?
Price the risk through structure: defer part of the payment against transition stability, insist on escrow with an inspection period and milestone releases, sequence technical diligence as a hard gate before any asset release, and remove embedded liabilities like discounted lifetime purchases before close.