← all playbooks

See where a competitor hires from and who is taking its people

Two ranked tables for one company and one function: the employers its current people joined from, and the employers its leavers went to, each with a count, the years of the moves and the sample size behind it. It is a sample of dated career histories, not a census, and the output says so.

use when
you want to know which employers feed a competitor's team and which ones are hiring its people away, before you decide where to source next
starts from
A list

The prompt

Paste it into Claude Code or the Claude desktop app with Hyreflow connected. The first line tells your agent to use Hyreflow, so it reads the play, asks before it spends anything, and hands the work back to you.

paste this into Claude
Use hyreflow and show me where the <FUNCTION> people at <COMPETITOR_NAME>
worked before, and where the ones who left went.

Their website is <COMPETITOR_WEBSITE>. I care about <TITLES_OR_SENIORITY> in
<COUNTRY_OR_REGION>, and moves since <YEAR>.

How I want it run:
- Count how many people match before you pull anyone, then propose a
  sample. Cap it at <MAX_PEOPLE> and print the cap at the top of the output.
- Current staff come from a search inside the company. For leavers, search
  public profiles that name it as a past employer, and tell me how many of
  those you could confirm.
- Pull dated work history for the sample. For current staff I want the
  employer straight before they joined. For leavers, the one straight after.
- Group trading names and subsidiaries of one employer together, and show
  me what you grouped.

Run five people first and tell me what the full sample costs before you do
the rest. Give me two ranked tables, feeders and destinations, with counts
and the sample size. Do not contact anyone.

Replace every <PLACEHOLDER> with your own detail. Everything else can stay as written.

What you need first

  • The competitor's name and website, and the function you care about, such as sales, engineering or finance
  • A sample cap you are comfortable with. Dated work history is paid per person, so the cap is agreed before anything runs
  • A Hyreflow workspace with credits

Tools it can reach for

The agent picks per step from what your workspace has. Nothing here is required by name.

What happens when you run it

Free steps are marked free. Anything that spends credits is marked, and the agent asks before the first paid run of any size.

  1. 1

    Pin down the company and the function

    free

    The competitor is tied to its website, and the function is widened into the job titles people there really carry. Both are shown back to you, because a search inside the wrong company or on one literal title wastes the whole sample.

  2. 2

    Count before pulling anyone

    credits

    People databases report how many profiles match a company and a title family alongside the smallest page they sell. That number decides how big a sample is worth buying, and the cap you agree is printed on the output.

  3. 3

    Pull the current-staff sample

    credits

    A search scoped to the competitor's own domain, filtered to your titles and region, capped at the agreed size. You pay per person returned, so the title filter stays on and the whole roster is never pulled.

  4. 4

    Find a sample of leavers

    credits

    People databases file people under their current employer, so leavers are found by searching public profiles that name the competitor as a past employer. Each search is billed whether or not it finds anyone, and a hit is only a lead until the dated history confirms it.

  5. 5

    Pull dated work history for both samples

    credits

    Each profile goes through a fixed chain of providers that stops at the first one to return a career history with start and end dates. It is paid per person, which is why the sample is capped. A profile that comes back with no history counts as a miss.

  6. 6

    Read the moves

    free

    For each current employee, the employer held straight before joining, with the year. For each confirmed leaver, the employer joined straight after. Leads whose history does not show the competitor are dropped and counted.

  7. 7

    Rank feeders and destinations

    free

    Trading names and subsidiaries are grouped, then both lists are ranked by how many moves each employer accounts for. The sample size, the confirmed leaver count and the pull date sit under the tables.

What a run costs

Credits are spent per candidate the play actually works, and a lookup that finds nothing usually costs nothing. The two figures are the run where the first provider answers and the run where every lookup walks its full chain.

candidatesif the first provider answersif every lookup walks the chain
25under $14.4 credits$3.535 credits
100$1.616 credits$14140 credits
500$7.676 credits$68680 credits
1,000$15150 credits$1351350 credits

Free before anything is charged

  • Pin down the company and the function
  • Read the moves
  • Rank feeders and destinations

What moves the number

  • Coverage on people search and work history. The chain stops at the first provider that answers, and only that provider bills.
  • How many candidates survive the free filters. Everything dropped before the paid steps costs nothing.
  • Providers you connect with your own key. Those calls bill your account, not your credits.

An estimate, not a quote, priced at the volume credit rate. Your agent sizes the run against your own workspace and tells you what it will cost before it spends anything.

A competitor's career histories are a map of where to source

A search tells you who works at a competitor today. It does not tell you how they got there. The dated work history does: the employer each person left to join, and, for the people who have since gone, the employer that took them.

Read across a few dozen histories and two patterns appear. The feeder companies are the employers the competitor keeps hiring from. People still working at those feeders sit one step earlier on a route the competitor has already proved, and few recruiters think to look there. The destination companies are the ones hiring the competitor's people away. They are rivals for the same talent, and employers with a proven appetite for that function.

Run it on a client's competitor and the same two tables answer a question clients rarely get evidence for: where do they find their people, and who is taking ours?

Dated history is bought per person, so this is a sample by design. The cap is agreed first and printed on the output.

What you get back

Two ranked tables for one company and one function. Feeders: the employer held straight before the competitor, how many of the sample came from it, and the years of those moves. Destinations: the employer joined straight after, with the same columns. Under both sit the sample size, how many leavers were confirmed out of how many were found, the employer names that were grouped together, and the pull date.

Nothing is sent, and no contact details are bought.

Variations worth knowing

One half only. If the question is where to source, skip the leavers. The feeder table is the more reliable half.

Split by seniority. Feeders for junior hires and for leadership hires are rarely the same. Ask for the tables cut by level.

Turn the feeders into a search. The top feeders become the source list for source from named competitors with your off-limits list enforced. For the wider market, see map a whole talent pool.

Where this goes wrong

Reading a sample as a census. A few dozen people out of several hundred show where the clusters are, not the full distribution. An employer that appears once is an anecdote. Quote the sample size with the table.

Leavers are harder to find than joiners. They come from a web search of public profiles, not from a database filter, and only count once dated history confirms them. That half is smaller and noisier.

Profiles lag and omit. A history holds what the person chose to write. Short stints and recent moves go missing.

Employer names do not match themselves. A group, its subsidiaries and an old trading name can be one feeder split three ways. The grouping is shown so you can correct it.

Small companies return little. A boutique competitor may have too few indexed people for a pattern to be real, and the output says so.

Questions

How big does the sample need to be?

Big enough that the main feeders show up more than once. A sample where every employer appears a single time tells you nothing, and a sample of the whole function costs more than the answer is worth. The agent reads the count first, proposes a size, states what it costs and waits. You can always extend a sample later, and profiles already paid for are kept.

Why is the leaver half weaker than the joiner half?

Because people databases are organised around where someone works today. The people search Hyreflow runs has no dependable filter on past employer, so leavers are found through a web search of public profiles and then confirmed against dated history. Fewer are found, some turn out to be wrong, and recent leavers may not have updated their profile. The output reports how many leads were found and how many were confirmed.

Do I pay for profiles that come back empty?

The work history lookup walks its providers in a set order and stops at the first hit, and a profile returned without any employment history counts as a miss, which usually costs nothing. The web searches for leavers are different: each search is billed whether or not it finds anyone. The five-person pilot shows what each row was really charged.

Can I show this to a client?

Yes, with the sample size on the page. It answers two questions clients ask without evidence: where do our competitors find their people, and who is taking ours. Present it as what a sample of public career histories shows. Presented as a complete picture of a competitor's hiring, it invites a challenge you cannot meet.

What do I do with the feeder list?

Source from it. People still working at a feeder are a step earlier on a route the competitor has already proved works, and they are rarely the first names on anyone's search. The destination list is useful in a different way: those employers compete for the same people, and they have shown an appetite for the function you recruit.