No graduate bench, no ramp-up, no kickoff workshop before anything happens. The people who diagnose and stabilise the platform are the same senior engineers who have done it before, on the ground within days of the call.
Why Recovery
For the moment it goes wrong.
Most enterprise DXP relationships do not end cleanly. They end with a missed release, a failed cutover, a security incident, or a slow erosion of trust until someone decides the supplier has to go. By the time the call comes, the platform is unstable, the internal team is exhausted, and a board-level conversation is happening about what to do next. Recovery is built for that exact moment. Not a sales pitch dressed as a diagnostic, and not a long discovery phase. Senior engineers on the ground in days, working a defined intervention with a fixed end.
The discipline is to fix what is actually broken, not to scope what would be profitable to fix. A crisis is not an opportunity to manufacture a large programme. It is a problem to be stabilised, honestly and quickly.
The discipline
You get a straight account of what went wrong and what state the platform is really in. The diagnosis is written to be put in front of a board, not to protect a commercial position.
Fixed scope, three to six weeks, a clear finish. Recovery is not an open-ended retainer. It restores the platform and hands you an honest map of the realistic options from here.
The method
Three phases. Fixed scope.
Senior-led from minute one. Recovery does not start with a kickoff workshop or a discovery period. It starts with triage, because the first job is to understand what is on fire and put it out.
01
Triage
Senior engineers establish what is actually happening: what is broken, what is at risk, and what is merely alarming. The platform is assessed under real conditions, fast, so the most urgent failures are understood before anything else is touched.
Output: Incident picture · Risk register · Immediate stabilisation plan
02
Stabilise
The urgent failures are fixed and the platform is returned to a stable, trustworthy state. The aim is a system the internal team can trust again, not a rebuild. Work is scoped to what restores stability, nothing more.
Output: Stabilised platform · Resolved critical issues · Restored confidence
03
Route
With the platform stable, you get an honest diagnosis and a route map of the realistic options from here. Ongoing support, a full move, or a long-term partnership. The recommendation is evidenced, and the decision is yours.
Output: Written diagnosis · Route map · Leadership readout
Recovery Three phases, fixed scope, a defined end. Phase 03 carries the lime mark
Fig 1 · Recovery Three phases, fixed scope, a defined end. Phase 03 carries the lime mark: the platform is stable and the route map is yours.
The terms
Fast in. Fixed end.
Senior-led, fixed-scope, with a defined finish. The terms are agreed before any work begins.
Days
Senior engineers on the ground
3 to 6 wks
End to end
Fixed
Scope agreed upfront
Senior
Engineers only, no bench
A stabilised platform
Returned to a state the internal team can trust again.
An honest written diagnosis
What went wrong and what state the estate is really in.
A route map
The realistic options from here, evidenced and prioritised.
A leadership readout
Written to go in front of a board, not to protect a position.
In practice
The call you make when it goes wrong.
Recovery is senior engineers on a real estate under pressure. The visual below is reserved for documentary photography of the practice at work, commissioned, never stock.
In within days
Senior engineers on the ground, working triage, while the team gets its footing back.
Holding quote · real attributable quote to be supplied before launch
James Andrews · Head of Delivery, TBSCGThe discipline is to fix what is actually broken, not to scope what would be profitable to fix.
Accreditations and platform partners
AWS Advanced Consulting Partner
AWS Advertising & Marketing Technology Competency
Magnolia
Contentful
Cloudinary
commercetools
Where the agentic lift happens
Triage at machine speed. Calls made by people.
Agentic tooling reads the telemetry, parses the logs and correlates the failure pattern at machine speed, so the first morning is spent on findings rather than trawling. The call on what to stabilise first stays with senior engineers, because that call is the whole job. The discipline behind it is the same one we apply to every AI capability we ship.
Questions
Frequently asked questions.
How quickly can you get involved?
Senior engineers are on the ground, on-site or remote, in days rather than weeks. Recovery does not start with a long discovery phase or a kickoff workshop. The first phase is triage, and it begins almost immediately.
What does Recovery actually fix?
What is actually broken, not what would be profitable to scope. Recovery restores a platform to a stable, trustworthy state. The discipline is to stabilise first and diagnose honestly, then give you a clear map of what comes next, rather than to manufacture a large programme out of a crisis.
How long does it take, and is the scope fixed?
Three to six weeks end to end, with a fixed scope and a defined end. The three phases, triage, stabilise and route, are agreed before work begins. There is no open-ended retainer and no scope creep built into the engagement.
Do we have to commit to a long-term relationship?
No. Recovery has a defined end and stands on its own. It is the most common entry point into a longer relationship with us, because of how it goes rather than because of any obligation. You own the findings and the route map, and you decide what to do with them.
What do we have at the end?
A platform restored to a stable state, an honest diagnosis of what went wrong, and a route map setting out the realistic options from here: ongoing support, a full move to a better platform, or a long-term engineering partnership. The choice is yours.
Where next
Once it's stable.
Recovery ends with the platform restored and an honest route map. Where it leads is your decision.
If you want it watched
24/7 Support Canopy
If it needs to move
DXP Replatforming The Banyan Method
If you want a partner
Long-term Partnership Grove
24/7 managed support. Senior engineers on warm bench, keeping the platform online so it does not fail again.
DXP replatforming. A full move to a better platform, in parallel, with you in control of the switch.
Long-term engineering partnership. Sustain, maintain, enhance, for the life of the platform.
Start here
Get senior engineers on it.
If the platform is unstable and the team is stretched, the first phase is triage and it can start in days. Fixed scope, a defined end, an honest diagnosis. You decide what comes after.