Skip to content
CDO On-Demand
← All case studies

Replacing 35 disconnected systems with one analytics platform

A nationwide services business was running on 35 disconnected systems, which meant no comprehensive view of performance, invoice disputes that extended the cash collection cycle, and a reporting function that consumed enormous manual effort. Consolidating onto a governed Azure platform cut reporting labor by 70% and delivered around $12M in annual savings.

Client
National uniform and facility services company
Engagement
Data transformation program leadership

$12M

Annual cost savings from efficiency and predictive analytics

70%

Reduction in manual reporting labor

95%

Improvement in data accuracy against a single source of truth

The situation

A nationwide uniform and facility services business had grown into an estate of 35 disconnected systems. The consequences were felt well outside the technology function.

  • No comprehensive view of performance. Critical data sat in departmental systems with no standardized integration, so nobody could see the business whole.
  • Manual reporting at scale. Teams extracted data by hand, rebuilt reports in spreadsheets, and reworked numbers, which introduced error and steadily eroded confidence in the metrics.
  • Invoice disputes. Disconnected billing and service systems produced frequent invoice matching errors, generating disputes and extending the cash collection cycle.
  • Reactive customer management. Without integrated data the company learned about service problems when customers complained, and missed cross-sell opportunities entirely.

The approach

A governed foundation. An Azure Data Lake capable of ingesting structured and unstructured data from all 35 sources, with governance policies and security controls established at the outset rather than retrofitted.

Pipelines that standardize as they load. Azure Data Factory pipelines carried validation, cleansing, and standardization, so that inconsistent definitions across ERP, CRM, and operational systems resolved into one agreed meaning per entity.

Analytics for two different audiences. Tableau delivered pre-built executive and departmental dashboards alongside self-service capability for business users, while Databricks supported the predictive work: churn prediction, demand forecasting, cross-sell identification, and route optimization for service delivery.

The outcome

  • $12 million in annual savings, through operational efficiency and the predictive analytics the platform made possible.
  • 70% reduction in manual reporting labor, as automated dashboards and self-service replaced hand-built extracts.
  • 95% improvement in data accuracy, once a single source of truth removed the version-control disputes.
  • Near real-time refresh, which changed the tempo of decision-making across the leadership team.

What made it work

The program never attempted a single large cutover. It ran in phases beginning with core financial reporting and expanding into operational analytics and machine learning, with every phase designed to deliver something measurable. Business stakeholders sat inside the delivery team and evaluated each technical decision against operational impact, and change champions in each department carried adoption further than any training program would have on its own.

Why this is relevant to you

Business, technical, and program together.

The business lens

The board-level symptoms were invoice disputes stretching the collection cycle and customer attrition discovered only after complaints arrived. Those were the problems the program was funded to solve. The platform was the means, and keeping the conversation on collection days and retention rather than on architecture is what kept the funding through a multi-phase build.

The technical work

Thirty-five sources with inconsistent definitions is a master data problem before it is an ingestion problem. The pipelines carried validation, cleansing, and standardization so that a customer, a service visit, and a billable item meant one thing across the estate, which is the precondition for the churn and demand models that followed.

Program and organization

This ran as a phased program with business stakeholders embedded in the delivery team, change champions in each department, and role-specific training from executive dashboards down to operational reporting. Sequencing quick wins early built the momentum that carried the longer-horizon machine learning work.

Services

Data platform architectureETL and governancePredictive analytics

Stack

Azure Data LakeAzure Data FactoryDatabricksTableau

Have a similar problem?

If that resembles the situation in your own organization, a short call is the quickest way to establish whether the same approach would apply to you.