A business case is not a pitch deck and it is not a project plan — it is the document that answers one question: is this worth doing, compared with everything else the business could do with the same time and money. Written well, it makes the decision easy. Written as a wish list with a budget attached, it gets shelved, and the good idea inside it never gets funded.
What changed in 2026
- Decision-makers expect a one-page version first. Long business cases increasingly get skimmed, not read; the strongest ones lead with a tight summary and put the detail in an appendix.
- AI-assisted forecasting made rough numbers cheap to generate, which raised the bar — a generic projection with no stated assumptions reads as lazy when better tools are one prompt away.
- Budget cycles tightened at many companies, so business cases increasingly compete directly against each other for the same pool of money, not just against inaction.
The structure that gets read
- Problem statement. What is the cost of the status quo, in time, money, or risk, stated in terms the reader already cares about.
- Options considered. Including doing nothing. Two or three real alternatives, not a strawman next to your preferred choice.
- Recommendation. State it plainly, in one sentence, before the supporting detail.
- Cost and benefit. What it costs to build or buy, what it returns, and by when, tied to a financial model if the numbers are more than a rough estimate.
- Risks and mitigations. Name the two or three ways this could go wrong and what you would do about each.
- The ask. Budget, headcount, or a decision by a specific date, spelled out, not implied.
Business case formats compared
| Format |
Length |
Best for |
| One-page summary |
1 page |
Fast-moving decisions, busy executives, initial approval to proceed |
| Standard business case |
3 to 6 pages |
Most internal proposals — enough room for real numbers and alternatives |
| Full investment case |
10+ pages with appendix |
Large capital spend, board-level approval, multi-year commitments |
Common mistakes that stall approval
- Burying the ask. If the reader finishes the document unsure what you want them to decide, you have not written a business case.
- Presenting only your preferred option. Without a real alternative, including doing nothing, the recommendation reads as a foregone conclusion dressed up as analysis.
- Numbers with no stated assumptions. A claim like a 20 percent saving needs a baseline, a source, and a note on confidence, or it reads as a guess.
- Skipping the risk section. Leaving out what could go wrong does not make the case stronger; it makes the reader do that thinking themselves, and they may conclude there is more risk than actually exists.
Tailoring the case to the audience
A finance leader reads for the numbers and the payback period first. An operations leader reads for what changes day to day. A chief executive reads the one-page summary and the ask, then delegates the rest for review. Write the full document once, then adjust the summary and framing for whoever is in the room, rather than writing three separate documents.
FAQ
How long should a business case be?
Short enough to read in one sitting. One page for a fast internal decision, three to six pages for most proposals, longer only for major capital spend where a detailed appendix is expected.
Do I need exact numbers, or are estimates okay?
Estimates are fine if you label them as estimates and state your assumptions. A conservative, sourced estimate is more persuasive than a precise-looking number nobody can defend under questioning.
What is the difference between a business case and a project plan?
A business case argues whether to do something and secures the decision. A project plan describes how to do it once approved. Keep them separate, or the business case gets too long to actually get read.
Who should review a business case before it goes up the chain?
At minimum, someone in finance or operations who will poke holes in the numbers, and ideally the person who will eventually approve it, informally, before the formal ask.
Where to go next