How CFOs lose their Sundays (and how to get them back).
Every CFO at a scaling company has a story about a Sunday they did not get to keep.
Mine was the Sunday before a quarterly board meeting. The board pack was due Monday morning. The numbers I had pulled together Friday afternoon were already out of date because, between Friday close and Saturday lunch, the engineering team had paid a vendor I had not booked, a hire had started a week early, and a new pricing tier had begun showing revenue I had not modelled. By Sunday morning I was rebuilding the runway model in my pyjamas, with my wife and kids navigating around me in the kitchen, missing the morning I had promised them.
This is not a heroic story. It is not a story I want to tell my kids. And it is not unique to me. Every CFO I have ever talked to at a scaling company has some version of it.
This post is about why the lost Sundays happen, and what it would take to actually get them back.
Why Sundays get eaten
The Sunday before something matters tends to be when finance work compounds.
Three things make this true.
The first is that finance work expands to fill the time before a deliverable. A board pack. An investor update. A leadership review. A quarterly forecast refresh. Each of these has a Monday-morning deadline. The work to produce them is rarely linear. It expands as the team discovers what is missing, what does not reconcile, what changed since the last refresh. The weekend becomes the buffer.
The second is that operational decisions accumulate during the week. The finance team is rarely the first to know about them. By Friday evening, the team learns about decisions that happened Tuesday or Wednesday that should have been in the model already. The reconciliation gets pushed to Saturday.
The third is that the model was never built to absorb continuous change. It was built as a quarterly artifact. Updating it mid-week feels like patching a thing that was supposed to be stable. The patching gets deferred until there is no choice but to do it, which is usually Sunday.
The Sunday rebuild is not bad time management. It is a structural fact about how finance has always worked.
The costs nobody talks about
The lost Sunday has a few obvious costs.
The family time. The relationships that suffer when this happens every quarter, then every month, then almost every weekend. Most CFOs at scaling companies are also parents, partners, or both. The Sundays they do not get to keep are the Sundays their families do not get to keep either.
The cognitive cost. The work done on a Sunday afternoon, after a long week, with kids in the background, is not the work that produces the best decisions. Mistakes get made. Numbers get pulled wrong. The fix lands in the board pack and shows up in the next variance.
The brain drain cost. The most talented finance people leave the companies where lost Sundays become the default. Not because they cannot do the work, but because they can do it somewhere it does not cost them their personal lives.
These costs are real. They rarely show up in any forecast or board pack. But they shape the kind of finance team a company is able to build and keep.
Why you cannot just work smarter
If you have been a CFO long enough, you have tried every version of the obvious answers.
Better discipline. Stricter deadlines. Earlier reconciliation. A "no work after 6pm" rule that lasts about three weeks before the next board cycle blows it up.
These do not work. The reason they do not work is that the structural shape of the work has not changed. The reconciliation still has to happen. The variance still has to be explained. The board pack still has to be built. If those activities take ten hours and you only have eight in the workday, the math forces the work to expand into evenings or weekends.
The only way to actually get the Sundays back is to remove the work, not to time-manage it.
What removing the work looks like
Most of the Sunday work falls into three categories.
Reconciling actuals to forecast. The work of pulling the latest data, comparing it to the plan, and explaining the variance. This work happens because the plan and the actuals are not connected in real time.
Rebuilding the model when assumptions change. The work of finding the broken formulas, replacing hardcoded values, and validating the new totals. This work happens because the model was built as a static document, not as a live system.
Re-narrating the variance for the board pack. The work of writing the story about why the variance happened and what to do about it. This work cannot be removed entirely, but it can be made shorter when the variance is small and well-understood.
Each of these can be removed by changing the cadence. Connect the plan to the operational systems. Surface drift as it starts. Maintain the model continuously. The reconciliation work goes away because it happens automatically. The rebuild work goes away because the model is never static. The narrative work shrinks because the variances are small enough and recent enough that the story writes itself.
This is what continuous financial planning actually delivers. Not faster Sundays. Sundays you do not have to spend on the model.
What to do about it
If you recognise yourself in this post, the question worth asking is not whether you can work harder. It is whether the structure of the job still requires the weekend to absorb its overflow.
If the answer is yes, the structure is broken, and no amount of better time management will fix it.
If the answer is no, you have already made the shift, and you know what it looks like.
For the rest, the path forward is to move finance into a cadence that does not require Sundays to absorb its compounding. To make the model live instead of static. To catch drift as it starts instead of in the close.
We built Peaky to make that possible. If you want to see what it looks like on your own data, you can start a trial at peaky.ai.
The financial infrastructure for scaling without surprises. The first Sunday you do not spend on the model is the one that proves it.


