I want you to do something a little uncomfortable before you read the rest of this.
Picture the moment in your upcoming board meeting when the digital initiative you've been planning to pitch gets killed. Not killed loudly. Killed politely. The way these things actually die in boardrooms.
The slide is up. You've made the case. You've shown the size of the prize. You've talked about the customer pain. You've named a budget range and a rough timeline. You're three or four minutes into the discussion.
And then one director, the one who always asks the careful question, leans forward and says some version of one of these things.
"This sounds like the kind of project that always grows beyond its original budget."
"Have we thought about what this is going to do to our team? They're already at capacity."
"I'd like to see more rigor on the customer side before we commit to building anything."
"I think there's something here, but maybe we should let it season for another quarter and revisit."
The other directors nod. The CEO does not push back. The conversation moves to next quarter. Or to a "let's get more clarity and bring it back," which is the same thing.
Your project is not killed. It is deferred. Which, given how busy everyone is, is functionally identical.
Now, the useful thing about picturing this scene clearly is that it tells you exactly what you have to defuse before the meeting starts. Each of those four sentences is a specific objection. Each one has a specific antidote. If you walk in with the antidotes already loaded, the sentences either don't get said, or they get said and you have a clean answer ready.
Let me give you the antidotes.
Objection one: "These projects always overrun."
This is the most common killer. It comes from real scar tissue. Almost every director has been on the wrong side of a digital project that started at $200K and ended at $1.2M.
The antidote is to make the spend structurally incapable of overrunning. Not promised to not overrun. Structurally incapable. Those are different things, and the director will know the difference.
How you do that: instead of pitching a project with a budget, you pitch an experiment with a fixed cost. Single outside operator, fixed-fee engagement, defined deliverable. The deliverable is not a product. It is a 90-day window of evidence. There is no scope to creep into, because there is no scope. There is only "did we generate the evidence or not."
The line that defuses the objection in advance:
"I want to flag something up front. Most digital projects overrun because they're sold as products with feature lists. This isn't structured that way. It's a fixed-fee engagement with a single outside operator. The cost cannot move. What we're buying is 90 days of evidence."
Now when the director raises the overrun objection, you've already addressed it. They will either ask a follow-up that takes them deeper into the structure (which is good for you), or they will mark this as "thoughtfully handled" and move on.
Objection two: "What about the team's capacity?"
This one comes from any director who has watched a side project quietly hijack a chunk of the existing team's bandwidth. They are right to ask. It happens constantly.
The antidote is to make the answer "no internal team involvement at all" before they ask.
The line:
"I want to be clear about who is doing the work. The entire project runs through one outside operator. Nobody on our existing team is being asked to spin up a new workstream. Our internal team's only involvement is approving the experiment at three checkpoints. That's it. The day-to-day load is zero."
This is the most underused move in board pitches. Most operators describe the project as "we'll have a small task force" or "I'll put one of our senior PMs part-time on this." That triggers every "this is going to eat into the core" alarm in the room.
The right move is to remove your internal team from the picture entirely. The board cannot worry about a capacity drain that doesn't exist.
Objection three: "I want more customer rigor before we commit."
This one is interesting because it is rarely a real objection. It is usually a polite way of saying "I don't believe the customer wants this and I want to slow it down."
The antidote is to make the experiment itself the customer rigor. The whole point of the 90-day experiment is to generate the customer evidence that the director is asking for. So you don't need to defend the customer hypothesis with surveys or interviews. You need to point out that the experiment exists to test exactly this question.
The line:
"That's the whole point of the 90-day experiment. We're not asking the board to commit to building a product on assumptions. We're asking the board to fund the test that produces the evidence. At the end of 90 days, we either have customers using a real version of the product, or we don't. If we don't, we close it. The evidence is the deliverable."
This reframes the experiment from "the thing you're worried about" to "the thing that addresses the thing you're worried about." Same project. Different positioning.
Objection four: "Let's let it season and revisit."
This is the deferral move. It is the polite kill. It is, in many ways, the worst outcome, because nobody objected on the merits and yet nothing happens.
The antidote is to remove the option of deferral by making the cost of waiting visible.
The line:
"I'd push back gently on that. The reason this experiment is on the agenda right now is that the cost of building this kind of test has dropped roughly 90 percent in the last 18 months. That window is closing as competitors figure it out. Waiting another quarter is not a neutral move. It's a decision to let competitors run the experiment first."
Most operators don't say this because it sounds confrontational. Said in the right tone, it isn't. It is just naming the actual situation, which is that doing nothing is also a decision with a cost.
If your board respects you, they will register the point. If they don't, the experiment was probably going to get deferred no matter what you said.
The structure of the meeting itself
A specific tactical move that is worth doing: give yourself five minutes at the start of your section to load the four antidotes before you ever describe the bet.
That sounds backwards. It isn't. The reason is that the antidotes are not really about defending the bet. They are about establishing the frame that the bet should be evaluated in. Once the frame is set, the bet itself takes much less time to explain.
The order looks like this.
One. "Here's how this is structured: outside operator, fixed cost, 90-day window, no internal team load."
Two. "Here's why we're doing this now: the cost of testing this kind of bet just dropped 90 percent."
Three. "Here's the specific question we're trying to answer: do customers actually want X, and will they pay for it."
Four. "Here's the decision point at the end: scale, kill, or pivot. We come back to the board with the evidence."
You can do all four of those in 90 seconds. By the time you get to the actual bet, the framing has already done most of the work.
The thing I want you to walk away with
Boards do not kill bets because the bets are bad. They kill bets because the structure feels open-ended, the team-load feels invisible, the customer evidence feels thin, and the deferral feels safe.
Picture the meeting before you walk in. Find the moment where the bet dies. Identify which of the four objections is doing the killing. Load the antidote. Practice the line.
That's the board-meeting test. Pass it, and the experiment gets greenlit. The doc finally moves.
Same playbook, different doorway: the field manual · the vocabulary swap.
If you want help building the antidotes for your specific bet and your specific board, book a call. Thirty minutes. We game-plan the meeting before you walk in. For the experiment structure boards accept, start with the 90-day path.