You have two clients. The system models one.
A staffing firm sells to the employer and recruits the candidate, and both are relationships that outlive any single placement. Most systems treat one as a contact and the other as an application.
Thirty minutes · no predetermined package
What a one-sided system does to a desk.
A strong candidate goes elsewhere because the client took five days to give feedback and nobody chased.
The same candidate is submitted to two clients by two recruiters in the same week.
Placement history lives in the ATS and relationship history lives in a recruiter's inbox.
Redeployment is missed because nobody knows which contractors finish this month.
Margin per placement is calculated after invoicing, which is after every decision that set it.
A departing recruiter takes their client relationships with them, because the system never held them.
What you are probably running, and what constrains it.
The typical stack
What the rules require
Six questions before changing anything.
How a placement actually happens.
The requisition
from a clientOften verbal, often incomplete, and the spec changes once candidates start arriving.
Sourcing
and submissionWhere recruiter time goes, and where duplicate submissions cost credibility.
The client's silence
where deals dieDays of no feedback while the candidate is being courted by three other firms.
Offer and placement
and the paperworkRight to work, classification, contracts — the part that carries the legal risk.
Redeployment
the next placementThe highest-margin work in the business, and it depends entirely on knowing when a contract ends.
What staffing firms ask.
What should a staffing CRM do that an ATS does not?
Hold the client relationship as seriously as the candidate one. An ATS models requisitions and applications well; the employer relationship that produces the next ten requisitions usually lives in an inbox.
Why do good candidates get lost?
Client silence. Days of no feedback while three other firms are courting the same person. Chasing feedback is a systemisable process and almost nobody systemises it.
Can this integrate with Bullhorn or JobAdder?
Yes. The ATS stays authoritative for candidates and requisitions, and the CRM holds the client relationship, the pipeline and the commercial history.
How do you prevent duplicate submissions?
By checking at submission against every open requisition rather than relying on recruiters to remember. The client always finds out first otherwise.
What is the most missed revenue in staffing?
Redeployment. Contractors finishing in thirty days are the highest-margin placements available and the ones nobody has a list of.
How is margin per placement tracked properly?
By recording pay rate, bill rate and time to fill against the placement as it happens, so margin is live rather than discovered at invoicing.
What happens when a recruiter leaves?
In most firms, the relationships leave too. Whether that happens is decided by where the relationship was recorded, long before the resignation.
What about worker classification and right to work?
Both are documentation problems with real penalties, and both belong on the placement record rather than in a folder somebody maintains.
What does a project like this cost?
It scales with ATS integration depth and the number of back-office systems rather than with desk count.