Recruiters sitting on a dormant candidate database / The problem
Ten years of candidates, nobody speaking to them
You have tens of thousands of candidates and no time to market a single one. Business development is what happens in the hours left over, and there are no hours left over. So new business leans on the same three accounts it leaned on last year, while the database you spent a decade building sits there earning nothing, because working it properly costs exactly the time you do not have.
Recruiters sitting on a dormant candidate database / What we found
Everything worked right up to the reply
Map it end to end and the sophistication turns out to be in the wrong half. Scoring, tiering, fatigue caps, drip windows, editable approvals, all upstream. Downstream of a reply, where every pound you earn actually happens, six empty columns and nowhere in the database to store a fee. Two genuine warm replies had sat untouched for over a fortnight, because no phone number was ever captured.
Recruiters sitting on a dormant candidate database / What we built
Outreach that costs nobody an hour
Every week it reads a batch of your dormant candidates, works out which firms would genuinely hire them, finds the person who does the hiring, and writes the approach in your voice with a reason attached you would be happy to read out on a call. Nothing sends until you click approve. It is not built to close a placement. It is built to open a conversation.
Recruiters sitting on a dormant candidate database / What changed
Four replies. No placements. The audit says why.
The honest numbers off the live engine: 197 candidates, 8,283 contacts enriched, 341 emails sent, four replies, zero placements recorded. Two of those four were an auto-responder and a complaint about where the details came from, so the true warm rate is nearer 0.6 per cent. Almost 8,000 enriched contacts were never sent to at all. Everything upstream of the reply works. Everything downstream of it was never built.
0Placements recorded after 197 candidates, 8,283 contacts enriched and 341 emails sent, on the engine's own internal audit.
Recruiters sitting on a dormant candidate database / Whose it was
Our own venture, with nothing to show yet
A UK construction recruitment desk running the first and only live instance, and it is only fair to say this one is ours: a venture we half own, not a client who paid us. Its own four-agent audit found six empty columns after the reply, a fee storable nowhere in the schema, and zero placements. This panel is here because it is true, not because it sells, and the reframe it produced is the useful part: the engine starts conversations, it does not close placements.
See the recruitment engine Book a call
All fourteen stories · MAX.AI · 2026