The business case is one of the most consequential documents an organization produces and one of the most routinely under-served. Too often it is written as a bureaucratic hurdle — a form to be completed so the real work can begin — rather than as what it truly is: the reasoned argument on which people are asked to commit significant money and risk. Approvers can tell the difference, and weak cases are rightly treated with suspicion.
A strong business case does something specific: it makes the decision easy for the person who must make it. It anticipates their questions, evidences its claims, confronts its own weaknesses honestly, and presents a clear-eyed case for action. Writing one well is a skill worth mastering, because good ideas are routinely rejected for want of a compelling case.
Lead with the problem, not the solution
The most common flaw in a business case is to open with the proposed solution, as though the reader already agrees a problem exists. Persuasive cases establish the problem or opportunity first — its scale, its cost of inaction, its strategic significance — so that by the time the solution appears, the reader is already asking "what should we do about this?" A solution presented before its problem is understood invites scepticism; one presented as the answer to a problem the reader now feels invites agreement.
Evidence every material claim
A business case lives or dies on the credibility of its numbers. Costs must be built up, not guessed; benefits must be quantified and their assumptions made explicit; the financial analysis must withstand scrutiny. Approvers are trained to probe optimistic assumptions, and a single indefensible number can discredit an otherwise sound case. Evidence, transparently presented, is what separates a proposal from a hope.
Confront the risks and alternatives honestly
A business case that presents only upside signals either naivety or salesmanship, and experienced approvers distrust both. The strongest cases confront their own risks openly and set out how they will be managed, and they consider genuine alternatives — including doing nothing — rather than presenting the favoured option as the only one. This honesty is persuasive precisely because it demonstrates that the recommendation has survived real scrutiny, not avoided it.
Make the recommendation and the ask unmistakable
Finally, a business case must be clear about what it is asking for. Vagueness about the decision required, the funding sought, or the commitment involved forces the approver to do work the author should have done, and invites deferral. A crisp recommendation — this is what we should do, this is what it needs, this is what it will deliver, this is why — respects the reader’s time and makes approval a straightforward act rather than a leap of faith.
The purpose of a business case is not to inform but to enable a decision. Write it for the approver, anticipate their doubts, and make saying yes the obvious, well-evidenced choice.
Key takeaways
- 1Establish the problem before presenting the solution.
- 2Evidence every material cost and benefit; a single weak number can sink the case.
- 3Confront risks and genuine alternatives honestly to demonstrate real scrutiny.
- 4State the recommendation and the ask unmistakably to make approval easy.
Frequently asked questions
How long should a business case be?
Long enough to make the argument, short enough to be read. A tight case with a clear executive summary and supporting detail in appendices serves approvers far better than a lengthy document that buries its argument.
Should a business case include a do-nothing option?
Yes. Considering the consequences of inaction, and genuine alternatives, strengthens a case by showing the recommendation was chosen against real options rather than presented in isolation.
