Skip to Main Content
top of page
← Back to Blog

Gaming Due Diligence and the Durability of Revenue

Gaming due diligence tests whether revenue can hold up when payer activity, platform access, or other dependencies change.

A growing revenue chart can get investors interested. Due diligence asks whether the business can sustain that performance when a major payer leaves, a distribution channel changes, or the team has to adjust the product.

Gaming Due Diligence and the Durability of Revenue — illustration from the original post
Artwork from the original LinkedIn post.

Trace revenue to its sources

Start with payer retention across mature cohorts. Then measure revenue concentration by player, market, and platform. Run a sensitivity case for each material dependency. For example, estimate the effect of losing part of a concentrated payer segment while holding the broader base steady.

Consider two studios with identical revenue growth. At one, repeat purchases come from several cohorts across multiple markets. At the other, a small group of players accounts for most of the increase. Ask each studio to show how much revenue would remain if spending in its largest payer segment fell, and reconcile the cohort totals with the underlying transactions. The result shows how much of the forecast rests on one assumption.

Check whether the team can respond

Ask how quickly the team can diagnose a shift, run a test, and change an offer or release. Reconcile reporting to underlying transaction records and check that metrics use consistent definitions. Operational flexibility and reliable data determine how much confidence to place in a forecast.

Rebuild the growth story by cohort

Ask for a monthly bridge that separates first-time payer revenue, repeat payer revenue, and revenue from reactivated players. Compare cohorts at the same age. If newer cohorts contribute more because the studio acquired more users, that can coexist with weaker revenue per acquired player. The investment question is whether an extra dollar of acquisition can still buy a cohort that pays back on the same terms.

Then make each downside case traceable. If a hypothetical payer segment contributes 30% of monthly revenue and spends 20% less, that is a 6% decline in total revenue before any changes elsewhere. Ask what evidence supports an offset. A forecast that assumes replacement spending should show which cohorts or channels could deliver it and how long that would take.

Identify the findings that change the deal

Distinguish a weakness that can be fixed after closing from a dependency that changes the valuation today. A reporting mismatch may be resolved by reconciling a ledger. A product that depends on one platform for distribution needs evidence of a viable fallback. State what you checked, how much of the downside you can bound, and what would have to be true for the forecast to hold.

bottom of page