Beyond the business case: A playbook for securing board-level buy-in

You’ve done everything right and navigated your first 100 days. You listened to front-line leaders, found the burning platform and tackled it head-on to deliver a clean, public win. In a few short months, you’ve earned credibility throughout the organization the old-fashioned way, by delivering results.

However, before you can cash in on that credit, you have to get buy-in from the board.

The time is right to unveil your bold, multi-year transformation plan to modernize the company’s core, open up new revenue streams and build a durable competitive advantage to grab shares in a crowded market. You have a meticulously crafted plan, the ROI projections are aggressive and the tech is future-proof.

And yet, when you present it, the reception is tepid: polite nods, a few pointed questions from the audit committee chair and a careful, noncommittal “Let’s revisit this next quarter.” The air goes out of the room. Your transformation is dead before it even starts.

If you’ve been in this seat before, you know the feeling. It’s a frustrating and surprisingly common pattern. As technology leaders, we are trained to believe that a logical, data-driven plan is the optimal way to make our case. We do the exhaustive work: we analyze the competitive landscape, map out the assumptions, architect the technical solution while stress-testing for every risk, model the financial payback and build a capacity plan, until we are convinced that our meticulous preparation will speak for itself.

But the uncomfortable truth is, for a board of directors, a carefully planned technical solution doesn’t guarantee victory. It just gets you through the gates and into the arena.

And after you’ve made your case with precision, after you’ve left it all on the field, you look out and only see polite, vacant nods that say, “The technology is impressive, but I don’t see the business case.” That’s when you realize the real contest hasn’t even started yet. No matter how airtight your design may be, our proposal must compete against finite capital, a stack of competing priorities and the board’s tolerance for risk.

What wins the room isn’t more data; it’s a better story. You need to create a narrative that connects your vision to the board’s mandate to protect the enterprise today and ensure its prosperity tomorrow.

To build and deliver that story effectively, I use what I call the 3Cs of Boardroom Communication. It’s a method designed specifically to move a proposal from a technical solution looking for a budget to a shared strategic imperative that the board feels a sense of ownership in championing.

1. Communicate: Translate technology into the language of fiduciary duty

As McKinsey’s New Year’s resolutions for tech in 2025 report emphasizes, an emerging responsibility for technology leaders is to “overinvest in clear and consistent communication about changes and opportunities,” which is the foundation for building alignment and trust with both the board and your teams. So, your first step is to stop talking like a legacy CIO and start talking like a director. A board has a fiduciary duty to manage risk and create long-term value. When you frame your vision in this language, you move from being a supplicant asking for money and become a partner helping them fulfill their primary obligations.

A few practical translations:

• Instead of “technical debt,” say “operational risk and its impact on our ability to meet future earnings projections.”
• Instead of “cloud modernization,” say “enabling the business agility required to respond to competitive threats.”
• Instead of “cybersecurity upgrade,” say “protecting the brand’s reputation and preserving shareholder value.”

I learned this lesson the hard way while seeking funding for a global enterprise service bus. The first pitch focused almost entirely on the technical design and surface-level system capabilities. Everything was laid out: the stack diagrams, the integration flows, the implementation timelines. The reaction? Polite disinterest.

The second pitch barely mentioned the tech. Instead, we reframed the discussion around business capabilities on the company’s roadmap that were impossible to deliver without it. We quantified the rising costs and reputational risks of doing nothing, and showed how the platform would keep our data consistent, address core customer complaints, while positioning us favorably for likely regulatory changes. The result? Immediate funding approval. The difference was stark: in the first meeting, it played like a vendor selling technology. In the second, we were partners in safeguarding the business.

2. Contextualize: Frame your move in the market

No board decision is made in isolation. As a recent Deloitte report on board governance makes clear, the board’s role is to “understand and oversee the risks AI poses to the company’s overall strategy… and monitor how AI can impact existing enterprise risks.” This is where you become their trusted guide, arming them with the external context that makes your proposal not just smart, but necessary.

Three levers make this work:

• Peer benchmarking: “I’ve analyzed our top three competitors. All have already deployed the kind of agile platforms this initiative will build. As of today, we’re at a disadvantage in time-to-market. We are doing monthly deployments that take three exhausting days over a weekend, while our competition is rolling out mid-day deployments.”
• Market opportunity: “The emerging Banking-as-a-Service market is forecast to reach $50 billion in the next five years. Our modernization program is the prerequisite for even competing in this space.”
• Analyst validation: “Gartner’s latest assessment is clear: organizations that fail to modernize core platforms will see accelerated declines in competitiveness, in customer acquisition and retention, as well as in attracting top talent.”

When a member of your board can confidently explain to an investor why your transformation matters in the competitive landscape, you’ve won more than the budget. You’ve created an informed advocate.

3. Co-own: Make it their idea

This last step is too frequently overlooked, and the most decisive. True board-level buy-in doesn’t happen during the big presentation. It’s sealed in the quiet conversations that happen in the weeks leading up to it.

If you step into that board session with your vision still wearing the label “CIO project,” you’re going to be fighting an uphill battle. The goal is to transform it into their plan. Insights from Harvard Law School’s Program on Negotiation reaffirm that “Groups that focus on making decisions through consensus building tend to reach agreements that are more stable, more efficient and wiser… .”

Start with the chairs of your most relevant committees: audit, risk and technology. Share early thinking and — most importantly — ask for their input in ways that engage them with the process:

• “From your seat on the audit committee, what financial or control-related blind spots do you see with this approach?”
• “You’ve seen transformations succeed and fail at other companies — what pitfalls should we be watching for?”
• “What would you need to see from me in the first 12 months to have complete confidence that we’re on track?”

These aren’t merely perfunctory questions. They are an invitation to co-authorship. When a director has helped to shape the narrative, they won’t just support the plan; they’ll defend it. This kind of dynamic can convert contentious approvals into near-unanimous support. This way, by the time you stand before the full board, you’re no longer facing a panel of skeptics; rather, you’re presenting alongside allies who see the strategy as partly their own.

A solid business case and technological design prove you’ve done the work. But a strategic narrative — built on communication, context and co-ownership will inspire the board to commit.

For CIOs, making this shift is everything. It’s how you move from pitching projects to co-authoring enterprise strategy. You begin to evolve from an operational leader to a strategic partner that boards rely on, not if disruption comes, but when.

In Part 3 of The CIO Masterclass, we’ll leave the boardroom and head to the engine room, exploring how to structure your technology organization so it can deliver on the bold commitments you’ve just secured.

This article is published as part of the Foundry Expert Contributor Network.
Want to join?