How to Build a Business Case Your Champion Can Defend

Somewhere inside your prospect's org, a VP or a senior director is going to bat for you. They sat through your demo. They ran a pilot. They believe your product solves a real problem. Now they need to convince their CFO, their procurement team, and a roomful of peers who have never spoken to anyone on your sales team — and who have no reason to trust your numbers.

That person is your champion, and the business case you hand them is either an asset or a liability. Most of the time, it's a liability.

What the room actually evaluates

When your champion walks into a budget review, nobody in that room is evaluating your product. They're evaluating the case for spending money. That's a different thing entirely. The CFO isn't asking "is this product good?" They're asking:

• Where do these numbers come from? — Can every figure be traced to a formula, an input, or a source? Or does the model produce a big number and ask you to trust it?
• What happens if the assumptions are wrong? — If we only capture 60% of the projected benefit, does this investment still make sense? Can the model show me that?
• Is this the vendor talking, or is this our analysis? — If the methodology smells like a sales tool, the credibility of the entire case collapses.

Your champion knows this. They've been in those rooms before. The anxiety isn't about whether your product works — it's about whether the numbers will hold up under questioning they can't predict.

The three things that kill a business case in finance review

After watching dozens of business cases get picked apart in procurement and finance reviews, the failure modes are remarkably consistent.

1. Opaque formulas

A spreadsheet or PDF that shows "Annual Savings: $1.2M" without revealing the formula behind it is not a business case. It's an assertion. Finance teams distrust assertions on principle — it's literally their job. When someone on the committee asks "how did you get to $1.2 million?" and your champion has to say "that's what the vendor's model produced," the case is effectively dead.

Transparent, deterministic formulas change the dynamic completely. When every output traces back to a clear calculation — hours saved per week × hourly cost × number of affected employees × 52 weeks — the champion can walk through the logic line by line. They can explain it because they can see it. There's nothing hidden.

2. Single-point estimates

A business case that says "you will save $2.4 million per year" is making a promise it cannot keep. Every experienced finance leader knows that point estimates in forward-looking models are fiction. The question is never "will we get exactly this number?" — it's "what's the range of likely outcomes, and does the investment still make sense at the low end?"

This is where Monte Carlo simulation earns its place. Instead of presenting a single number and hoping nobody pushes back, you present a probability distribution: "The conservative estimate (P10) is $1.6M. The expected case (P50) is $2.4M. The optimistic scenario (P90) is $3.1M." Your champion doesn't have to defend a specific number anymore — they're presenting a rigorous analysis with a methodology the finance team recognizes.

3. Vendor-favorable assumptions

Everyone in that room has seen a vendor ROI model before. They know the game: aggressive adoption rates, best-case timelines, productivity gains that assume perfect rollout. A templated business case built from the vendor's default assumptions is immediately suspect. The finance team will mentally discount every number by 40–60% — and they'll be right to do it.

The fix isn't to sandbag your own numbers. It's to let the prospect own the assumptions. When your champion can say "I adjusted the adoption rate to 65% because that's realistic for our org" or "I used our actual fully-loaded cost per FTE, not the vendor default," the case stops being a vendor document and starts being an internal analysis. That distinction matters more than the size of the number.

What a defensible case looks like

A business case that survives finance review has four properties:

• Transparent formulas — Every output is the result of a visible calculation. No black boxes, no "proprietary methodology," no hidden assumptions. The champion can trace any number back to its inputs.
• Editable inputs — The prospect can adjust variables — headcount, hourly costs, adoption rates, implementation timelines — and watch the model respond. This is critical. When the model is flexible, it's their model. When it's locked, it's your assertion.
• Probability ranges — Instead of a point estimate, the case presents conservative, expected, and optimistic scenarios derived from simulation. This reframes the conversation from "do we believe this number?" to "does the investment make sense across the likely range?"
• Grounded assumptions — Inputs are sourced from industry benchmarks, the prospect's own data, or both. Every assumption has a basis that can be stated out loud without embarrassment.

Notice what's missing from that list: a big number. The biggest number doesn't win. The most credible number wins, because credibility is what your champion is actually selling in that room.

How to arm your champion

The shift here is subtle but important. You're not building a business case for your champion. You're building a model that your champion uses to construct their own business case.

In practice, that means:

• Give them the model, not a document. A static PDF is a dead end. An interactive model where they can change inputs and see outputs update is a tool they can use in their own analysis process.
• Make the variables visible and adjustable. If your model assumes a $75/hour fully-loaded cost, the champion should be able to change it to $82 because that's what their finance team uses. Every variable they adjust is a variable they now own.
• Show the methodology, not just the result. The champion needs to be able to answer "where does this number come from?" for every line. Deterministic formulas with visible variables give them that. If they can't explain the math, they can't defend the math.
• Include the conservative case by default. Don't make the champion ask for it. When the P10 scenario is front and center alongside the expected case, it signals analytical rigor — not sandbagging. It also gives the champion an easy answer to "what if this doesn't work as well as projected?"
• Let them present it as their analysis. The best outcome is when your champion walks into the room and says "I built a model to evaluate this" — not "the vendor sent me a business case." Everything about the case should support that framing.

The case that wins isn't the biggest

It's tempting to optimize for the largest possible ROI number. Bigger number, more compelling case, easier sale — that's the logic. But it's wrong, because it ignores the environment the number has to survive in.

Your champion's credibility is on the line. If they present a number that gets shredded in review, they don't just lose this deal — they burn political capital they can't get back. They know this. It's why so many champions go dark after asking for a business case and receiving something they can't defend.

The best business case isn't the one with the biggest number. It's the one your champion can defend without you in the room.

Give them transparent math. Give them adjustable inputs. Give them probability ranges that hold up under scrutiny. Give them a model they can make their own.

That's not a weaker case. That's the only case that actually closes.