Building a Business Case That Survives the Hard Questions
Most business cases are not rejected because the idea was bad. They are rejected because the document could not answer the questions a careful reader was always going to ask. A business case is not a sales pitch; it is an argument built to be tested. The version that survives scrutiny is the one written, from the first draft, as if a sharp committee will try to take it apart. In 2021, with budgets tight and recovery uncertain, that committee got sharper, and the easy approvals dried up.
Start with the problem, not the solution
The fastest way to lose a room is to open with what you want to buy or build. Open instead with the problem, stated in terms the organization already cares about: a cost it is bleeding, a risk it is carrying, a commitment it is failing to meet. If you cannot describe the problem without naming your preferred solution, you do not yet understand the problem well enough to spend money on it.
Anchor the problem in evidence the reader can check, then size it. 'Manual reconciliation costs roughly two staff-days a week and caused three reporting errors last quarter' invites scrutiny and survives it. 'Our process is inefficient' invites a shrug.
The sections a tough committee actually reads
A business case can be ten pages or two, but it must answer the same questions in roughly this order.
Options, including doing nothing. Always carry the do-nothing baseline and at least one genuine alternative. A case with only one option reads as a decision already made, and reviewers distrust it on sight.
Costs, whole-life and honest. Capital plus the years of running, support, and change that follow. Padding gets you caught; lowballing gets you a project that fails its own budget. Name the assumptions behind every number.
Benefits, owned by someone. Separate cashable savings from softer gains, and attach each benefit to a named owner who will be accountable for delivering it. An unowned benefit is a wish.
Risks, stated plainly. List what could go wrong and what you will do about it. Naming your biggest risk yourself builds far more trust than having the committee find it for you.
The recommendation and the ask. State which option you back and exactly what you need to proceed. A case that ends without a clear decision sends everyone back to their inbox.
Make the benefits believable
Benefits are where most cases quietly fall apart. The temptation is to inflate them until the return looks irresistible, but an experienced reviewer discounts inflated benefits on instinct, and that discount sinks the whole document. Restraint reads as credibility.
Tie every benefit to a baseline you can measure today, so you can prove the change later.
Be explicit about which savings free up actual cash and which only free up time.
State when each benefit lands; a benefit with no date is impossible to hold anyone to.
Say how you will know it arrived, before you ask for the money, not after.
A business case is not finished when it is approved. The same document becomes the yardstick you are measured against, so the credibility you build by being conservative now is the credibility you will be glad of at the first review. Promise what you can defend, defend what you promise, and the next case you bring forward will be read with the benefit of the doubt.
If you need a business case that holds up in front of a board or a funding body, XNM's program & project delivery advisory can help you build the argument and the evidence behind it.