Executive Search Firm Software Problems: The 7 That Cost Real Money, and How to Avoid Them
The most expensive failure mode is an off limits check that evaluates against a stale company field on the person record. A partner in one practice calls a candidate whose record still shows the employer she left, when in fact she joined a client of another practice eighteen months ago and your firm placed her there. The check passes, the approach happens, and you have breached both a client relationship restriction and a placement guarantee in one phone call. Nobody did anything wrong except trust a field that describes 2023.
Why does the data model get built like a recruitment database?
The biggest scope failure in retained search is accepting a contingent recruitment shape for the data. A person record with a current company field, a job record with a pipeline, and a set of stages from applied to placed. It is what most systems in the wider recruitment market look like, it is what a general purpose customer relationship management (CRM) tool gives you by default, and it is almost useless for search.
Retained search is not a pipeline business. It is a mapping business. The valuable object is not the candidate you are speaking to this week, it is the structure of a sector: which organisations exist, what their functional structures look like below the two people visible online, who has held which position and when, and who moved where. A single current company field cannot hold that, and everything downstream inherits the limitation.
Two consequences follow immediately. Off limits checks evaluate against employment that may be years out of date, which is the failure in the opening scenario. And market maps cannot be assembled from the database, so researchers keep building them in slide decks, which means the firm's core asset is stored in a format that cannot be queried, merged or refreshed.
The fix is a modelling decision made in week one. People have employment histories made of positions with start and end dates. Organisations have functional structures. Positions have holders over time. Ask any developer to model a person who has held four roles at three companies and is currently on garden leave. If they reach for a single company field, walk away, because this is a rebuild rather than a patch.
What goes wrong when you migrate years of research records?
Migration is where search projects lose their schedule, and it is almost always underestimated because everyone assumes it is an export and an import.
The recurring problems are specific to this industry. The same senior person exists three times, once from a 2016 search, once from a business development list, and once from a spreadsheet a partner maintained, with different spellings and no shared email address, because senior people change both employer and personal address. Duplicate detection on email therefore fails on exactly the population you care about. Employment histories conflict between records and there is no rule for which to trust. Notes and documents are attached to whichever duplicate the consultant happened to open, so merging records without care either loses history or attributes a reference to the wrong person.
There is also a quieter problem. Legacy records carry candidate personal data collected years ago under whatever practice existed then, and migrating all of it wholesale imports a retention obligation you have never assessed.
Practical fixes. Migrate active and recent records first and leave the deep archive in a read only store you can search but do not maintain. Deduplicate on the person using name, employment history overlap and document evidence, not on email. Make merge decisions reviewable and reversible, with a record of what was merged. And decide retention rules before the import rather than after, because retrofitting erasure handling into a research database with fifteen years of accumulated notes is genuinely painful work.
Why do mailbox, calendar and document integrations break after launch?
Because they are where consultants actually live, and they are the integrations most often specified in a single line of a proposal.
Mailbox synchronisation fails in adoption rather than in code. If logging an approach requires opening a separate system, it will not happen, and within two months your activity data is fiction. Worse, naive mailbox capture pulls in everything, including correspondence with a candidate about another firm's search, which then becomes visible to colleagues who should not see it.
Curriculum vitae extraction degrades quietly. It is accurate on the clean documents used in the demonstration and much weaker on the scanned biography, the two page European format with dates in a different order, and the deck a candidate sends instead of a document. When extraction silently produces an employment history that is approximately right, every off limits check and market map built on it is approximately right too, which is the worst possible property for a control.
Calendar coordination across three diaries and two time zones is trivial to describe and consumes a surprising amount of an associate's week when it is not built properly.
The fixes: capture activity where the consultant already works, with explicit control over what is filed and what is not. Treat extraction output as a proposal that a researcher confirms rather than as data, and show confidence at the field level so the weak values are the ones reviewed. And measure adoption directly in the first month, because a system consultants route around is worse than the spreadsheets it replaced.
What happens when candidate confidentiality and data protection are not covered?
Two gaps do the damage, and both are easy to defer and expensive to retrofit.
The first is client portal visibility. Clients ask for transparency, and the wrong portal gives them the longlist. Names of people who have not agreed to be considered, internal notes about a candidate's likely salary expectations, or the fact that a client's own finance director appears in another search are all one careless share away when visibility is granted by folder rather than by record. The model has to make a longlisted person invisible to the client until a consultant explicitly releases them, and document sharing has to be granted per candidate rather than per project.
The second is candidate data protection. Approaching senior people generates personal data they did not volunteer, and in several jurisdictions that carries notification, retention and erasure obligations. The awkward part is the interaction: an erasure request arrives from someone who appears in a completed search you have contractual reasons to retain, and the system has to express that distinction rather than either refusing outright or deleting evidence.
The fix is to take the legal position from counsel for each country you operate in, then require the developer to design to it, including how erasure touches search records, notes and documents separately. A firm that treats this as a phase two feature will discover the problem when a request arrives, which is precisely when improvisation looks worst.
Should you build custom or configure what you already own?
A boutique with three or four consultants in one sector should buy. Invenias, Thrive TRM, Clockwork and FileFinder all give you a working search database immediately at a small fraction of a build, and a bespoke system will not win you a mandate. If your differentiation is entirely relationship led and your searches are conventional, spend the money on researchers.
Before assuming custom, audit what your current system already does that nobody set up. Off limits fields that were never populated from client agreements. Structured competency criteria that exist but are unused because the specification arrives as an attachment. Report templates nobody configured, so every partner exports to a document and formats by hand. A surprising share of the pain in this category is unused configuration rather than missing capability.
The build case appears when two or more of these are true. You operate across practices or offices where an off limits breach can happen between teams that never speak. Market maps are something you sell or charge for and therefore need to be queryable. Your assessment methodology is proprietary enough that encoding it strengthens the pitch. Or, the clearest signal, you already run a packaged system and your researchers still keep the real work in spreadsheets and slide decks.
How do hidden costs get into the quote?
Search projects overrun in a consistent set of places, and none of them are the parts buyers scrutinise.
- Migration and deduplication. The single most underestimated line. Judgement about duplicates and conflicting employment histories cannot be automated away.
- Document extraction quality. Reliable is a different project to approximately right, and only reliable is safe to build controls on.
- Report templating. Sounds trivial, never is, because every partner has a view on the layout of a candidate report and the views conflict.
- Multi office and multi currency. Fee structures, invoicing and data protection obligations that differ by country add real weeks.
- Mailbox and calendar work. Priced as an integration, delivered as an adoption programme.
Digital Heroes delivery experience puts a focused first release covering the search record, structured organisations and people with position history, longlists and an enforced off limits engine at $60,000 to $130,000 over 12 to 16 weeks, with a full platform including portal, assessment and referencing at $150,000 to $360,000 phased over 6 to 12 months. Cutting scope to one practice and recent records is the cheapest way to protect that band.
What separates a build that works from one that fails here?
Working builds put the control at the moment of risk. The off limits check runs when a name enters a search or an approach is logged, evaluates against dated rules derived from client agreements and placements, and requires a named partner to override with a recorded reason. A weekly exception report is not a control, it is a post mortem with better formatting.
They earn adoption before they add features. One practice, recent records only, activity captured where consultants already work. If the research team is still maintaining a parallel spreadsheet after a month, nothing built later will fix that, and the portal certainly will not.
They leave the client portal until the internal data is trustworthy. A portal built on a database full of duplicates and stale employment damages client confidence faster than having no portal at all, because now the client can see the mess.
And they settle ownership before kickoff. The repository, the cloud accounts and the full candidate and organisation database belong to the firm, with a structured export you test during the build rather than at renewal. Your research database is the accumulated value of every search the firm has ever run, and it should never sit anywhere you cannot walk out with in full on a day of your choosing.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
Riley plans content for APAC clients, working out what a site needs to say, in what order, and who it is for before a page gets designed. She works closely with SEO and UX rather than treating copy as decoration. Her posts help readers judge whether their content is doing any work.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Why do off limits breaches still happen when we have an off limits field?
Because the check evaluates against a current company field that describes where someone worked when the record was last touched. Senior people move, so the field is stale on exactly the candidates most likely to be restricted. The rule has to evaluate against dated employment history and against restrictions derived from client agreements and placement guarantees with their own effective periods, and it has to run when a name enters a search rather than in a weekly report.
What is the most underestimated cost in a search software project?
Migration, specifically deduplication. The same senior person commonly exists three times with different spellings and no shared email address, because senior candidates change both employer and personal address, so matching on email fails on the exact population that matters. Employment histories conflict between records and notes are attached to whichever duplicate a consultant happened to open, so merges need human judgement and have to be reviewable and reversible.
Why do market maps keep ending up in slide decks even after we buy a system?
Because the data model cannot hold them. A map is organisations with functional structures and people with positions over time, and a system built around a person with one current company field has nowhere to put that. So researchers build the real picture in a deck, the deck is emailed, and the next search in that sector starts from nothing. On a fixed fee, the days spent rebuilding a picture the firm already had come straight out of margin.
How do we give clients a portal without exposing the longlist?
Make visibility a property of the record rather than of a folder. A longlisted person should be invisible to the client until a consultant explicitly releases them, and documents should be shared per candidate rather than per project. Just as important, do not build the portal until the internal data is clean, because a portal over a database full of duplicates and stale employment lets the client see the mess and damages confidence faster than having no portal.
How reliable is curriculum vitae parsing in practice?
Good on clean documents and much weaker on scanned biographies, European formats with different date conventions, and decks sent instead of documents. The dangerous property is silent approximation, because an employment history that is roughly right makes every off limits check and market map built on it roughly right too. Treat extraction output as a proposal a researcher confirms, and surface field level confidence so weak values are the ones reviewed.
How should erasure requests be handled in a research database?
Deliberately, and designed in from the start. Approaching senior people creates personal data they did not volunteer, and an erasure request may arrive from someone who appears in a completed search you have contractual reasons to retain. The system has to express that distinction across search records, notes and documents separately rather than deleting everything or refusing everything. Take the position from counsel per country and make the developer build to it.
When should a search firm stay on Invenias or Thrive TRM?
When you have a handful of consultants in one sector and conventional searches. Those products give you a working database immediately for a small fraction of a build. Before assuming otherwise, audit what your current system does that nobody set up: off limits fields never populated from client agreements, structured competency criteria unused because specifications arrive as attachments, and report templates never configured. Unused configuration causes more pain in this category than missing capability.
Why do consultants abandon systems the firm has paid for?
Because logging activity requires leaving the mailbox, and consultants live in the mailbox. Capture has to happen where they already work, with explicit control over what gets filed, since naive capture pulls in correspondence that colleagues should not see. Measure adoption directly in the first month, and treat a surviving parallel spreadsheet as a project level failure rather than a training issue, because no later feature repairs it.
How long does it take to build a custom CRM from scratch?
How small can the first version of my software be and still be worth building?
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
How many SaaS seats do we need before building custom becomes cheaper?
Is Zoho or Pipedrive good enough for a small sales team, or should we build custom?
What questions should I ask a development agency on the first call?
Should we pay a consultant to customize Salesforce or just build our own CRM?
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Is custom software more secure than off-the-shelf SaaS?
How does moving our data from Salesforce or spreadsheets into a custom CRM work?
How many developers does it take to build a custom CRM?
Who can build a custom CRM software system?
Digital Heroes builds custom CRM software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other CRM software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
