Growth metrics sit in layers. The lower layers are not useless, but they are easier to game and easier to misunderstand. The higher layers are harder to measure, but they are closer to the decisions executives actually need to make.
The first layer is activity: traffic, impressions, leads, installs, signups, meetings, trials, and demos. These numbers are useful because they show motion. They are dangerous because motion is not value. A company can increase activity while making the business worse.
The second layer is efficiency: CAC, conversion rate, cost per lead, ROAS, funnel velocity, and sales productivity. These metrics are stronger because they connect input to output. But they can still hide margin, customer quality, saturation, and causality.
The third layer is business quality: gross margin, retention, churn, net revenue retention, expansion, support load, refund rate, onboarding completion, and product usage. These metrics begin to answer whether acquired customers are worth having.
The fourth layer is capital recovery: gross payback, net payback, and incremental net payback. This is where growth becomes a cash recycling system. The company can see how long money is trapped, how confidently it returns, and whether the next dollar still clears the bar.
The fifth layer is allocation: IRR, absolute size, liquidity, confidence, strategic option value, and portfolio role. This is where executives compare unlike opportunities. A small fast-payback motion may fund the business. A larger slower-payback motion may build the next curve. A risky bet may be justified if it creates a valuable option.
The growth metric stack helps teams stop asking one metric to do every job. Activity metrics diagnose volume. Efficiency metrics diagnose funnel mechanics. Business-quality metrics diagnose customer value. Capital metrics diagnose cash recovery. Allocation metrics decide where the next dollar should go.
A serious review should climb the stack. If activity is down, inspect the funnel. If efficiency is up, inspect customer quality. If payback is attractive, inspect incrementality. If IRR is high, inspect scale and liquidity. Each layer checks the layer below it.
The stack also clarifies ownership. Marketing may own activity and channel efficiency. Product may own activation and retention. Sales may own conversion and cycle quality. Finance may own margin and cash timing. Executives own allocation across the whole system.
The operator test: look at the current growth dashboard and label each metric by stack layer. If most of the dashboard sits in activity and efficiency, the company is not yet managing growth as a capital allocation problem.
A stack also prevents executive teams from arguing across layers. One person says signups are up. Another says retention is weak. A third says payback is too long. They may all be right. The question is which layer is currently governing the decision.
For example, an early product-led motion may need activity metrics to understand whether demand exists at all. Once demand is visible, efficiency metrics help improve the funnel. Once customers arrive, business-quality metrics show whether they are worth keeping. Once spend increases, capital metrics decide whether the motion deserves more money.
The stack should also expose missing links. If the company has activity and payback but no customer-quality metrics, it may be buying customers without knowing whether they retain. If it has ROAS and retention but no incrementality, it may be measuring credited growth rather than caused growth.
The operating artifact should be one page, not a giant taxonomy. Put each major growth motion on the left and the strongest available metric at each layer across the row. Blank cells are useful. They show where the company is making allocation decisions without the evidence that would make those decisions safer.
The stack is also useful for diagnosing why a team is stuck. If activity is healthy but payback is weak, the issue is probably quality, margin, conversion, or retention. If payback is strong but scale is tiny, the issue is opportunity size. If attribution is strong but incrementality is unknown, the issue is evidence quality.
A growth leader can use the stack to make sharper asks of other functions. Instead of telling product that activation is bad, they can show how activation is changing payback. Instead of telling finance that a channel is strategic, they can show which layer of evidence is strong and which layer is still uncertain. The stack turns metric debate into operating diagnosis.
For a real operating review, each metric should have a job title. Activation tells the team whether people reach value. Retention tells the team whether value lasts. Contribution margin tells the team whether revenue is worth having. Payback tells the team how quickly capital recycles. Incrementality tells the team whether spend changed behavior. Mixing those jobs creates noisy debates.
The stack is especially helpful when leadership wants one number. One number is usually fine for a headline, but bad for diagnosis. A CEO can ask for the single constraint that matters this quarter while still requiring the supporting layers that explain it. That balance keeps the meeting decisive without making the analysis fake.
A common mistake is to promote a diagnostic metric into a funding metric because it is easy to measure. Clicks, meetings, signups, and MQLs can all be useful signals. They become dangerous when they are allowed to move capital without proof that they lead to durable revenue, contribution, or learning.
This is part 6 of 10 in The Capital Allocation Theory of Growth.