.png)
Find out what an agent already covers and where capacity already sits inside the team. Then hire for the half that is left, or redeploy and open nothing. This is cost avoidance, not recruitment.
$ Start with one open roleCopyThe spec comes from whoever last held the job. Nobody checks what the agent layer now covers, so you hire the whole role and pay for the half that no longer needs a person.
Hatch reads the work already happening in the role, marks what the agent layer now returns, and shows what is left for a person. You open a smaller req, or none at all.
Hatch reads the tasks in the role as they happen and marks the ones the agent layer now returns. You find that out before the req, not a year after the hire.
What remains is the part that still needs judgment, context and a person in the room. That is the job you are actually hiring for, and it is usually smaller than the one you wrote down.
Set the role as written against the role as it stands now. The difference is avoided salary, avoided ramp time and headcount you did not need to open. That is the line your CFO cares about.
Someone inside may be two tasks away from the role. Hatch shows where capacity already sits before you go outside and pay to bring it in.
Hatch reads eight behavioral dimensions, drawn from nine peer-reviewed meta-analyses and 2,200 behavioral profiles. Nothing for the candidate or the team to fill in.
The shape of a job keeps moving as the agent layer takes more of it. Hatch keeps reading, so the next req starts from what is true this quarter rather than what was true at the last one.
The same scan run on four open roles. Each comes back with a different split between what the agent layer now returns and what still needs a person.
ROLE Support Engineer READS the work already happening: tickets, threads, docs AGENT now returns triage and first-reply drafts PERSON still owns escalations, judgment calls and the customer relationship HIRE the half that is left: one role, scoped to what an agent cannot cover. Avoided: most of a second headcount.
ROLE Account Executive READS the work already happening: calls, notes, pipeline updates AGENT now returns research and follow-up drafts PERSON still owns the room and the negotiation HIRE the half that is left: one closer, not a full desk of coordination work. Avoided: the coordinator req you were about to open.
ROLE Operations Manager READS the work already happening: runbooks, approvals, handoffs AGENT now returns reporting and routine approvals PERSON still owns exceptions and the calls nobody wrote down HIRE the half that is left: one manager, scoped to exceptions rather than reporting. Avoided: a second ops hire and months of ramp.
Engineering role, scanned before the req ROLE Backend Engineer READS the work already happening: commits, reviews, tickets; AGENT now returns scaffolding, tests and first-draft reviews PERSON still owns design decisions, tradeoffs and what breaks in production HIRE the half that is left: one engineer, senior enough to make the calls AVOIDED the junior req and its ramp. SCAN again next quarter, because the split keeps moving .
Sometimes most of it does. Sometimes half of it has quietly moved to the agent layer.
Salary you do not commit to, plus the ramp time you do not spend getting there.
Hatch shows where capacity sits before you pay to bring the same capacity in.
The same reading continues after the start date, so the answer is not a guess at month six.
We backfilled the role exactly as it was written, and found out later that half of it no longer needed a person.
The agent spend shows up on the cloud bill. The work it absorbed never shows up anywhere.
Every req costs salary plus months of ramp before anything comes back. I want to know the ramp is buying something a person actually has to do, not something the agent layer picked up last quarter while nobody was looking.
Twice now the person we needed was already here, and we went outside anyway.
Our job specs describe the last person who held the job, not the job. We rewrite the title and keep the duties, then wonder why the hire looks like a poor fit six months in.
I do not want a hiring freeze. I want to open the req that is actually left.
Enough to read one role and see whether the job you are about to post is still the job.
Start freeFrom $2,500 a year for 5,000 credits up to $36,000 for 100,000. Priced on credits consumed, not seats.
Book a demoBespoke. SSO, a named engineer, and a security review before anything is connected.
Talk to usThirty days, one named engineer, and a readout of what your team and your agents actually produced. $2,500, credited in full against your first year.
