£347,000. That's the central estimate one COO put on the annual cost of keeping their current platform running - not improving it, not building anything new, just maintaining the status quo. Direct costs, lost revenue from a conversion rate half the sector average, a security exposure they'd been quietly hoping wouldn't materialise, and two senior hires who'd cited "outdated tools" in their exit interviews.
He'd known most of this intuitively for over a year. Said as much in board meetings. We can't afford to keep doing nothing. The board nodded, agreed it was a concern, and moved to the next agenda item. Three consecutive quarters, same outcome.
Then he put it on one page. Four sections. A financial comparison with three scenarios and explicit assumptions the CFO could trace to source. The board approved Phase 1 funding in the same meeting.
The argument hadn't changed. The format had.
I was in the room for that one - we'd been working with him on the business case for about six weeks by that point. And I'll be honest, even I was a bit surprised by how clean the outcome was. Phase 1 approved, Phase 2 scoped for the following quarter, no death-by-committee. The template did something his previous presentations hadn't: it gave the board a question they could actually answer.
I've watched this play out more times than I can count. A managing partner or COO walks into a board meeting with a genuinely compelling case for digital investment. They talk about risk, competitive pressure, client expectations, talent retention. They're right on every point. The board listens politely, asks a few questions, and defers the decision.
We know the cost-of-inaction argument. The board has heard it. It doesn't move them.
You're probably nodding. And honestly, I'd push back on that - the board hasn't heard the argument. They've heard a narrative. They've heard you advocate for something you believe in, which is exactly what they expect you to do, and exactly why they discount it. A managing partner arguing for digital investment is doing their job. A CFO wouldn't present a revenue forecast as a story and expect the board to act on it. They'd present numbers, assumptions, scenarios, and a net position.
That's the shift. Not from wrong to right, but from advocacy to analysis. And the difference in how boards respond is - honestly, it still surprises me sometimes.
I've written separately about how to present a digital investment to a sceptical board, and this template is the centrepiece of that conversation. But the template itself needs its own explanation, because getting the structure right is what makes the difference between a board that debates and a board that decides.
The entire thing fits on a single page. That's not a design preference - it's a constraint that forces clarity. If you can't make the case in four sections on one page, you haven't distilled it enough. Boards read summaries, not documents. The net position line at the bottom is what they'll take from the room. Everything above it is what they use to decide whether to trust it.
Here's the structure:
Section 1: Current annual cost of doing nothing
This is the estimated annual cost across five categories: direct platform costs, lost revenue, risk exposure, competitive deterioration, and talent impact. Each expressed as a range with a central estimate.
Direct platform costs are usually the easiest line to populate - pull it straight from your IT budget and maintenance contracts. Hosting, licensing, support contracts, the developer time spent patching things that shouldn't need patching. Most firms I work with can get this number in an afternoon.
Lost revenue is the most important line and, fair warning, the hardest to argue against once it's quantified. This comes from your conversion rate data, client retention figures, and commercial benchmarks. If your website converts at 1.2% and the sector benchmark is 2.8%, that gap has a monetary value. It's not theoretical. It's pipeline you're not generating. I've written a companion piece on the cost of doing nothing that walks through the estimation methodology in detail, but the short version is: find the gap, find the volume, do the maths.
Risk exposure should be probability-weighted. Not worst-case scaremongering, but an honest actuarial estimate. The average cost of a data breach is $4.45m. If your platform has known vulnerabilities with, let's say, an 8% annual probability of exploitation, that's a weighted annual exposure of roughly $356,000. Your CFO will appreciate the methodology even if they quibble with the probability estimate. That's fine. Let them adjust it. The structure survives the adjustment.
Competitive deterioration is where peer investment benchmark data earns its keep. "Firms in our peer group are investing £X annually in digital capability. We are investing £Y. The gap has widened for three consecutive years." That's not advocacy. That's a data point.
Talent impact is the one most people forget. I used to underweight it myself - it felt soft compared to the revenue and risk lines. Then I started asking HR teams to pull the exit interview data. The number of senior hires citing outdated tools as a reason for leaving, or the incremental cost of recruiting into a firm with a reputation for legacy infrastructure - it adds up faster than you'd expect. It doesn't need to be precise to the penny. It needs to be defensible.
Each of these lines should be completable with imperfect data. You don't need a two-month audit to populate this template. You need reasonable estimates from available sources, with the methodology stated clearly. A CFO doesn't expect omniscience. They expect intellectual honesty about what you know, what you've estimated, and how.
Section 2: Projected three-year cost if we continue as we are
This is the three-year compound of the annual estimate. Not simply multiplied by three - that would assume inaction costs stay flat, and they don't. Maintenance costs escalate. The conversion gap widens as competitors improve. Security risk compounds as platforms age. Talent costs increase as expectations shift.
The compounding effect is what changes the psychology. An annual cost of £347,000 feels manageable. We'll get to it next year. A three-year projection of £1.2m - accounting for escalation - does not feel manageable. It feels like what it is: a material financial exposure the board is choosing to accept.
Section 3: Cost of the proposed investment
Phase 1 cost as a specific figure. Not a range - a number the board can approve or reject. Subsequent phases indicated as ranges, clearly labelled as indicative.
Present this on the same line as the three-year inaction cost. The visual proximity forces the comparison. You're not asking the board to approve spending. You're asking them to compare two financial positions.
One critical mistake to avoid here: don't understate the cost. Implementation costs must include internal resource, not just external fees. If the project needs your Head of Marketing for 30% of their time over four months and your IT lead for 20%, that's a cost. A board that approves an investment and then discovers it requires three months of senior management time they weren't told about - that's a trust problem. And trust problems contaminate every subsequent request. I've written about how to propose a phased digital investment separately, and the Phase 1 costing methodology there maps directly into this section.
Section 4: Net position
The difference between the three-year cost of inaction and the cost of investment, expressed across three scenarios: conservative, central, and optimistic.
This is the line the board will anchor on. Everything above it is evidence. This line is the verdict.
And here's something I learned the hard way: the board will apply the conservative scenario to their own assessment. Always. They'll read all three, but they'll mentally commit to the most cautious one. So make damn sure the conservative scenario still makes a compelling case. If the net position is positive only in the optimistic scenario, you haven't got a board paper - you've got a wish list.
Position the template as a financial comparison, not a business case. Subtle difference, massive impact. The board has seen business cases. They know what they look like. They know the person presenting one is advocating for something. A financial comparison is a more neutral format - it asks for a judgement between two positions rather than an approval of one.
Present your assumptions explicitly alongside the figures. Every number should be traceable to a source and a methodology. Not in a 40-page appendix - right there on the page, in a smaller font if necessary. A CFO who can trace every figure back to its origin is persuaded by the numbers. A CFO who can't is suspicious of them. And a suspicious CFO will find the holes, publicly, in the meeting. I've seen it happen. It's not fun.
Lead with the three-year compounding impact. The annual cost may feel tolerable. The three-year figure typically does not. That's not manipulation - it's accuracy. Inaction costs compound. Presenting only the annual figure actually understates the problem.
One more thing: account for implementation time in your three-year comparison. If Phase 1 takes six months, you don't get twelve months of benefit in year one. You get six. A board that spots you've ignored this will question everything else on the page. Rightly so.
Three recurring errors. Any one of them can sink an otherwise solid paper.
Overstating the revenue benefit. If your lost revenue estimate includes a line like "increased brand perception leading to higher win rates" without a specific mechanism connecting the investment to the outcome, it will get challenged. And if one line gets successfully challenged, the board's confidence in every other line drops. Connect every revenue figure to a specific, traceable mechanism: a conversion rate improvement of X% based on benchmark Y, a specific client relationship at risk, a measurable reduction in proposal turnaround time. The more specific, the harder to dismiss.
Understating implementation costs. I mentioned this already but it bears repeating. External fees are the easy part. Internal time, opportunity cost, the distraction factor of running a significant project alongside business as usual - these are real costs and the board knows it. Include them. If anything, round up slightly. A board that feels you've been conservative with costs is more inclined to trust your revenue projections.
Pretending returns start on day one. They don't. A six-month implementation phase means your three-year benefit window is actually thirty months. Adjust accordingly. This feels like it weakens the case, but it actually strengthens it - because it demonstrates rigour, and rigour is what moves boards from "interesting" to "approved."
Boards don't assess financial comparisons for absolute accuracy. They test for internal consistency. Does the methodology make sense? Are the assumptions plausible? Do the numbers add up? Is there anything that feels like it's been inflated to make the case?
That's a different standard than "is every number precisely correct." And it's a more achievable one. You don't need perfect data. You need a defensible methodology, honest assumptions, and internal coherence.
The other thing: if your CFO sees the template before the board meeting, their questions will shape the conversation. That's not a risk - it's an opportunity. Send it to them 48 hours ahead. Let them poke at it. Adjust where they're right. Explain where you disagree. A CFO who's already stress-tested the numbers and found them solid becomes your strongest ally in the room. A CFO who's seeing it for the first time becomes your most dangerous questioner.
I've turned this structure into a one-page document you can actually use - formatted for printing, bringing to a board meeting, or sharing digitally ahead of one. It includes all four sections, the three-scenario net position comparison, and guidance notes for populating each line.
Download the one-page board briefing template here - formatted for printing and bringing to a board meeting, with guidance notes for populating each section.
If you want the full methodology behind the cost categories - particularly the lost revenue and risk exposure lines - there's a companion piece on the cost of doing nothing that walks through the complete framework this template summarises.
The template isn't a replacement for the board conversation. It's the anchor for it. But it changes the nature of that conversation from "should we invest in digital?" to "which financial position do we prefer?" And in my experience, that's a question boards are considerably more comfortable answering.