Leadership market density: measuring the depth of a talent pool

Total headcount in a function or industry tells you almost nothing useful. There might be fifteen thousand people with 'VP of Marketing' in their title across a region, but the number who have run a demand-generation function at a company between $50M and $200M in revenue, in a specific category, within the last six years, could be a few hundred — or a few dozen.

Density is density within constraints. The constraints are the job itself: scope, scale, industry context, and recency of relevant experience. A density estimate that ignores these filters is just a vanity metric. A density estimate that applies them rigorously becomes a planning input, because it tells you whether you are searching a pond or an ocean.

Most leadership roles can be bounded using four filters applied in sequence. Function and level narrows by title equivalence — not literal title matching, but equivalent scope of responsibility. Scale narrows by the size of organization or budget the person has operated at, since a leader who has run a 20-person team rarely transfers cleanly into running 200. Industry or category narrows by domain fluency, distinguishing someone who understands the buyer and regulatory environment from someone who would need a year to catch up. Geography or mobility narrows by where candidates actually live or are willing to relocate to, which matters enormously for in-person or hybrid leadership roles.

Each filter should be applied with intent rather than reflexively. Over-filtering on industry, for example, can shrink a dense pool into an artificially thin one when the underlying skill is actually transferable — a topic covered in more depth in the companion guide on adjacent-industry talent.

Start by writing the role's non-negotiable scope in one sentence — for example, 'owns a $40M-plus paid marketing budget across two or more regions.' Then identify the realistic population: the universe of companies that would produce someone with that scope, typically 15 to 40 companies depending on the industry's concentration. For each company, estimate how many people currently or recently held an equivalent role — usually one to three per company, since most leadership functions have a single owner at any time.

Multiply the company count by the average leaders-per-company figure, then apply a mobility discount, since not everyone in that population is open to moving, even passively. For planning, test several explicit availability assumptions rather than applying a supposedly universal discount. For example, a hypothetical 70 percent reduction is a sensitivity scenario, not a benchmark; willingness, mobility and compensation require direct confirmation. What remains is not a list of candidates — it is a structural estimate of how large the addressable pool actually is.

Consider a company hiring a Head of Revenue Operations to support a $60M ARR SaaS business selling into mid-market accounts. The scope filter rules out RevOps leaders who have only worked in enterprise or SMB motions, since the GTM muscle differs meaningfully. The scale filter rules out anyone who has not operated with a book of business above roughly $40M ARR, since smaller-scale RevOps leaders often have not built the systems this role requires. The industry filter is kept loose, since RevOps skill transfers reasonably well across B2B SaaS verticals.

In this hypothetical calculation, 30 companies produce an initial population of 45 leaders. Reviewing scale leaves 32; applying the industry requirement leaves 24. An explicitly assumed availability reduction of about 46 percent leaves 13. These inputs are illustrative and should be tested against actual evidence rather than borrowed as market-wide rates. The planning value is the distinction between qualification and confirmed willingness, not an impression of precise market measurement.

The chart above illustrates how each filter removes a portion of the population rather than a fixed count, so the effect compounds. Starting from an invented base of 45 plausible leaders, the scale filter removes those who have not operated at the required budget size, leaving 32. The industry filter removes those without adjacent domain fluency, leaving 24. The mobility discount — applied last because it reflects willingness rather than qualification — removes roughly 46 percent of the remaining 24, leaving an estimated 13 people who are both qualified and plausibly reachable.

The order of presentation matters for interpreting which assumptions narrow the pool. If fixed percentages were applied independently, their multiplication would give the same final result in any order; in actual reviewed records the criteria can overlap, so teams should document counts at each step. Running the filters in a consistent sequence makes density estimates comparable across different roles and searches over time.

The most common mistake is anchoring on title rather than scope — assuming anyone with 'VP' in their title is interchangeable, when scope varies enormously between companies of different sizes and structures. A second mistake is ignoring recency, counting someone's relevant experience from eight years ago as equally valid as a current mandate, when markets, tools, and buyer behavior have moved on. A third is treating density as static; headcount growth, layoffs, and M&A activity shift the available pool constantly, so an estimate from a year ago may no longer hold.

A fourth pitfall is failing to distinguish between density and availability. A market can be dense with qualified people who are deeply entrenched and unlikely to move, which should change sourcing strategy and timeline expectations even though the raw numbers look healthy.

The real value of a density estimate is not analytical precision — it is the conversation it enables with hiring managers and boards before a search begins. A density figure in the low teens tells a stakeholder that the search will take longer, that compensation flexibility matters more, and that the brief may need to widen on one dimension, such as geography or adjacent industry. A density figure in the high dozens suggests a faster process is realistic and a narrower brief is affordable.

Framing this early avoids the common friction point where a search stalls at week six and stakeholders ask why 'there aren't more candidates,' when the honest answer was knowable from the outset. Density estimates reframe that conversation from frustration to planning.

Once a density estimate is in hand, it becomes a direct input into brief calibration. If the number is uncomfortably small, the team has three levers: widen the scale band, loosen the industry filter to include adjacent sectors, or expand the geographic radius. Each lever has a cost — widening scale may mean more onboarding risk, loosening industry may mean a longer ramp, and expanding geography may mean relocation packages. Choosing which lever to pull should be a deliberate trade-off discussion, not an afterthought once a search has already stalled.

This is where a density estimate and a role calibration exercise work together: density tells you how much room exists, and calibration tells you which dimension is safest to flex given the actual requirements of the job.

PeerSearch.ai can support an initial working set: start with an executive’s LinkedIn URL, then use prompts to filter and reorder the profiles returned. Projects can organize selected profiles and History preserves past searches. A search is capped at 200 profiles, including the starting executive, so a result set is not a complete market census. Export access depends on the plan; scope, availability and suitability still require independent review.

Regardless of the tool used, the discipline is the same: define the boundary honestly, apply filters in a consistent order, and treat the resulting number as a planning input rather than a precise headcount.