Main content

AI cannot fix a broken data foundation — and most services firms have one

By Raju Malhotra April 10, 2026

Your browser doesn’t support HTML5 audio

Dyslexia mode
Excerpt:
Certinia's Raju Malhotra argues that most professional services firms are investing in AI before they have fixed the data problems underneath it. Here is why that is backwards and what to do instead.

(©AndreyPopov - canva.com)

Growing a professional services firm is a lot like building a house. You wouldn't hire five different contractors who've never met, give them five different sets of blueprints, and expect a livable home.

In a poorly orchestrated project, the plumber installs high-end fixtures exactly where the plans say. Only then to have the electrician tear out the drywall the next day because nobody planned for the HVAC unit. Each contractor is technically successful in their own silo, but the project ends in rework, blown budgets, and a foundation that can't support a second floor.

This is the data reality for many growing services firms pursuing AI transformation. Gartner estimates that organizations lose an average of $12.9 million annually due to poor data quality and siloed information.

This lack of data quality erodes trust at the leadership level, and the numbers are striking. According to diginomica’s 2026 Enterprise Data Health Study, when senior practitioners were asked what percentage of data they would pass to their CEO without checking it first, the most common answer was close to zero. That verification burden is already consuming 30% to 70% of people's time in manual reconciliation, before AI enters the picture at all. Layering AI onto a disconnected data stack means automating insights that the organization itself has little confidence in.

What is fragmentation debt and why it stops AI from working

When firms try to leap from mid-market to enterprise scale, they usually hit a wall. The culprit is rarely talent, ambition, or capital. It’s fragmentation debt.

Fragmented data creates cascading failures across your entire delivery lifecycle. If your project margins are calculated in a spreadsheet that finance doesn't see until three weeks after a milestone, your AI is training on fiction. By the time your predictive tool flags a resource leak, the margin has already evaporated.

Bolting AI onto a disconnected stack compounds the problem rather than solving it. You end up automating bad decisions at scale. The 2025 Global Service Dynamics Report found that high-performing organizations (those hitting 40% EBITDA margins) don't necessarily have more sophisticated AI than their peers. They have the data discipline to make AI useful. Standardization is the bedrock, and without it, you're just moving messy data around faster.

The architectural paths to AI-ready data

There are three common approaches firms take toward data unity, and in practice, the most effective path often draws on some combination of all three.

Data lakehouses can play a meaningful role in targeted areas of the business — consolidating reporting or analytics for a specific function, for instance — though implementing them enterprise-wide is difficult and often results in stale data that is hours or days old, a real liability in a services business where resource availability changes by the minute.

Data federation allows AI to query across silos without moving data. It reduces some friction and can serve as a useful bridge in parts of the organization, but often remains a read-only solution that struggles to take real-time action where it counts.

The most powerful anchor of this strategy is a platform approach consolidating core workflows onto a single architecture (or at minimum, dramatically reducing the number of platforms) so there is far less data to move or map in the first place. Not all firms can realistically consolidate onto one platform enterprise-wide, but shrinking to a tightly controlled set changes the equation significantly. This is what enables AI to shift from summarizing information to acting on it, such as triggering resource requests, adjusting billing, executing workflows, because it has write access to a unified, trustworthy system.

Where data hygiene is high, as SPI Research has documented in CRM and PSA environments, AI delivers measurable performance gains. Where the foundation is fragmented, the technology stalls regardless of how sophisticated the model is.

Three operational shifts for services leaders who Want AI to deliver

From chat to action.Treating AI as a tool that answers questions leaves most of its value on the table. Hard ROI comes from specialist AI agents that understand the services math behind your business — margin calculations, resource constraints, billing rules — and can execute against them autonomously.

From integration to architecture. The greatest threat to AI effectiveness is the brittle act of gluing AI onto a legacy stack. Consolidating workflows onto a unified platform eliminates integration friction and gives AI the continuous context it needs to drive outcomes rather than just observe them.

From probabilistic to deterministic.Generic AI models lack business context, which leads to hallucinated project P&Ls and misinterpreted revenue rules. High-performing firms are moving toward rules-bound AI trained on real-world services data, where every action is auditable and governed by the specific logic of the business.

How to assess whether your services business is actually AI-ready

Most leaders of growing services businesses believe they're ready for AI. The more useful question is whether their data foundation is ready for it. The firms making real progress understand that architectural discipline is what makes AI capability useful in the first place.

A good place to start is an honest assessment of where your biggest risks actually live — your data and architectural integrity, value chain connectivity, and operational scalability. A cold-eyed audit of those three dimensions will tell you whether your systems are positioned to support the AI roadmap you're planning, and where to focus before you commit to the next phase of it.

Disqus Comments Loading...