The vendor AI landscape
Every major HR technology vendor has shipped or announced an AI assistant in the past two years. SAP has Joule. Workday has the Workday Assistant (and the broader Illuminate platform). Microsoft has Copilot. Oracle has AI agents embedded in HCM Cloud. ServiceNow has Now Assist. Each represents a significant engineering investment and a genuine step forward in usability.
But each one has the same structural constraint: it can only see the data inside its own platform.
Joule can answer questions about data in SuccessFactors. It cannot see what is in your Workday instance, your Greenhouse ATS, your Culture Amp engagement surveys, or your LinkedIn Recruiter pipeline. Workday Assistant can reason about Workday data. It is blind to SAP, ServiceNow, and your learning platform. Copilot sees the Microsoft graph – emails, calendar, documents, Teams messages – but knows nothing about your HCM data.
This is not a bug. It is architecture. Each vendor built its AI to serve its own ecosystem. And within that ecosystem, these assistants are genuinely useful. The problem emerges when you ask them to do what agents need to do: reason across the full picture.
Why single-system intelligence falls short
Consider a straightforward workforce question: “Should we be concerned about attrition on the data engineering team?”
To answer this well, an agent needs to assemble context from at least five sources:
| Data point | Where it lives | What it reveals |
|---|---|---|
| Compensation vs. market | HCM + market data provider | Are we paying below market? |
| Engagement trends | Survey platform | Are scores declining over time? |
| Internal mobility activity | Talent marketplace / HCM | Are people looking for new roles? |
| External job market signals | Market intelligence | Are competitors hiring for these skills? |
| Manager effectiveness | 360 feedback / engagement tool | Is the manager a factor in attrition risk? |
| Learning completion | LXP / LMS | Are people investing in growth or checked out? |
| Recent org changes | HCM / HRIS | Has the team been restructured recently? |
No single system holds all of this. A vendor AI assistant answering from one system gives you a partial answer at best, and a misleading one at worst. Workday might report that compensation is at market – but without engagement data or external signals, it misses the full picture. Joule might flag a performance trend – but without compensation context, the recommended action could be wrong.
Partial answers lead to poor decisions
The danger of single-system intelligence is not that it gives wrong answers. It is that it gives incomplete answers that feel authoritative. When an AI assistant confidently says “attrition risk is low” based solely on compensation data, a manager might stop investigating – missing the engagement decline and external market pressure that tell a different story.
Consider two scenarios for Tomoko, an HR director overseeing engineering teams:
Single-system answer: Tomoko asks the HCM assistant about attrition risk. It reports that compensation is within range, recent performance reviews are satisfactory, and no one has submitted a resignation. Conclusion: risk is low. Tomoko moves on to other priorities.
Cross-system answer: An agent with access to multiple systems reports that while compensation is at market, engagement scores on the team have dropped 18% over two quarters, three team members have updated LinkedIn profiles in the past month, two competitor companies have posted 15 data engineering roles in the region, and the team's manager has the lowest effectiveness scores in the engineering org. Conclusion: risk is high, and here are three recommended interventions ranked by likely impact.
Same question. Radically different quality of answer. The difference is not intelligence – both AI systems are capable. The difference is context.
The vendor incentive problem
There is a structural reason why vendor AI assistants are unlikely to solve this on their own: the business model incentive points the wrong direction.
SAP wants you to consolidate onto SAP. Workday wants you to consolidate onto Workday. Microsoft wants everything in the Microsoft graph. Each vendor's AI strategy is designed to make its own platform stickier, not to be a neutral orchestrator across competitors' systems.
This is rational business strategy, but it creates a gap. The AI assistants get smarter within their own data domain, and the space between systems – where the most important workforce context lives – remains unaddressed.
Integration platforms like Workato and MuleSoft can move data between systems, but they do not reason over it. They are plumbing, not intelligence. What is missing is a layer that both connects to multiple systems and reasons across the assembled context.
What cross-system context enables
When an agent has access to a unified context layer – a component that reads from multiple systems, normalizes the data, and makes it available for reasoning – entirely new categories of action become possible:
- Proactive retention that correlates compensation, engagement, external market, and behavioral signals before an employee starts interviewing
- Intelligent internal mobility that matches people to opportunities based on skills, career interests, team needs, and organizational priorities – not just job title keywords
- Workforce planning that accounts for supply (current skills), demand (strategic priorities), market conditions (talent availability), and financial constraints (budget) simultaneously
- Onboarding orchestration that coordinates actions across HCM, IT, learning, facilities, and team communication without requiring a human to manage each system individually
None of these are possible with single-system intelligence. Each one requires the agent to see across boundaries that vendor AI assistants cannot cross.
The integration layer is not enough
Some organizations attempt to solve this with integration platforms – tools like Workato, MuleSoft, or Boomi that connect systems and synchronize data. These are valuable infrastructure, but they address a different problem. Integration platforms move data between systems. They do not reason over it.
Synchronizing compensation data from Workday into a data warehouse does not create the intelligence to detect that a specific employee is a flight risk. Piping engagement survey results into the HCM does not generate the insight that declining engagement combined with below-market compensation and increasing external demand for a person's skills constitutes an urgent retention situation. The plumbing is necessary but insufficient.
What agents need is not just data connectivity. They need a layer that assembles context from multiple sources, normalizes it into a unified model, and makes it available for real-time reasoning. This context layer must understand that “Software Engineer III” in Workday and “Senior Developer” in the ATS refer to the same role. It must correlate an engagement score from one system with a compensation band from another and a skills profile from a third. It must do this continuously, not in nightly batch jobs, because agents operate in real time.
A concrete example: the redeployment gap
Yuki, a supply chain analyst at a manufacturing company, is on a team being restructured. In a single-system world, the HCM flags her as “impacted” and HR begins outplacement processing. But an agent with cross-system context sees something the HCM cannot: Yuki completed a data analytics certification through the LXP last quarter, her skills profile shows strong overlap with three open roles in the commercial analytics team, her engagement scores were high before the restructuring announcement, and her manager's 360 feedback highlights her as a top performer.
The agent does not just flag the match – it assembles a redeployment brief, notifies the hiring managers for the matching roles, and sends Yuki a message in Teams: “I found three roles that match your skills and interests. Want to explore them?” Instead of losing a strong employee to outplacement, the organization redeploys her in days. This outcome is impossible when each system only sees its own data.
Setting up the architectural answer
The single-system intelligence problem is not a criticism of any specific vendor. It is a description of the structural gap that exists when each system only sees itself. Closing that gap requires something none of the individual vendors will build: a cross-system context layer that is vendor-neutral, continuously updated, and purpose-built for agent reasoning.
This is the architectural foundation that makes agents possible. In the next article, we will examine the specific model for how this context layer is structured – what we call the four-rings architecture – and why it enables capabilities that no single-system approach can match.
The problem is not that vendor AI assistants are unintelligent. The problem is that they are blind outside their own system. And workforce decisions almost always require context that lives in more than one place.
Key terms
Single-system intelligence cannot solve cross-system problems. To move from answering questions to taking action, agents need a unified context layer that assembles data across HCM, ATS, engagement, learning, and market sources - the foundation for what we will explore as the four-rings model.