Recruitment Automation Workflow Replacement

The Problem

A specialist recruitment firm placing technical staff into mid-market businesses was handling candidates almost entirely by hand. CVs arrived by email and were saved into folders by consultant. Initial screening notes lived in a shared spreadsheet that consultants updated when they remembered. Calls were logged sporadically, and follow-up reminders depended on each consultant’s personal calendar discipline.

The visible cost was candidates falling through the cracks. A strong candidate would be screened, marked as promising, and then contacted again two months later, by which point they had taken another role. Less visibly, consultants spent a startling proportion of their day on administrative work that had nothing to do with the parts of recruitment that earn fees. Multiple consultants estimated that fifty to sixty percent of their week was admin, scheduling, and chasing.

The firm had bought a generic ATS two years earlier and bounced off it. The tool was built for high-volume recruitment with fixed pipelines, and the firm’s actual workflow (long, consultative placements with a lot of relationship management between stages) did not fit. The ATS was abandoned within four months and the spreadsheet returned.

The Approach

We built a workflow platform shaped around how the firm actually worked, rather than imposing an industry-standard pipeline on top of it. Candidates have a record, but the record is structured around stages the firm itself defined: initial screen, technical screen, client introduction, interview prep, interview, offer, placement, aftercare. Each stage carries its own checklist, its own follow-up cadence, and its own visibility rules.

The automation work was about removing the chasing. When a candidate enters the “interview prep” stage, the platform schedules a follow-up reminder, sends the candidate a prep document, and notifies the consultant if the client has not confirmed the interview by a configurable deadline. CV intake from email is automated too. Incoming CVs land in the platform, with parsed contact details and a draft record ready for the consultant to confirm rather than create from scratch. The underlying workflow engine follows the same patterns described in our workflow engine system.

The System We Built

A custom recruitment workflow platform built on Laravel with a structured pipeline that consultants can adapt per role type. Email-to-record CV intake with parsed contact details. Configurable stage automations covering follow-up reminders, candidate communications, and consultant nudges. Integration with the firm’s existing email and calendar so scheduling does not require leaving the platform. A consultant dashboard surfacing every candidate at risk of falling out of contact based on time-since-last-touch. Reporting on conversion between stages, so the firm can see where candidates drop and intervene.

The Outcome

The “we forgot about a strong candidate” failure mode has largely disappeared. The dashboard surfaces every candidate with no recent contact, and the time-since-last-touch metric forced a behaviour change: consultants now reach out before the system flags them rather than after.

Consultant admin time has come down materially, by the consultants’ own reckoning. The time freed up is being reinvested into the consultative, relationship-heavy work that closes placements, which is the work the firm wins on.

What We Learned

The earlier ATS failure was not a fluke. Generic recruitment software is built for the high-volume, low-touch end of the market, and forcing it onto a consultative business creates resistance that no amount of training overcomes. Building the workflow around the firm’s actual stages, rather than translating their work into an off-the-shelf model, was the difference between adoption and another shelfware purchase.

For the pipeline side of a recruitment operation rather than the workflow automation side, see the recruitment agency pipeline platform case study. The internal SOP platform for distributed team covers a related project where standardising process across people was the primary goal.

Recruitment Workflow Holding You Back?

If your recruitment firm has rejected one or more off-the-shelf ATS platforms because none of them fit how you actually place candidates, get in touch to talk through what a workflow built around your model could look like. The case studies overview has more context on how we approach this type of build.