Supplier-exit platform stabilisation

What was on fire when Localhost arrived

A UK client platform was still carrying weekday traffic after the previous delivery partner had stepped away. Leadership could see symptoms (missed releases, unclear ownership of integrations, rising incident noise) but not a trustworthy picture of what was salvageable versus what needed a controlled rebuild.

What the Rescue spike owned

Localhost ran a time-boxed engagement with a named outcome: a written risk picture across the live path, a short stabilisation plan for the highest-impact failures, and a clear recommendation for the next commercial shape. Specialists were matched to the stack under one Localhost contact, not dropped in as interchangeable capacity.

What the client could decide afterwards

The public-safe residue is the decision itself: continue as fixed-scope Build where the done definition was finally clear enough to sign, move into Managed Service where ongoing ownership was the real gap, or stop before more budget followed an unrecoverable path. Client identity stays unpublished; the useful proof is the Rescue pattern, not a logo.