CCaaS ROLLOUT
TURNAROUND

A REPLACEMENT FOR A 20-YEAR-OLD LEGACY PLATFORM

The client was replacing an unsupported, custom-built customer contact platform with a Call Centre as a Service solution from a young technology provider still operating with a start-up mindset. That brought real strengths: speed, flexibility and the ability to configure custom capabilities. It also brought weaknesses: inconsistent standards, limited delivery discipline and a reluctance to push back on bespoke requests. The first rollout was already well behind schedule, with a hard legacy-support deadline approaching in mid-2026. Strategically, it was one of the provider's most critical programmes in EMEA: failure would have damaged confidence well beyond this individual client.

A PROGRAMME WITHOUT A RELIABLE DELIVERY SYSTEM

I inherited a programme in month 11 of an intended 12-month rollout, but no service had been signed off by the client. Requirements and documentation were incomplete, roles were unclear, workstreams were not defined, the backlog was unreliable and releases were reaching production without adequate testing. The German-speaking client team and largely non-German-speaking provider team also had to bridge a significant language and working-culture gap. A core team of 15 was largely junior, inexperienced and part-time, with additional specialists brought in only at peak points.

ESTABLISH THE FACTS, THEN REBUILD CONTROL

I began by meeting the dispersed team, assessing programme maturity and learning the CCaaS solution quickly enough to lead credibly. My formal reporting line was to the VP of Professional Services for EMEA, with an informal line into the SVP for Customer Success and Technical Account Management, reflecting the wider ambiguity around ownership. I had no formal authority to change staffing or priorities, so I used evidence, clear escalation and practical influence to secure more senior presence and focus.

I moved team meetings away from complaints about the client and towards content, commitments and decisions. I clarified roles and responsibilities, held people accountable for their outputs, created a structured backlog and prioritisation approach, introduced a PM/PMO cadence, and improved communication with senior client stakeholders.

A WORKABLE PROGRAMME WAS HANDED OVER

After 2.5 months, the programme had a realistic roadmap, transparent risks and issues, defined workstreams, clearer staffing requirements, a test-management process and honest status reporting. A first batch of services was brought live and accepted by the client. The client relationship moved from open threats to terminate the engagement towards a willingness to work together. I handed over a functioning programme structure to a newly hired internal Program Manager.

STABILISATION IS NOT THE SAME AS A MIRACLE

The programme was stabilised, not magically completed. At handover, the roadmap remained ambitious, the operating model was not yet sustainable, qualified people were a critical dependency, complex-service documentation was incomplete and client trust was still fragile. The value of the intervention was an honest perspective, a clear path back to delivery and the foundations for a good outcome under severe time pressure.