Every HR software vendor is selling AI right now. Sit through a few demos and they start to blur — each one shows an assistant answering questions, and there's no obvious way to tell which is actually any better.
We've just finished this year's Gartner Hype Cycle for HR Technology — all 137 minutes of it, by Gartner's own estimate. Partly because ClayHR is named in it, mostly because it's the clearest annual read on where this market is heading.
What follows is our own argument, sharpened by the read.
Here's what actually separates those demos: an AI assistant can only be as useful as the data it's allowed to see and the things it's allowed to do.
If the system underneath keeps most of its data locked away, treats the fields you added yourself as second-class, and hardcodes its workflows, then the assistant on top has very little to work with. It still demos beautifully — the demo only covers what works. It disappoints later, when people start asking real questions that cut across parts of the system the assistant was never given access to.
So the AI question turns out to be a question about the system underneath it. Usually asked a year too late.
All-in-one HR suites won for good reasons. One vendor, one database, one login was a real improvement on a drawer full of disconnected tools.
That deal rested on two assumptions: that a vendor could predict what most companies needed, and that connecting other systems was too expensive to bother with.
Both have weakened. Companies got more complicated — matrix reporting, contract workers, multiple countries, reorganizations every few quarters — and suites handle these as exceptions to a standard shape, because a standard shape is what makes a suite sellable in the first place. Meanwhile, connecting systems got far easier and cheaper. What's left of the all-in-one argument is mostly about having fewer vendors to manage, which is a purchasing preference rather than a technical one.
The alternative Gartner describes publicly is composable: build your HR stack from pieces you assemble, instead of buying one large system and adapting to it. Our shorter version — you should be able to model the company you actually have, not the one your vendor assumed you'd be.
The word gets used loosely. Four things separate the real thing from the label:
Each of these costs the vendor something to support. That's exactly why the list is a useful test.
We built ClayHR around this idea, so it's worth being direct about how.
You extend the system without us. Your administrators add custom fields, tables and lists themselves — and control who can see and edit each one, and report on all of it. That last part matters more than it sounds. Something you can't secure or report on isn't really part of your system; it's a text box.
Workflows get built, not requested. Multi-stage processes with tasks, checklists, deadlines and progress tracking, set up by the people who actually run the process.
The API reaches what the app reaches. Anything you can see in ClayHR, you can reach through the API — including the fields and tables you created. And an API key carries exactly the same permissions as the person it belongs to, so an integration never becomes a quiet way around your access rules.
The AI sees the whole picture. Because the things you add are treated the same as everything else, AskHR works across all of it. Skill Bridge Gap is the clearest example: working out the gap between what someone can do today and what a target role needs means reading their record, their performance history, the role definition and their training data together. That only works if those things are genuinely connected.
Assembled systems need someone who owns the overall design. A suite makes that role invisible; a composable stack makes it explicit — and companies without someone holding the whole picture end up more scattered than the single system they left behind.
And if you're stable, in one country, and your processes look much like everyone else's, buying the all-in-one is still a sensible decision. Composability is worth its cost when your complexity is permanent rather than temporary.
If you're thinking through what your HR stack should look like, we're happy to talk it through — including the cases where the answer isn't us.