The Revenue System Required to Scale a B2B Company
A sales process is not a revenue system.
A sales process describes how a deal moves. A revenue system is everything that decides which customers a company goes after, how it reaches them, what it offers them, how it wins them, how it delivers what was sold, whether the customer stays and grows, and whether any of it costs less the second time. The sales process is one part of that, and not the part where scaling is usually lost.
Why the smaller object gets all the attention
Because it is the visible one.
Deals are legible. They have stages, dates, owners and a number attached, so they get the reporting, the tooling and the management attention. The decisions that actually govern whether growth holds are mostly made earlier and elsewhere: which customers were selected, what was promised, how the price was set, what delivery committed to. Those decisions have no stage and no owner, and they are usually not recorded as decisions at all.
A company can have an immaculate sales process sitting on top of a revenue system that cannot scale, and the sales process will not tell it so.
That is the whole test, and it is more demanding than it sounds.
It does not mean the people stop mattering. It means the reason a customer buys exists somewhere other than in a person’s head, in a form that survives being handed to somebody who was not there when it was learned. It means the choice of which customers to pursue is a rule rather than an instinct. It means what happens after the sale is designed rather than improvised, because a delivery that is improvised every time is a cost that never falls.
Companies that scale are not the ones with better people. They are the ones where capability was converted into something transferable before the growth arrived, rather than after.
This is why the two subjects belong on one page.
Whether the revenue holds is decided by which customers were selected and what was promised to them. Whether the way of winning transfers is decided by whether the reason they buy was ever stated. Whether the base grows from inside is decided by what happens after the sale and by whether the cost of the next customer is falling. Whether the pace is absorbable is decided by how much of the system is improvised, because improvisation consumes attention, and attention rather than capital is the scarce input in scaling.
Each of the four failures traces back to something in the system rather than to something in the market or in the team. That is the useful part. It means the finding points somewhere.
Where the system breaks first
Almost always at selection.
A company that has not decided precisely which customers it is for will win a set of customers that have little in common. Nothing then repeats, because there is no pattern to repeat. Delivery cannot be standardised, because every implementation is different. The base does not compound, because expansion has to be invented separately for each account. The organisation absorbs badly, because every new person has to learn a set of exceptions rather than a rule.
One unmade decision produces four symptoms in four different parts of the company, and it is usually diagnosed as four problems.
Repair or rebuild
The question is whether the system is sound and under-instrumented, or unsound and well-run.
The first is common and cheap to fix. The company knows who it is for and how it wins, but none of it is written, measured or taught, so it does not survive being scaled. The repair is largely one of making the implicit explicit.
The second is more serious. The company has grown by taking what was available, and the answer to what it is for is a list rather than a description. That is a rebuild, and it costs more the longer it has been growing, because there is more revenue attached to the pattern being changed.
Telling them apart requires knowing which one has failed and why, which is a diagnostic question, and it should be answered before any building starts.
Why the diagnosis and the build are kept apart
Revenue Arc diagnoses. Independent partners build. No fee crosses that line in either direction.
The reason is structural rather than decorative. A firm that diagnoses and then sells the remedy has an interest in the finding, and everybody involved knows it, including the company being read. It does not require anybody to behave badly for that interest to shape a conclusion, which is why the safeguard has to be architectural rather than a matter of professional restraint.
The practical consequence is that a reading can return an answer that generates no further work. It can say the company is already scaling and should be left alone. A reading incapable of that answer is not worth commissioning.
Where this page stops
This page describes what a revenue system is and what makes one scalable. It does not give the design of a working system, the sequence in which a broken one is repaired, or the evidence that establishes which of the two situations a company is in. Describing the shape of an answer is one thing. Knowing which shape a particular company needs is another, and it is settled on evidence rather than on preference.
The Build is delivered by independent partners, on the evidence a reading produced, and it begins where the diagnosis ends. Where it is not yet clear which of the two situations a company is in, that is the question to settle first: mark@revenuearc.co.uk.