Verticals · Staffing & recruiting
Every placement is a deal with a person in the middle.
Searches run as pipelines, candidates and clients live in one directory, and a placement carries a fee, terms, and a close — because it’s a deal from first principles.
Why one system
The ATS knows the candidate, the CRM knows the client, and the placement — the thing you’re actually paid for — falls into the gap between them.
One system where the search, the candidate, and the fee run as one pipeline from sourced to placed.
The objects you’d define
searches
deal · workflow · tasks
The role you’re filling: client on one side, candidate on the other, a fee riding on the outcome.
candidates
contacts · email · social
One person across every search, interview, and placement they’ve ever touched — history included.
clients
contacts · website · activity
The hiring companies, their people, and every search you’ve run for them.
interviews
tasks · activity · notes
Scheduled, owned, and logged against both the candidate and the search.
- Sourced
- Interview
- Offer
- Placed
A searches pipeline — client ↔ candidate — same deal primitive, your labels.
How it runs.
An employment pipeline is a deal pipeline — the offer amount is a salary, the final amount is what was signed, and the stages progress toward a close like any other.
The candidate is one record, not a copy per search: their interviews, offers, and placements accrue on them, so the second time they come around, the history is already there.
Approval gates hold where they matter — an offer doesn’t go out until the client’s sign-off is in.
Nomi keeps the desk moving: candidates advance through their stages with your gates intact, the searches that stall don’t hide, and “who’s in Offer this week?” is a single query across the board.
Nothing here is an industry edition — it’s the same primitives, named by the people who run the business.