Business Case · Enterprise 02 / 06

Building the $2M case for platform consolidation

Three tools, three bills, and three sets of frustrated users. Here's how I structured the argument that got a $2M investment approved.

$2MInvestment secured
3.2×Projected ROI
6 wkFrom kickoff to approval
1stBoard meeting presented

The company had grown through acquisition and organic expansion. The result: three overlapping tools doing roughly the same job, three separate contracts, and an internal team that had learned to hate all of them equally.

Engineering wanted to consolidate. Finance wanted the savings. But nobody had made a compelling, board-ready case — and without that, nothing would move.

I was asked to own the business case end-to-end: the analysis, the stakeholder alignment, the written document, and the board presentation. I had six weeks and a part-time data analyst.

I started by mapping the actual cost of the status quo — not just the contract values, but the hidden costs: engineering time spent maintaining three integrations, support load from users context-switching between tools, and the opportunity cost of not having a single source of truth.

The hidden cost was bigger than the contracts. License costs were $340K/year combined. But when we added engineering overhead, support time, and duplicated data management, the true annual cost was closer to $890K.

01
Cost analysis. Full TCO for the current state, including soft costs. This reframed the investment from "we want to spend $2M" to "we're currently losing $890K/year staying still."
02
ROI model. Conservative, base, and optimistic scenarios. I used the conservative case in all presentations to build credibility.
03
Risk register. Identified the top 5 risks (migration data loss, user adoption, vendor lock-in, timeline overrun, integration failure) and mitigation for each.
04
Phased roadmap. 3 phases over 18 months. Phase 1 decommissions the least-used tool and delivers the first ROI signal within 6 months.
The board deck

Presentation deck

In Google Slides: File → Share → Publish to web → Embed tab → copy the src URL and paste above.

Open presentation ↗

The full business case presentation as delivered to the C-suite and board. Includes ROI model, risk register, and phased roadmap.

Before the board presentation, I ran three rounds of stakeholder reviews: engineering leads, finance, and the heads of the two main user teams. Each session surfaced objections that I incorporated into the document. By the time the board saw it, the key internal stakeholders were already aligned.

"A business case that surprises the board has already failed. The real work happens in the weeks before the room."

$2MApproved

Full Phase 1–3 budget secured at first board presentation.

3.2×Projected ROI

Conservative case, 3-year horizon.

18 moTo full consolidation

Phased to hit first savings milestone at 6 months.

Business cases fail for two reasons: they're not credible (the numbers look made up) or they're not aligned (someone important was surprised in the room). I've found that doing the alignment work first — even before you have all the numbers — makes the case stronger because you're incorporating real objections, not anticipating hypothetical ones.

Using the conservative scenario as my headline number was a deliberate choice. It invited scrutiny rather than avoiding it, and it meant every challenge in the room was one I'd already addressed in the document.

← All work
Next case study
0→1: The feature that became the #1 activation driver →