Why five HR tools is worse than one
The standard advice is to buy the best tool for each problem. In practice, this produces a specific kind of problem that compounds over time.
There is a standard advice loop in HR technology that goes roughly like this: find the best tool for each problem, integrate them loosely, and treat the resulting collection as your HR stack.
The logic is sound in theory. Use the best recognition tool for recognition. Use the best onboarding tool for onboarding. Use the best performance tool for performance. Buy best-in-class, integrate via API, move on.
In practice, this advice produces a specific kind of problem that compounds over time.
The five-tool problem
Consider a reasonably well-resourced People Team at a 300-person company. They have:
A recognition tool. An onboarding platform. A performance management system. An engagement survey tool. A people directory.
Each of these tools was bought to solve a real problem, at a real moment, when that problem felt urgent. Each one works, more or less, for the thing it was designed to do.
The problem is what happens at the edges.
When someone who has been recognised consistently across three teams over the past year is considered for a promotion, the recognition tool has data about that. The performance system doesn't know. The people directory doesn't know. The manager making the promotion decision is working from memory and from whatever made it into the last performance review.
When a new hire is onboarded, the onboarding platform captures their first 90 days. The recognition tool doesn't know they're new. The engagement survey treats them the same as someone who has been there for three years. When they become fully embedded in the team and start contributing, nobody connects that arc to the onboarding experience that preceded it.
The tools are silos. The data they generate never talks to anything else.
The hidden cost of integration debt
Every tool in a disconnected HR stack creates integration debt.
Integration debt is the cost of maintaining the connections between systems that weren't designed to talk to each other. It shows up as manual data exports, CSV uploads, Zapier automations that break when either system updates its API, and duplicated employee records that drift out of sync.
It also shows up as something harder to measure: the cost of decisions made without the context that exists in another system.
The manager who doesn't know that the team member they're about to put on a performance plan has been recognised five times in the past quarter by colleagues they respect. The People Team that doesn't know that the department with the highest attrition also has the lowest cross-team collaboration rate. The executive who doesn't know that the person they're considering for a leadership role has quietly become the most trusted technical voice in the organisation.
This context exists. It is just not connected.
What a connected platform actually enables
The argument for a connected platform is not that individual tools are bad. It is that the value of people data is multiplicative, not additive.
Recognition data plus skill data plus onboarding data plus collaboration data is not four separate things. It is a graph: a map of how people, relationships, expertise and contribution interact across the organisation.
That graph becomes useful for questions that no single tool can answer. Who is ready to step up? Where are the knowledge risks? Which teams are thriving and which are isolated? Who should mentor whom?
These questions require context that only emerges from connected data.
The consolidation question
The objection to platform consolidation is usually that no single platform does everything as well as the best point solution for each problem. This is sometimes true. A specialist recognition tool probably has more features than the recognition module in a broader platform.
The relevant question is not which tool has more features. It is which decision gets you better outcomes.
A recognition tool with 40 features whose data never talks to your performance system produces worse decisions than a recognition tool with 20 features whose data directly informs your succession planning.
Features are not the product. Connected understanding is the product.
The right way to consolidate
Consolidation doesn't mean replacing everything at once. It means being intentional about which tools generate the data that feeds everything else.
Start with the data foundation. The people graph -- who works where, who reports to whom, what skills exist, what relationships are active -- is the foundation that makes everything else more valuable. Build that first.
Add products that generate signals into that foundation. Every recognition, every onboarding milestone, every document request, every project contribution adds to the graph.
Only then does intelligence become possible -- because the graph is rich enough to support inference.
Five tools that don't talk to each other will never get you there, no matter how good each individual tool is.
Your HR team is spending 20% of their time on document requests. Here's the proof.
Employment confirmation letters. Salary confirmations. Visa support letters. These requests arrive every week, at every company, and almost all of them are still handled manually.
🎯 People OpsWhat a Head of People actually needs from software
Most HR software is designed for administrators. The people who make strategic decisions about talent are still working from spreadsheets and institutional memory.
🔍 Org GraphThe difference between recording work and understanding it.
Every company has systems that record work. Very few have systems that understand it. This distinction matters more than most people realise.