Written by: Ser Cappelle (CEO/CFO & Co-Founder at Peaky)
Date: June 15th, 2026
For most of my career I worked as a fractional CFO. Different companies, different industries, different stages. The pattern was always the same. Somewhere around mid-quarter, someone would walk into my office with a number. Usually the CEO. Sometimes a board member. Almost always it was a number I should have been the first to see.
"What's our actual burn this quarter? Are we still on plan?"
I would say I had to check. I would go back to the model. I would pull the latest accounting export, compare it against the forecast, and discover that something had quietly broken three or four weeks earlier. A senior hire we had brought forward. A pricing change marketing had quietly rolled out. A churn rate that had crept up a quarter point a month for two months running. The information was always there. It was sitting in HubSpot, or Stripe, or the HR system, or the bank statement. It had been visible for weeks. It just had not surfaced in finance yet.
I would walk back into the CEO's office, give them the updated number, and we would have the same conversation we had every quarter.
We should have seen this sooner.
Every company I worked with had good people. They were doing their jobs well. Sales was running their pipeline. HR was tracking the hires. Engineering was paying their vendors on time. The operational side of the business was working. The problem was the bridge between the operational side and the financial plan.
Finance refreshes monthly. Sometimes quarterly. Sometimes annually. Operations changes every day. The gap between those two paces is where surprises live. By the time finance closes the books and sees the variance, the business has already drifted weeks past whatever caused it. The cause is no longer fresh. The window to act has already closed.
What I came to realize was that this is not an exception. It is the default state of finance at every scaling company I have ever worked with. The fact that the CEO and the CFO are often looking at different numbers is not a failure of either of them. It is a structural fact about how finance has always worked.
The financial plan is a static document. Reality is not.
The cost of that gap is real, and it compounds. At a Series A company I worked with, marketing tripled spend on a campaign during a single month. The new CAC was visible in Stripe and the ad platform from week one. The forecast was rebuilt at the end of the month, by which point burn had already exceeded the plan by close to fifty thousand euros. Nobody had done anything wrong. They just had not seen it in time to react.
At a Series B company, churn was the silent killer. It crept up half a point one month, another half the next. Each individual move was within tolerance. The cumulative move was not. By the time the trend was visible in the forecast, six months of compounding had already shifted the runway model by a full quarter.
These are not horror stories. They are Tuesdays. Every CFO at a scaling company has lived some version of them. Most have lived several. That is the gap I wanted to close.
When we started building, we needed a name for the moment when the plan and the business stop telling the same story. We landed on drift. It is a word every CFO already understands. You drift off course. You drift apart. You drift behind.
The three kinds we see most often are:
Assumption drift. The plan was built on a growth rate, a hire date, a conversion number. The actual data has been telling a different story for weeks. Nobody has updated the assumption yet.
Performance drift. The forecast said one thing for the closed period. The actuals came in differently. The variance is real, and it is going to compound into next period if nothing changes.
Structure drift. A new ledger account, a new entity, a new revenue stream that the model does not even know exists yet. The business has shape that the plan has not caught up to.
Each one is silent on its own. Together, across a quarter, they are the difference between a plan that is roughly right and a plan that has quietly become fiction.
We started Peaky to make the financial plan keep up with the business. Not a better dashboard. Not another forecast template. A live system. Peaky connects the financial plan directly to the operational systems where reality changes first. The CRM where the pipeline shifts. The accounting system where vendors get paid. The HR system where headcount grows. The billing platform where churn shows up.
A set of agents watches the drivers behind the plan. When an assumption breaks, you see it. When a budget line drifts, you see it. When an operational signal moves in a direction that will eventually hit the numbers, you see it. Not next month in the close. The moment it starts.
What this means in practice is that the plan stays alive. It refreshes itself as reality changes. The CFO no longer spends four days a month rebuilding a model that is already out of date the moment it is finished. The CEO does not have to wait until the monthly board pack to know if the company is on plan. The next conversation between the two of them starts from a shared, current set of numbers.
One of our first customers put it more cleanly than I have managed to:
"Things move fast at our stage and financial visibility is usually the last thing that keeps up. We started testing Peaky to fix that. Having everything in one model instead of scattered across systems, that alone makes it worth it."
Gijs Van Laer, Founder at XFA
That is the version of finance we are trying to make standard.
When the plan keeps up with the business, the CFO's job changes. Less time goes into reconciliation, rebuilding, and reporting. More time goes into the parts of the job that actually move the business forward. Capital allocation decisions. Pricing strategy. The conversations with the CEO about where to lean in and where to pull back. The kind of strategic finance work that most CFOs got into the job to do, and most CFOs end up not having time for.
The role moves from historian to advisor. From describing what happened last month to shaping what happens next quarter. From being the last to know to being the first. That is the shift we are trying to make possible. Not just for finance teams. For the whole leadership team that depends on them.
Today we are opening Peaky to the world. We have been quietly building with our first customers for a year. They have helped us figure out what works, what does not, and what the product needs to look like to actually solve the problem. We have shipped fourteen integrations, a growing roster of AI agents working in the background, multi-entity consolidation, and a public API. We are signing customers across the Benelux and beginning a partnership with EMAsphere that opens the French market alongside the Belgian and Dutch one.
If any of the stories above sound familiar. If you have ever looked at your numbers and thought we should have seen this sooner. We would love to hear from you. You can start a trial at peaky.ai and have a live financial plan running on your own data within a day. The first drift signal usually shows up shortly after. From there, the plan stays current. So do you.
Your business moves. Your plan does not have to lag behind.
The financial infrastructure for scaling without surprises.
That is what we are building.
