Retained Executive Search Software: Why Your Market Maps Die at Project Close and Your Off Limits List Lives in Someone's Memory

Why one phone call can end a client relationship

A partner in the industrials practice calls a chief technology officer about a chief operating officer role. Twenty minutes into a good conversation, the candidate mentions she joined her current employer eighteen months ago. That employer is a client of the firm's technology practice in another country, and she was placed by the firm. Two off limits agreements just became a problem: the client relationship one, and the placement guarantee one. Nobody did anything malicious. The off limits list is a tab in a workbook that is updated when someone remembers, and the partner is in a different office and a different practice.

Retained search runs on this kind of knowledge. Who is off limits and until when. Which candidate was longlisted for a similar role nine months ago and said not yet. What the org structure of a target company actually looks like below the two people on LinkedIn. Which reference gave a careful answer that meant something. Invenias by Bullhorn, Clockwork, Thrive TRM and FileFinder all serve this market and each does part of the job properly. What they were not built to do is enforce your firm's specific rules automatically at the moment of an approach, and hold the research asset in a form that survives the search that produced it.

The economics make this sharper than in contingent recruitment. You are paid a fixed fee regardless of how many hours the research team spends, so every hour spent rebuilding a market map that already existed comes straight out of margin. In search firm projects we have worked on, the recurring pattern is a researcher spending two to three days at the start of each search assembling a picture the firm already had, from documents nobody can find, because the previous version was a PowerPoint attached to an email.

Problem 1: off limits is a rule, and rules must be enforced where the risk is

Off limits arises from several sources: an active client relationship with a defined scope and duration, a placement with a guarantee period, a contractual restriction negotiated into a specific agreement, and sometimes a partner's judgement about a relationship that is fragile. Those sources sit in contracts, in the placement record and in people's heads.

Systems in this category will hold an off limits flag. What they generally do not do is derive it from its sources with dates, apply it across the whole firm regardless of office and practice, and put the check in front of the consultant at the moment they add a name to a longlist or log an approach.

What a custom build does: model off limits as a set of rules with effective periods, generated from client agreements and placements and supplemented by manual entries with an owner and a reason. The check runs when a person or company enters a search, not in a weekly report. A blocked approach can be overridden only by a named partner with a recorded justification, which is the audit trail you want if a client ever raises it. Because people change employers, the rule must evaluate against the candidate's employment at that moment rather than a stale company field, which is precisely the failure in the opening scenario.

Problem 2: the market map is the firm's real asset and it is stored as a document

A researcher spends days building a picture of a sector: the target companies, their structures, the people in the relevant functions, tenure, background and how to reach them. That map is worth more than the search it was built for. Stored as a slide deck, it is unusable six months later because it cannot be queried, updated or merged.

What a custom build does: hold the map as structured data, meaning organisations with functional structures, positions with holders over time, and people with employment histories rather than a current company field. Then the second search in that sector starts from the first, and a refresh is an update rather than a rebuild. Position history is the detail that makes this work: knowing that a person held a role from 2021 to 2024 lets the system answer who ran supply chain at a target company two years ago, which is the sort of question a client asks and a document cannot answer. Over a few years this compounds into genuine sector intelligence, which is the thing clients actually retain your firm for.

Problem 3: assessment has to be structured or the client report is an opinion

A retained search sells judgement. The evidence for that judgement is a competency specification agreed with the client, interviews conducted against it, references taken and a written assessment. In most firms the specification is a Word document, the interview notes are in an email, and the report is assembled by hand for each candidate at the end.

What a custom build does: turn the role specification into a structured set of criteria that interviews are conducted against, so evidence attaches to a criterion rather than sitting in a paragraph. Candidate reports generate from that evidence with the firm's own formatting, which recovers a substantial slice of consultant time on every search. Referencing becomes a workflow with consent captured, questions tied to the same criteria, and responses recorded. The comparison view a client wants, meaning four candidates against eight criteria on one page, becomes a query rather than a formatting exercise at midnight before a shortlist meeting. Firms that do this find their reports get more consistent across consultants, which matters when a client works with several of your partners.

Problem 4: the client wants a portal, and giving them the wrong one is worse than none

Clients ask for visibility. What they should see is progress, the shortlist, the reports you have chosen to share, interview scheduling and a status summary. What they must not see is the longlist with names of people who have not agreed to be considered, your internal notes, or the fact that their own chief financial officer appears in another search.

What a custom build does: a portal where visibility is explicitly granted per candidate and per document, branded as the firm's own, with a status view generated from the search record so nobody rebuilds a weekly update deck. Candidate confidentiality is enforced by the model rather than by care: a person in a longlist is not visible to a client until a consultant releases them. Candidate data protection also belongs here. Approaching senior people generates personal data they did not volunteer, and in several jurisdictions that carries notification, retention and erasure obligations. Build retention rules and erasure handling in from the start and confirm your specific position with counsel, because retrofitting this into a research database with fifteen years of accumulated records is genuinely painful.

Problem 5: researcher productivity is your margin

On a fixed fee, every hour saved in research is margin retained. The largest single time cost is finding and maintaining accurate data about people and organisations, followed by scheduling and follow-up.

What a custom build does: reduce typing. Candidate records assemble from documents the researcher already has, with extraction pulling employment history from a curriculum vitae into structured positions rather than a text blob. Duplicate detection runs on the person rather than the email address, because senior candidates change both employer and address. Outreach sequences with reminders stop follow-ups being remembered rather than scheduled. Calendar coordination for client interviews across three diaries and two time zones is a small feature that consumes a surprising amount of an associate's week. None of this is glamorous and all of it is measurable: the honest test is whether a search still takes two to three days of setup, or whether it starts from an existing map on day one.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, the numbers for search firms look like this. A focused first release covering the search and mandate record, structured organisations and people with position history, longlist and pipeline management, and the off limits rules engine runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding the client portal, competency assessment and report generation, referencing, business development and origination pipeline, and productivity tooling runs $150,000 to $360,000 phased over 6 to 12 months.

What drives cost up: data migration, because importing years of records from a legacy search system involves real judgement about duplicates and about which employment history to trust. Document extraction quality, if you want curriculum vitae parsing that is genuinely reliable rather than approximately right. Multi-office and multi-currency operation, particularly where fee structures and data protection obligations differ by country. Integration with mailbox and calendar, which is where consultants live and where adoption is won or lost. And report templating, which sounds trivial and never is, because every partner has an opinion about the layout of a candidate report.

What keeps cost down: starting with one practice, migrating only active and recent records rather than the full archive, and leaving the client portal to phase two once the internal data is trustworthy. A portal built on messy data damages client confidence rather than building it.

Build versus buy, and when buying is right

Buy if you are a boutique with three or four consultants working in one sector. Invenias, Thrive TRM, Clockwork and FileFinder all cost a fraction of a build and give you a working search database immediately. Buy also if your firm's differentiation is entirely relationship-led and your searches are conventional, because a bespoke system will not win you a mandate.

Build when two or more of these are true. You operate across practices or offices where an off limits breach can happen between teams that do not talk. Market maps are a product you sell or a service you charge for, and they need to be queryable rather than presented. Your assessment methodology is proprietary and differentiates your pitches, so encoding it matters. You want a client portal that is genuinely your firm's rather than a vendor's screen with your logo. Or you have run a packaged system for years and your researchers still keep the real work in spreadsheets and documents.

The judgement we would offer is this: buy the database, build the intelligence. If your firm's advantage is that you know a sector better than anyone else, then the structure that holds that knowledge is your product, and a document folder is not a structure.

How to choose a developer for search firm software

Ask them to model a person who has held four roles at three companies and is currently on garden leave. If their data model has a single company field on the person, market mapping will never work and off limits checks will evaluate against stale employment.

Ask how the off limits check runs. It should trigger at the moment a name enters a search, evaluate against dated rules from client agreements and placements, and require a named override with a reason. A weekly exception report is not a control, it is a post mortem.

Ask how they will handle candidate data protection, including retention periods and erasure requests across search records, notes and documents. If they have not thought about how erasure interacts with a completed search you need to retain for client reasons, they have not built for this industry. Take the legal position from counsel and make sure the developer designs to it.

Ask who owns the code, the cloud accounts and the candidate and organisation database, in writing, before kickoff. At Digital Heroes the client owns everything from the first commit. Your research database is the accumulated value of every search your firm has ever run, and it should never sit anywhere you cannot extract it from in full, in structured form, on a day of your choosing.