Money Without Magic

I've sat in a lot of rooms where somebody stands up and announces a number that isn't quite true. Not dishonestly, usually. Nobody sets out to mislead anyone. It's more that a projected saving feels like the natural language of business, so people reach for it instinctively, even when the evidence underneath it is thinner than the confidence with which it's delivered. This tool will save two hundred thousand pounds a year. This will free up fifteen percent of a manager's time. I've said things like that myself, earlier in my career, and I cringe slightly now thinking about how little was actually behind some of those figures.

The trouble with invented savings is that they're brittle in a very specific way. They sound wonderful in the room where they're first presented, and then somebody, somewhere down the line, tries to actually bank the saving and can't quite find it. That gap between the promise and the reality doesn't just embarrass the person who made the claim. It poisons the credibility of every real number that comes after it.

So I've tried, not always successfully, to build a different habit into how we talk about value at pilot stage, which is honestly the stage where the temptation to oversell is strongest, because there's so little hard evidence yet and so much hope.

Rather than reaching for a saving, I describe what manual behaviour actually disappears because of what we've built. Rather than promising a return, I describe what decision moves earlier in somebody's day than it used to. Rather than claiming efficiency, I describe what becomes reusable for the next thing we build after this one.

That sounds like a small linguistic difference, and I suppose technically it is. But it changes the entire conversation with a finance director. Instead of saying a tool saves labour hours, which invites an immediate and entirely fair question about exactly which hours and how you know, you can say something like, this removes the need for a weekly regional review of deployment variance, because the exceptions now surface automatically before anyone needs to go looking for them. That's not a projection. It's a description of something that's already true, and it's very hard to argue with something that's already true.

I've learned to save the numbers for the moments when there's a real baseline behind them, a measured before and a measured after, rather than an estimate dressed up to look like evidence. Numbers earned that way carry an entirely different weight in the room. People lean forward slightly, because they can tell the difference, even if they couldn't quite articulate what it was that changed in how you were speaking.

What I believe, more firmly the longer I do this, is that credibility compounds faster than any spreadsheet projection ever will. A leader who consistently underclaims and then delivers a little more than promised earns a kind of trust that no amount of confident forecasting can buy. And trust, it turns out, is the actual currency that lets you keep building the next thing, and the thing after that, without having to prove yourself all over again every time you walk back into the room.

This has made me much more comfortable saying 'I don't know yet' in rooms where people would prefer a number. There is a strange pressure in business to turn uncertainty into a percentage as quickly as possible. Sometimes the most credible answer is that I have seen enough to justify the next test but not enough to claim the saving. That can feel less impressive in the moment. It ages much better.

When the evidence does arrive, it tends to be stronger because it belongs to the operation rather than the presentation. A manual step has genuinely disappeared. A supplier invoice is genuinely lower. A store has genuinely changed what it does. Those are the numbers I want. The discipline should make us ambitious about value and conservative about pretending we have already created it.