Bench Desk
Builds the day's hotlists, matches vendor requirements to your bench, submits each profile once, and sorts the replies.
Bench Desk on synthetic data: 40 consultants, 30 vendors, one morning's hotlists and replies
Hotlists go out at each mail server's pace
Every field shows the words it came from; a recruiter approves each submission
Two recruiters, one consultant, one end client: submitted once
The whole demo as a video, with captions and chapters
Demo built on synthetic data.
1 of 5: The morning
The problem
A bench-sales team spends most of its day on work that follows rules — which consultants go on which hotlist, who fits which requirement, which vendor replied about what. Portals time out mid-submission and nobody is sure the profile went through. Rate confirmations arrive as PDFs and get typed into the ATS by hand.
What it does
Each morning it builds hotlists by skill and sends them to the right vendor lists, paced so no portal or mail server blocks you.
It reads incoming requirements and ranks your consultants for each one, with the reasons, for a recruiter to approve.
It submits each approved profile once. If a portal fails, the submission waits and goes through when the portal is back.
It reads rate confirmations into the record — rate, end client, dates — and leaves a field empty when the document doesn't state it.
It sorts vendor replies and drafts answers to the routine ones. Anything about rates, right-to-represent or legal terms goes to a person.
Try to break it
On the call we'll trigger these, live:
- A vendor portal stops responding at 10 a.m. Submissions wait in line and go through when it's back, and none are sent twice.
- Two recruiters approve the same consultant for the same end client. The second submission is stopped, with the first one's details.
- A rate confirmation is a blurry scan. The fields it can't read stay empty and the document goes to a person.
- A vendor replies about a rate change. It never gets an automatic answer.
Where it runs
A desktop in your office or a cloud account in your name.
Who else does something like this
Bullhorn Automation automates recruiter workflows inside Bullhorn's applicant tracking system.
Bench Desk is built around C2C bench sales — hotlists, vendor portals, rate confirmations — and runs on machines your firm controls.
The rules it respects
A recruiter approves every submission, and nothing rejects a candidate automatically. Every submission is logged with who approved it and when.
What our tests measured
How we testThese figures come from test runs on Google's Gemini (gemini-3.5-flash-lite), a hosted model, on synthetic data. We'll add runs on a local model.
- Run on 4 October 2026
- Model: gemini:gemini-3.5-flash-lite
- 451 examples
For your engineers
- Engines
- Reconciler, Extractor, Gatekeeper, Proof Console
- Sealed mode
- Test passed: with sealed mode on, it refuses every outbound connection except to the model you've approved.
Data flow



