The build that turned a Deloitte award into a business.

The Situation

A federal oversight mandate forced the client to split program management from service delivery — no vendor could hold both sides. Deloitte had won the management side: a sole-source vehicle with a $250M ceiling. On paper, a landmark award. In practice, worth zero — the ceiling converted to revenue only if the agency's business units sent work through it, and those units had just been forced to surrender vendors they trusted. Five multi-million-dollar programs in distress transferred on day one. The operating engine that would run them had thirty days to exist.

Why It Mattered

There was no gap between sale and execution — delivery started ahead of the engine built to run it. Five live programs operated under the vehicle's name from day one, judged by units looking for their reason to route around it. A single visible stumble in the first wave would have set the pattern, and the ceiling would have stayed what it was at award: a number on paper. The engine had to stabilize distressed work immediately, in plain view of skeptics, and scale without the bench drag, contracting friction, or process overhead that would hand them their reason. It did — the first wave landed without a misfire.

What Was Actually Breaking

The visible problem was missing infrastructure — no team beyond the capture group of seven, no operating model, no commercial structure, no execution controls.

The real problem was that the standard playbook for building a professional-services business would have failed on contact. It assumes time, sequencing, and slack. None existed. Bench hiring would have burned cash ahead of demand that hadn't committed. Sequential contracting would have stalled conversion while skeptical units watched the clock. Heavy methodology would have added drag at the precise moment the business had to be fast, controlled, and credible — all three at once, from day one.

What Changed

As deputy program manager, the operating engine was mine to build — the processes, the operationalizing, the scaling. The standard build would have lost the race. I built just enough operating engine to convert demand into delivery immediately, then scaled it without adding the weight that would have broken it.

• Built modular service packages and standard deal language so work moved into delivery in days, not after contracting cycles the skeptics could point to

• Tied hiring to visible demand so capacity scaled with real work instead of burning cash on a bench

• Built a live delivery picture from the units' own tracking data, so no one could run a private narrative against numbers they themselves produced

• Enabled delivery data to tell its own story, good or bad — but every report arrived with a roadmap for what came next. Oversight became a path forward instead of a verdict, and skeptics became senders of work.

The Result

Scaled the business from a standing start to a $36M annual run rate in 30 months — with the technology business growing at a 68% CAGR — and it held. Grew the organization from 5 to 140 people in 24 months. Raised project success rates from 62% to 84% across a portfolio that began with five distressed programs. The work produced $1.8B in validated, audited client benefits.

Approaching the end of the base term, the client — the same organization whose units had resisted the vehicle — exercised every option year available. The engine ran for 3.5 years after my departure.