A CFO does not reject your business case because the math is wrong. They reject it because the story does not hold together. A number appears with no cause. A benefit shows up that was never set up. The case reads like a list of claims instead of one argument that builds.

A business case is a story in six chapters, and each chapter causes the next. Get the order right and the return at the end feels inevitable. Get it wrong and the whole thing falls apart under the first hard question.

Why a business case is a story, not a spreadsheet

Spreadsheets do not persuade. Arguments do. The numbers matter, but only once the person reading them can see where each one came from. That is what a story gives you: a chain the CFO can follow from the cost of the problem today to the return on fixing it.

When a buyer can trace your final ROI back to a cost they already recognise, the business case stops being your claim and becomes their decision. That is the whole game.

The six chapters, in order

1. Current state

What does the problem cost today, per year? This is the baseline every other chapter is measured against. The more specific, the better. Not "manual work is slow." Instead: the hours, the fully loaded cost, the number a finance team would accept.

2. Investment

What is the total cost of ownership? License, setup, training, internal time, ongoing upkeep. Put the full number on the table yourself. A CFO will find the costs you left out, so name them first and keep your credibility.

3. Capabilities

What can the business do after this that it cannot do now? Talk capabilities, not your feature list. Each capability should map back to a cost you named in the current state. If it does not, it does not belong.

4. Future state

How does the business work differently once those capabilities are in place? Describe the before and after in the client's own words, not yours. If they would not say it in their own meeting, cut it.

5. Value

What is the future state worth, and how confident are you? Break it down by type of value, lead with a conservative case, and name the main risk out loud. A number with a stated risk beside it is more believable than a bigger number with none.

6. Economic return

What does the CFO get back, and why now? Payback period, three-year ROI, and the cost of delay: the annual value divided by twelve, for every month the decision waits. The cost of delay is what turns "interesting" into "this quarter."

The order is the argument

Skip a chapter and the gap shows. A return with no cost behind it looks invented. A capability with no cost attached looks like a feature you are proud of for no reason. The current-state cost earns the right to talk about the investment. The capabilities explain how the future state happens. The value comes from the future state, and the return comes from the value. Pull one link and the chain breaks.

Put it on one page

Most sellers carry this in their head and lose half of it in the room. The fix is to write it down before the meeting, in one view, so you can see where the story breaks before the CFO does.

That is exactly what the Value Story Canvas is for. One page, six boxes, the question to answer in each, and a short check to run before you send anything to the client. It is the six-chapter value story from the book Fly the Deal, turned into a tool you fill in for a live deal. Get the free canvas here.

Once the story holds, the next job is to say it in the room. For that, see how to present the case to a CFO in five slides, or bring the whole method to your team through value selling training.