New

Peaky raised €1.1M, led by JK Invest

→

All articles

Company

/

Written by Peaky

The hidden cost of unnoticed drift.

€410K
Cost of twelve weeks of unnoticed drift
€410K
Cost of twelve weeks of unnoticed drift

Drift is expensive. Most CFOs already know this in a vague, intuitive way. What is less obvious is where exactly the cost lives, and how to put a number on it.

This post is about the math.

At a Series A or Series B company, a single unnoticed drift typically costs between fifty thousand and one hundred thousand euros. That number is not made up. It comes from looking at what actually happens when a finance team finds out about something three or four weeks late. The breakdown is worth understanding, because once you can put a number on the cost, the decision to fix the cadence becomes much easier.

Where the cost lives

The cost of drift is not the drift itself. The change in the underlying business often is not catastrophic on its own. A campaign that doubles spend is not a disaster. A pricing change that takes a quarter to flow through the model is not a disaster. A senior hire that gets pulled forward by six weeks is not a disaster.

The cost is the delay between drift starting and finance noticing.

That delay produces three distinct expenses.

The decision cost. If finance had known about the change in week one, the team would have made a different decision in week two. Maybe a smaller media buy. Maybe a slower second hire. Maybe a pricing tier rolled out with a different timing. Those week-two decisions never happen, because finance has not seen the data yet. The decision that would have been cheap to make in week two is now a more expensive decision to make in week five.

The reaction cost. Once the drift becomes visible in the close, the response is rarely measured. Hiring freezes. Marketing budget pullbacks. Pricing experiments that get killed before they have a chance. These are not bad decisions. They are over-corrections forced by the fact that the team had to react to four weeks of compounding rather than four days of it.

The rebuild cost. Every time drift surfaces in the close, finance has to rebuild the model. Reconcile the actuals. Update the assumptions. Recompute the downstream impact. Rewrite the board narrative. This is four days a month of finance time that should have gone into strategic work.

Add them together and you get something close to the fifty-to-one-hundred-thousand-euro number. Not because any one of those costs is huge. Because together, on top of the underlying business move, they multiply.

The compounding problem

The hidden cost is not just that drift is expensive. It is that drift compounds while it is unnoticed.

A growth assumption that drifts by one percentage point in January is small. The same drift, compounded across twelve months, can shift annual revenue by enough to require a new fundraise timeline. A churn rate that creeps up by half a point per month sounds harmless. Over a year, it can shift net revenue retention by ten points and the runway model by an entire quarter.

The shape of the cost is exponential. Each week of unnoticed drift produces a slightly larger gap. Each week of larger gap produces a slightly larger reaction when finance finally sees it. By the time you are explaining the variance to the board, the cost has compounded into something that would have been a routine adjustment if it had been caught in week one.

This is why fast detection matters more than perfect detection. A drift you catch in week one is a small line item. A drift you catch in week six is a board conversation.

A worked example

Let’s do the math on a single mid-size drift.

Imagine a Series B company with twenty-five employees, two million euros in ARR, and a forecasted annual burn of two and a half million euros. The plan assumed a churn rate of 1.5% monthly. The actual churn rate, starting in March, drifts to 2.7%.

If finance catches this in April, the conversation is small. CS gets briefed, a retention play gets prioritised, the next two months stabilise. The net impact on annual ARR is maybe sixty thousand euros, none of which is catastrophic.

If finance catches this in July, the math is different. Five months of compounding churn at 2.7% instead of 1.5% means the company has lost roughly one hundred and eighty thousand euros in annualised ARR that it was supposed to have. The runway model is off by a full quarter. The fundraise conversation that was supposed to happen at month twelve is now happening at month nine. The CS team gets a six-month-old problem instead of a two-month-old one.

Same drift. Same business. Five months of difference between when finance noticed. One hundred and twenty thousand euros of additional cost, plus an entire fundraise timeline pulled forward, plus three Sundays of model rebuilding that did not need to happen.

This is what compounding drift looks like in numbers.

Why most companies accept this cost

The cost is hidden because nobody assigns it a line item. There is no expense category called “drift compounded between when it started and when we noticed”. There is no row in the variance analysis called “decisions we would have made differently if we had known”.

The cost lives in opportunity cost terms, which is the easiest kind of cost to ignore. The team that lost five months of runway visibility does not show that as a P&L impact. They show it as a fundraise timeline change, or a hiring slowdown, or a quarter that did not hit plan. The drift is the cause. The visible cost is the symptom.

This is why most CFOs vaguely know drift is expensive but cannot put a number on it. The expense never gets booked.

How to quantify your own cost of drift

If you want to know what unnoticed drift is costing your business specifically, four questions will get you close.

How often does your forecast get refreshed against actuals. Weekly is rare. Monthly is normal. Quarterly is too slow. The longer the cadence, the higher the cost.

How many days does it take to find out about a meaningful operational change. From the moment the change happens to the moment it shows up in finance’s view. If the answer is more than five days, you are paying drift compounding.

How many drivers in your plan are hardcoded versus pulled from operational systems. Hardcoded drivers do not drift in the model. They drift in reality, while the model continues to show them as static. The more hardcoded, the more compounding cost is hiding in plain sight.

How often does the team rebuild the model because actuals diverged from forecast. Quarterly is normal. Monthly is suspicious. Every close is a sign that the cost is now substantial.

The answers do not give you a perfect number. They give you an order of magnitude. For most Series A to C companies, the cost lives somewhere between fifty thousand and three hundred thousand euros a year. It is rarely less. It is often more.

What to do about it

You can keep paying the cost. Most companies do. The cost is invisible enough that nobody escalates it, and the work to fix it feels like a project no one wants to own.

Or you can change the cadence. Move finance from a monthly refresh to a continuous one. Connect the plan to the systems where reality changes. Catch drift in week one instead of month two.

That is the choice continuous financial planning offers, and it is what we built Peaky to make possible.

You can see what catching drift in week one looks like on your own data at peaky.ai. Most teams have their first drift signal surfaced within a day of connecting their first integration.

The financial infrastructure for scaling without surprises.

Previous

How to spot assumption drift early.

Next

Never the last to know.

Keep exploring

Getting started

From your Excel plan to a live plan in a day.

Integrations

The systems Peaky connects to, and what each one brings in.

The Forecast Audit

Nine questions to find out whether your forecast is a report or a tool.

Peaky app icon

Sync or sink.

Ask AI for a summary of this website