the role, in the words you would use to describe it to a colleague
No fields, no dropdowns, no required asterisks. A sentence is the whole brief.
Recruitmentum is an agentic ATS and CRM. You describe the role in a sentence. Agents build the search, work the field, rank what comes back and write the outreach — and then stop, and wait for you.
Early access · a few desks at a time
Every other tool asks you to fill in the form first. Here the form is the agent’s output, not its input — you read what it decided, and you argue with it.
the role, in the words you would use to describe it to a colleague
No fields, no dropdowns, no required asterisks. A sentence is the whole brief.
titles the ones people actually hold places where the work is, and where it hires from depth the band you meant ruled out the near-misses, named
The search you would have built by hand — written where you can see it, and change it.
— has built exactly this, for someone else — next door to it, and ready to move — did it before, somewhere harder and the rest, each with its reasoning
Not a list. A ranked argument, with a letter already drafted for every name on it.
A sentence becomes a search strategy you can read: the titles it will look for, the places it will look in, the depth it is aiming at, what it has ruled out. Disagree with any of it and you change the sentence, not a screen of filters.
Everyone who comes back is measured against the actual role — its constraints, its domain, its language — and arrives with the reasoning attached, so a shortlist is an argument rather than a list.
Messages are drafted per candidate and per contact, then queued. Nothing leaves the building until you say so, and every send, reply and follow-up lands back on the record it belongs to.
New roles, moves, funding, headcount — signals arrive against the client they concern, matched to the job when there is one, sitting on your worklist when there is not.
Stages move as the work moves. The numbers on the dashboard, the forecast and the client-facing portal are all reading the same rows, so there is nothing to reconcile at the end of the week.
Anything you can do in the interface, the copilot can do in a sentence — the same code path, the same permissions, the same audit trail. It is a rule we hold ourselves to, not a subset we got round to.
Everyone else spent a generation adding fields. We spent ours removing them.
We are taking on a few desks at a time, so the agents get shaped by real work rather than a demo dataset. Leave an email and what you are hiring for, and we will come to you when there is room.