In my experience, most large-scale digital investment proposals get deferred at least once before approval. Not rejected outright - deferred. Sent back for "more detail." Kicked to the next quarter. Asked to be "re-scoped."
The proposal sits in limbo. The problem it was meant to solve gets worse. And six months later, someone dusts it off and tries again, usually with a bigger number attached because the original estimate is now out of date.
I've watched this cycle play out dozens of times. And the thing that strikes me every time is that the underlying investment case is usually sound. The technology choice is reasonable. The team presenting it has done their homework. The problem is almost never the quality of the case. It's the structure of the ask.
Think about what a £500k or £1m digital investment proposal actually asks a board to do. It asks them to assess a projection of what will happen over two to three years, based on assumptions about technology adoption, competitive response, organisational capability, market conditions, and about fifteen other variables that nobody in the room can verify.
That's not an approval decision. That's a bet. And boards - particularly in professional services, where partners are personally exposed to financial risk - are structurally allergic to bets.
The board doesn't have the patience for a phased approach. They want to know the total cost and timeline upfront.
I hear this constantly. And I understand why you believe it - boards do ask for the total number. But here's what I've learned: they ask for the total number because that's the format you've given them. You've presented a single, monolithic programme with a single price tag, so their only option is to say yes or no to the whole thing. Most of the time, they say "not yet," which is just a polite no.
The irony is that boards are actually very comfortable with phased commitments. They make them all the time. Every lateral hire with a probation period is a phased commitment. Every new office lease with a break clause is a phased commitment. Every pilot of a new service line is a phased commitment. The concept isn't foreign to them. You're just not presenting your digital investment in that language.
I was in a board meeting a while back - professional services firm, about 200 people, good business - where the partners had been sitting on a website and CRM proposal for nearly a year. The number was £480k. Every quarter it came up. Every quarter it got deferred. When we finally got in the room, it took about twenty minutes to see what was happening: the proposal was structured as a single programme with a single approval point, and the board couldn't get comfortable with the full number. We restructured it on the spot. Phase 1 became a 90-day sprint to fix the enquiry-to-onboarding handoff - the bit that was actively losing them money - at around £80k. They approved it before lunch. Phase 2 followed three months later without a single difficult conversation.
The structure that changes the approval dynamic looks like this: a small, specific, measurable Phase 1 - typically 90 days - whose results either justify or don't justify proceeding to Phase 2.
Phase 1 is small. Not trivially small - the smallest investment that can produce credible evidence. One use case. One team. One clearly bounded problem. If you're proposing an AI implementation, it's not "explore what AI can do for our business." It's "use AI to reduce first-draft document review time for the due diligence team." If you're proposing a website overhaul, it's not "redesign the entire digital presence." It's "rebuild the three highest-traffic service pages with proper conversion paths and measure the impact on enquiry volume over 12 weeks."
Phase 1 is specific. Clear boundaries. No scope creep. No "and while we're at it." The moment Phase 1 starts expanding to accommodate adjacent problems, it stops being a test and starts being a programme - which is exactly what the board was nervous about funding in the first place.
And Phase 1 is measurable. Success criteria agreed before the work begins, not interpreted retrospectively. "A 40% reduction in first-draft review time, measured across the next 10 matters, confirmed by the team lead by week 12." "A 25% increase in qualified enquiries from restructured service pages, measured against the same period last year." Numbers. Dates. Named people who confirm them.
Its results fund Phase 2 - not through a formal mechanism, necessarily, but through the evidence it produces. A Phase 1 that delivers against its stated criteria is the most compelling Phase 2 proposal you'll ever write. I've written about this in the context of AI pilots separately, and the logic is identical - the same four criteria (specific use case, measurable outcomes, realistic scope, governed timeline) apply whether you're piloting an AI tool or testing a new digital platform.
This is the practical bit. If you're sitting there thinking "fine, I'll try phased" - these are the four decisions you need to make before you walk into the boardroom.
First: choose the initiative with the highest impact-to-risk ratio. Not the most ambitious one. Not the one that's most interesting to you personally. Not the one the technology partner is most excited about. The one most likely to produce undeniable evidence of value within 90 days at minimum cost and disruption. I was working with a consulting firm last year where the CTO wanted Phase 1 to be a full knowledge management overhaul. Exciting project. Genuinely important. But it touched every team in the business and had at least four stakeholders who'd need to agree on taxonomy before a single piece of content moved. We steered him towards automated proposal generation instead - one team, one workflow, one measurable output. Sixty per cent reduction in proposal turnaround time within the first quarter. That result made the knowledge management project a straightforward Phase 2 approval.
Second: define the success criteria before the work begins. Three specific, observable outcomes that constitute success. Not five. Not "we'll know it when we see it." Three. Agreed by you and the relevant board members before Phase 1 starts. Write them down. Print them out. Stick them on the wall if you have to. Because if you don't agree what success looks like upfront, you'll spend week 13 arguing about whether the pilot "worked" instead of presenting evidence that it did.
Third: set the timeline at 90 days. Long enough to produce meaningful evidence. Short enough to maintain momentum and avoid the governance overhead of a longer programme. I've seen 60-day Phase 1s that felt rushed and 6-month Phase 1s that lost all urgency. Ninety days is the sweet spot for most mid-market firms - roughly a quarter, which maps neatly to existing board reporting cycles.
Fourth: name the person accountable for delivery. One person. Not a committee. Not a working group. Not "the digital team." One human being with explicit authority to make the decisions required within Phase 1's scope. If that person has to convene a meeting every time they need to approve a vendor invoice or sign off a design decision, your 90-day Phase 1 will take 180 days and you'll be back to square one.
This is where most people get the framing wrong. They present the full three-phase programme as if the board is approving all of it today. The board panics. They see the total number. They start asking questions about Phase 3 contingencies when you haven't even started Phase 1.
Your board presentation should include an indicative view of Phase 2 and Phase 3 - what they'd involve, roughly what they'd cost, what they're contingent on. But explicitly framed as options rather than commitments.
The language that works - and I mean this quite literally, use words close to these: "If Phase 1 delivers against its success criteria, we would recommend proceeding to Phase 2, which would involve [scope] at approximately [cost], with a gate review at [milestone]. That decision would be made at the Phase 1 gate review and would not require today's approval."
Read that again. The crucial phrase is "would not require today's approval." You're giving the board enough context to assess whether the full investment is proportionate to the opportunity, without asking them to commit to it. You're asking for a low-stakes, reversible decision - fund 90 days of work - rather than a high-stakes, irreversible one.
Some boards genuinely do prefer a comprehensive investment case upfront. I've sat in rooms where the chair has said "just tell me the full number." If that's your board, give them the full number - but present it as a total envelope with stage gates, not as a single committed spend. The psychology is different even if the maths is the same.
Stage-gate governance isn't bureaucratic overhead. It's the mechanism that converts a series of small approvals into a coherent investment programme.
Each gate review has three components. A report on what the previous phase delivered against its stated criteria - honest about what worked and what didn't. A recommendation about whether to proceed, informed by evidence rather than sunk cost logic. And a specific request for the next phase - scope, cost, timeline, success criteria, identical structure to the Phase 1 request.
That last bit matters more than people think. The board that approved Phase 1 is significantly more likely to approve Phase 2 if Phase 1 delivered. You've built credibility. You've demonstrated that the team can scope, deliver, and measure. You've shown the board that their governance structure works. Phase 2 isn't a leap of faith - it's a decision based on evidence they've seen with their own eyes.
And if Phase 1 doesn't deliver? That's valuable too. You've spent a fraction of the full programme budget to learn that the approach needs adjusting - or that the investment isn't worth pursuing. That's not failure. That's governance working exactly as it should. Compare that to discovering the same thing 18 months and £800k into a monolithic programme. Which, by the way, I've also seen. It's not pretty.
There's a companion piece on what boards should know before approving a digital transformation budget that covers the governance perspective in more detail - worth reading if you're trying to understand how your board thinks about these decisions.
I said earlier that boards aren't actually opposed to phased approaches. But let me be honest about the one scenario where phasing genuinely gets pushback: when the board suspects you're using it to obscure the total cost. If Phase 1 is £80k, Phase 2 is £200k, and Phase 3 is £350k, and you present Phase 1 without mentioning the rest - you haven't built trust. You've undermined it.
The phased approach works because it's better governance, not because it's a technique for sneaking large investments past the board one slice at a time. Be transparent about the indicative total. Be clear that subsequent phases are contingent on results. And be willing to say, in the room, "If Phase 1 doesn't work, we stop."
That willingness to stop is, paradoxically, the thing that makes the board most willing to start.
I've written separately about making the cost-of-inaction case, which is the other half of this conversation - because sometimes Phase 1 becomes approvable not because of what it promises, but because of what continuing to do nothing is already costing you.
Take whatever proposal you've been working on - the full programme, the big number, the 18-month timeline - and ask yourself four questions.
What's the single highest-impact, lowest-risk initiative within that programme? What three measurable outcomes would prove it's working? Who would be accountable for delivering it in 90 days? And what would need to be true for the board to fund Phase 2?
If you can answer those four questions clearly, you have a Phase 1 proposal. Not a watered-down version of the full programme. A genuine test that produces the evidence your board needs to make a bigger commitment with confidence.
At Distinction, we use a framework called WHNN® - the What and the How, for the Now and the Next - to structure this kind of phased delivery. It runs on a quarterly cycle, which maps neatly onto the 90-day Phase 1 logic: agree what you're doing and why, deliver it, review the evidence, decide what comes next. If you want the detail on how that works in practice, there's a piece on it here.
But the underlying principle is simple enough. Stop asking the board to trust a three-year projection. Ask them to fund a 90-day test instead.
The investment may be the same. The approval probability is very different.
If you want the Phase 1 proposal structure as a template - covering scope, success criteria, timeline, governance, and gate review format - download it here.