You have a board meeting in three weeks. You want to use part of it to introduce a new digital initiative. Maybe it's the side bet you've been sitting on for three years. Maybe it's a new product line. Maybe it's a platform play your industry is moving toward. Whatever it is, you know that the way you frame the conversation in those 20 minutes will determine whether the bet gets greenlit, killed, or quietly shelved as "interesting, let's revisit next quarter."
If you do this wrong, your board hears "the president wants to play with shiny digital objects." That's the kiss of death.
If you do it right, your board hears "our president has identified a real, contained, intelligently-staged opportunity that protects the core business while exploring meaningful upside." That's a different meeting.
The difference is not the bet. The difference is the framing. Let me walk you through how to do this.
The four questions your board is actually going to ask
Before you walk into that room, write these four questions down. They will all be asked. Sometimes by different board members. Sometimes by one director who has read the deck carefully. But all four will be in the room with you whether anyone says them out loud or not.
1. How big a bet is this, really?
Your board needs to know the actual capital and time exposure. Not a range. A number. They are not asking because they want to say no. They are asking because their job is to know.
2. What does failure look like, and what does it cost?
This is the question that makes most operators sweat. The instinct is to talk about why it won't fail. That's the wrong move. The right move is to define failure precisely, price it, and demonstrate that you've already thought through how to absorb it.
3. Who is doing the work, and what does it cost the existing business?
This is the structural question. They want to know whether you are about to pull your A-players off the core P&L to play with a new toy. If the answer is yes, the meeting is over. If the answer is no, you need to be very specific about who is doing the work and where they sit.
4. How will we know if it's working, and when?
The "milestone and decision" question. They want to see that you have a clear go/no-go gate, not an open-ended commitment.
If you walk in with crisp answers to these four questions, you're ahead of 90 percent of the digital initiatives that get pitched at boards.
The framing that works
Here's the structural move. The bet has to be presented not as a new initiative but as a staged experiment.
Those are two different things in board language. A new initiative implies headcount, budget, multi-quarter commitment, organizational change. A staged experiment implies a small contained spend with clear milestones and a defined kill switch.
Your board is allergic to the first. They are open to the second. The actual work is identical. The framing is doing all the heavy lifting.
Try this opening structure when you walk into the room.
"I want to bring something to the board. It is not a new initiative. It is a 90-day experiment, capped at $X, run by a single outside operator with no impact to our existing business. At the end of 90 days, we will have hard customer evidence about whether the bet is worth scaling. If the evidence is good, we'll come back to the board with a real proposal. If it's not, we close the experiment, and we've spent less than [a known reference point]."
That paragraph is doing several things at once. Let me unpack what each line is doing, because this is the core of the technique.
"It is not a new initiative." You are pre-empting the trigger word that activates board skepticism. "Initiative" is a word they associate with budget bloat and quarterly check-ins that go nowhere.
"It is a 90-day experiment." You are defining the time box. Boards trust time-boxed work because it has a natural off-ramp.
"Capped at $X." You are defining the financial exposure. Numbers calm boards. Vagueness scares them.
"Run by a single outside operator." You are answering the structural question before they ask it. No headcount risk. No internal disruption.
"With no impact to our existing business." You are saying the magic words. The board's primary job is to protect the existing business. If you can credibly claim non-disruption, you've removed their biggest objection.
"At the end of 90 days, we will have hard customer evidence." You are defining the deliverable as evidence, not a product. Evidence is something the board can act on. A product is something the board has to evaluate.
"If the evidence is good, we'll come back." You are staging the bet. You're not asking for permission to run a multi-year program. You're asking for permission to run one short experiment that ends with a real decision point.
"If it's not, we close the experiment, and we've spent less than [a known reference point]." You are pricing failure. Boards relax when they know the downside is bounded and small.
The reference point trick
That last move, the "known reference point," is worth its own paragraph because it does more work than people realize.
Boards are very good at evaluating numbers in context. They are bad at evaluating numbers in isolation. If you walk in and say "the experiment costs $60,000," some directors will think that's small and some will think that's large, depending on what they're comparing it to in their head.
Your job is to put the comparison in their head for them.
Examples of reference points that work:
- "Less than we spend on our annual sales kickoff."
- "Roughly 2 percent of last year's marketing budget."
- "About what we spend on a single trade show booth."
- "One sixth of what the [Industry Conference] sponsorship cost us last year."
- "Less than we paid the consulting firm that produced the strategy deck nobody used."
Pick a reference point that the specific people in your boardroom remember spending money on. The reference point makes the number feel responsible instead of speculative.
What to do when the questions get hard
Here's the move when a director pushes back. And one of them will. They're board members; pushing back is their job.
Whatever the question is, your first move is agreement. Not capitulation. Agreement.
If a director says "this sounds like the kind of digital project that always overruns," your answer is not to argue. It is to agree, and then differentiate.
"You're right that most digital projects overrun. That is exactly why we're structuring this differently. The reason digital projects overrun is that they're sold as products with feature lists and timelines. We're not buying a product. We're buying 90 days of evidence. The deliverable is the evidence, and the cost is fixed."
The agreement disarms them. The differentiation re-frames the bet. They cannot say "you didn't hear me," because you obviously did. They are now responding to your reframe rather than holding their original objection.
This is a much better position to be in.
The thing I want you to walk away with
A digital side bet does not get killed in a board meeting because it's a bad idea. It gets killed because the language used to describe it activates the board's risk-management instinct.
The same exact bet, framed as a 90-day capped experiment with a single outside operator and a clear evidence-based decision point, is one your board will almost certainly approve.
The work is the same. The framing does the work.
Walk into the next meeting with the four questions answered, the staged-experiment language ready, the reference point chosen, and the agreement-then-differentiate move loaded for when somebody pushes back.
That is the board-meeting test. Pass it, and the doc finally moves.
Same playbook, different doorway: the vocabulary swap · the pre-mortem.
If you want help building the actual board language for your specific bet, book a call. Thirty minutes. We will work through exactly how to position the project for your specific board. If you need the underlying build framed for this pitch, see the 90-day program.