12 Months Before

There's a detail I've come to pay attention to that isn't in any framework or any KPI dashboard: the file size of the monthly business review. When things are going well, the deck is lean. Numbers, charts, done. When things start getting complicated, the deck grows. Not because anyone decides to make it bigger, but because each number that looks unusual needs a slide to explain it. Revenue down? A slide about the pipeline. Churn up? A slide about the product roadmap. A deck that went from twelve pages to thirty-eight pages in nine months tells you something that none of the individual slides admit: the company has shifted from reporting results to explaining results. When a company starts explaining its numbers, it has already stopped hitting them.

I've been thinking about why decks grow that way, why the explanations multiply without anyone noticing the pattern. And it keeps coming back to the same thing: each slide, taken on its own, makes sense. Each explanation is accurate. Each response is the one you'd want the management team to give. The problem is never in any single slide. It's in the accumulation.

A few clients are paying late. Enterprise sales in France are lumpy. A single deal slipping from Q3 to Q4 can make a quarter look catastrophic and the next one look brilliant without anything fundamental changing. A margin dip needs context. Headcount continues against a plan approved six months ago, because you don't want a company where every manager freezes hiring at the first revenue wobble. That's how you lose good people and signal panic to the team.

Each of these responses, taken alone, is the right response. Each one adds a slide. That's what makes the problem so hard. There's no villain. There's no moment of deception.

I think about this more than I probably should, this idea that two completely accurate perceptions of the same company can coexist without anyone being wrong. The CEO's version is true: the client relationship is intact, the contract is valid, the delay is a timing issue on the client's side. The treasury team's version is also true: the money isn't coming, and what was a 45-day DSO six months ago is now 78 days and climbing.

The system naturally resolves this in favor of the optimistic version, because the optimistic version comes from the person with the most authority and the most external context. A reassuring number kills curiosity. The board hears the CEO's version, not because the CEO is suppressing the treasury team's version, but because the CEO genuinely doesn't know it. Information in organizations flows through filters that strip out urgency.

What starts to complicate things is when these individually correct responses happen simultaneously across multiple dimensions of the same company. One late-paying client is normal. DSO drifting up across the entire book while the CEO assures you it's temporary, that's a pattern. And each dimension gets its own slide. The deck keeps growing.

But even deck inflation is noisy compared to what's happening underneath. The cash conversion cycle moves silently and slowly enough that each individual data point looks acceptable. Trends are harder to see than levels, especially when the person responsible for explaining the number has a structural incentive to frame each quarter's number in context rather than in sequence.

And this is where the European reality starts to matter in ways that the American SaaS playbooks don't prepare you for. The fixed cost base doesn't move. The company keeps hiring because the plan says to hire, and the plan was approved when the numbers looked different, and nobody in the organization has the incentive or the authority to say "the plan is wrong, stop hiring." Saying that would mean admitting something that nobody wants to admit yet.

I want to be fair here, because it's easy to judge this from the outside. The CEO believes the optimistic version because clients are still saying positive things in meetings. The head of sales believes it because the pipeline has deals in it. The VP of engineering believes it because the product roadmap is strong. The CFO might see it earliest, but the CFO's job in most companies at this stage is to support the CEO's narrative, not to contradict it. And the board (if there is one) sees a curated version of reality every quarter, filtered through a deck that has grown from twelve pages to thirty-eight precisely because it now takes thirty pages to make the numbers tell a comfortable story. None of these people are wrong. None of them are lying. They're each responding to the information available to them, filtered through their position in the organization and their natural incentive to believe that things will work out. The system creates the blindness. Not malice, not incompetence. Architecture.

What I find genuinely uncertain (and I notice I keep circling back to this without resolving it) is whether this is a failure of governance or just a structural feature of how organizations work. The interval between when the financial signals arrive and when decisions get made is where all the damage happens. All of it is visible in the numbers, usually six to nine months before anyone frames it as a problem. But decisions lag signals because decisions require consensus, and consensus requires that enough people in the room agree that the current explanation has stopped being sufficient. And that consensus forms slowly because each person in the room has their own version of events, and each version is internally coherent.

In that interval, cash burns. Not catastrophically, not in a way that triggers anyone's alarm system, but steadily, at a rate slightly higher than the plan assumed. The plan assumed DSO would hold and it didn't. The plan assumed new hires would be productive by Q2 and they weren't. The plan assumed churn would stabilize and it accelerated slightly. Each variance is small. Each is explainable. The aggregate is a company that is burning four months more runway than anyone thinks.

The twelve months before a company needs help are not twelve months of crisis. They're twelve months of accurate explanations that never get read together.

The financial signals are always early enough. The organizational response almost never is. I'm not sure what to do with that asymmetry, except to notice that the difference between companies that make it through and companies that don't is almost never the severity of the underlying problem. It's how long the organization takes to stop explaining and start acting. And I don't know how to fix that, because the explaining is rational, every step of the way.