Profitable UA can still destroy a studio

A studio can have cohorts that pay back inside six months, a growth team that hits every efficiency target, a board that approves every budget increase, and still find itself unable to make payroll. This is not a story about bad UA. It is a story about the difference between profit and cash, and about how paid acquisition converts one into the other on a timetable the studio does not control.

The thesis is uncomfortable for growth teams: at a certain rate of scaling, a profitable UA operation becomes the single largest consumer of working capital in the company, and the more efficiently it works, the more capital it demands. Payback dashboards never show it, because whoever designed them was answering a different question.

Two clocks running at different speeds

Every install purchased starts two clocks. The first is the ROAS clock, which measures how quickly the cohort's revenue accumulates against what was spent. The second is the cash clock, which measures when money actually leaves and enters the bank account. Growth teams live on the first clock while finance lives on the second, and the gap between the two is the whole mechanism.

Consider the outbound side. Most ad networks and self-serve platforms bill on short terms, some by prepaid balance, some by card on a rolling basis, some on net-30 invoicing for larger accounts. Broadly, a studio pays for the media it buys in a given month either inside that month or early in the following one.

Now the inbound side. In-app revenue does not arrive when the player pays. It arrives when the store pays the developer, which for both major app stores is on a monthly cycle with a lag after the period closes. Revenue earned at the start of one month may not be in the studio's account until well into the second month after. Ad revenue from mediation partners runs on its own net terms, often longer.

So a cohort that "pays back in day 90" on the ROAS clock has typically not returned the cash by day 90. The spend left in month one. Store payments for that first quarter of trading trickle back from month two onwards, the last of them arriving in month five, so cash payback tends to land a month or two behind ROAS payback; the gap then widens with every extra month of payback horizon the studio tolerates.

Why scaling makes it worse, not better

Hold spend flat and the gap is a one-off working capital requirement that the studio swallows once and then stops thinking about. Scaling turns it into a hazard.

Take an illustrative studio spending 500,000 a month with 120-day cash payback. At steady state it has roughly four months of spend, two million, tied up in cohorts that have not yet returned their cash. Now it decides to double spend over a quarter because the cohorts are performing. By the end of that quarter it is spending a million a month, and the capital tied up in unreturned cohorts is heading towards four million. The extra two million has to come from somewhere before the new cohorts return it. Nothing about the campaign has gone wrong. Every cohort is on track. The studio simply needs two million more than it did, and it needs it now.

This is why the studios that get into trouble are so often the ones with good numbers. Bad UA gets cut early because the dashboards say so. Good UA gets scaled, and scaling is what stretches the balance sheet. The incentive structure inside the growth team points the same way, since nobody in it wins anything for spending less than the model allows.

The second-order effect that most coverage misses: any deterioration on the revenue side reaches the cash clock late, and all at once. Say a platform change knocks fifteen percent off late-cohort revenue; a competitor's launch or a creative fatigue cycle would do the same damage, and the ROAS dashboard picks it up within weeks. The bank account shows it two months later, by which point the studio has already committed two more months of spend against the old forecast. Sensor Tower's State of Gaming 2026, published in February, described an industry with mobile IAP revenue roughly flat and installs down around seven percent; in that environment the odds that some cohort under-delivers late are not small.

A framework: cash payback and capital at risk

Two numbers should sit alongside ROAS payback in every budget review.

The first is cash payback, which is ROAS payback plus the weighted average delay between earning revenue and banking it. Working it out once, by revenue source, is a morning's job with the finance team. The answer for a mostly IAP game on the major stores will usually be longer than the ROAS figure by a month or more; for a game leaning on ad revenue through mediation, longer still.

The second is capital at risk, which is monthly spend multiplied by cash payback in months. This is the amount of cash the UA operation has permanently borrowed from the rest of the business at the current run rate. Any proposed increase in spend should carry the increase in capital at risk it implies, plus a plain statement of where that capital comes from.

A decision rule follows. Set a ceiling for capital at risk as a share of available cash and committed facilities, and treat spend increases that would breach the ceiling as financing decisions, not marketing decisions. Scaling from 500,000 to a million a month is not "the campaigns are working"; it is "we are advancing two million to the app stores and asking them to return it over the next five months". Framed that way, the question of whether to do it is obviously one for the whole leadership team.

Where the pressure to ignore this comes from

Investor and acquirer attention rewards growth, and the market for studios has been active this year, with Scopely's majority stake in Loom Games in February valuing a twenty-person team at over a billion dollars on the strength of one hit. Growth at that pace is worth a great deal to whoever owns the studio at the point of sale, which is precisely why the pressure to scale spend ahead of cash is strongest at the moment it is most dangerous.

The studios that handle it well tend to do one unglamorous thing: they negotiate the outbound clock. Longer payment terms with networks, credit lines secured against receivables from the stores, and revenue-based financing tied to cohort performance all narrow the gap between the two clocks. None of them improve ROAS by a single point. All of them are the difference between a good campaign and a solvent studio.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• The CFO conversation every UA lead has
• ROAS targets versus payback windows