A business case answers one question for the sponsor: is the change worth doing? It sets out:
- the problem or opportunity, and the options (including doing nothing);
- the costs: one-off (build, training, migration) and running (licenses, support);
- the benefits: money saved or earned, and non-money benefits such as risk reduced;
- the numbers: net benefit (benefits minus costs over a period), payback period (how long until cumulative benefits cover the costs) and ROI (net benefit ÷ cost, as a percentage);
- the risks and the recommendation.
Benefits rarely start on day one: people need time to adopt a new process. A business case that counts full benefits from go-live is optimistic. Show when benefits begin, and be honest about which ones are estimates.
Every benefit needs an owner who will be asked, after go-live, whether it arrived. That is where the business case meets solution evaluation.
The numbers in a business case.