Table of Contents
Do not index
The Predictive Path
Course 2: Revenue as a system
Why the parts don't add up
Where the work shifts from watching revenue to shaping it — by changing what revenue is taken to be.
Course 1 left you with a hard fact: you can watch the revenue engine in fine detail and still not be able to steer it. This course explains why — and begins the turn. The watching never became steering because revenue isn't a funnel or a stack of functions each doing its job well; it's a system, and you've been managing its parts. What follows is the shift from running the pieces to seeing the whole.
Start here
Course 1 ended at a diagnosis and stopped there on purpose. It named, from five angles, a single fault: a revenue organization watches outcomes after they have formed instead of building them before they take shape — and the unease senior leaders feel in an otherwise well-run company is what that fault feels like from the inside.
This course is where the answer begins. It is the first move, and the one everything else in The Predictive Path depends on.
What this course is
In most companies, revenue is run in pieces. Marketing owns demand, sales owns the close, customer success owns the renewal, finance owns the plan — and each is measured on its own part. Every team can hit its own number while the company as a whole still misses, because no one is accountable for how the parts add up. That is not a discipline problem. It is what happens when revenue is treated as a set of separate functions rather than one thing.
Course 2 puts the parts back together. It treats revenue as a single system: one population of customer relationships, opened from several different sources, all running and changing at the same time, with the company's result being whatever that whole population adds up to. The job of leadership is to run that system as a whole — not to optimize the pieces and hope they cohere.
That shift is what the course builds, lesson by lesson. It starts by replacing the funnel with a revenue system, and showing why improving each part on its own can make the whole worse. It establishes the customer lifecycle as the one stable thing every number is read against, and why a company has to hold on to what the lifecycle teaches instead of relearning it each year. And it ends on the questions leadership actually owns: how growth is configured to the company's situation rather than simply pushed, where real leverage sits, what a customer is worth across its whole life, and how a team chooses deliberately between two futures instead of defending one forecast.
Who this is for
This course is written for the people accountable for revenue outcomes: the CEO, the CFO, the CRO, the CMO, the customer leader. It assumes you are experienced and already data-literate, and that the difficulty at your level is not a shortage of information. It does not teach the mechanics of any one function — that is the work of the courses that follow. It works at the altitude where the whole revenue system is visible at once, across every department, because that is where the shift it describes actually happens.
It assumes Course 1. The problem named there is the problem this course answers, and the answer reads as one only against that diagnosis.
How to read it
The lessons are sequential and they build — each assumes the vocabulary the one before it established, and the course compounds a shared language on purpose, the way it argues a revenue system should. But each lesson also stands on its own, and the ideas tend to become recognizable the moment they are named, so it is fine to enter where a title catches you.
This is the course where the relief Course 1 withheld begins to arrive — not as a tool, and not yet as a method, but as a clearer way of seeing the thing you are responsible for, clear enough that it can finally be shaped.
Next up
Course 2 begins by changing the object itself — from revenue as a funnel that ends at the sale to revenue as a system of customer relationships that mostly begins there.
→ Start Course 2 with Lesson 1: Revenue is a system, not a funnel
———
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
The Predictive Path lessons
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.