Most compliance budget requests fail for the same reason: they are built on fear, and the person holding the purse has become immune to it. "If we do not fund this, we could be fined" is technically true and completely unpersuasive, because every function says a version of it and the finance director has learned to discount all of them. A business case that wins is not louder about the danger. It is quieter, and it is built the way finance thinks: expected value, not dread.
Why fear loses
Fear loses because it cannot be compared. "We might be fined" gives the decision-maker nothing to weigh against the cost of the ask, so it becomes a matter of nerve rather than analysis, and nerve favours saying no to a spend. The moment you convert the fear into a number and a probability, you give finance something they can actually work with, and you move the conversation from "are you scared enough" to "does the maths work". Finance can say no to fear all day. They struggle to say no to a positive expected value.
The three things a winning case has
A compliance business case that survives a spreadsheet has three parts. The expected cost of the failure you are preventing: the size of a plausible failure multiplied by how likely it is, honestly estimated. The cost of the ask: what you want, all in. And the return: the difference, plus any upside beyond avoided loss, faster deals, market access, lower insurance, less rework. That third part is what separates a good case from a defensive one. If all you offer is avoided loss, you are asking to be tolerated. If you can also show upside, you are asking to be invested in.
The solution, as a business-case template
Build the case in five lines
- Name the specific failure this prevents, not "risk" in general. One concrete thing that could go wrong.
- Size it: the full cost if it happened, using the six-line bill, fine, remediation, legal, lost business, time, reputation.
- Weight it: multiply by an honest probability. Expected cost is size times likelihood.
- Price the ask: everything the fix costs, over a sensible period.
- Show the return: expected cost avoided, minus the ask, plus any upside like faster sales or market access.
The move that changes everything: honesty about probability
The instinct is to inflate the likelihood to make the case look urgent. Resist it, because the person you are convincing can smell it, and one inflated number sinks the whole case. Use a probability you can defend, even a low one. A one-in-twenty chance of a large loss is still a serious expected cost, and offering an honest low probability builds the credibility that makes finance believe your other numbers. Compliance leaders who win budgets are trusted with numbers precisely because they do not oversell them. That trust is the real asset, and fear-selling spends it.
Questions to pressure-test your business case
- Have I named a specific failure, or just waved at "risk"?
- Have I sized the full six-line cost, not just the fine?
- Is my probability one I can defend, or one I inflated?
- Have I shown any upside, or only avoided loss?
- Would this case convince me if I controlled the money?
Winning compliance budget is not about being more frightening. It is about being more numerate. Convert the fear into an expected cost, price the ask, show the return including the upside, and be scrupulously honest about probability so your numbers are believed. Do that and you stop being the function that asks to be tolerated and start being the one finance invests in, because you brought them the one thing fear never can: a case that adds up.
Notes and sources
From the book
The Compliance Business Model NavigatorFifty business-model patterns behind the compliance industry, each explained in plain language and carried by a real, named company.