Here's a number I want you to sit with: £0.
That's what most firms write down as the cost of their last deferred digital investment. Not because they analysed the alternative and concluded it was free. Because nobody analysed the alternative at all.
I've sat in enough budget meetings to know how this goes. A digital investment proposal gets picked apart line by line - implementation cost, licence fees, internal resource, risk of overrun. Fair enough. That's due diligence. But then the comparison option - keep things as they are - gets assessed with all the rigour of a shrug. We'll revisit it next year. And that's it. The "do nothing" option gets approved unanimously, without anyone ever costing it.
This is the asymmetry that kills good investment decisions. The proposal gets stress-tested. The alternative doesn't. And the CFO or managing partner who quite rightly demands a credible ROI on the investment is, without realising it, applying zero financial scrutiny to the option they've actually chosen.
We don't have the budget for this. The ROI isn't clear enough.
I hear this constantly. And sometimes it's the right call - genuinely. But here's my challenge: if the ROI on the investment isn't clear enough, what's the ROI on doing nothing? Have you actually worked that out? Because "do nothing" has a cost profile too. It's just that nobody's ever put it on a spreadsheet.
A few years back, I was working with a professional services firm that had deferred a platform modernisation decision three times in four years. Each time, the board looked at the investment cost and decided it wasn't the right moment. Reasonable people, reasonable caution.
What nobody had calculated - and I'll be honest, I hadn't pushed hard enough on this early enough - was that the firm had been paying what I started calling a "platform tax" the whole time. Escalating maintenance costs. Developer hours spent patching rather than building. A content team that had quietly given up trying to do anything interesting because every change required a support ticket and a two-week wait.
When we finally sat down and added it all up, the cumulative cost of those four years of inaction was higher than the investment they'd been deferring. Not dramatically higher. But higher. The room went quiet for a moment. Then the CFO said something I've thought about since: "Why has nobody shown me this before?"
Good question. The answer, I think, is that the costs of inaction are spread across budget lines, absorbed into overhead, and attributed to everything except the actual cause. They don't show up as a line item called "cost of not investing." They show up as "IT maintenance," "recruitment," "lost pitch," "staff turnover" - individually unremarkable, collectively significant.
The point isn't that inaction is always more expensive. Sometimes it isn't. The point is that you can't know until you've done the maths on both sides.
Through working with mid-market B2B service firms over the past two decades, I've found that the costs of inaction cluster into five areas. Not every area will hit your firm equally - a financial services business might be heavily exposed on risk, while a consulting firm might be bleeding revenue through a poor digital experience. But they're all worth estimating, even roughly.
Direct platform costs are the most tangible and the easiest to calculate. Maintenance contracts, support costs, hosting, and - critically - the developer hours spent keeping an ageing system operational rather than building new capability. Research suggests organisations running legacy platforms spend somewhere between 60 and 80% of their IT budget on maintenance rather than innovation. That's not a technology problem. That's a financial drag that compounds every year you don't address it.
To estimate this for your firm: pull your last 12 months of platform-related invoices and your development team's time logs. Separate "keeping the lights on" from "building something new." The ratio will probably depress you.
Lost revenue is harder to pin down but often the largest number. It covers the enquiries not converted because of a poor digital experience, the clients retained at lower margins because their portal is frustrating, and the competitive pitches lost before the meeting because your digital presence didn't pass the qualification round.
I remember a managing partner - this was maybe three years ago, a mid-sized law firm - who told me, somewhat sheepishly, that three prospects in a single quarter had mentioned the firm's website in the "why did you choose someone else" conversation. He'd collected these comments separately, filed them under "feedback," and never added them up. When we estimated the value of those three lost opportunities, the number was larger than the entire proposed website investment. He sat back in his chair and said nothing for about ten seconds. I've seen that reaction more than once.
You know your average conversion rate. You know your average contract value. If your website converts at 1% when the sector benchmark is 3%, you can calculate what that gap costs you in pipeline terms. It won't be precise - but it'll be defensible.
Risk exposure is where CFOs in regulated industries should pay closest attention. This covers the probability-weighted expected cost of a security incident, a compliance failure, or a business continuity event attributable to ageing infrastructure. IBM's annual research puts the average cost of a data breach at $4.45 million globally. Your firm's exposure will be different - but even a 5% annual probability of a significant incident on an end-of-life platform gives you a meaningful expected cost figure. If your platform vendor has announced end-of-life dates, this number gets more urgent every quarter.
Competitive deterioration is the squishiest category, and I'll be honest about that. But "hard to measure precisely" doesn't mean "zero." The question is: at what rate is your firm's digital capability falling behind your competitors, and what effect is that having on your win rate?
Maybe it's a percentage point or two on win rate each year. Compound that over three to five years and it starts to look like a strategic problem, not a cosmetic one. Talk to your business development team. Ask them how often the website or client portal comes up in competitive situations. The answers are usually more revealing than any benchmark data.
Talent impact is the one that surprises people most. Technical talent won't join firms running ancient platforms if they can work somewhere modern. And your non-technical staff - the marketing team, the content editors, the client-facing teams - are quietly frustrated by systems that make simple tasks unnecessarily difficult. The cost shows up in recruitment premiums, longer hiring cycles, and turnover that gets attributed to "culture" when the exit interviews, if you read between the lines, are really saying "your tools are rubbish."
The framework doesn't require precise figures for every category. It requires defensible estimates with explicit assumptions.
For each of the five areas, produce three estimates: a low (conservative assumptions), a central (your best judgment), and a high (reasonable worst case). And - this is the bit people skip - write down the assumption behind each number. Right next to it, not in a footnote. "Low estimate: £40k, assuming current conversion rate is within 0.5% of sector average" is infinitely more useful than just "Low estimate: £40k." The assumption is what makes the number debatable rather than dismissible.
Add up the central estimates. Multiply by one, three, and five years - remembering that several of these costs compound rather than simply repeat. That's your cost-of-inaction figure.
Now put it next to the investment cost. Not as advocacy. As comparison.
To make this concrete: a 200-person consulting firm considering a £150k website rebuild might find direct platform costs running at £35k a year, lost revenue somewhere between £80k and £120k, risk exposure around £15k, competitive deterioration perhaps £30-50k, and talent impact around £20k. Central estimate for inaction: roughly £200k a year. Over three years, that's £600k against a £150k investment. A 400-person law firm looking at a £300k portal rebuild might find the annual inaction cost running closer to £380k - meaning the investment pays back in under a year on central assumptions. I've seen this pattern enough times that it no longer surprises me. What surprises me is how rarely anyone runs the numbers before deciding to wait.
That said - and I mean this - I've also seen cases where the honest comparison favours waiting. A firm with a recently updated platform and a modest improvement proposal might genuinely find that the inaction cost is lower than the investment cost over a three-year horizon. The framework doesn't exist to manufacture a predetermined answer. It exists to make sure you're comparing like with like.
When you take this to the board, structure it as a genuine comparison. Two columns. Left: cost of the proposed investment - implementation, ongoing licence, internal resource, risk of overrun. Right: cost of the alternative, the five categories above with best available estimates. Bottom of the page: how the cost trajectories diverge over three and five years.
The investment cost is front-loaded and largely fixed. The inaction cost is ongoing and typically escalating. Over three years, the comparison almost always looks different than it does over one.
The typical dynamic in a budget meeting without this framing is: someone proposes an investment, the CFO asks for the ROI, the proposer struggles to make it compelling enough, and the decision gets deferred. The implicit comparison is "spend this money" versus "spend nothing." And "spend nothing" always wins that fight, because it sounds free.
When you reframe it as "spend £150k on the investment" versus "spend £200k a year on inaction," the conversation shifts. The CFO starts interrogating assumptions on both sides. The managing partner asks which cost categories are most material. You end up having a strategic conversation about trade-offs rather than a defensive conversation about whether the investment is "worth it."
That's the real value. Not the spreadsheet. The conversation.
The next time someone in your firm says "we don't have the budget," the right response isn't to argue harder for the investment. It's to ask: "Have we costed the alternative?"
For the underlying data on what legacy platforms actually cost organisations over time, both The Replatform Reckoning and The Customer Experience Dividend go deeper into the evidence. Both are on our site. And if you want a template that covers all five cost categories and produces a board-ready comparison table, the cost-of-inaction calculator is available to download - designed to be completed by an operations leader or managing partner with access to basic financial information, not by a data science team.
The whole point is that this analysis should be achievable. Not academic.