If AI Eats the Application, What Is Left of Recruiting?
JBD Note: Guest essay by Martin Lenz, CEO of Jobiqo, on why the infrastructure behind recruiting may matter more as the interfaces in front of it may matter less.
“There are only two ways to make money in business: bundling and unbundling.”— Jim Barksdale
Jim Barksdale’s famous line came back to me with the announcement of ClaudeForce. The immediate question is whether Claude is beginning to eat Salesforce. A more interesting one is what exactly there is to eat.
For most of the SaaS era, the answer seemed obvious. An application was the product. Salesforce was where salespeople managed customers; Workday was where companies managed employees; an ATS was where recruiters managed candidates. Software companies assembled data, workflows, business logic and an interface, wrapped a subscription around the whole thing and charged according to the number of people who needed access.
Talroo brings clarity to improve new-hire retention
You filled the seat, but not with someone who plans to stay. The candidate made it through your entire interview process while quietly interviewing with other companies that pay 25% more.
When expectations aren't clear up front, retention suffers.
Get clarity up front with Talroo's SmartQualify.
Frontier AI is beginning to pull that bundle apart. A user no longer necessarily has to understand the application in order to use its capabilities. An AI system can work across data and workflows without requiring someone to spend their day navigating every underlying application in the traditional sense.
It is tempting to take this argument to its logical extreme and conclude that the model becomes the product. I am not convinced.
Anyone who has spent a lot of time working in ChatGPT, Claude or similar systems will probably recognise the contradiction. The first few hours can feel extraordinary. After a few months, the limitations become harder to ignore. Work disappears into conversations. Projects multiply. Decisions made three weeks ago become difficult to find. The model can create a dashboard, a document or an application almost on demand, but that does not mean you want a new one every morning.
There is considerable value in knowing where things are.
A CRM pipeline looks roughly the same when you return to it tomorrow. A recruiter knows where the candidates for a job sit, which stage they are in and what has happened to them. An advertising manager can look at a campaign and understand its history. Good software creates institutional memory as much as it provides functionality.
So perhaps AI will not kill the application layer. It will change its purpose. The model becomes a remarkably powerful way to express intent and to orchestrate work, while applications provide the persistent structure around that work. The screens may become simpler and some may disappear altogether, but companies will still need records, permissions, transactions, histories and reliable processes.
Recruiting offers a particularly good illustration of what this could mean.
Over the past two decades we have built a surprisingly complicated collection of software around a fairly simple economic problem. An employer has a job. Somewhere there are people who might be suitable for it. The difficulty is finding enough of the right people at an acceptable cost and turning their interest into applications.
Around that problem sits an ATS, a career site, job boards, aggregators, recruitment marketing software, programmatic advertising, social networks, search engines, CRMs, matching technology and analytics. Each has accumulated its own interface. Recruiters have become accustomed to moving between them because there was no better way for computers to understand what they were trying to achieve.
AI changes that assumption.
A recruiter should eventually be able to say something along the lines of: “I need more qualified applicants for these 30 nursing jobs. We have €12,000 left this month. Focus on the locations where we are falling behind and don’t spend money on jobs that are already performing.”
That instruction contains far more useful information than a series of campaign settings. A capable model can interpret it. It can understand the jobs, compare their performance, decide which ones need help and determine what should happen next.
Yet understanding the instruction does not produce a single candidate.
For that, the model needs access to the machinery of the recruitment market. It needs jobs and structured job data. It needs advertising inventory, audiences and distribution channels. It needs to know where a particular job is likely to perform and what that reach will cost. It needs to launch campaigns, move budgets, collect applications and understand which sources produced useful candidates. Eventually, it needs enough feedback to distinguish cheap traffic from actual recruiting outcomes.
This is where the discussion about AI and recruiting becomes more interesting than another debate about whether ChatGPT will replace job boards.
AI may well reduce the importance of many destinations. A recruiter might spend less time inside a recruitment advertising platform. A candidate may sometimes discover an opportunity through an AI assistant rather than beginning on the homepage of a job board. Some search boxes, filters, campaign forms and reporting screens will inevitably disappear.
But the economic activity behind them does not disappear. Jobs still have to reach people. Employers still compete for scarce candidates. Publishers and specialist communities still aggregate audiences. Media still has a price. Applications still need to be attributed and evaluated. Budgets still need to find their way to the places where they produce the best result.
A world of AI agents may make the infrastructure connecting these things considerably more important.
In fact, a world of AI agents may make the infrastructure connecting these things considerably more important.
This changes how recruitment technology companies should think about their position in the market. The more useful question may no longer be whether a company owns the recruiter’s daily interface. It may be whether its capabilities remain valuable when that interface is controlled by somebody else.
A recruitment platform that can expose job distribution, audience access, campaign execution, taxonomy, matching, tracking or application-quality signals as reliable capabilities may become more relevant in an AI-driven market, even if humans interact with it less directly.
The same is true for job boards.
The traditional job board has been both infrastructure and destination: it aggregates jobs, attracts an audience, provides search and sells access to employers. AI may weaken the importance of the destination without eliminating the value of the network behind it. A specialist healthcare site, a regional publisher or a national employment marketplace still has jobs, relationships, first-party audiences, domain authority and knowledge of its market. Those assets can become part of a larger recruiting network even if fewer transactions begin on its homepage.
There is an analogy here with other parts of the internet. Payments became more valuable as they became easier to embed. Cloud infrastructure became vastly more important while becoming almost invisible to the end user. The most consequential infrastructure businesses are often those consumers rarely know they are using.
Recruiting has never quite developed an equivalent layer. Its infrastructure remains fragmented between job boards, ATS vendors, aggregators, advertising networks, publishers and large technology platforms. Every participant protects a piece of the workflow, and employers pay for much of the resulting complexity.
The agent does not care whether the inventory sits behind a beautiful dashboard. It does not want another login. It needs an action it can take.
AI creates an opportunity to reorganise that market because agents are much better at dealing with capabilities than humans are at dealing with dozens of applications. The agent does not care whether the inventory sits behind a beautiful dashboard. It cares whether the inventory is available, relevant, measurable and accessible. It does not want another login. It needs an action it can take.
That suggests a different architecture for recruiting.
An ATS or recruiting workspace may remain the persistent home for jobs, candidates and decisions. AI systems may increasingly understand objectives, identify problems and decide what actions to take. Beneath them, a more open infrastructure layer could connect jobs to audiences, media, marketplaces, matching systems and measurement.
The boundaries between those layers will not be neat. Some ATS vendors will move into orchestration. Some job boards will become infrastructure providers. Some advertising platforms will move closer to systems of record. Some frontier AI companies may move further down the stack themselves.
That uncertainty is precisely why openness matters.
The winners may be the systems that can participate in several possible futures: useful through their own interface, useful through an ATS, useful through a specialist agent and useful through whatever general-purpose AI assistant eventually becomes part of everyday work.
Which brings us back to Barksdale.
SaaS spent twenty years bundling functionality, workflow, data and interfaces into applications. Frontier AI is starting to pull those bundles apart. ClaudeForce is interesting because it makes that process visible: the interface, the intelligence and the underlying enterprise system no longer have to belong to the same company.
The next phase will be a rebundling.
The open question is what the new bundle looks like.
In recruiting, it may combine persistent systems of record, AI-driven orchestration and a much more connected infrastructure for distribution, matching, advertising and measurement.
If that happens, the most important shift will not be that AI replaces recruiting software.
It will be that recruiting software stops being defined by the screen through which we access it.
[Want to get Job Board Doctor posts via email? Subscribe here.]


Comments (0)