How mature is your revenue engine?
Most companies are strong on one or two pillars and quietly weak on the rest. The trouble is they fix the visible one. A maturity read across the five pillars of a revenue operating system, and the order in which to repair them.
Summary
- A revenue operating system has five pillars: planning, demand generation, execution, governance and predictability. Almost every company is genuinely good at one or two of them and quietly weak on the rest.
- The weakness is rarely where the attention goes. When revenue misses, the money goes into the top of the funnel, even when the deals were dying at a specific gate three stages down.
- Sequence the repairs by what is binding, not by what is loudest: governance first, then execution, then planning, then demand generation. Predictability takes care of itself once the other four are real.
Ask a founder how the revenue engine is doing and you will usually get the revenue number.
That is an understandable answer and an unhelpful one, because the number is an outcome. It tells you the engine produced something last quarter. It tells you nothing about whether it will produce the same thing next quarter, or why it produced what it did, or which part of it is carrying the rest.
A revenue operating system has five pillars. Almost every company we meet is genuinely good at one or two of them and quietly weak on the others. And the weakness is rarely where the attention goes, because the pillar that feels urgent is almost never the pillar that is binding.
The five pillars, as a maturity read
Planning. At the weak end, the plan is a target on a slide with a growth percentage attached. In the middle, it is decomposed by segment or product but not by driver. At the strong end, it is a build: coverage, conversion, cycle and capacity, each with a named owner, where you can point at any number and say what has to be true for it to happen.
Demand generation. Weak looks like hope: some marketing, some referrals, no relationship between effort and outcome. Middle is activity that is measured but not modelled. Strong is a coverage equation. You know your conversion from enquiry to revenue and can back-solve how much top-of-funnel the plan requires, then hold someone to producing it.
Execution. Weak means stages named after what your seller did, no exit criteria, and a pipeline that looks better than it is. Middle means a defined process that people follow inconsistently. Strong means buyer-verifiable exit criteria, where two people would place the same deal in the same stage, and where you can see which gate loses deals and which stage holds them.
Governance. Weak is a meeting that reads numbers out. Middle is a review that diagnoses but does not decide. Strong is a charter: a named number, a named owner, a threshold, a forum, where every review ends in a decision that changes what somebody does next week.
Predictability. Weak is a forecast that is a feeling. Middle is a forecast that is usually roughly right. Strong is forecast accuracy tracked as a metric in its own right, per person, over time, so calibration becomes coachable.
The pattern we see
Two things come up again and again.
The first is that the visible pillar gets the investment. When revenue misses, the instinctive diagnosis is almost always demand generation: we need more leads. So money goes into the top of the funnel. Sometimes that is right. Frequently the pipeline was adequate and the deals were dying at a specific gate three stages down, which more leads will not fix. You simply end up with a larger pipeline that converts at the same broken rate, and a higher cost of acquisition to show for it.
The second is that predictability gets treated as a tool problem. Forecasting software gets bought.
Predictability is not a pillar you can install; it is the output of the other four done well.
You cannot forecast your way out of leaky execution or absent governance. You can only forecast the leak more precisely.
Why an honest read is harder than it sounds
Self-assessment on this is genuinely difficult, for a reason that has nothing to do with candour.
You are closest to the pillar you personally built. A founder who came from sales will rate execution generously and may not notice that the plan was never a build. A founder from a finance background will have a rigorous plan and a pipeline nobody engineered. The pillar you are strongest on is also the one you inspect most carefully, which means the weakest pillar is often the one receiving the least scrutiny, precisely because nobody in the room is fluent enough in it to ask a hard question.
That is why a structured read beats a conversation. Not because the questions are clever, but because they are the same questions asked of every pillar, without the asker's bias about which one matters.
What to do with the profile
Once you can see the five pillars side by side, the sequencing becomes straightforward, and it is usually not what people expect.
Fix the binding constraint, not the loudest complaint.
If execution is weak, more demand makes it worse, not better, because you are feeding a leaking pipe faster. If governance is weak, any fix you make to the other pillars will decay within two quarters, because nothing holds it in place.
Our rough ordering, where several pillars are weak at once: governance first, because it is cheap and it makes every subsequent fix stick. Then execution, because it converts pipeline you already have into revenue you are currently losing. Then planning. Then demand generation, which is the most expensive to improve and the least useful to improve first. Predictability takes care of itself once the other four are real.
Where to start
We built ROSA for exactly this: a short diagnostic across the pillars of a revenue operating system. Twelve questions. It produces a profile rather than a score, because a single number would repeat the original mistake of treating revenue as one thing.
It takes a few minutes, and the output is the thing most companies are missing: not a verdict on how good the engine is, but a clear read on which part of it is holding the rest back.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
Related reading
