A business case should survive a finance review

A business case written only for the enthusiastic sponsor can fail when finance asks basic questions. Which benefits are incremental? When do they arrive? What investment is required? What happens if adoption is slower than expected?

Separate the mechanism from the number. If the proposed work reduces time spent on administration, explain how that time becomes a business benefit. Released capacity, lower external spend and reduced headcount costs are different outcomes. Do not count all of them from the same saved hour.

Make timing visible. Costs may arrive before benefits, and benefits may depend on changes outside the engagement. A simple monthly view can be more informative than a large annual return figure.

Include a conservative scenario. If the case only works when every assumption is favourable, the buyer should know. Sensitivity analysis need not be elaborate: change the adoption rate, delay the benefit and increase implementation effort to see which assumption matters most.

Invite the client's finance or operating owner to validate inputs. The adviser can provide structure, but the organisation often holds the information needed to make the case credible.

The document should also identify benefits that remain qualitative. Improved confidence or clearer accountability may be valuable without an invented financial value. Leaving a benefit unmonetised is preferable to assigning it a number that cannot be defended.