Recruiters stop chasing the latest file
Draft status, timestamps, and next actions stay on the same Placement instead of hiding in email threads.
Recruiters stop chasing Word files and approval emails because draft, review, and signed status stay on the same Placement.
See the product first, then the workflow, rollout, and blocker answers below.
Step 1 · Placement
Rachel opens Bullhorn. Candidate, client, start date, and rate are already there.
No copy-paste. No side tabs.
Step 2 · Generate
RecruiterDocs picks the right template and maps Bullhorn fields into the right clauses.
If something is missing, it is caught here.
Step 3 · AI checks
As soon as the draft is made, AI checks the clauses automatically.
Approvers see flagged points in plain English before anything is sent.
Step 4 · Approval
James reviews the draft, AI notes, and labels in RecruiterDocs, not in an email chain.
His approval is saved on the contract timeline.
Step 5 · Signed
Once approved, the contract goes out for e-signature from the same flow.
Rachel comes back and sees Signed on the Placement.
Every action from Bullhorn pull-through to approval and signature status stays tied to the same contract trail.
Recruiters can answer “is it drafted, approved, sent, or signed?” from one contract desk instead of chasing Ops, legal, or inboxes.
Sees draft, approval, send, and signed state without asking Ops for the latest file.
Reviews and comments on the same contract record instead of separate inbox threads.
Finds the decision trail later without reconstructing who approved what.
Draft status, timestamps, and next actions stay on the same Placement instead of hiding in email threads.
Legal or external reviewers can use a secure OTP link when they need to approve outside the internal team.
Labels and review context stay attached to the same version instead of being tracked in a side spreadsheet.
Every version, approval, and signature event is searchable later without asking who has the latest file.
RecruiterDocs is built for Bullhorn staffing teams that need one contract workflow, not a separate signing tool dropped on top of the process.
Perm, contract, umbrella, and multi-brand desks can stay in one workflow instead of splitting process by team.
You do not throw away 40 Word templates. The normal path is to map the contracts you already run and remove the manual edits around them.
Ops, legal, or client-side approvers can use a secure OTP link when they need to approve outside the recruiter account model.
Most teams start with one desk, one approval route, and the first live templates before widening rollout across the agency.
Agencies do not usually need another isolated e-sign tool. They need the Bullhorn workflow, the approval trail, and the signature status to stay together.
Most agencies go live by moving existing templates and one real approval path first, then widening the rollout once recruiters trust the flow.
There is one software price: £20 per user / month. Starter rollout is for one desk from 10 users. Agency rollout is for 25+ users or multiple desks. The difference is rollout scope, not a hidden product tier.
£20 / user / month
Same seat price, lighter rollout scope for one desk proving the workflow with live templates.
£20 / user / month
Same seat price, broader rollout scope once you want multiple desks, more templates, and a full move away from Word plus email.
Custom scope
For larger teams with multiple brands, approval paths, or a more involved rollout and review process.
Pricing is simple: per-user, monthly, with rollout scoped around your templates and Bullhorn setup. Starter and agency rollout share the same software price. Multi-brand work is scoped separately because the rollout work is genuinely different.
No. The base commercial model is per user, not per contract.
No. The main commercial question is rollout scope, not how many templates you keep live.
Most agencies are live in 2-3 weeks once the first real templates and Bullhorn flow are agreed.
No. We agree the signing path during rollout. If you already have one, we work with it. If not, we do not expect you to arrive with the whole signature stack pre-solved.
Yes. The workflow is built for Bullhorn staffing agencies across perm, contract, umbrella, and mixed desks.
No. The normal rollout path is to start from the templates you already use, map them properly, and remove the manual editing around them.
Approval steps sit on the same contract record, so approvers can review, comment, and resolve without turning the process into a side thread in email.
Yes. External approvers can use a secure OTP link, so they can review and approve without needing the same internal account setup as recruiters.
Usually SSO, API detail, deployment, and data-handling questions. We share security and API material early so IT does not need to wait for the end of the sales process to review it.
If IT, compliance, or operations need detail before the demo, there is a cleaner answer than “we’ll get back to you later.”
Recruiters, approvers, and signers do not need the same access or the same screen to move a contract forward.
Your existing contract wording does not get thrown away. Templates, approvals, and signature events stay tied to one record.
We can share security and API information before the demo so the buying conversation does not stall on unanswered IT or procurement questions.
Share a Bullhorn sandbox and a few example contracts. We will show the flow on your own process, not on a generic slide deck.