STEP 5
The Business Case (Template 8)
The honest version — where the recurring cost is genuinely higher, and the case is made anyway.
This is the part most people get wrong. A managed service usually costs more in cash terms than break‑fix, and a business case that pretends otherwise falls apart the moment a finance manager reads it. The case is built on avoided capital spend, removed risk, and reclaimed billable time — stated plainly, with the arithmetic shown. Figures are in generic currency units — the shape of the arithmetic is the point, not the specific numbers.
| Current state — annual | Amount |
|---|---|
| Break‑fix contractor invoices (12‑month actual) | $68,000 |
| Cyber insurance loading (no MFA / untested backups) | $14,000 |
| After‑hours and weekend recovery work | $9,000 |
| Billable time absorbed by two engineers acting as unofficial IT | $51,500 |
| Recurring cost of the status quo | $142,500 |
| Pending file server replacement (quoted, due this budget cycle) | $46,000 capex |
| Outage exposure — 3 significant outages in 18 months, ~$38,000 average | ~$76,000/yr annualised |
| Proposed — annual | Amount |
|---|---|
| Managed IT — 92 seats @ $95/seat/month | $104,900 |
| Security stack (MFA, EDR, email security) — 92 @ $28/month | $30,900 |
| Backup & DR — servers and Microsoft 365 | $13,800 |
| Microsoft 365 Business Premium uplift — 92 @ $12/month | $13,200 |
| Recurring total | $162,800 |
| Transition and cloud migration (one‑off, year one only) | $34,000 |
The ArithmeticAssumptions stated, both cases shown
Year one
Proposed $196,800 vs status quo $142,500 = $54,300 more cash out.
The insurance loading is already inside the $142,500, so its removal is captured in that difference — it is not an additional offset. The one genuine offset in year one is capital: the $46,000 server replacement that no longer happens.
Net before counting any outage reduction: $8,300 behind.
Year one, conservative case
Assume outages reduced by 50% only: +$38,000 → net benefit ≈ $29,700. Payback inside year one.
Year one, aggressive case
Assume outages reduced by 85%: +$64,600 → net benefit ≈ $56,300.
Year two onward
$162,800 vs $142,500 = $20,300 more cash out, with the insurance removal already inside that figure. Offset by the conservative outage reduction of $38,000 → net ≈ $17,700/yr conservative, $44,300 aggressive.
Not counted in any of the above
Dave's redeployment to the stalled document management project. We deliberately left it out of the numbers and mentioned it in one sentence — an unquantified benefit stated modestly is credible; the same benefit with a number attached invites an argument you can't win.
Assumptions, stated on the page
Charge‑out rate $140/hr (theirs). Outage average from their own incident recollection, not our modelling. Seat count 92 with ±5 tolerance before repricing. Insurance loading removal confirmed by their broker in writing, not assumed.
The double‑count trapThe most common error in a business case shaped like this one is counting a saving twice — once by putting the cost inside the status‑quo total, and again as an offset against the new spend. If a cost appears in the current‑state column, its removal is already in the difference between the two totals. Only items sitting outside both totals are offsets: avoided capital, avoided risk. A finance manager finds this in about ninety seconds, and finding it discredits every other number on the page.