The Sunday Afternoon CFO

Sunday, 3pm

You're not working. But you're not not working. There's a board meeting on Tuesday and you know the numbers aren't quite where they need to be. Not wrong, exactly. But not the kind of numbers you'd stake your reputation on without checking one more time. So you open the laptop.

You tell yourself it's 20 minutes. Forty-five minutes later, you've found a variance that needs explaining and you're drafting a note for your team to pick up first thing Monday. Your partner asks if everything's alright. "Fine. Just checking something."

Monday

Someone from the commercial team asks for a scenario. "What happens to margin if we lose the Henderson contract and raw materials go up 8%?" Reasonable question. You should be able to answer it in an hour. You can't, because your model doesn't work that way. You promise it by Wednesday, knowing it'll take longer.

Meanwhile, your team is still reconciling last month's actuals. It's the 8th working day. The close should have been done by day 5.

Tuesday

Board meeting. You answer most questions confidently. The numbers are solid. Then the chair asks something you weren't expecting: "Can you show us the impact if we accelerate the European expansion by six months?" You say "absolutely, we'll model that and come back to you." Calm. Professional. Inside, you're calculating how many hours that answer will take your team, on top of everything else they're carrying.

"Can you get back to us?" You've said that phrase more times than you'd like to count.

Wednesday

Your best analyst mentions, in passing, that a recruiter reached out. They don't say they're interested. They don't need to. You know why the recruiter called. Your analyst is good. They're also spending 70% of their time on data consolidation. They didn't get a master's degree for that.

You make a mental note to have a retention conversation. But you know the real problem isn't their pay or their title. It's the work itself.

Thursday

Month-end process kicks off for real. You already know it'll take too long. Same issues as last month: data arrives late from two subsidiaries, one team submits in the wrong format, someone has to manually adjust the intercompany eliminations because the model doesn't handle the new entity properly.

Your team handles it. They always do. That's the problem. Because they handle it, nobody above you sees the cost.

Friday

You look at the planning platform landscape for the twentieth time this year. You read a comparison article. You look at pricing. You think about the business case you'd need to make, the disruption of implementation, the risk that it goes wrong and your name is on it.

You close the browser. Maybe next quarter.

This isn't failure

If any of this sounds familiar, you're not failing. You're operating at the limits of tools that weren't designed for what you're being asked to do. Every workaround your team has built is evidence of their competence, not their inadequacy.

The question isn't whether you need to change. You already know the answer to that. The question is whether the cost of changing feels less dangerous than the cost of another year like this one.

A different kind of answer

The Bolt Blueprint exists to answer that question. It takes two weeks, costs £5,000, and tells you whether the investment makes sense for your specific situation. Sometimes it tells you not to invest at all. That's the point.

It's not a sales exercise. It's the document that turns "I think we need to do something" into "here's exactly what we need to do, what it costs, and what happens if we don't."