Workflow Assessments
Two weeks. One shortlist. A number for every candidate
"We should use AI for that" has come up in three meetings and nobody has a number attached. An assessment gets you one: a short, structured pass through your ATS, your back office and your shared inboxes that ends with a ranked list of agent candidates and the evidence behind the ranking.
What we do
- Interviews. Forty-five minutes each with two to four recruiters, an account manager, the person who runs timesheets and onboarding, and the owner.
- A read-only systems pass. Your ATS configuration, custom fields, workflow stages and API allowances, plus the spreadsheets and Slack channels that carry work the ATS does not.
- An estimate per candidate workflow. Revenue at stake (redeployment, reopened reqs) or hours recovered per week (chases, data entry).
- A data-access and security map. What an agent would read, what it would write, which system is the source of truth, and who approves each action.
- A compliance note. Personal data handled, retention, and whether the workflow touches an employment decision covered by NYC Local Law 144, Illinois HB 3773, or a client's own vendor policy.
You receive a ranked shortlist of three to five agent candidates with the estimates above, a one-page architecture sketch for the top candidate, and a short written note on anything you should fix before building anything, such as ATS hygiene or API limits.
Who this is for
Owner-led staffing and recruiting firms, typically 10 to 150 internal staff, running Loxo, Crelate, JobAdder, Vincere, Recruiterflow, or another non-Bullhorn ATS, with contractors on assignment and a back office that runs on a spreadsheet and one indispensable person.
How we work with you
- Hourly, time and materials. Senior US engineers, billed by the hour, with the scope and an estimate of the hours agreed in writing before we start.
- Typically two weeks. Long enough to count rather than guess; short enough that the findings are still true when you act on them.
- The person who assesses is the person who builds. If a build follows, there is no hand-off and no re-discovery.
What it is not
- Not a strategy deck. The output is a build plan a senior engineer would sign.
- Not a software selection exercise. If a feature inside your ATS already does the job, we say so and stop.
- Not a commitment to build. Roughly a third of assessments should end with "not yet"; we would rather say so than build something that will not pay back.
Next step
Contact us with your ATS, your contractor headcount, and the workflow that hurts most. Reply within one business day.