The strategy that stays on the slide

Do not index

The Predictive Path

Course 1: Strategy without control

Lesson 5: The strategy that stays on the slide

The strategy that stays on the slide

Why a strategy everyone can recite is followed about one day a year.

Most strategies get touched twice a year — the day they're set and the day they're graded. In between, the decisions that move margin, retention and cash get made without them. A strategy that never reaches the daily call isn't being run; it's being reported on. This lesson is about the distance between the plan on the slide and the work that produces the result.

Nobody runs your strategy

Your strategy is followed about one day a year. It is set at the offsite, repeated at the all-hands, agreed by everyone in the room. Then the company goes back to work and runs on something else for the other 364.

The board does not see this. The board sees the strategy presented, accepted, and reported against, and assumes it is the thing driving the decisions underneath. It is not. The decisions underneath are made on local signals the strategy was never translated into. The strategy and the company are running in parallel, and only one of them is touching customers.

That is the subject of this lesson, and there is no gentle way to put it: a strategy everyone agrees with can still be a strategy the company never actually runs. The agreement is real. The execution of it is not. The two are different things, and most organizations have the first while believing they have the second:

A stated strategy lives in language. A direction, an ambition, a slide everyone can recite.

An operative strategy lives in decisions. The thousands of small customer-level choices the company makes every week — which demand to chase, which deals to take, which terms to accept, which accounts to invest in.

They are supposed to be the same thing. In a small company they are, because the people making the customer-level choices are the people who hold the strategy in their heads. As the company scales, the distance between the slide and the choices opens, and nothing closes it. The strategy stays in language. The choices get made on whatever signal is in front of the person at the time.

Watch where the strategy actually is

The fastest way to see this is to take the five outcomes every SaaS strategy is built on, and ask, for each one, where it is actually formed. Not where it is reported. Where it is made.

Margin. Formed at the moment a customer is admitted: the discount that was approved, the support tier that was promised, the pricing exception that closed the quarter. Sales made those calls against close rate. The strategy said "protect margin." Margin was not in the room when the discount was signed.

Net revenue retention. Formed by selectivity — what this customer actually needed at entry, and whether it had real room to grow. But the selection, the contract structure, the onboarding path, and the expansion path were never designed as one thing between sales and customer success. Each was decided separately, by a different function, on a different signal. The strategy said "grow through expansion." Nobody owned the path that expansion would have to travel.

Cash stability. Formed in the contract, deal by deal — billing frequency, payment terms, the up-front-versus-ratable structure a rep conceded to get the deal in this quarter. The strategy said "stabilize cash." The person agreeing the terms was closing, not running the cash position.

Expansion. Formed by which segments were acquired and whether the product landed deeply enough to grow inside the account — and whether anyone designed an expansion path at all, or just hoped one would appear. Decided in demand and in onboarding, long before a CS team is asked to deliver it. The strategy said "expansion-led." The demand engine was optimizing cost per lead.

Retention. Formed before the customer was ever signed: did this kind of customer — this segment, this need, this profile — historically stay, and did it hit the onboarding milestones that the ones who stayed hit. Fit was the decision. The strategy said "durable base." Whether the customer fit the pattern of customers who last was not a question anyone's weekly numbers were measured against.

Five outcomes the strategy is entirely about. Five different decisions, made by different people, on different signals, at different points. The strategy is present in none of them. That is the whole problem, and it is not subtle once you look directly at it: the strategy governs the slide; local signals govern the company.

The strategy is discovered after the books close

There is a tell, and every leadership team will recognize it. The strategic goals do not show up while the decisions are being made. They show up after the quarter closes, and after the year closes — when finance consolidates the numbers and reports them.

That timing is the problem. By the time margin is in the board deck, every discount that set it was approved months ago. By the time NRR is reconciled at year-end, the cohorts that determined it were selected and onboarded a year before. Finance does not get to change any of it. Finance gets to explain it. The same shape as the impossible jobs a few lessons back: the function holding the number had no hand in the decisions that made it, and the decisions are closed by the time the number is legible.

So the strategy conversation turns into something else entirely:

explaining the variance against plan

reconciling why the customer mix moved

adjusting next year's forecast to the reality this year produced

refining the narrative for the board

And nothing in that conversation feeds back. The discovery that this segment churned, or that those deals carried thin margin, arrives too late to change the selectivity that produced them and too late to hit the financial target it already missed. The next cycle starts on the same signals. Strategy has quietly become a reporting function — it describes the company accurately, after the fact, and steers it not at all.

Why it feels present but does nothing

This explains a tension leadership teams live with and rarely name. The strategy feels clear. Execution looks energetic. Results arrive. Confidence is still thinner than it should be.

The instinct is to suspect alignment — the team must not be bought in, the priorities must not be sharp. That instinct finds nothing, because alignment was never the problem. Everyone agrees. Agreement is not what would have made the strategy operative.

What is missing is causal. The company cannot say which decisions carried the strategy and which ran on local signal — because the strategy was never in the decisions to begin with. A year of individually defensible choices, each made on what was in front of the person at the time, sums to a customer base that does not match the slide. No single decision is where it went wrong. The strategy was never in any of them.

Strategy is real only where a decision touches a customer

A strategy becomes operative in exactly one place, and it is not the offsite. It is the moment a decision touches a customer. Stated as the goals the strategy actually names:

Margin is not a finance result. It is the accumulated consequence of which customers were admitted, on what pricing, with what support intensity.

NRR is not a customer-success metric. It is the consequence of selectivity at entry and whether the path to growth was ever designed.

Cash stability is not a billing matter. It is the consequence of contract structures set deal by deal.

Expansion is not a CS motion. It is the consequence of which segments were acquired and whether an expansion path existed to begin with.

Retention is not a save play. It is the consequence of whether the customer ever fit the pattern of customers who stay.

Each of these is, underneath, a pattern of customer-level behaviour — or it is nothing the company can act on. If the strategy cannot be said in those terms, it cannot reach the decisions that would produce it.

And this does not stay at the customer level. The segment number is just these decisions added up across a segment; the company number is just them added up across everything. A strategy that entered none of the individual decisions cannot be present in their sum — the company result is the total of choices the strategy never reached, which is why it can miss the plan while every team did its job. The strategy can be reviewed against that total. It was never in it.

What this lesson is, and what comes next

This names a problem. It does not solve it. A strategy that is not expressed as customer-level behaviour stays on the slide and turns into reporting — that is the diagnosis, and Course 1's job is to make the diagnosis exact, not to start the fix.

The fix is real and it has a name and a place in this curriculum. It is not here, because reaching for it now would skip the steps the rest of the Academy is built to take properly.

What is settled is this. Strategy does not fail in well-run companies because it is wrong, or unclear, or under-supported. It fails because it is written in a language the company's decisions cannot read, and saying it louder does not change that.

Next up

Course 1 has named the problem from five angles. The closing essay does not add a sixth — it names the single shift all five have been circling, and points at where the work begins.

→ Continue to Towards a repeatable engine

———

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