Annual and quarterly UA budget planning

Two ways exist to build a UA budget, top-down from a revenue target and bottom-up from channel capacity, and the studios that only do one tend to discover the other's constraint mid-quarter, at the worst possible time to discover it.

Top-down: fast, but blind to capacity

Top-down planning starts from a revenue or user-growth target the business has set, backs into an implied number of installs at current conversion and monetisation rates, then prices that install volume at the current blended cost per install to arrive at a required budget. The method is fast and easy to communicate upward, but it says nothing about whether the available channels can actually absorb that spend without cost per install inflating well past the assumption the plan was built on.

Bottom-up: grounded, but needs history

Bottom-up planning starts from each channel's realistic capacity at a stable cost per install, sums across channels, and compares the resulting install volume against the revenue target. This method exposes capacity constraints early, before a budget is committed rather than after, but it requires channel-level history a newer studio, or a studio entering a new region for the first time, may not yet have.

The gap is the real planning conversation

The difference between what the business wants from a top-down target and what channels can realistically deliver at a stable price bottom-up is where the actual planning conversation belongs. That gap should surface a decision, accepting a higher blended cost per install, extending the timeline to hit the target, or adding a new channel to close the volume shortfall, rather than getting smoothed over into a single optimistic number that satisfies both sides on paper without holding up in execution.

Seasonality and contingency

Known seasonal effects, a stronger holiday quarter, a softer mid-year stretch, should shift both the top-down assumption and the bottom-up capacity model, since channel pricing moves with the same seasonal demand that affects revenue. A contingency reserve, held back from the annual budget as an unallocated amount rather than a fixed percentage since the right size varies by studio, exists for a mid-year opportunity, a channel pulling back and pricing softening unexpectedly, a new channel worth testing, or a mid-year shock, a network policy change, a measurement framework shift that affects reported efficiency. The reserve needs criteria for release attached to it. Otherwise it tends to sit unused by default until the year ends.

Stress-testing the plan against a platform shock

A budget built only around a base-case blended cost per install misses a category of risk that has become routine in mobile UA, a platform policy change, a measurement framework shift, or a major network's pricing move that alters blended cost per install mid-quarter without warning. Building a simple stress case alongside the base case, what happens to the plan if blended cost per install rises by a defined margin for one full quarter, forces the reconciliation step to include a genuine downside scenario rather than only the optimistic top-down number and the bottom-up capacity check.

The stress case does not need to be elaborate to be useful. Naming which channels would absorb a reallocation first if another channel's pricing spiked, and confirming the contingency reserve's release criteria actually cover that scenario rather than only a growth opportunity, turns the contingency line from a vague buffer into a plan with a defined trigger. Studios that have already answered this question before a shock hits move spend within days rather than losing most of a month to an ad hoc scramble, and that speed advantage is often worth more than the reserve amount itself.

Review cadence and a repeatable structure

An annual budget set at the start of the year is rarely still accurate by the fourth month, given how quickly network pricing and channel supply move over that span. A quarterly reforecast against actuals catches the larger drifts, and monthly checkpoint reviews within each quarter catch a single channel drifting off plan while there is still time to correct course, rather than after the quarter has already closed.

A repeatable structure holds up better than rebuilding the exercise from a blank page each cycle: set the revenue target, calculate implied installs at current conversion, run the bottom-up channel capacity check, resolve the gap with an explicit decision, adjust for seasonality, size the contingency reserve, and set the trigger for the next quarterly reforecast. The discipline that separates a UA budget from an accounting exercise is that reconciliation step between top-down and bottom-up, done honestly rather than papered over into a single agreeable figure.

Related archive reading

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

• A UA Budget Planning Template Built for a Flat Market
• The UA reading list: reports and benchmarks that matter