Table of Contents
- The Predictive Path
- The impossible jobs
- The roles are not hard. They are impossible.
- One line, broken in four places
- Decide locally, answer globally
- Sales: told to forecast a cascade it cannot see
- Marketing: optimized for the front of the line, judged on the back of it
- Customer success: handed the consequences, not the decisions
- Finance: told to defend a number it had no authority to set
- The variance no one can attribute
- How fragmentation manufactures blame
- The real cost: leadership without leverage
- Why this is not a people problem
- Next up
Do not index
The Predictive Path
Course 1: Strategy without control
Lesson 3: The impossible jobs
The impossible jobs
Why fragmentation turns reasonable expectations into roles that cannot be done.
Every revenue leader is handed the same impossible deal: local visibility, global responsibility. Sales sees its own pipeline but answers for revenue decided long after the deal closes; marketing is judged on demand it can't follow into the base; finance defends forecasts whose assumptions it doesn't own. None of them can see the whole they're accountable for — so the failure is structural, not personal. This lesson is about that deal, and what it costs the people who take it.
The roles are not hard. They are impossible.
Most revenue organizations are full of competent people. Marketing runs campaigns well. Sales runs a disciplined pipeline. Customer teams work hard to keep and grow accounts. Finance closes the books cleanly and the forecast reconciles. Competence is not missing anywhere.
And the results still cannot be explained. Revenue grows, but no one can say which customer choices made it durable. Margin holds, but no one can say whether it survives the next phase. Cash stabilizes, but no one can name the contracts or segments that did it. The organization can describe what happened. It cannot say how it was built.
So it does the only thing left. It assigns responsibility for the parts no one could see.
Sales is told to forecast a pipeline, and then blamed for the margin, churn and expansion the rest of the company built on top of that pipeline — none of which sales could see. Marketing is judged on demand quality it never gets to observe. Customer teams are held to the retention of customers they did not choose. Finance is told to defend a number it did not get to set. None of these expectations is unreasonable on its own. Together they describe four jobs that cannot be done — not because the people are weak, but because each one is held accountable for an outcome it structurally cannot see being formed.
That is the claim of this lesson, and it is worth stating without softening. These are not hard jobs that better people would do better. They are impossible jobs, and they are impossible by construction.
One line, broken in four places
To see why, stop looking at the four functions as four functions. Look at them as four cuts across a single line.
A SaaS revenue system is one continuous chain. It starts before any customer exists — with a marketing budget and the pipeline that budget is meant to create. Pipeline becomes a new-customer forecast. The new-customer forecast becomes a revenue forecast. The revenue forecast drives everything downstream of it: cost of goods as more customers need serving, operating expense as the company staffs to the plan, customer-success capacity sized to the accounts arriving, the P&L, the margin, the cash. Spend at the front of the line propagates all the way to the financial statements at the end of it. It is one cascade, and every part of it is a consequence of the part before.
Now mark where the organization cuts that line. It cuts it between marketing and sales. Again between sales and customer success. Again between customer success and finance. The line that is one cascade in reality is run as four segments in practice, and each segment is operated by people who can see their own segment and almost nothing past the cut on either side.
That is the structural fact underneath all four impossible jobs. The cascade is real. The visibility is segmented. Each function makes decisions that travel the full length of the line, while seeing only its own piece of it. Everyone is working blind to everything their decisions actually set in motion.
Hold that image. The rest of this lesson is just what it looks like from inside each segment of the broken line.
Decide locally, answer globally
Every function makes its decisions with the information inside its own segment. Marketing commits budget against pipeline targets. Sales moves deals between pipeline stages. Customer success spends retention effort against account health. Finance assembles the forecast from whatever the first three hand it.
Every one of those decisions is locally reasonable. None of their consequences stays local. The segment marketing bought shows up as cost-to-serve in customer success a year later. The deal structure sales agreed to shows up as a cash-timing problem in finance after signature. The expansion customer success encouraged shows up as margin dilution no one forecast. The decision and its consequence sit on opposite sides of a cut in the line, owned by different people, separated by enough time that by the time the consequence is visible the decision behind it is gone.
Decide locally. Answer globally. That is the contradiction every one of these roles is built on, and it is why strategy in these companies quietly turns into blame.
Sales: told to forecast a cascade it cannot see
Start with the function blamed first and most.
The company does not start forecasting when a deal closes. It starts forecasting from the pipeline. Pipeline coverage and stage probabilities become the new-customer forecast. The new-customer forecast becomes the revenue forecast. And the revenue forecast is the thing the entire company then plans against — cost of goods scaled to the customers expected, operating expense committed to the headcount the plan implies, customer-success capacity hired against the accounts that are supposed to arrive, the P&L and the cash built on top of all of it.
Every one of those downstream commitments traces back to numbers that originate in the pipeline. And the pipeline is the one part of the line sales can actually see. Sales moves deals from one stage to the next. It does not see the customer's eventual support intensity, the segment's real expansion behavior, the cash timing the contract terms imply, the margin the relationship will carry two years out. None of that is in the pipeline. The pipeline is stages and probabilities — and those probabilities are not science. They are a working estimate, applied by people under quota pressure, calibrated mostly by feel.
So the company builds a full financial cascade on top of stage percentages, and then, when the forecast misses, asks why sales got it wrong. Sales did not get it wrong. Sales was asked to originate a company-wide forecast from the only segment of the line it can see, about consequences that form entirely on the far side of cuts it cannot see across. That is not a forecasting failure. It makes the role impossible.
Marketing: optimized for the front of the line, judged on the back of it
Marketing is measured on the segment it can see: lead volume, conversion, cost per opportunity, channel performance. It is held accountable for something it cannot see: whether that demand became durable, high-margin, expandable customers.
When downstream value disappoints, marketing is blamed for "quality." But quality was never something marketing was allowed to observe — it is inferred backward, after customer behavior on the far side of two cuts in the line has already played out. Marketing is asked to optimize the front of the cascade while being judged on the back of it, with the middle invisible to it the entire time.
Customer success: handed the consequences, not the decisions
Customer success is expected to prevent churn, drive expansion, and protect margin. It inherits all three after the decisions that determine them are already made — the customer selected, the deal structured, the pricing and expectations set, all upstream, all across cuts CS had no part in.
By the time risk is visible inside the CS segment of the line, the decisions that created it are several months and at least one cut away. CS is then held accountable for outcomes that were substantially set before it ever touched the account. The effort is real. The visibility came too late to matter.
Finance: told to defend a number it had no authority to set
Finance is where the broken line ends, and where its consequences land hardest.
Finance owns the P&L. It owns the margin. It owns the forecast variance in front of the board, the quarterly explanation, the credibility of the number. What finance does not own is almost anything that actually determines those things. It did not create the pipeline. It did not set the deal structures. It did not select the segments or the customers. It consolidates a forecast assembled from inputs every other function produced, after month-end, and then is told to stand behind it.
There is a sharper version of this, and it is worth stating plainly. Finance does not even take those forecasts at face value. It applies a discount to them — every department's forecast comes in and finance haircuts it, because finance has learned the upstream numbers run hot. So the number the company commits to is the upstream functions' forecast, adjusted by finance's judgement of how wrong it usually is. When that number misses, finance defends the variance. So who actually owns the forecast? The functions that produced inputs they had no downstream visibility to test? Or finance, which did not produce them, cannot change them, discounts them on instinct, and then has to account for the gap? There is no clean answer, and the absence of one is the point. Responsibility for the number sits with the function that had the least authority over what went into it. That is not a finance failure. It makes the role impossible.
The variance no one can attribute
Watch the forecast over several quarters of this and a pattern appears that has no owner.
The forecast misses. Not wildly — it misses, and it misses somewhere different each time. One quarter the gap is margin. The next it is cash timing. The next, expansion came in light. Each miss gets a plausible after-the-fact explanation from whichever function is nearest the damage. None of the explanations predicts the next miss, because the misses are not coming from one segment of the line. They are coming from the cuts between segments, and the cuts move.
This is what erodes leadership confidence before it erodes results. A forecast that is wrong by a known amount in a known direction is just a bias you correct. A forecast that is wrong by a different amount in a different place every quarter, always explained and never improved, cannot be corrected, because nothing about the explanation makes the next one better. The instinct is to push the function holding the number — finance — toward more conservative estimates. That narrows ambition and does nothing to the variance, because the variance was never finance's to control. It belongs to the broken line.
How fragmentation manufactures blame
When the outcome disappoints, the organization runs the same loop every time. Sales blames demand quality. Marketing blames execution. Customer success blames deal fit. Finance blames the assumptions. Each one is correct from inside its own segment of the line. None of them is in control of the line.
That loop is almost always read as a misalignment problem — the teams need to communicate better, meet more, agree on definitions. That reading sends the company looking for the fix in the one place it cannot be. The loop is not teams failing to coordinate. It is the necessary output of cutting a single cascade into four blind segments and then asking each segment to answer for the whole. Better meetings do not rejoin the line.
The real cost: leadership without leverage
For the leadership team this resolves into something worse than any single miss.
Executives set strategy, commit to targets, and stand behind outcomes — without access to how those outcomes are constructed, because the construction is spread across four segments none of them can see end to end. They can observe performance. They can explain it afterward. They cannot say, with confidence, what happens if they change one thing — tighten selectivity, shift pricing, slow expansion, enter a new segment — because the effect of that change propagates down a line they cannot see down.
That is not a knowledge gap more reporting closes. More reporting describes the segments in finer detail. It does not rejoin them. So leadership's decisions get more cautious, because acting confidently requires a grip on a cascade the structure has cut into pieces. Targets get hedged in the same breath they are set. Strategy narrows toward what feels survivable. Ambition contracts while every dashboard stays green.
Why this is not a people problem
Be exact about what is and is not being claimed. No individual failure is required for any of this. Competence is not the issue — it was everywhere in the opening paragraph. Effort is not the issue. Even alignment, in the sense of the teams agreeing, is not the issue. The roles are impossible for a reason underneath all of those: the system cuts a single cascade into segments and withholds, from each one, the visibility into everything its decisions set in motion past its own cut.
When understanding does not travel the length of the line, the organization still demands the things only the whole line produces — predictable revenue, stable margin, durable expansion, a credible forecast. Those form at the end. Accountability is assigned at the segment where each decision was made, blind to the end. That contradiction is the impossible job. It is not a flaw in the people holding the roles. It is the shape of a line broken into four.
That break was not anyone's decision. It is what a revenue system becomes when it outgrows the size one person could hold in their head, and nothing was built to carry understanding across the cuts it now has. The next lesson goes after the model the organization still uses to picture that system — and why that model hides the very thing leadership most needs to see.
Next up
If fragmentation turns roles into impossible jobs, the next thing to question is the model the organization uses to picture revenue at all — because the picture is part of why the line stays broken.
→ Continue to One customer, four versions
———
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.
