Design revenue, don't just report it

Do not index

The Predictive Path

Course 2: Revenue as a system

Lesson 7: Design revenue, don't just report it

Design revenue, don't just report it

Why most growth is accidental, and what it takes to construct it on purpose instead.

Most revenue is reported, not designed — watched after the fact on a dashboard, corrected when it drifts, explained once the quarter has landed. But every stage of the lifecycle carries a setting, and those settings can be chosen deliberately instead of inherited by accident. A dashboard explains the result; design creates it. This lesson is about the difference between running the system you happen to have and building the one you meant to.

Growth you can't reproduce is not control. It's luck with good timing.

The last lesson ended on a distinction: leadership through escalation, which pushes harder once the heading is already wrong, and design, which becomes possible while the heading can still be set. This lesson takes up the design side and asks the question underneath it — when a company grows, does it know how it did that, well enough to do it again on purpose?

For most companies, the honest answer is no. The revenue came in. The year was good, or good enough. But asked to explain exactly which decisions constructed that result — which segments carried it, which paths held their margin, what would have to be repeated to get the same outcome again — the account turns vague. The number is real. The construction of it is a story assembled afterward.

This is accidental growth, and the first course named the problem it creates: an outcome you cannot deliberately repeat is not one you control, even when it is good. A strong quarter that no one can reconstruct is not evidence of a system working. It is evidence of a system the company cannot yet steer, producing a result it happened to like this time.

Accidental growth feels like control because the numbers are watched closely and the reviews are frequent. But watching an outcome form is not the same as having built it. The watching is real. The construction is mostly happening on its own.

Most companies know exactly one part of the machine.

There is one part of the revenue system most companies understand well, and it is worth being precise about, because it is the source of the feeling of control.

They know the pipeline. Marketing generates demand, the demand moves through stages, and past a certain point the stage-by-stage conversion is stable enough to forecast net-new acquisition with reasonable confidence. This deal count, at this average size, at these conversion rates, produces this much new revenue. That competence is genuine. It is the one place in the whole system where the inputs are understood well enough to act with a known effect.

But even here the knowledge is thinner than it looks. The pipeline can be forecast from its stages; what actually produces that pipeline — which segments the demand is drawn from, which channels bring durable customers rather than merely cheap ones — is far less understood. So the one part the company trusts is really half-understood: it can forecast what happens once demand exists, without fully knowing how to construct the demand it wants.

And that is the lit part of the system. It is where attention goes, where the dashboards are sharpest, where leadership feels most fluent. The trouble is everything it sits in front of.

Every stage of the lifecycle has a dial. Most companies have set one.

Think of the revenue system as a control board. Every stage of the customer lifecycle has a dial on it — which segments demand is drawn from, what the contract is shaped like at signature, which onboarding path a new customer is put on, how expansion is prompted, how renewal is handled, what a customer is allowed to cost to serve. The board runs the whole length of the lifecycle, not only the part before the sale closes.

A dial is not a switch you flip once. Each setting commences a play that runs for a stretch of time. Turn the onboarding dial to high-touch and you have committed a customer to a ninety-day guided path — and committed the company to the cost of delivering it. Turn it to self-serve and a different play runs, at a different cost, producing a different rate of customers who actually reach value. The setting is chosen in a moment. The play, and its economics, run for months.

This is the part the familiar language of growth levers gets wrong. A lever sounds like a one-time push — add the spend, get the growth. A dial is a setting that stays where it is and keeps producing its play until someone moves it. And here is the uncomfortable part: every dial on the board is always at some setting, whether or not anyone chose it. A company that has never looked at its onboarding dial still has one, sitting at whatever position it drifted to. The board is never blank. It is only, usually, unattended.

The dials belong to the segment. Every segment runs the same board — the same stages, the same dials — but the settings sit in different positions, and that is exactly why segments produce different economics. One segment's board is set to a high-touch onboarding path and a quarterly contract; another's to self-serve and an annual prepay. Same dials, different positions, different outcomes. The individual customer inherits its segment's board and gets adjusted only where an account earns it — a reference customer you deliberately carry at a lighter margin, say, by turning one or two of its dials off the segment's default on purpose.

Set against that picture, what most companies actually do is narrow. They watch one dial closely — the acquisition dial, the one feeding the pipeline — and tune it with real skill. The rest of the board sits at settings no one chose, producing plays no one is watching, resolving into margin and cost months later as if by weather. It is not that the company has no control board. It is that it has its hand on one dial out of a dozen.

Why an unattended board makes growth accidental.

Put the lit dial and the unattended ones together, and the randomness explains itself.

A company turns the dial it can see — it pushes pipeline — and then lives with whatever the rest of the board happens to be set to. Retention lands where it lands. Expansion reaches some accounts and not others. Cost to serve drifts. The margin resolves a year later and surprises everyone. The growth that results was not constructed; it was one dial set on purpose while a dozen others ran on settings no one had chosen.

An outcome produced that way cannot be repeated, because no one knows which settings produced it. When a segment turns out well, the company cannot say whether it was the onboarding path, the contract shape, or simply a good cohort — so it cannot deliberately do it again. When margin erodes, the cause feels mysterious for the same reason: it was several dials sitting in the wrong positions, none of them visible, none of them chosen. The mystery is not bad luck. It is the signature of growth assembled from a board no one was reading.

Either you know the whole board, set across the lifecycle and tuned per segment, or you know one dial and you are guessing on the rest. Guessing sometimes lands well. That is precisely what makes it so easy to mistake for skill.

Designing revenue is reading the whole board and setting it on purpose.

Designing revenue is the opposite stance. It means the full board is visible — not just the acquisition dial, but the contract, onboarding, expansion, retention and cost-to-serve dials too — and visible in the company's own economic terms, segment by segment. It means each dial is set deliberately for each segment, because the company knows what settings have actually produced durable, profitable customers there. And it means those settings are applied at the customer level as the default next steps, adjusted only where an account earns a deliberate exception.

When that is true, capital and capacity get allocated against what is actually coming rather than after it arrives. A segment whose board produces real expansion and contained cost to serve earns more acquisition spend and more capacity, on purpose. A segment whose board resolves poorly gets its dials reset, or its inflow slowed, before another year of cohorts is admitted on the old settings. The growth that results can be explained, because it was constructed: these segments, these dial positions, this allocation, producing this outcome — and repeatable next year, because the company knows what it set.

This is not the same as having a tool for each dial, and it is not yet the work of computing exactly what each setting will produce. It is the stance underneath that work: knowing the dial exists, knowing it is set at the segment and applied at the customer, and turning it knowingly instead of leaving it to drift. How each dial is actually read and tuned — how expansion is judged, how cost to serve is modelled, how the whole board is set across many segments at once — is the work of the courses that follow. The foundation is the posture itself: growth is something you set, not something you receive.

Accidental growth doesn't survive scale. Designed growth compounds.

The difference between the two stances is small at first and decisive over time.

Early on, with a handful of segments and a short history, an unattended board is survivable. A founder holds the settings in their head without ever naming them as dials. But every new segment, every new product line, every new market adds another full board to a system where most of the dials are already unattended. The randomness does not stay constant as the company scales. It multiplies, because the number of unwatched dials multiplies. This is why a company can feel more in control at thirty people than at three hundred, with far better dashboards at three hundred.

Designed growth moves the other way. Each segment whose board is known and set on purpose becomes a pattern the company can reuse and refine, and each resolved cohort sharpens the settings for the next. The system gets more repeatable as it scales, not less, because the dials are named, owned and tuned rather than left to chance. The accidental factor is what gets engineered out.

That is the whole of it. Managing revenue explains outcomes after they form. Designing revenue constructs them — by knowing every dial in the lifecycle, setting it deliberately at the segment, applying it at the customer, and refusing to let the result stay a matter of luck.

Next up

Designing revenue means knowing what each customer is actually worth to design around — across the whole life.

→ Continue to A customer's worth across the whole life

———

This article is part of The Predictive Path

By Niko Laine, SaaS CFO

→ About the author

→ LinkedIn

You can read it on its own or explore the full curriculum.

→ View The Predictive Path

→ Explore courses