Search firms
Software for a search that runs for months
A retained search is a project with milestones, a research phase and a client who expects a report long before a shortlist exists.
Surhires supports retained and contingent search firms with staged retainer invoicing tied to search milestones, exclusivity terms recorded on the assignment, market mapping as structured research rather than a spreadsheet, and progress reporting a client can be shown at week three rather than week nine.
By Surhires Editorial · Published · Reviewed
A search is a project, not a stage in a pipeline
Contingent recruitment is transactional by design: several agencies work the same role, the first acceptable shortlist wins, and the desk optimises for speed. Retained search is the opposite. The firm is paid to run a defined process, the client has committed money before a candidate exists, and the deliverable at week two is research rather than resumes.
Systems built for high-volume contingent work model this badly. They assume a requisition, an application flow and a stage machine that starts when a candidate applies. A retained search starts with a market to be understood: which companies hold this capability, who sits in the relevant seat at each of them, who has moved recently, who is off-limits, and which of them will take a call.
Surhires models the search as the object. The mandate carries its own scope, its fee structure, its milestone schedule, its exclusivity terms, its research universe and its longlist, and the candidate pipeline hangs off it rather than defining it.
Retainer milestones and staged invoicing
A retained mandate is usually billed in thirds: an engagement fee on signature, a second stage on shortlist delivery, a completion fee on placement. Variations are endless. Some clients pay a fixed engagement plus a percentage on completion, some tie the middle payment to a specific number of qualified candidates presented, some pay a container fee that is credited against the final invoice.
Surhires records the fee structure on the mandate when it is signed and raises each stage as its own billing event when its trigger condition is met. The trigger is a real event in the system, not a note: shortlist delivered means the shortlist document was shared with the named client contact on a date the record can show.
That matters most on the awkward conversations. When a client disputes a second-stage invoice, the answer is a timestamped record of what was delivered and when. When a search is cancelled, the system knows which stages were invoiced, which are due and what the mandate says about cancellation.
- Fee structure recorded at mandate signature, including percentage basis and any cap
- Milestone triggers tied to system events rather than to a manual status change
- Credited engagement fees carried against the completion invoice automatically
- Cancelled and paused mandates keep their invoiced and outstanding stages visible
Exclusivity is a term you have to be able to enforce
Exclusivity looks like a contract clause and behaves like an operational risk. A firm that has a six-week exclusive on a role needs to know when it expires, because the commercial position on day forty-three is completely different from the one on day forty-one. A firm working a contingent role alongside three competitors needs its recruiters to know that too, because it changes how much unpaid work is sensible.
The mandate carries its engagement type, its exclusivity period and its expiry date, and the pipeline view shows both. An exclusive that is running out generates a task before it lapses so somebody can have the extension conversation rather than discovering the position changed.
Off-limits agreements are recorded against client organisations for their duration, so a recruiter searching a market sees which employers are protected and why before making an approach rather than after.
Mapping a market, not responding to applications
The core intellectual work of a search firm is the map: a structured picture of who does this job, where, at what level, and how they got there. That map is an asset that outlives the mandate, and in most firms it lives in a researcher's spreadsheet, gets emailed as a PDF, and is rebuilt from scratch the next time a similar brief arrives.
Surhires holds the map as records. A target organisation is an entity with people mapped against it and a note on why it matters to this brief. A mapped individual becomes a candidate record with the source of the intelligence, the approach status and the outcome. The next search into the same market starts from what you already know, which is the compounding advantage a firm is supposed to build.
The Candidate Sourcing Agent searches that internal map before it goes anywhere else, so a person your researcher spoke to eighteen months ago surfaces before you pay for the same discovery twice.
- Target organisations as records, with mapped individuals and coverage state
- Approach status per mapped person: not approached, approached, engaged, declined, off-limits
- Research notes attributed to a researcher and dated, so intelligence ages visibly
- Maps reusable across mandates in the same market rather than rebuilt per search
The report a client expects mid-search
Retained clients pay early and wait. What keeps a mandate healthy through the quiet middle is a report that shows work: how many organisations mapped, how many individuals identified, how many approached, how many engaged, how many declined and for what reason, and what the market is saying about the compensation the client has offered.
In most firms that report is built by hand in a slide deck every fortnight, which means it is expensive, inconsistent and late when the search is going badly, which is exactly when it is most needed. Surhires derives it from the mandate record. The counts are real, the decline reasons are coded, and the compensation feedback is what candidates actually said.
The client can be given a portal view of the same data rather than a document, without seeing anything else in your database and without consuming a seat.
Long cycles need a different definition of activity
A contingent desk can be managed on weekly submittal counts. A search that runs sixteen weeks cannot: there will be weeks with no submittals in which the search is going well, and weeks with three submittals in which it is going badly. Measuring a search consultant on the contingent metric is how firms end up with rushed shortlists.
Surhires tracks the search's own progression: universe defined, mapping complete, approaches made, engaged conversations, longlist assembled, shortlist presented, client interviews, offer, placed. Ageing is measured against your own history for that discipline, so a mandate that is genuinely slow becomes visible without penalising the ones that are simply long.
Forecasting works the same way, from mandate stage and your own conversion history rather than from a percentage typed into a field by a consultant who wants the number to look reasonable.
Contingent and retained on the same desk
Very few firms are purely one or the other. Most run a retained practice alongside contingent work, sometimes for the same client, occasionally on the same role after a contingent search stalls. The two need different workflows and the same database.
Surhires keeps one candidate database and one client record, and lets the mandate decide the process. A contingent role runs a short stage set and bills once on placement. A retained mandate runs the research stages and bills on milestones. An owner sees both in the same revenue view, with retained revenue split between invoiced and contracted-but-unbilled, because those are not the same money.
What you get
Mandate record
Scope, fee basis, milestone schedule, exclusivity and research universe held as one object.
Staged invoicing
Engagement, shortlist and completion stages raised as separate billing events on real triggers.
Fee structures
Percentage, fixed, container and credited engagement fees modelled without a spreadsheet.
Exclusivity tracking
Engagement type and exclusivity expiry visible on the pipeline, with a task before it lapses.
Off-limits register
Protected client organisations recorded with duration and reason, surfaced during search.
Target organisation records
The companies in scope for a brief, with coverage state and mapped individuals attached.
Approach status
Every mapped person carries where the conversation reached and why it stopped.
Reusable market maps
Research from a closed mandate feeds the next search into the same market.
Search progression stages
Universe, mapping, approach, engagement, longlist, shortlist and offer as distinct states.
Mid-search client report
Mapped, approached, engaged and declined counts derived from the record rather than typed.
Coded decline reasons
Why a mapped candidate said no, in a fixed list, so patterns in a brief become visible.
Client portal view
A shared read-only view of one mandate, without a seat and without database access.
Long-cycle ageing
Time in stage benchmarked against your own history for that discipline, not a global default.
Revenue split
Invoiced retainer, contracted but unbilled, and contingent completion fees reported separately.
Questions recruiters ask
Can we invoice a retainer in stages that do not match thirds?
Yes. The fee structure is defined per mandate: any number of stages, each with its own basis and trigger. Container fees credited against completion, fixed engagement plus percentage on placement, and payment tied to a number of qualified candidates presented are all configurable without a custom build.
Does the client see our research?
Only what you share. The portal view exposes the counts and the shortlist you publish to that mandate. Your target organisation records, mapped individuals, approach notes and internal assessments stay inside your tenant. Deciding what a client sees is a per-mandate setting, not an all-or-nothing switch.
How does exclusivity actually change anything in the system?
It sets the mandate's engagement type and an expiry date, both shown on the pipeline. A task is raised before the exclusive lapses. It does not stop anyone from working the role; it makes sure nobody is unknowingly doing exclusive-level work on a contingent basis after the clause expired.
We already keep maps in spreadsheets. Is importing them realistic?
Usually yes, for the structured columns. Organisation, name, title, source and status import cleanly. Free-text research notes import as notes on the record. Where a spreadsheet holds one company per tab with inconsistent headers, the honest answer is that the first import is a paid concierge project rather than a self-serve upload.
How is a mandate different from a job in the system?
A job is a requisition to be filled. A mandate is a paid engagement with a fee schedule, exclusivity terms, a research scope and milestone deliverables, and it can hold more than one seat. Contingent roles run as jobs. Retained work runs as mandates because the commercial and reporting shape is different.
Does the forecast include retained revenue that has not been invoiced?
It is shown separately. Contracted but unbilled retainer stages are a different kind of certainty from a contingent placement that might close, and merging them produces a number nobody should plan against. The forecast shows invoiced, contracted, and pipeline as three figures with the assumptions visible.
Keep reading
See it against your own reqs
Bring one live role and three resumes. In twenty minutes you will see the match scores, the shortlist and the placement invoice that comes out the other end.