Market mapping in recruitment is the structured research of an external market: the employers that hold the experience a client needs, the people in the relevant roles, and what that field means for the hire. It is done before a search to set the brief, or alongside one to prove coverage. The output is a documented picture of the market, not a list of CVs.
This guide works through the whole process on one illustrative brief, from the scoping conversation to the recommendations page. It includes an employer inclusion/exclusion matrix, copyable company and people tables, an annotated summary and a scope checklist. The method holds for any sector; swap in your own brief as you read.
What market mapping means in recruitment
A market map answers a client's question about a labour market they do not employ. Recruiters use it for four kinds of decision:
- Whether to hire externally at all. How deep is the relevant pool, and does it exist at the seniority the client wants?
- Where to look. Which employer segments hold the experience, including adjacent ones the client had not considered?
- What the brief should be. Which requirements are realistic, which ones narrow the field to a handful of people, and which could flex?
- What it will cost. How do pay bands and package structures vary across the field?
In an agency, the work is external. That separates it from the internal nine-box review that shares a name in corporate HR. The terms "market mapping" and "talent mapping" overlap heavily in agency use; talent mapping vs market mapping sets out the distinction. This guide is the practical process.
- 01Define the briefRole family, seniority, geography, and the rule for what is in or out.
- 02Company universeCompanies before people, so your network doesn't pose as the market.
- 03Map the peopleFind who fits each company. One consistent row each.TalentMaps
- 04Layer intelligenceComp, availability, movement, a diversity lens. The judgement on top.
- 05Package & presentA branded deliverable that leads with the read, not the rows.TalentMaps
The worked example: the brief
A fictional UK payments company, called "the client" here, has around 140 engineers and is preparing for a regulated product launch. Its CTO wants a VP Engineering to run delivery across four platform teams. Before agreeing a retained search, the client asks the agency three questions: how many credible people exist in the UK, where they work, and whether the London-only requirement is realistic.
That is a market-mapping brief, not yet a search. Each step below uses it.
Step 1: Agree the role, geography, evidence standard and exclusions
Every weak map fails at the edges. Before you find anyone, agree six things with the client and write them down.
| Boundary | What to agree | In the worked example |
|---|---|---|
| Role family | The responsibility being mapped, not only the title | Leaders running engineering delivery for a product or platform, including VP, Director and Head of Engineering titles |
| Scale | The size of organisation or team that makes experience comparable | Currently or recently leading 60–250 engineers, or a platform of comparable complexity |
| Geography | Where people must be based, and whether hybrid or relocation counts | UK, with London and hybrid-commutable hubs flagged separately |
| Evidence standard | What counts as support for a row | Remit stated on a company page, public profile, filing or talk; every row dated and sourced |
| Exclusions | Employers or people you cannot or will not include | The client's own staff; the agency's off-limits clients; anyone the client asks to omit |
| Output | What the client receives, and in what format | A summary, the employer universe with decisions, a people table and recommendations |
The evidence standard is the boundary most often skipped. Without it, a map mixes verified remits with guesses, and the client cannot tell which is which. Agree that every row carries its source and the date you checked it, and that availability, interest and salary are never inferred from a public profile.
Write the inclusion rule as a sentence someone else could apply. For the example: include UK-operating companies where a single engineering leader is responsible for delivering a regulated or high-availability financial product at 60–250 engineer scale. If two researchers would build different maps from your rule, it is not finished.
The talent mapping brief and scoping template turns these boundaries into a document the client can sign off.
Step 2: Build the employer universe
Start with employers, not people. If you begin with the leaders you already know, you build your network into the map and present it as the market. Starting from an employer universe produces a field you can defend.
Build it in two passes. The direct set is the obvious match: other payments and banking-infrastructure businesses at a similar stage. The adjacent set holds the same experience under a different label, such as engineering leaders in large banks' payments divisions or high-availability consumer platforms. Adjacent segments are often where a map earns its fee, because they surface people the client's own team would not have searched for.
Then decide each segment out loud. A matrix makes the reasoning visible to the client.
| Employer type (fictional examples) | Decision | Why |
|---|---|---|
| Payments and card-acquiring scale-ups, Series B or later, UK engineering hub | Include | Same regulatory exposure, product type and team scale |
| Banking-as-a-service and core-banking infrastructure providers | Include | Platform reliability and regulated delivery at comparable scale |
| Challenger banks' platform and payments engineering | Include | Directly comparable remit; check the team size of each leader |
| Large banks' payments technology divisions | Borderline | Relevant domain, but leaders may run much larger, more governance-heavy functions; calibrate with the client |
| High-availability consumer marketplaces with in-house payments teams | Borderline | Transferable scale and reliability experience; regulated delivery needs checking person by person |
| Crypto exchanges | Borderline | Some comparable payments engineering; differing regulatory regimes; client decision |
| Pre-Series A fintechs | Exclude | Team scale below the agreed floor |
| Offshore delivery centres with no UK engineering leadership | Exclude | No UK-based leader with the agreed remit |
| The client and the agency's off-limits clients | Exclude | Agreed exclusion |
Borderline is a legitimate answer. Record it, explain it and resolve it during calibration rather than hiding it inside "include". When real employers illustrate a category in your own work, check their sites or official records and date that evidence; employer facts and candidate judgements should never be confused.
In the worked example, the researcher checks 46 employers: 31 included, 9 borderline and 6 excluded. These fictional counts illustrate a coverage report. They do not establish that 46 employers is sufficient for another brief; explain the segments investigated, discovery methods and unresolved gaps against the agreed inclusion rule.
Step 3: Identify people, with source dates, remit and uncertainty
Now find the people inside each included and borderline employer. For each, keep one consistent row. Consistency matters more than volume: a table where every row has the same fields is readable, while one where every row has different gaps is not.
Record five things beyond name, title and employer:
- Remit. What they actually lead: team size, platforms, products, regions. A title is a label; remit is the evidence.
- Source and checked date. Where the remit came from and when you saw it. A company page, a public profile, a conference talk or a filing.
- Uncertainty. What you could not confirm. "Team size not stated" is more useful than leaving the cell blank.
- Research priority. Approach first, investigate further or outside scope, with a reason.
- Contact status. Not contacted, contacted, replied, declined. Keep this separate from fit.
Do not record a guess about who might move. Tenure, a reorganisation, a funding round or a leadership change are company events; they are not evidence that a named person wants a new role. Availability is established in a conversation, and the map should say so.
This step is the slow middle of the work, and it is where most of the cost sits. TalentMaps is built for it: paste the public LinkedIn URLs you have identified and it enriches each one into the same structured profile shape, with work history, education and location in consistent fields. You still decide who belongs on the map, and every enriched profile deserves a sense-check against the source.
Copyable tables for the worked example
These are the working tables behind the example, with fictional rows. Copy the CSV blocks into a spreadsheet to start your own.
Employer universe (extract)
| Ref | Employer (fictional) | Segment | Decision | UK engineering presence | Source | Checked |
|---|---|---|---|---|---|---|
| E01 | Company A | Payments scale-up, Series C | Include | London HQ, ~180 engineers | Company careers page | 2 Oct 2026 |
| E02 | Company B | Core-banking infrastructure | Include | London and Edinburgh | Annual report | 2 Oct 2026 |
| E03 | Company C | Challenger bank | Include | Manchester platform hub | Engineering blog | 3 Oct 2026 |
| E04 | Company D | Large bank, payments technology | Borderline | Several UK sites; team size unclear | Company site | 3 Oct 2026 |
| E05 | Company E | Pre-Series A fintech | Exclude | ~15 engineers | Funding announcement | 3 Oct 2026 |
ref,employer,segment,decision,decision_reason,uk_engineering_presence,source_url,checked_on
E01,Company A,Payments scale-up (Series C),Include,Same product type and scale,London HQ (~180 engineers),,2026-10-02
E04,Company D,Large bank payments technology,Borderline,Scale and governance differ; calibrate,Several UK sites,,2026-10-03
E05,Company E,Pre-Series A fintech,Exclude,Below team-size floor,~15 engineers,,2026-10-03
People (extract)
| Ref | Title | Employer | Remit, as evidenced | Source, checked | Uncertainty | Priority | Contact |
|---|---|---|---|---|---|---|---|
| P07 | VP Engineering | Company A | Four platform teams, card processing | Conference talk, 2 Oct | Team size not stated | Approach first | Not contacted |
| P12 | Director of Engineering | Company C | Payments and ledger, ~90 engineers | Public profile, 3 Oct | Hybrid location unclear | Approach first | Not contacted |
| P19 | Head of Payments Engineering | Company D | Payment rails within a larger group function | Company site, 3 Oct | Remit may sit under a wider CTO organisation | Investigate | Not contacted |
| P23 | Director of Platform | Company B | Core platform reliability | Public profile, 2 Oct | No regulated product launch evidenced | Investigate | Not contacted |
ref,title,employer_ref,remit_evidenced,source_url,checked_on,uncertainty,research_priority,priority_reason,contact_status
P07,VP Engineering,E01,Four platform teams; card processing,,2026-10-02,Team size not stated,Approach first,Matches scale and regulated delivery,Not contacted
P19,Head of Payments Engineering,E04,Payment rails within a larger group function,,2026-10-03,Remit may sit under wider CTO org,Investigate,Scale mismatch possible,Not contacted
The talent mapping tracker is a PowerPoint version of the people table, laid out for presenting rows to a client. Keep the working copy in a spreadsheet or your recruitment system, where contact history belongs.
Step 4: Separate market coverage from a qualified shortlist
A market map and a shortlist answer different questions, and confusing them is how maps get oversold.
| Market map | Shortlist | |
|---|---|---|
| Question | Who appears relevant across the agreed market? | Which assessed, interested people should the client meet? |
| Size | The whole field in scope | A handful |
| Evidence | Public and documented sources, dated | Conversations, assessment, references as agreed |
| Contact | Mostly not contacted | Contacted and engaged |
| What it can claim | Coverage of a defined universe, with gaps reported | Fit and interest for named people |
Report coverage honestly. In the worked example: 46 employers checked; 212 people identified in relevant roles; 58 within the agreed remit and scale; 17 marked "approach first". The 17 are not a shortlist. They become one only after contact and assessment, which is the next stage of a search. When you get there, how to present shortlisted candidates covers that meeting, and what is candidate mapping explains the stage in between.
"No one found" at an employer can mean the role does not exist there, or that the person is not visible publicly. Report those employers as unresolved, not as empty.
Step 5: Turn rows into findings
A list of people is a directory. The map's value is the interpretation the client cannot get from a database. Work from the rows to a small number of findings, each with the evidence that supports it.
For compensation, give bands from a stated source, such as your own placement data or a published survey, and label them as estimates. For movement between employers, describe the pattern you observed and the period it covers. If the client asks for a representation view of the market, agree the method first; do not infer protected characteristics of named individuals from photos or names.
Here is how the worked example's rows become findings:
| What the rows show | Finding for the client |
|---|---|
| 58 leaders in remit; only 19 lead more than 120 engineers | The pool exists, but the part at the client's target scale is small. |
| 11 of the 17 priority leaders are outside London, mainly Manchester and Edinburgh | A London-only requirement removes most of the strongest field. Hybrid with London travel keeps it. |
| 6 priority leaders work in large banks' payments divisions | The adjacent segment is real, but its leaders run larger, more governance-heavy functions. Calibrate before approaching. |
| Remit could not be confirmed for 9 people | These are research gaps, not exclusions. They need conversations, not assumptions. |
Step 6: The annotated summary
The client reads the summary first and often only the summary. Write it last. This is the worked example's one-page read, with notes on why each line is there.
- Coverage first. States the universe and the rule before any names, so the number is defensible.
- The finding the client did not ask for. Location was an assumption in the brief; the map tested it.
- A decision, not an observation. Each finding ends with what the client should consider changing.
- Uncertainty in plain sight. Gaps and contact status are stated, so nobody mistakes the map for a shortlist.
- A next step with an owner. Calibration is the bridge from map to search, and the moment the client commits.
Step 7: Use the tracker and present the report
The deliverable has two layers. The people rows are evidence, and the report around them is the agency's judgement.
| Part of the deliverable | Who produces it |
|---|---|
| Brief, inclusion rule and employer decisions | The researcher, agreed with the client |
| Structured people rows | The researcher, with enrichment tooling doing the copying and formatting |
| Remit evidence, uncertainty and priority | The researcher |
| Compensation bands and movement patterns | The researcher, from stated sources |
| Findings, summary and recommendations | The researcher or consultant |
| Branded layout and export | Tooling or the agency's own templates |
Two free templates support this. The market map report template is the full research presentation, with sections for the market, employer universe, people, pay and recommendations. What goes in a market map explains each section and how to run the meeting.
TalentMaps produces the candidate-report part of that deliverable. PDF reports can include the cover, authored brief and rationale, candidate profiles grouped by tier, and closing page. The editable PowerPoint export uses its own slide layout, with summary counts and candidate fit notes; it is not a page-for-page copy of the PDF. Market analysis, the employer matrix and recommendations remain researcher-authored, in the report template or your own format.
A report generated by TalentMaps
Inspect the actual candidate-report PDF or editable PowerPoint. These files were generated on 27 October 2026 by the application's current export functions, using fictional candidate records. The PDF uses the Classic layout. They demonstrate report formatting, rather than live enrichment accuracy or customer results.
The example starts with two prepared profiles. Maya Collins is placed in Tier 1 for the fictional payments brief; Daniel Osei is placed in Tier 2 as a platform-delivery comparison. The fit notes explain the apparent match and the questions still to test. These classifications are illustrative recruiter judgements; neither person is real or has been contacted.
| Part of the example | Input or authored work | What the export shows |
|---|---|---|
| Candidate records | Prepared fictional names, locations, career histories and education | Consistent candidate pages |
| Brief and rationale | Written for this fictional engagement | Authored brief and rationale in the PDF; the current PowerPoint summary shows candidate counts |
| Tiers | Assigned by the recruiter | Tier labels and candidate ordering |
| Fit notes | Written by the recruiter | A fit note on each candidate page in both formats |
| Employer universe and analysis | Separate researcher work | Kept in the wider market report, not generated from these candidate records |
For a real project, identify the public LinkedIn URLs, import and check the profiles, write the brief and fit notes, assign tiers, then review the exported files. Keep source dates and unresolved questions in your working research record. The shortlist meeting guide explains how to present that judgement to the client.
The free shortlist presentation template is a separate PowerPoint download with a manual comparison worksheet and next-steps page. It is edited in PowerPoint; it is not an upload template for TalentMaps.
The scope checklist
Before you send a market map, check it against the brief:
- The inclusion rule is written as a sentence, and the client agreed it
- Each employer has a decision: include, borderline or exclude, with a reason
- Each person row has a remit, a source and a checked date
- Uncertainty is recorded rather than left blank
- Availability, interest and salary are not inferred from public profiles
- Contact status is separate from fit
- Coverage is reported: employers checked, people identified, people in remit, unresolved employers
- Findings each point to evidence in the rows
- The summary states gaps and that the field has not been contacted
- The recommendation names a next step
Applying the method to your sector
Nothing in this process is specific to payments. The boundaries, employer matrix, evidence standard and coverage report work for any market; what changes is the employer segments, the remit that matters and the signals worth recording. The sector guides cover those differences, including fintech, private equity, life sciences, legal, cybersecurity, SaaS, renewable energy, professional services, financial services, healthcare, engineering, construction, the public sector, logistics and defence.
For the end-to-end method without a worked example, see how to do talent mapping. For where mapping sits in the wider agency model, read the complete guide to talent mapping for recruitment agencies. When you have the URLs for your own field, start a map in TalentMaps and let the tooling carry the copying and formatting.
Frequently asked questions
- What is market mapping in recruitment?
- Market mapping is the structured research of an external market before or during a hire: the employers that hold the relevant experience, the people in the agreed roles, and what that field means for the client's brief, budget and approach. It records its scope, sources and gaps, so the client can see what was covered as well as who was found.
- How long does market mapping take?
- It depends on the brief more than the headcount. A single-function map of one country usually takes a researcher several days, most of it spent identifying people, checking remits and keeping rows consistent. Scoping and the final read are shorter but carry most of the value. Rare profiles, tight geographies and discreet briefs take longer.
- How many companies should a market map cover?
- There is no universal number. Write the inclusion rule first, then report which employer segments were investigated, how employers were found and how many were included, borderline, excluded or unresolved. A count alone does not prove completeness or representativeness. Agree completion criteria and disclose remaining coverage gaps.
- Is a market map the same as a shortlist?
- No. A market map shows coverage: who appears relevant across an agreed universe, with evidence and uncertainty recorded. A shortlist is a much smaller group who have normally been contacted, assessed and have confirmed interest. Most people on a map have not been approached, so the map should never describe them as available or interested.
- Can you market map a sector without LinkedIn?
- You can, but it is slower and patchier. Professional profiles are the most complete public record of who works where, so most maps start there and corroborate with company websites, filings, regulators' registers, conference programmes and press. Record which source supports each row, because no single source is complete.