# The Talent Map Playbook: Target Companies to a Named Pool

*You can build a talent map for one role family: 20 to 50 tiered companies, named profiled candidates, a documented coverage figure, and a defensible pool estimate with a refresh cadence.*

- Canonical URL: https://www.refolk.ai/guides/talent-map-playbook-named-pool
- Pillar: Recruiting and sourcing
- Format: Playbook
- Published: 2026-10-05
- Last reviewed: 2026-10-05
- Reading time: 16 min
- Keywords: how to build a talent map, talent mapping process steps, target company list for sourcing, talent map deliverable template, passive candidate market map

## Key takeaways

- Most working talent maps focus on 20 to 50 target companies rather than the full market, and aim for 80 to 90% coverage of a tightly defined segment, not the whole population.
- A six-month-old map of senior talent can have around 20% of names already at new companies, which is why a quarterly refresh is arithmetic, not a nicety, for high-velocity functions.
- In Refolk's index the US Platform Engineer / SRE population is 9,060 against 2,943 in the UK, a 3.08x multiple that geography math must account for before you quote a pool size.
- Title taxonomy inverts by market: in Refolk's samples SRE dominates the US at 68% while Platform Engineer dominates the UK at 52%, so a single search string systematically under-covers abroad.
- Only about 5 to 10% of a passive pool is genuinely receptive within a 90-day window, so a 9,060-person pool implies roughly 450 to 900 reachable-now candidates before reply and interest filters.
- One backend-engineering map served three requisitions over six months, which is the whole case for building the map before the role opens rather than cold at the point of need.

A talent map is a tiered list of source companies plus the named people inside them, built for one role family before the requisition opens. This playbook is for in-house recruiters, sourcers, talent leaders, and founders doing their own hiring who want to start the next search warm instead of cold. It walks the full build end to end: scope, company tiers, named people, enrichment, a documented coverage figure, a defensible pool-size estimate, and a refresh cadence - so what you produce is a reusable deliverable, not a one-off shortlist.

Most recruiting content covers the reactive single-req shortlist, or a one-off company teardown, or exemplar-to-lookalike comparables. None join the company side and the people side into a single map with a coverage number and a refresh rhythm. That join is the whole point here.

## What a finished talent map actually contains

A finished talent map is a persona plus named profiles plus a pool-size figure, tiered by source company and packaged for hiring-manager calibration. It is not a spreadsheet of names, and it is not a market-sizing memo. It is both, joined.

The deliverable has five parts. First, a one-line scope that defines the segment. Second, a tiered list of 20 to 50 source companies. Third, named people inside those companies, each enriched into a comparable row. Fourth, an ICP persona drafted from the profiles and a pool-size estimate with its assumptions shown. Fifth, a refresh cadence with a named owner.

Most talent maps focus on 20 to 50 target companies rather than the full market, and aim for 80 to 90% coverage of the defined segment. That coverage figure is practitioner convention, not a published standard - no regulator or benchmark body sets one - so you own the responsibility of making it honest by naming the denominator you measured against.

#### The five layers of a talent map

1. **Scope** - One sentence: role, seniority, geography, time horizon
2. **Company tiers** - 20 to 50 firms tagged direct, adjacent, feeder
3. **Named people** - Individuals pulled inside each tier
4. **Enriched rows** - Tenure, reporting line, skills, signals, source
5. **Persona + pool + cadence** - The calibration output and refresh owner

*Each layer depends on the one above it, which is why scope is load-bearing.*

The reason to build this before a role opens is that the cost amortizes. One map for backend engineering served three reqs over six months, and per-req cost drops with every role the same map serves. Organizations using continuous talent mapping report 38% shorter time-to-fill on critical roles, and only 36% of companies do talent mapping proactively (Deloitte, 2024) - so the field is open.

**38% - Shorter time-to-fill on critical roles**

Reported by organizations that run continuous talent mapping rather than reactive single-req sourcing.

## Scope the segment before you touch a single name

Scope is the one sentence the entire map hangs from. Get it wrong and every downstream number lies. A map of "tech talent in EMEA" is useless; a map of "principal security engineers in the UK and Ireland with cloud infrastructure experience" is actionable.

Pin four things with the hiring manager: role and function, seniority band, geography, and time horizon. Talent mapping works best focused on a narrow set of 5 to 10 high-priority roles over a 6-to-18-month horizon, so resist the urge to map everything. The scope sentence is what the hiring manager signs off, and it is the sentence you will later point to when someone questions the coverage figure.

Scope is also where title taxonomy bites. Titles are market-specific, and a single search string under-covers abroad. In Refolk's index the split between Site Reliability Engineer and Platform Engineer inverts across markets: SRE dominates the US sample while Platform Engineer dominates the UK. A US-tuned query run on a UK segment would systematically miss the majority title and quietly fail the 80-90% coverage bar.

| Title | US sample share | UK sample share |
| --- | --- | --- |
| Site Reliability Engineer | 68% (17/25) | 36% (9/25) |
| Platform Engineer | 24% (6/25) | 52% (13/25) |

These are directional sample figures from Refolk's index top-title counts, not a census - but the direction is the lesson. If you scope across two markets, you need both title strings, or your map tells you the wrong thing about the smaller market.

> **Watch out:** One search string will not cover two markets
>
> In Refolk's samples the dominant title flips between the US and the UK. Build your query from both titles before you quote coverage, or you will miss the majority of the segment in whichever market you tuned against last.

## Build the tiered company list

The company list is the backbone of the whole map; every strong candidate you find will sit inside one of these firms. Build it in three tiers and cap it at 20 to 50 companies.

- **Tier 1, direct competitors.** Firms hiring for and employing the exact profile. This is where the densest, most relevant talent lives.
- **Tier 2, adjacent and academy companies.** Neighboring sectors that grow the same skills, plus the firms that train people well and that you can poach from.
- **Tier 3, feeders and white-hot names.** The companies people regularly move out of into your segment, plus recent IPOs and fast-growing startups building the same capabilities.

The cap is not arbitrary. Employer concentration tells you where coverage effort pays off. In Refolk's UK Platform Engineer / SRE sample, one bank, JPMorganChase, was the single most frequent employer at 3 of 25 profiles, and London alone held 8 of 25. A handful of Tier-1 firms and one city can deliver most of a segment, which is the quantitative basis for not trying to map the full market.

#### From market to a named pool

| Stage | Figure | Note |
| --- | --- | --- |
| US segment population | 9,060 | From Refolk's index for Platform Engineer / SRE |
| Named on the map | 20 to 50 companies | Tiered source firms, not the whole market |
| Receptive now | ~450 to 900 | 5 to 10% of the pool in a 90-day window |
| Genuinely interested | smaller still | After reply and interest filters |

*Volumes narrow at each stage, which is why the finished pool is far smaller than the headline population.*

## The talent-mapping process, step by step

The process runs eight stages from scope to a cadence. Research is the bulk of it: reviewing profiles, building personas, estimating pool sizes, and cross-referencing against past hires is roughly a week of recruiter time per function when done manually. The stages below assign an owner and a rough duration to each.

#### Build the map in eight stages

1. **Scope the segment** - With the hiring manager, pin role, seniority, geography, and horizon into one sentence the manager signs off. Half a day to a day.
2. **Build the tiered company list** - List direct competitors, then adjacent and academy firms, then feeders and white-hot names. Tag by tier and cap at 20 to 50. Half a day to a day.
3. **Audit internal data** - Capture job history, tenure, performance, mobility flags, and stated ambitions for current staff before mapping outside. Half a day.
4. **Populate named people** - Work company by company, pulling matches with current title, tenure, and reporting line, to about 80 to 90% of the segment. Two to four days.
5. **Enrich and tag** - Add prior companies, skills and signals, flight-risk flags, contact path and status, source, and last-updated date so every row is comparable. One to two days.
6. **Draft persona and compute pool size** - Draft the ICP from about 20 profiles, then run the funnel to a defensible number with assumptions shown. Half a day.
7. **Package and calibrate** - Build a one-page brief with five example profiles and present coverage and density until the hiring manager calibrates "good." Half a day.
8. **Attach refresh cadence** - Assign a cadence and owner and set trigger rules for job changes, layoffs, and comp shifts. Ongoing.

### Audit internal data before the external market

Skills inventories and performance data must precede external market research so you can prioritize build versus buy. Audit what you already know first: a minimum dataset per employee covers job history, tenure, performance ratings, current development plans, internal mobility flags, and stated career ambitions. Skipping this produces a real false positive - mapping externally for a role an internal successor already fills.

### Populate and enrich into comparable rows

Pull the individuals who match the target profile, recording current title, tenure, and where they sit in the reporting line. Then enrich. Enrichment is what makes the map a planning tool rather than a contact list: tenure at current company, prior companies, education, flight-risk signals, and notable work. A workable column set:

- Name and current role
- Company and tenure
- Seniority and function
- Location
- Key skills and signals
- Contactability: verified contact path and status
- Source and last-updated date

More expert maps add the reporting line, reconstructing who reports to whom as an org-chart deliverable. That is what lets a hiring manager see team sizes and structures, not just a list.

Finding the named people inside 30 or 40 firms, across two title taxonomies and multiple markets, is the part that eats the week of recruiter time. This is where asking for the people in plain English removes the most friction, because it collapses the company-by-company query-building into one request.

I ran this search: `Platform engineers in London with Kubernetes and Terraform, currently at fintech companies, flagged if tenure is over 3 years.` - [see the full result list](https://www.refolk.ai/s/09qfzfmwsm).

*Returns named people inside your Tier-1 and Tier-2 London firms, already tagged with the tenure signal you need for flight-risk ranking.*

I built [Refolk](/) so that step - naming the people inside your target companies - is a sentence rather than a day of X-ray strings. You describe the segment and the signals, and the named rows come back ready to enrich.

## Derive a defensible pool-size estimate

A defensible pool size comes from funnel math off the addressable pool, never from a gut figure. Compare the pool to the number of hires in the plan, not to how big the raw number feels.

The chain is: total addressable pool, times the share you can actually reach, times reply rate, times the share of repliers genuinely interested, times interview-to-offer and offer-acceptance rates. Each multiplier shrinks the number, and the shrinkage is the point - it turns an impressive headline into a plan you can stand behind.

Start with the addressable figure and net out geography immediately. A pool of 4,000 that sits 80% in a timezone or jurisdiction you cannot hire in is not a pool of 4,000. Geography is also where the role-family multiple matters:

| Market | Mapped population | Share vs US |
| --- | --- | --- |
| United States | 9,060 | 100% |
| United Kingdom | 2,943 | 32% |
| US:UK multiple | - | 3.08x |

Population figures come from Refolk's index for Platform Engineer / SRE; share and multiple are derived from those two numbers. A plan built on US headroom cannot be ported to the UK by assuming parity - the UK pool is roughly a third of the US one.

Then discount for receptiveness, or the plan overstates headroom. Only about 45% of passive talent is open to a well-targeted message, and roughly 5 to 10% are genuinely receptive within a 90-day window. Apply that to the 9,060 US figure and you get on the order of 450 to 900 reachable-now candidates before reply and interest filters. Reply rates sharpen it further: average InMail response runs 10 to 25%, and skilled sourcers hit 30 to 50%.

> **Rule:** Always state the denominator
>
> Coverage of 80 to 90% is meaningless without the total in-segment population it is measured against. Write the denominator next to the coverage figure, every time, or the number is theater.

> A pool of 4,000 that sits where you cannot hire is not a pool of 4,000.
> </pull-replace>

> A pool of 4,000 that sits where you cannot hire is not a pool of 4,000.

## How talent maps go wrong

Most talent maps fail in predictable ways, and every failure has a false positive that looks like success and a one-line check that catches it. This is the most valuable section to re-read before you ship a map.

| Failure mode | What it looks like | The check |
| --- | --- | --- |
| Scope too broad | A huge, impressive list with no shared profile | Can you state the segment in one sentence? |
| Coverage theater | "90%" with no stated denominator | Can you name the total in-segment population? |
| Contact list, not a map | Rows of names, no tenure or signal | Does every row have tenure and a signal? |
| Pool size by gut | A big number that collapses under filters | Have you shown the funnel multipliers? |
| Build once, forget | High confidence in a stale map | Is a cadence and an owner attached? |

**Scope too broad.** A map of "all engineers in London" is not useful; a map of "senior Go engineers at fintech companies in London" is. The false positive is a large list that impresses in a meeting and guides nothing.

**Coverage theater.** The 80-90% target is against the defined segment. A narrow scope inflates coverage, a vague one makes it unmeasurable. Because most maps cover only 20 to 50 hand-picked firms, "90% coverage" can still miss most of a 9,060-person national pool. Name the denominator.

**Contact list masquerading as a map.** Without enrichment, the rows are useless. Tenure, prior companies, flight-risk signals, and notable work are what make the map a planning tool. If a row has only a name and a title, it is not mappable.

**Pool size by gut.** The false positive is a big raw number that collapses after reach, reply, and interest filters. Show the multipliers or do not quote the number.

**The "70% passive" trap.** The headline that most talent is passive is technically true and strategically useless - it tells you pool size but nothing about who will reply or who is worth an InMail. Segment the receptive 5 to 10% separately.

**Keyword-only matching.** Matching on title keywords converts no better than cold email, while behavioral-signal matches convert at 2 to 3x keyword-matched candidates. Rank rows on signal and tenure, not on title strings.

**Build-once-and-forget.** Maps that are not refreshed on pace with skill change give false confidence. With a roughly 2.5-year half-life of technical skills and the WEF projecting 39% of workers' core skills change significantly by 2030, a static map ages fast.

**Internal data skipped.** Mapping externally for a role an internal successor already fills wastes the whole effort. Audit the bench first.

## Attach a refresh cadence so the map stays alive

Decay, not errors, is what kills talent maps, so every map ships with a cadence and a named owner. A six-month-old map of senior talent may already have 20% of names at new companies - that drift is why cadence is arithmetic, not administrative.

Match the cadence to the velocity of the role family. High-velocity functions run quarterly; high-priority critical roles may need monthly updates; executive and specialist families can run annually with a light pass when a req opens. Layer trigger-based refreshes on top for off-cycle events.

| Role family | Base cadence | Off-cycle trigger |
| --- | --- | --- |
| High-velocity (eng, sales) | Quarterly | Competitor layoff or comp shift |
| High-priority critical roles | Monthly | Named candidate job change |
| Executive / specialist | Annual + light pass at req open | Comp benchmark move |

Base cadences follow practitioner convention; triggers are the events worth watching for. Monitoring can flag off-cycle changes automatically: someone changed jobs, a target company announced layoffs, or a new candidate entered the market. One of the sharpest triggers is a competitor hiring pullback, which is exactly when a mapped segment becomes reachable. A query like finding platform engineers at companies that recently announced layoffs with open-to-move signals is the kind of trigger pass that keeps a map warm between full refreshes.

## Package, calibrate, and keep it current

Package the analysis into a one-page brief, not a raw spreadsheet, so the hiring manager can calibrate "good" against real people. Review about 20 profiles from your target companies to draft an ICP persona capturing title, scope of ownership, depth of domain, and the signal density that separates the top 10% from the merely qualified. Then pull five example profiles into the brief.

The brief should carry talent density by geography, competitor org structures where you reconstructed them, candidate persona summaries, the pool-size estimate with its funnel, and the coverage figure with its denominator. Cataloging 40 named external candidates at competitor companies as backup is a realistic target for a single role family.

**One-page calibration brief skeleton**

```
SEGMENT: <role, seniority, geography, horizon in one sentence>
COVERAGE: <X%> of <denominator: total in-segment population>
POOL SIZE: <addressable> -> <reachable now> -> <likely interested>
  Assumptions: receptive 5-10% / reply 30-50% / interest / offer-accept
COMPANY TIERS: Tier 1 <direct>  Tier 2 <adjacent/academy>  Tier 3 <feeders>
PERSONA: title / scope of ownership / domain depth / top-10% signals
FIVE EXAMPLE PROFILES: <name, company, tenure, standout signal> x5
REFRESH: cadence <quarterly/monthly/annual> | owner <name> | next review <date>
```

*Replace the bracketed prompts with your segment's specifics; keep it to one page.*

Before you call the map done, run the checklist. It encodes every failure mode above as a thing to verify.

#### Ship checklist for a talent map

- [ ] The segment is stated in one sentence the hiring manager signed off.
- [ ] The company list is 20 to 50 firms, each tagged by tier.
- [ ] Internal bench and feeder patterns were audited before external mapping.
- [ ] Coverage is stated as a percentage with its denominator named.
- [ ] Every row has tenure, a signal, and a last-updated date.
- [ ] The pool-size estimate shows its funnel multipliers and nets out geography.
- [ ] The receptive 5 to 10% is segmented separately from raw pool size.
- [ ] A refresh cadence and a named owner are attached, with trigger rules.

Keeping the map current is cheaper than rebuilding it. The research cost of a first build - about a week of recruiter time per function - amortizes across every req the map serves, and 44% of sourced hires now come from people already in a company's CRM or ATS, up from 29.1% a few years earlier. A maintained map is that CRM, built deliberately. Set the next-review date the day you ship, name the owner, and let the trigger alerts do the off-cycle work so the next search starts warm.

## Frequently asked questions

### How many companies should a talent map cover?

Most working talent maps focus on 20 to 50 target companies rather than the full market. Tier them: direct competitors first, then adjacent industries and feeder or academy companies people move from, plus notable recent IPOs or fast-growing startups that build the same skills. The cap exists because employer concentration is real. In Refolk's UK Platform Engineer sample one bank and a single city accounted for a large share of profiles, so a handful of Tier-1 firms delivers most of the segment.

### What coverage percentage means a talent map is complete?

The practitioner convention is 80 to 90% coverage of the defined segment, not the whole market. No regulator or benchmark body publishes a coverage standard, so this figure is convention rather than law. The number is only honest if you can name the denominator: the total in-segment population you are measuring against. A narrow scope inflates coverage artificially, and a vague scope makes coverage unmeasurable.

### How do I derive a defensible talent pool size estimate?

Use funnel math, not a gut figure. Start with the total addressable pool, then multiply by the share you can actually reach, reply rate, the share of repliers genuinely interested, and interview-to-offer and offer-acceptance rates. Net out geography you cannot hire in first. In Refolk's index the US Platform Engineer / SRE pool is 9,060, but with only 5 to 10% receptive in a 90-day window that is roughly 450 to 900 reachable now, before reply and interest filters.

### How often should I refresh a talent map?

Match cadence to velocity. High-velocity functions like engineering and sales benefit from a quarterly refresh; high-priority critical roles may need monthly updates; executive and specialist families can run annually with a light pass when a req opens. Add trigger-based refreshes for competitor layoffs, comp benchmark shifts, and named-candidate job changes. A six-month-old senior map can already have around 20% of names at new companies, so cadence is not optional.

### What fields turn a list of names into a usable talent map?

Enrichment is what separates a planning tool from a contact list. Each row needs name and current role, company and tenure, seniority and function, location, key skills and signals, contactability with a verified path and status, and source plus last-updated date. Expert maps also record where the person sits in the reporting line. Without tenure and at least one behavioral signal per row, the map cannot be ranked or trusted.

### Is building a talent map before a role opens worth the time?

Yes, because the cost amortizes across requisitions. Research is the bulk of the work, roughly a week of recruiter time per function, but one backend-engineering map served three reqs over six months, dropping per-req cost each time. Organizations using continuous talent mapping report 38% shorter time-to-fill on critical roles, and direct sourcing yields about 4x more hires per application than job boards.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/talent-map-playbook-named-pool*