Table of Contents
Do not index
The Predictive Path
Course 2: Revenue as a system
Closing essay
From siloed parts to one system
What changes when a leadership team stops running revenue as separate departments and starts running it as one thing.
Across this course the same shift kept returning: revenue is not a funnel, the parts can each win while the whole loses, the lifecycle is the axis that holds, understanding decays unless it's built to persist, timing is the leverage, growth is a configuration, and steering is a choice between futures. Pull them together and one picture remains: the parts were never the system. This closing piece names the turn the rest of the curriculum builds on — you stop optimizing pieces and start designing the whole.
By the end of Course 2, one idea has replaced another. The company that began the course running revenue as a set of separate functions — each with its own number, its own quarter, its own definition of winning — can now see revenue as a single system, and run it as one. That is the shift the whole course was built to produce.
Where most companies start
In most companies, revenue is run in pieces. Marketing is measured on leads, sales on bookings, customer success on retention, finance on the plan. Every function works hard at its own part and is rewarded for it, and nothing in the arrangement asks whether the parts add up. So they often don't. A strong lead quarter feeds deals the company cannot serve well. A heroic bookings number rests on discounts that break the economics two years later. Each department is doing its job; the company still misses. This is the siloed organization — and it is not a failure of effort. It is what happens when a company measures the parts and assumes the whole will take care of itself.
What the course showed
Course 2 took that arrangement apart and put it back together as one object. It showed that revenue is not a funnel that ends at the sale but a system of customer relationships, most of whose value is decided after the close. It showed why improving one part on its own can make the whole worse, and why the entire customer lifecycle — not the quarter, not the function — is the one stable thing every number should be read against. It showed that growth is configured to a company's real situation rather than simply demanded, that leverage is mostly a question of timing, and that what a customer is worth only makes sense measured across its entire life. And it ended where leadership actually sits: choosing deliberately between two possible futures, rather than defending a single forecast after the fact.
Watching versus running
The difference all of this adds up to is simple to state. Run in pieces, revenue is something you watch: you stand over each function's number, read it once it has landed, and react. Run as a system, revenue is something you steer: you hold the whole population of customer relationships at once, you see how a move in one place changes the others, and you set the conditions before the outcome forms. Course 1 called these two postures reporting and construction. Course 2 is the course where construction becomes something a leadership team can actually do — because it is the course that supplies the single object there is to construct.
What it gives back
That is the relief Course 1 withheld. The unease it named — being accountable for something you can see but cannot steer — was never a personal shortcoming. It was what it feels like to run a system while looking at it in pieces. Seen whole, it can be steered. The control was always there; the picture was what was missing.
Where this leads
If revenue is one system, the people running it need one language for it — shared definitions of customer, segment, revenue, margin, and time that mean the same thing in every function. Without that, the system fragments straight back into the silos this course spent nine lessons joining. That shared language is where The Predictive Path goes next. The function courses that follow it — marketing, sales, customer success, finance — each show how one part works in service of the whole rather than on its own. The picture does not change; the resolution does.
Next up
With the system in view, the next course gives every function the shared language to reason about it together.
→ Continue to Course 3: A common language for revenue
———
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
Written by
Niko Laine is a B2B SaaS CFO. He writes about revenue intelligence — how leaders see, predict, and steer revenue as it becomes a system rather than a number.