Case Study 2 — Deep Dive: The Business Case That Forgot to Price "Do Nothing"

A note on accuracy. Composite, fictional-but-realistic. The company (a regional e-commerce retailer), the people, and the numbers are invented to illustrate how an options analysis succeeds or fails. Nothing here is a real organization's data.

The situation

Daniel Osei led platform engineering at a regional online retailer. The company's order-management system ran on hardware in a leased data center—aging servers, a manual failover process, and a lease coming up for renewal. Daniel knew the company should move to a managed cloud service, and he was right. But his first business case nearly died in committee, and the reason is instructive: he built a one-sided pitch and called it a business case.

The first attempt — a pitch in a business case's clothing

❌ Before (no real options, no cost of inaction):

We should migrate our order-management system to CloudHost. CloudHost is a leading managed platform with excellent reliability and scalability. The migration would cost $260,000, and it would modernize our infrastructure, reduce our operational burden, and prepare us for future growth. We strongly recommend proceeding.

The committee's reaction was predictable and fatal. The CFO asked the cheapest possible question: *"What happens if we just renew the data-center lease and keep running what we have? That's a lot cheaper than $260,000."* Daniel didn't have a number. He said the current setup was "risky" and "hard to maintain," which sounded—to a CFO weighing a concrete $260,000 against a vague "risk"—like an engineer wanting a shinier toy. The business case was tabled.

The failures map exactly to §20.3:

  • No options. A single recommendation ("migrate to CloudHost") with no alternatives reads as a sales pitch, and decision-makers distrust pitches.
  • No "do nothing" baseline. The most important comparison—migrate vs. stay put—was never made, so the committee couldn't see whether $260,000 was a good deal or a bad one.
  • Unquantified value. "Reduce operational burden," "prepare for growth"—invisible to a numbers-driven reader (§20.10).
  • Benefits, not consequences. Nothing made the committee feel the cost of the status quo.

The rebuild — a genuine options analysis

Daniel went back and did the work the CFO's question demanded: he priced every path, including doing nothing, and put them on the same axes.

✅ After (four options, same axes, "do nothing" priced):

We evaluated four paths for the order-management system over a three-year horizon, comparing total cost and operational risk:

Option 3-yr total cost Operational risk Notes
Do nothing (renew lease, keep current hardware) **~$520K** | **High** | Lease renewal + aging-hardware replacement + manual failover. One extended outage during peak could add $200K+ in lost orders.
Renew lease, refresh hardware $410K Medium Buys ~4 years, but we still own failover, patching, and capacity planning.
Build private cloud in-house $480K Medium-High Full control; 10-month build; we own all maintenance and on-call.
Migrate to CloudHost (managed) $340K Low Automated failover, elastic capacity, vendor-owned uptime; 12-month payback vs. "do nothing."

We recommend migrating to CloudHost. Once the true cost of the status quo is counted—lease renewal, an unavoidable hardware refresh, and the outage risk during peak season—it is the lowest-cost option over three years, not the most expensive, and it carries the lowest operational risk.

Why it's better: The reframe is the whole story. In the "before," $260,000 looked like a *new expense* set against a free status quo. In the "after," the status quo is correctly priced at ~$520,000 (because "doing nothing" isn't free—it means renewing the lease, replacing dying hardware, and absorbing outage risk), which makes the $340,000 migration the *cheaper* path. The CFO's killer question—"why not just stay put?"—is now answered *in the document, before it's asked*, with a number. And because the committee can see four options on two consistent axes, the recommendation reads as the survivor of a fair comparison, not as Daniel's pet project. (The migration's total even rose from the pitch's $260K to a more honest $340K once Daniel included migration labor and parallel-running costs—and the more honest, higher number was more persuasive, because it survived scrutiny.)

Why the cost of inaction is so often the decisive number

Notice what carried the decision: not the migration's benefits, but the cost of the alternative everyone defaults to. This is a pattern worth internalizing. Decision-makers have a strong bias toward inaction—doing nothing feels safe, free, and reversible. Your job, when the status quo is genuinely costly, is to put a price on it. "Doing nothing" almost never actually means spending zero; it means accepting ongoing costs and rising risks that simply aren't on anyone's spreadsheet yet. Surface them, quantify them, and the comparison often flips.

This is also why a single honest, higher cost can beat a lowball. Daniel's rebuilt case asked for more money than his pitch ($340K vs. $260K) and was more likely to be approved—because the number was defensible and the comparison was fair. A business case earns trust by showing its work; a pitch asks for faith, and experienced committees don't give it.

The lesson

A business case is not "the case for the thing I want." It is an honest comparison of the realistic options—including the option of doing nothing—decided on the same axes and justified by the numbers. The move that rescued Daniel's case was the one his pitch skipped: pricing the status quo. When you find yourself writing "this is risky and hard to maintain," stop and put a number on the risk and the maintenance, then set it beside your proposal's cost. More often than you'd expect, the most persuasive figure in the whole document is the cost of changing nothing at all.

Related: Chapter 20 §20.3 · Case Study 1 · Further Reading