I've sat in a board meeting and watched a managing partner spend forty-five minutes presenting a genuinely strong case for digital investment - well-researched, commercially grounded, clearly argued - and walk out with nothing approved. Three board members had checked their phones. Two had raised objections nobody had anticipated. The whole thing ended with "let's take this offline and come back with more detail."
He came to me afterwards, genuinely baffled. "What did I do wrong?"
The answer wasn't the quality of the investment. It was the format of the conversation. And that's a fixable problem.
McKinsey put a number on it in 2024: 88% of large digital transformations fail to achieve their original ambitions. What that stat doesn't capture is how many of those failures were baked in before a single line of code was written - in the board meeting where the investment was approved, or half-approved, or watered down and hedged with so many caveats that the programme was structurally underfunded from day one.
This piece is designed to be practically useful. Not in a "here are some principles to think about" way, but in a "you have a board meeting next Tuesday and you need to be ready" way.
I've been presenting to our board for years. I know how to run a board conversation.
I'm sure you do. But presenting quarterly results and asking a board to approve a significant digital investment are two completely different things. One is reporting. The other is persuasion. And the mechanics of persuasion in a boardroom are more specific - and more predictable - than most people realise.
The single most effective reframe I've seen in board conversations about digital investment: don't open with the cost of the investment. Open with the cost of inaction.
Every board has been asked to approve investments before. They've developed antibodies to it. The moment you put a number on a slide, the conversation becomes about that number - whether it's too high, whether it can be phased, whether there's a cheaper option. You've lost control of the frame before you've established the stakes.
Instead, spend the first two minutes on what happens if the board defers for another twelve months. Be specific. Which competitor has already moved? Which client expectation is going unmet? What's the operational cost that's compounding month on month? The principle is simple: the board needs to feel the weight of not deciding before they're asked to decide.
Then - and only then - make the ask. And make it specific and phased. Not "we'd like approval for a £500k digital transformation programme." Something like: "We'd like approval for Phase 1 - an £80k pilot over 90 days - with a gate review before any further commitment is made."
The psychology of this matters. A board that feels it's being asked to approve a contained, evidence-based next step responds very differently from one that feels it's being asked to write a blank cheque. I've seen the same investment get rejected as a full programme and approved as a phased pilot in the space of three weeks. Same board. Same people. Different framing.
There are five objections that come up in almost every board conversation about digital investment. The specific language varies, but the shape is remarkably consistent. If you prepare a specific response for each of these before you walk into the room, you're not hoping to be persuasive - you're prepared to be.
"We can't afford it."
The instinct is to counter with "we can't afford not to." Please don't. That phrase has been used so many times it's become meaningless. Board members hear it and immediately discount whatever comes next.
Do the maths in advance instead. Take the cost of the proposed Phase 1 - let's say it's £80k over 90 days - and put it alongside what the firm is currently spending to maintain the status quo. Legacy platform maintenance, manual workarounds, the revenue leaking through a website that converts at 0.3% instead of 2%. When a board member can see that the firm is already spending £120k a year just keeping an ageing platform alive, an £80k pilot to start replacing it looks different.
And the phased structure matters here. You're not asking for the full programme budget. You're asking for the first step, with a gate review before anything else is committed. That's a fundamentally different financial conversation.
"We tried this before."
This is often the hardest objection in the room, and it deserves serious treatment. The board member raising it isn't being difficult - they're being rational. They remember the last time the firm invested in a digital initiative, and they remember it didn't deliver what was promised.
Don't be defensive. And don't pretend the previous attempt didn't happen. I was working with a professional services firm last year where the COO told me, quite bluntly, that the board would never approve another website project because the last one had been "a disaster." When we unpacked what actually went wrong, it came down to three things: the scope was never properly defined, there was no governance framework, and the firm had signed up for a "done for you" delivery model that left the internal team with nothing when the agency moved on.
So the response wasn't "this time will be different" - it was "here are the three specific things that went wrong, here's which of those were on our side, and here's specifically what we'd do differently in governance, scope control, and delivery model." That's a conversation a board can engage with. Vague reassurance isn't.
"It's not a priority right now."
This one's often code for "I don't feel the urgency." The response isn't to argue that digital should be a priority in the abstract. Make the cost of deferral concrete and specific.
Which competitor has replatformed in the last eighteen months? Which client has mentioned - even casually - that your portal or website feels dated? What's the monthly cost of the manual processes your team runs because the current platform can't automate them? I've seen boards shift on this objection when a managing partner puts up a single slide showing how firms of similar size and sector are investing in digital - not as a guilt trip, but as context.
The priority argument becomes much easier when you can say: "Three of our five closest competitors have invested in their digital platforms in the last two years. Two of them are winning pitches we're not being invited to. I'm not suggesting we panic, but twelve more months of deferral has a cost we should quantify."
"Show me the ROI."
Fair question. Terrible when answered with a single headline number.
Present three scenarios instead: conservative, central, and optimistic. State the assumptions explicitly for each one. The conservative case might show the investment breaking even within eighteen months based purely on operational cost savings. The central case adds revenue uplift from improved conversion. The optimistic case includes competitive positioning and talent benefits.
A single ROI number invites the board to argue about whether it's realistic. Three scenarios with visible assumptions invite the board to discuss which scenario they think is most likely - and that's a fundamentally different conversation. You've moved from defending a number to facilitating a judgement.
A three-year total cost of ownership comparison is useful here too. Legacy platform maintenance running at £3-5m over three years versus £2-3m for a modern platform investment - with significantly more capability at the end of it - is a comparison that tends to land.
"Can't we just fix what we have?"
Sometimes the honest answer is yes. If the current platform is fundamentally sound and the problems are about content, configuration, or process, incremental improvement might genuinely be the right path. I'd be lying if I said every firm needs a replatform.
But more often, "can't we just fix it" is a deferral strategy dressed up as pragmatism. Answer it specifically: what is the current platform unable to do that the proposed investment addresses? Not "it's old" - that's not compelling. Something like: "Our current CMS cannot support the personalised content delivery our clients expect, and it's architecturally incompatible with the AI capabilities we'll need in the next two years. Patching it will cost roughly £X per year with diminishing returns, while replacing the foundation in Phase 1 costs £Y with compounding returns."
Be honest. If incremental fixing is a viable alternative, say so. Boards respect honesty more than salesmanship.
Not a slide deck. Not a 40-page business case. A one-page summary.
I know that sounds almost offensively simple. But the discipline of getting your entire argument onto a single page is exactly what forces you to know what you're actually asking for. If you can't fit it on one page, you haven't clarified your thinking enough.
Three sections. That's it.
The first is the commercial case for acting: cost of inaction, peer position, competitive consequence. Two or three sentences, backed by the specific data you've prepared.
The second is the proposed Phase 1: scope, cost, timeline, success criteria, and governance. Be specific. "A 90-day pilot to rebuild the enquiry-to-onboarding journey, costing £80k, with weekly progress updates and a formal gate review at day 90 before any further commitment."
The third is the decision being asked for. Not "we'd like the board's support." Something like: "Approve Phase 1 budget of £80k to begin within 30 days, with a gate review at 90 days before any further commitment is requested."
That one-page summary is your centrepiece. Everything else - the three-scenario ROI, the cost-of-inaction analysis, the peer benchmarking data - lives in a pack that's available if anyone wants to go deeper. But the conversation starts and stays with the one page.
Leading with technology. The moment you say "headless CMS" or "composable architecture" or "API integration layer" in a board meeting, you've lost half the room. The board's frame is commercial risk and return. Translate everything into commercial consequences. "A platform that lets the marketing team publish content in hours instead of weeks" means something to a board. "A decoupled frontend with a headless CMS backend" means nothing.
Asking for everything at once. Even if the full programme is the right answer - and it often is - asking for it all in one go is structurally less likely to succeed than asking for Phase 1 with a gate. The board needs to develop confidence. Give them a way to say yes to something small before asking them to say yes to something large.
Assuming the data speaks for itself. It doesn't. Not in a boardroom. Data needs to be contextualised, narrated, and connected to something the board cares about. A stat about conversion rates means nothing until it's connected to "that's roughly £400k in revenue we're not capturing." Do that translation work before you walk in.
Board dynamics are political. Members have histories, alliances, and prior positions they've taken publicly. The FD who blocked the last technology investment has reputational skin in the game. The board member who championed the previous failed initiative might be defensive. The non-exec who joined six months ago has no context.
Nobody can script their way through that. But the managing partners I've seen succeed in these conversations are the ones who've had the pre-meeting conversations. They've spoken to the FD privately before the board meeting. They've briefed the chair. They've identified who's likely to be supportive and who's likely to object, and they've tailored their preparation accordingly.
The one-page summary and the five objection responses aren't a substitute for that political groundwork. They're the foundation that makes the political conversations productive instead of improvised.
If you've got a board conversation coming up, here's what I'd suggest. Print the one-page summary. Write out your specific response to each of the five objections - not generic principles, but the actual words you'd say in your boardroom, with your numbers, your competitors, your context. Rehearse the three-move opening: cost of inaction, commercial stakes, phased ask.
Then walk in without a slide deck.
If you want the five objection responses as a formatted one-page script - with evidence placeholders for each response - you can download the board presentation script template here.
It won't guarantee a yes. But it will guarantee that the conversation is one you've prepared for rather than one you're improvising through. In my experience, that's usually the difference.