How to write a technology business case the board will actually approve
A technology business case that fails board approval usually fails for one of three reasons: it speaks technology rather than business, it makes claims it cannot evidence, or it does not address the risks the board is actually concerned about. None of these failures are about the quality of the underlying technology decision. They are about the quality of the communication.
Write for the CFO, not the CTO
Most technology business cases are written by people who understand the technology deeply and are presenting to people who do not. The natural instinct is to explain the technology: the architecture, the integration complexity, the migration approach. The board does not need to understand the technology. It needs to understand the financial return, the organisational risk, and the strategic rationale.
The CFO question is: what is this costing, when does it pay back, and what happens to the number if the assumptions are wrong? Every technology business case needs to answer that question clearly, with sensitivity analysis, before it goes to a board. If the break-even is year four on optimistic assumptions, say so and explain why the investment is still the right decision.
Do not bury the risk
Technology business cases often present risk in a section at the back of the document that no one reads carefully. Boards know this. Burying risk looks evasive and erodes trust in the rest of the document. The significant risks belong in the executive summary with mitigations, not in an appendix.
A board that discovers a significant risk that was not clearly surfaced in the business case will not approve the next business case easily. Transparency about risk builds the credibility that makes future investment easier to secure.
Base case, realistic case, optimistic case
Single-point financial projections in technology business cases are rarely believed by financially sophisticated boards. Presenting a base case on conservative assumptions, a realistic case on most likely assumptions, and an optimistic case on favourable assumptions demonstrates analytical rigour and gives the board a range it can evaluate rather than a number it is expected to accept.
The strategic rationale has to be explicit
Why now, why this, why us? The board needs to understand why this investment is the right use of capital at this time. Technology business cases that focus entirely on the internal case without addressing the competitive or strategic context miss the question the board is implicitly asking. If there is a compelling strategic reason to invest: regulatory change, competitive pressure, operational risk, it should lead the business case, not be mentioned in passing.
