← Back to news

Your Board Wants ROI in Six Months – Your Contact Center Needs Eighteen

The board-floor gap in enterprise contact center AI deployment has become the defining tension in CX transformation, driven by a fundamental misalignment between investor expectations and operational reality. Boards are anchoring their timelines to high-profile success stories—Salesforce's $100 million in annualised savings through Agentforce, Klarna's 700-agent equivalent automation, Octopus Energy's 44% email automation—whilst investors now expect positive ROI within six months. Yet MIT NANDA's 2025 research reveals that only 5% of integrated AI pilots actually extract measurable value at scale, with meaningful contact center AI deployment typically requiring four to eighteen months before genuine operational impact. The remaining 95% stall at proof of concept, trapped in a cycle where pilots never reach production and ROI conversations perpetually defer to the next quarter. This is not a technology readiness problem; it is a structural mismatch between two incompatible conversations happening in the same boardroom, where CX leaders are being asked to commit to timelines they know are unrealistic and success metrics that remain undefined.

The danger lies not in moving slowly but in moving without operational discipline. Klarna's cautionary tale—where aggressive automation reduced headcount from 5,500 to 3,400 before the CEO admitted the approach had produced "lower quality" service and began rehiring—demonstrates how cost-first thinking without clear success criteria produces spreadsheet wins and customer relationship losses. The pressure to hit six-month targets without defining what success actually means creates structural conditions for failure, where pilots are designed to disappoint rather than deliver. For CX leaders already managing stretched teams and data estates requiring remediation, this pressure compounds the complexity of knowledge hygiene work, integration challenges, and change management that rarely appear in original business cases. The organisations closing this gap are approaching it differently: they promise proof delivered in sequence rather than transformation borrowed from vendor case studies, building durable confidence through realistic twelve-month roadmaps that compress timelines without cutting corners. For teams running Agentforce or evaluating similar platforms, the question becomes not whether to automate, but whether your organisation has the data readiness, operational discipline, and board alignment to execute a deployment that actually reaches production rather than stalling in perpetual pilot mode.