Value beyond the subscription price
A technology business case should compare a proposed change with the real current position and credible alternatives. It must show which benefit matters, what it will cost to reach it and which assumptions could make the decision fail.
Measure the current cost and performance first. Estimate benefits conservatively, include setup, migration, internal effort, integrations, training, support, usage, renewal and exit, then test best, expected and adverse scenarios. Assign an owner to every material assumption.
Build the model in seven blocks
- Baseline: record current volumes, errors, waiting time, staff effort, supplier costs, workarounds and risk exposure.
- Options: compare doing nothing for now, improving the present system, changing process and buying or building alternatives.
- Benefits: connect each claimed improvement to a measure, starting value, realistic target, timing and accountable owner.
- Whole-life cost: include evaluation, setup, configuration, data work, training, operation, support, change, renewal and exit.
- Capacity: identify people, skills, decision time and operational work that the organisation must supply.
- Risk and uncertainty: show ranges, dependencies and the consequence if adoption, volume, price or delivery differs.
- Decision and review: state why the preferred option wins and when evidence will be checked after implementation.
Calculate total cost before claiming a return
Expected case
Use the most defensible adoption, delivery, benefit and cost assumptions, with sources recorded.
Adverse case
Test slower adoption, a delayed launch, higher migration effort, price change or an important integration failure.
Decision threshold
State the maximum cost, minimum benefit or latest delivery date at which the preferred answer changes.
Do not monetise what you cannot support
Keep financial savings, capacity released, risk reduction and service quality visible as separate benefits. Do not count the same saved hour both as a cash saving and as new productive capacity unless the organisation can show how each is realised.
The GOV.UK Service Standard asks teams to understand total cost of ownership and preserve the ability to make different choices in future. The principle applies beyond government even though the standard itself is written for government services.
Business case and total-cost FAQs
What costs are commonly missed in a technology business case?
Internal staff time, data cleaning, migration, integrations, identity setup, training, temporary parallel operation, support, usage growth, price changes, specialist assurance, downtime and exit work are often outside the headline licence price.
Should every benefit be converted into money?
No. Quantify what can be supported, but keep service quality, resilience, accessibility, risk and compliance outcomes explicit rather than forcing an invented cash value. The decision should show how each material benefit will be evidenced.
How far ahead should total cost be modelled?
Use a period that covers implementation, a representative operating cycle and a realistic renewal or replacement decision. Test more than one horizon where contract length, growth, support life or exit timing could change the preferred option.
Continue your business technology decision
Use the next guide that matches the requirement, investment, supplier, implementation, migration, access, continuity or renewal question you still need to resolve.
