Executive leadership in the AI era has a data problem, not an ambition problem. More than half of CEOs report that AI has delivered neither higher revenue nor lower costs over the past year, according to PwC's 2026 Global CEO Survey. Separate research from MIT's NANDA initiative found that 95% of enterprise AI pilots failed to produce a measurable impact on the P&L within six months. These aren't small numbers, and they say less about the limits of AI itself than about the systems it's being layered onto.
The pattern shows up repeatedly across organisations: a finance team adopts an AI forecasting tool, HR rolls out an AI-assisted hiring workflow, and marketing brings in a content generation platform. Each tool performs well in isolation. Few of them share data with one another, which means each is working from a partial view of the business. Leadership teams end up with more AI capability but not necessarily more clarity.
For a growing number of organisations, the fix isn't another AI tool. It's Microsoft Dynamics 365, used as the connective layer that everything else sits on.
The AI Era Paradox: High Investment, Uneven Returns
Executive appetite for AI is not in question. The Conference Board's 2026 C-Suite Outlook Survey found that 43% of respondents named AI and technology as their top investment priority for 2026, ahead of product innovation and customer experience. Microsoft's own disclosures show the scale of enterprise AI rollout: Microsoft 365 Copilot has crossed 20 million paid enterprise seats, and more than 60% of Fortune 500 companies now run at least 10,000 Copilot seats each.
Investment and deployment, however, aren't translating evenly into results. WRITER's 2026 Enterprise AI Adoption survey of 1,200 C-suite executives found that only 29% report significant organisational ROI from generative AI, even though 92% see individual productivity gains. The gap between individual usefulness and organisational return is where most leadership teams are currently stuck.
A large share of that gap traces back to fragmented data. When sales, finance, and operations run on separate systems, AI tools can only ever answer questions using the slice of information they have access to. The output looks confident. It's often incomplete.
Why Executive Leadership, Not IT, Now Owns This Problem
AI has moved up the executive agenda quickly. LHH's 2026 View from the C-Suite report found that digital and emerging technology rose seven places in a single year to become the top perceived leadership skill gap, with 49% of executives naming AI and emerging technology a top development priority. That's a shift from AI being a technical initiative managed by IT to a core executive responsibility.
The organisations seeing measurable returns tend to share one trait: they addressed data fragmentation before layering on AI. Finance, sales, operations, HR, and customer service run on one connected platform, so that whatever AI tool sits on top of it, Copilot or otherwise, has a complete and consistent data set to work from.
This is the role Dynamics 365 plays for many of these organisations.
What a D365 Backbone Actually Changes
Dynamics 365 provides a shared data model across core business functions, rather than separate databases for each department. In practice, this means sales, finance, and operations teams are working from the same real-time data, and any AI layer built on top of it, including Microsoft Copilot, which is now deeply integrated across the D365 suite, can draw on the full picture rather than a single department's slice of it.
Some concrete examples of what this enables:
- Finance teams get forecasting built on live operational data rather than a static end-of-quarter export. Early enterprise pilots of Excel Copilot, built on connected data, reportedly improved financial modelling workflows by 30-40%.
- Sales teams get pipeline visibility that already accounts for supply chain and finance constraints, rather than working from sales data alone.
- HR teams get workforce planning tied to actual business performance data, not a standalone HR system disconnected from the rest of the organisation.
- Customer service teams get full context on each customer's order history, billing status, and prior support tickets, because that information lives in one system rather than three.
None of this requires an executive team to become AI specialists. It requires treating data unification as a leadership priority rather than a background IT task.
The Real Difference Between an AI Tool and an AI Backbone
Industry data on AI-driven process automation shows real gains are achievable: connected automation initiatives are delivering roughly 40% reductions in processing time in enterprises that have unified their core systems, per recent CEO-level research. The gap between the 56% of CEOs reporting no measurable AI return and the organisations pulling ahead isn't primarily about budget or ambition, both groups are investing heavily. It's about whether AI sits on top of one connected system or a patchwork of disconnected tools.
An AI tool answers one question well. An AI backbone makes every tool built on top of it answer questions better. Executive leadership in the AI era increasingly means asking a more fundamental question before the next AI purchase: does the business run on a foundation that AI can actually use well? For many organisations, that answer starts with unifying the systems their core business functions run on.
If your organisation is evaluating what a connected, AI-ready foundation actually looks like, book a 30-minute D365 fitment call with Dynamics Monk's implementation team. We work with leadership teams across the UK, UAE, Australia, and Southeast Asia on exactly this transition.
