Most growth reporting explains what happened. A serious growth allocation review decides what should happen next. That difference changes the meeting, the dashboard, the prep work, and the quality of executive debate.
A reporting meeting can tolerate descriptive metrics. Spend went up. CAC moved. Conversion changed. Pipeline grew. A review that allocates capital needs stronger evidence. Which channel deserves more money? Which segment should be capped? Which experiment should graduate? Which motion should be killed?
The growth allocation review should start with the business model and the current constraint. Is the company optimizing for learning, revenue growth, profitability, market entry, retention, liquidity, or strategic position? The same numbers mean different things depending on the constraint.
The core table should include channel or segment, current spend, marginal CAC, gross margin, gross payback, net payback, incremental net payback, confidence level, saturation risk, scale ceiling, liquidity impact, and next-dollar recommendation.
Each recommendation should be explicit: increase, hold, cap, reduce, test, redesign, or kill. Vague commentary should be pushed out of the review. If the team cannot make a recommendation, the missing evidence should become the next experiment.
The review also needs a decision log. Growth decisions decay when nobody remembers why money moved. For each allocation choice, record the thesis, expected payback, confidence level, owner, evidence threshold, and revisit date. This turns growth from a series of budget arguments into an operating cadence.
The cadence should match the business. Paid channels may need weekly tuning. Enterprise sales capacity may need monthly or quarterly review. Strategic market entry may need milestone-based review. The point is not to review everything constantly. The point is to match decision frequency to evidence frequency.
Finance, growth, product, sales, and customer success should all have a seat when their economics are implicated. Growth allocation is cross-functional because acquisition quality, activation, margin, retention, implementation, and support all shape return.
The operator test: after the next growth review, ask what changed in allocation. If no budget, owner, threshold, or experiment changed, it was not an allocation review. It was a performance readout.
The final claim is simple. Growth teams should not exist to make charts go up. They exist to help the company allocate scarce cash into uncertain customer acquisition loops better than competitors do. The next dollar is the job.
The review should also separate operating updates from allocation decisions. A channel owner may need to explain what happened, but the executive team needs to decide what changes. Mixing those two jobs creates meetings where everyone understands the story and nobody moves the money.
A useful format is to require every channel owner to bring one of five recommendations: fund more, hold, cap, reduce, or test before deciding. The discipline is not that every recommendation must be right. The discipline is that every update has to connect to a capital decision.
The review should include a red-team moment. Ask what would make the recommendation wrong. The answer might be weaker incrementality, margin erosion, sales capacity, market saturation, fraud, support load, or a dependency on a product change that is not actually committed. This turns optimism into inspectable risk.
Finally, the review should create memory. Six weeks later, the company should know which decisions were made, what was expected, what happened, and what was learned. Without that memory, growth allocation becomes a series of confident meetings with no compounding judgment.
The strongest reviews are short enough to matter. If the packet is fifty pages, leaders will skim for the chart that confirms their prior view. A tighter packet should make the trade visible: what we know, what we do not know, what we recommend, what could make us wrong, and when we will revisit.
The meeting should end with commitments. Budget moves, test owners, kill criteria, definition changes, or follow-up evidence should be written down before people leave. Growth discipline is not the sophistication of the model. It is whether the model changes what the company does with money.
Over time, the review should improve judgment. The team should be able to look back and ask which channels surprised them, which assumptions were too optimistic, which early warnings were ignored, and which allocation choices compounded. That feedback loop is where growth becomes an institutional capability rather than a sequence of campaigns.
That is the standard worth aiming for: fewer theatrical readouts, more explicit capital decisions, and a memory of why the company believed each dollar deserved to be spent.
The review should have a clear pre-read rule. If a number is there only because it is interesting, cut it. If it cannot change a budget, owner, threshold, test, or definition, it belongs somewhere else. The scarce resource in the room is not data. It is executive attention on the few decisions that actually move growth capital.
A good review also protects teams from hindsight fog. When a bet works, the decision log should show whether the company predicted the reason correctly. When a bet fails, it should show whether the evidence was weak, the assumption was wrong, or execution broke. That difference is how the organization gets better at allocating the next dollar.
The first few reviews may feel awkward because teams are used to explaining performance, not recommending capital movement. That discomfort is useful. It reveals which numbers are decoration, which owners lack decision rights, and which bets are running without a clear evidence threshold.
This is part 10 of 10 in The Capital Allocation Theory of Growth.