The Budget Defence I Learned in Banking That Still Works in Any Boardroom
“Why does it have to be this much?”
Eight words, asked without raising a voice, from a managing director three seats down a table I had not yet earned the right to sit at. I was twenty-six, presenting a budget line for a new relationship-manager hire on the mid-market desk, and I had built my case the way everyone around me built theirs: enthusiasm, a growth forecast, two comparable hires that had worked out well. None of that answered his question. The room went quiet long enough that I could hear the air conditioning. My request wasn’t rejected — it was tabled, sent back for a rewrite with six days before the next committee sat.
(This article was created with AI assistance; all stories and insights are based on 35 years of real client work.)
Quick answer: A budget line survives committee scrutiny when it answers three questions before anyone has to ask them: why this number, what happens if it isn’t funded, and how you’ll know it worked. Most requests only answer the first — enthusiasm and a forecast — and get tabled, not rejected, until someone adds the other two.
I spent those six days doing what I should have done the first time: talking to the one person on that committee who had actually read my proposal closely enough to ask a real question. He told me, not unkindly, that my pitch had been a wish, not a defence. A wish says what you want. A defence says why the number is right, what it costs the business if the answer is no, and how anyone in that room — including him, six months later — would know whether the decision had paid off. I had given him none of the three. I’d given him enthusiasm wearing the clothes of a business case.
The Question Behind the Question
“Why does it have to be this much?” was never really about the number. It was a test of whether I had done the thinking the number implied.
A credit or budget committee that approves requests for a living develops a kind of radar for a figure that was chosen rather than built — rounded to the nearest convenient thousand, matched to what was “normally” asked for, or anchored to a vague sense of scale instead of a specific cost. Committees that review resource requests for a living have seen hundreds of numbers; the eight-slide structure most finance committees now expect exists precisely because so few requests arrive able to show their working.
I later watched this pattern from the other side of the table, coaching a plant operations VP at a mid-cap manufacturing group through a main board capital request. His first draft read almost exactly like mine had at twenty-six — three bullet points on why the new packaging line would help, a number at the bottom, no sense of where the number came from. He had the budget right. He just hadn’t shown the board the arithmetic, and a board that can’t see the arithmetic assumes there isn’t any.
The pattern holds regardless of seniority or sector, which is what makes it worth naming properly instead of treating each failed pitch as a one-off. A first-time presenter and a twenty-year veteran make exactly the same mistake under the same pressure: both reach for conviction when the room is actually asking for arithmetic.
Conviction is audible — it’s in the tone, the pace, the eye contact. Arithmetic has to be said out loud, in a specific sentence, or it doesn’t exist as far as the room is concerned. Nobody in a budget committee has ever been persuaded by how certain someone sounded about a number they couldn’t trace.
The Three-Question Budget Defence
What that managing director was teaching me, in four blunt words, became a structure I have rebuilt for every budget line, every client capital request, and every coaching session since. I call it the three-question budget defence, and it has exactly three components. Leave one out and the case collapses back into either a wish list or a spreadsheet — neither of which a committee can actually act on.
One: why this number. Not “why we need more resource” — why THIS figure, specifically, and not the one either side of it. The answer has to trace back to something countable: a unit cost, a comparable hire’s first-year output, a quoted price from a supplier. A number with no traceable origin reads as a guess no matter how confidently it’s delivered.
Two: what happens if it isn’t funded. A single, bounded sentence naming the specific cost of saying no — not “we’ll fall behind,” but what falls behind, by how much, and by when. This is the sentence most presenters cut because it sounds like a threat. It isn’t a threat; it’s the other half of the comparison the committee is there to make, and without it they’re being asked to evaluate one side of a decision that actually has two.
Three: how you’ll know it worked. One observable signal, checkable by someone other than the person asking for the money, on a date that isn’t “eventually.” Many presenters answer the first two questions and go quiet on this one — but a committee that has been burned before by requests with no follow-up accountability learns to discount everyone’s “why” and “what if” until someone also commits to a check.
Get Winning Presentations’s stories in your inbox
Join Medium for free to get updates from this writer.
Put together, those three sentences would have turned my twenty-six-year-old pitch from a wish into a defence: the hire costs £68,000 fully loaded, matched to what the two most recent comparable hires on the desk cost in their first year (why this number); without it, the desk’s coverage gap on three mid-market accounts stays open through the next renewal cycle, risking roughly £40,000 in at-risk fee income (what happens if it isn’t funded); and the committee would see the hire’s revenue contribution against that £40,000 benchmark at the six-month review (how you’ll know it worked). Three sentences. Not a longer pitch — a different one.
The Twenty-Second Test
Before any budget line goes into a committee pack, it needs to survive one check. Write the three answers as three sentences, nothing more. Read them aloud, timed. If the read takes longer than twenty seconds, the case is still carrying language that isn’t doing any of the three jobs — trim it. If any one of the three questions has no sentence at all, the case isn’t ready, no matter how polished the slide around it looks.
This is also, not coincidentally, close to what the questions a CFO reliably asks before signing off a budget line are actually probing for — most of the common ones collapse into some version of these same three, asked from a different angle. A presenter who has already answered them once doesn’t get caught answering them badly a second time, under pressure, in front of the room.
The operations VP ran his rebuilt case through the same test before his board meeting. His sentence on “what happens if it isn’t funded” came in four seconds over the limit — not because it was too long, but because he’d written it with two qualifying clauses that hedged the number instead of defending it. He cut the hedges, said the number plainly, and the board approved the request without the extended Q&A his first draft would have triggered.
Where the Defence Usually Breaks
Each of the three questions fails in its own characteristic way, and recognising the failure mode is faster than rebuilding from scratch. The “why this number” answer breaks when it’s anchored to precedent instead of arithmetic — “that’s roughly what we asked for last year” is not a reason, it’s an absence of one. The “what happens if it isn’t funded” answer breaks when it’s vague enough to apply to any request in the building — “we’ll fall behind the market” could be the cost of approving or declining almost anything, and a cost that generic persuades nobody. The “how you’ll know it worked” answer breaks when the checkpoint has no date attached — “we’ll monitor it” is not a commitment, it’s a sentence designed to avoid being held to one.
Senior committees develop a practised ear for all three failure modes, because they hear them constantly. The presenter rarely notices which one they’ve fallen into, because each sounds, in the moment, like a perfectly reasonable sentence. It’s only against the other two questions — asked together, out loud, in twenty seconds — that the gap becomes visible.
The fix for each failure mode is smaller than it looks. A precedent-anchored number gets fixed by replacing “roughly what we asked for last year” with the actual unit of measure behind it — cost per hire, cost per unit, cost per hour of downtime avoided. A generic cost-of-inaction gets fixed by naming the one thing that actually breaks first, not the three vaguer things that might eventually follow. A dateless checkpoint gets fixed by picking any specific date on the calendar and writing it down — a wrong date corrected later is a smaller problem than no date at all, because a missing date signals nobody intends to check.
Frequently Asked Questions
What if the committee never asks any of these three questions out loud?
Then the defence has done its job before anyone needed to ask. Committees that don’t interrogate a request aren’t skipping the test — they’re confirming, silently, that the case already passed it. The danger sign isn’t a quiet room; it’s a quiet room followed by a deferral nobody explains.
Where did the three-question structure actually come from?
From a single sentence a managing director asked me early in my banking career, and from watching the same gap — enthusiasm with no traceable number, no named cost of inaction, no accountability checkpoint — repeat across every budget and capital request I’ve reviewed or coached since, in banking and in the boardrooms I work in now.
Does this work for requests that aren’t about money — headcount, timeline, or a change in direction?
Yes. Swap “why this number” for “why this scope,” and the other two questions hold exactly as written: what does saying no cost, specifically, and how will anyone know later whether the decision was right. Any request that displaces something else in a limited budget — money, people, or time — answers to the same three-question structure.
The next time you sit down to defend a number in front of a room that didn’t ask for it, do three things before anyone else speaks: say why this figure and not a rounder one near it, name what the business loses if the answer is no, and tell them the date you’ll both find out whether you were right. Twenty seconds, three sentences, and the four words that once sent me back to my desk for six days won’t get the chance to be asked — because you’ll have already answered them.
If you’re building the case for your own budget line and want the structure built onto the page before you walk into the room, the Executive Slide System (£39) gives you 26 executive slide templates, 93 AI prompts, and 16 scenario playbooks for board, investor, executive, and committee presentations — built for exactly the kind of defence this article just walked through. Get the Executive Slide System →
About the Author
Mary Beth Hazeldine is the Owner & Managing Director of Winning Presentations. With 24 years of corporate banking experience at JPMorgan Chase, PwC, Royal Bank of Scotland, and Commerzbank, and 16 years coaching senior professionals across financial services, manufacturing, and technology, she advises executives on structuring presentations for high-stakes funding and approval decisions.
