Source

Every requirement, candidate and application in one place.

Open a role, bring candidates in the way they actually arrive — a career page, a bulk folder of resumes, a referral, a manual add — and keep every application tied to the job it was for.

Who it is for
Recruiters and agency owners running more than a handful of open roles
The problem
Requirements live in email, candidates live in a spreadsheet, and nobody can answer 'who have we already spoken to for this role?' without asking three people.

What it does

The short version.

  • Jobs with their own hiring stagesEach role defines the stages it actually uses, not one global pipeline.
  • One candidate, many applicationsA person applies to several roles without becoming several records.
  • Bulk resume intakeDrop a folder of resumes onto a job and process them file by file.

In detail

What is actually in here.

The modules behind this stage. Each one is specified and built against a written brief before it ships.

  • JobsRequirements, per-job hiring stages, and job health rules that flag a role going stale.
  • CandidatesThe person record — profile, resume history, notes, and every role they have been considered for.
  • ApplicationsThe join between a candidate and a job, carrying its own stage, timeline and evaluation.
  • Bulk resume intakeAdd many candidates to a job at once, with deterministic matching against people already on file.

The AI boundary

What the model offers, and what you own.

AI proposes

A job description can be turned into structured fields, and a resume into a candidate profile.

A person confirms

A recruiter reviews the extracted fields before the job opens or the candidate record is written.

Try it on one role.

Create a workspace and open a job. Nothing here requires you to migrate anything first.