← all playbooks

Build the candidate pool for a funded company before its roles exist

For each recently funded company that fits your desk: the roles it is likely to open, marked as inference, and a small scored pool of people who could fill each one, ready to show before a job ad exists.

use when
a company in your niche has just raised and you want to open the conversation with people in hand, not a capability statement
starts from
Just your niche

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 build a candidate pool for the roles a recently funded
company is about to open.

Find companies that raised <ROUND_TYPES> in the last <DAYS> days in
<GEOGRAPHY>, in <INDUSTRIES>. My desk places <SPECIALISM>.

Then:
- Drop any company my desk could not serve. A raise alone is not a reason.
- For each one left, check which roles it already advertises, then tell me
  the <ROLES_PER_COMPANY> roles in my specialism it is most likely to open
  next, and why. Mark these as your inference, not as fact.
- For each likely role, source <POOL_SIZE> people near the company who
  could do it. Pull their work history and score them before I see them.
- No contact details yet. I will tell you who to find them for.

Run one company end to end first and tell me what the full run costs
before you do the rest. Do not contact anyone, candidate or company.

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

What you need first

  • Your niche: the disciplines you place and the geography you cover
  • The round types and the time window you care about
  • A cap on pool size per company, because this is speculative work
  • 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

    Pull the funding signal

    credits

    Recent rounds filtered by type, location and recency. Discovery is charged per round returned, so the window and the round types are set tight before it runs.

  2. 2

    Keep the companies your desk can serve

    free

    A filter on sector, size and location, using the data that came back with the round. Companies outside your disciplines are dropped before anything further is spent on them.

  3. 3

    Check what they already advertise

    credits

    The company's live openings are read so the pool is not built for a role that is already public. This lookup is charged per company whether or not it finds any openings.

  4. 4

    Infer the likely roles

    credits

    What the round is for, the company's stage and its sector are turned into the two or three roles in your specialism it will most plausibly open next. Each is labelled as inference with the reasoning shown, so you can overrule it before any sourcing runs.

  5. 5

    Source a small pool per role

    credits

    A search near the company for each likely role, counted first and capped at the pool size you set. Small on purpose: the role is a guess, and a guess does not earn a full search.

  6. 6

    Pull work history and score

    credits

    Dated career history for the pool, then a score against the inferred role with the evidence kept. Ask for people who have done the job at a company one stage further on and they rank first.

  7. 7

    Hold contact details until the role is real

    credits

    Personal email and LinkedIn are found only for the people you name, once the conversation with the company has started. Nothing is spent on reaching candidates for a role that may never open.

What a run costs

Credits are spent per company 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.

companiesif the first provider answersif every lookup walks the chain
25$990 credits$30300 credits
100$35350 credits$1191190 credits
500$1751750 credits$5955950 credits
1,000$3503500 credits$1,20011900 credits

Free before anything is charged

  • Keep the companies your desk can serve

What moves the number

  • The channel. This play buys personal email, because these are candidates, and a work inbox is the wrong place to approach one. A personal address costs more to find than a work one.
  • Coverage on people search, work history and personal email. The chain stops at the first provider that answers, and only that provider bills.
  • How many companies survive the free filters. Everything dropped before the paid steps costs nothing.
  • The scoring and drafting steps run on the metered agent, charged on what they read and write rather than per company, so they sit outside this table.
  • 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.

Turn up with people, not a pitch

A company that has just raised has a hiring plan in a spreadsheet and no job ads yet. The funding play uses that gap to find the person who owns the hiring and reach them early. This play is its twin. It uses the same gap to build the thing that makes that person reply.

Every agency that spotted the round sends the same message: congratulations, we recruit in your space, can we talk. A message that says "you will need a head of customer success next, and here are three people who built that function at companies one stage ahead of you" is a different kind of message. It shows you understand what the money is for, and it puts evidence on the table before anyone has asked.

You can only send it if the pool exists before the job ad does.

What you get back

Per company: the round, what it appears to be for, the roles already advertised, and the two or three roles the agent thinks come next, each marked as inference with its reasoning. Under each inferred role, a small scored pool: name, current title and employer, dated history and why they fit. No contact details until you ask, and nobody contacted.

Variations worth knowing

Name the roles yourself. If you know the pattern in your niche, put it in the prompt. Your read of what a medtech company hires first after a Series B beats anything inferred from a press release.

Anonymise for the pitch. Ask for the pool as blind profiles: career shape and evidence, no names. That is the version that goes to the company.

Size instead of source. Sometimes a number is enough: how many people near them could do this job. Sizing the pool costs less than sourcing it.

Where this goes wrong

Treating the pool as a shortlist. The role is a guess built from stage and sector. There is no spec, no salary and no hiring manager's view of the must-haves. The pool starts a conversation. When a real brief arrives, run a real search.

Going wide. This is speculative work. A small pool per role, across a few well-chosen companies, is the whole play. A large pool for every company that raised is a bill for roles that may never open.

Approaching candidates too early. Telling someone about a job that does not exist costs you that person twice: once when nothing follows, and again when the real role opens and they do not pick up.

A stale round. The window is short. A raise from several months ago has been worked by everyone, and the roles it paid for are already advertised or filled.

Questions

How can it know which roles a company will open?

It cannot know. It infers from what is public: the type and size of the round, what the company said the money is for, its sector and what it already advertises. A company that raised to enter a second market will need sales and country leadership. One that raised to finish a product will need engineers. Each inferred role is labelled as a guess with the reasoning beside it, and you can replace it before any sourcing runs.

Why not wait for the job ad and run a proper search?

Because by then you are one of several agencies answering the same ad. Opening with three relevant profiles and a view of the market is a different conversation from opening with a request for a call. The pool does not have to be perfect to do that job. It has to be credible.

Should I contact these candidates before I have the role?

No. The play does not look up contact details until you ask, and it never contacts anyone. Approaching people about a role that does not exist burns the candidates and your name with them. Show the company anonymised profiles first, and approach the people once there is something real to tell them.

How is this different from the funding play that finds the hiring manager?

That play finds the buyer. This one builds what you bring to the buyer. They share a trigger and run well together: one produces the contact, the other produces the reason that contact should reply.

Can I run this automatically every week?

Yes, once a manual run has shown that the role inference is sensible for your niche. It converts into a scheduled workflow that sweeps for rounds and leaves the companies, inferred roles and pools waiting in your workspace. It does not contact anyone. Prove it by hand first and keep the cap per company, because speculative sourcing on a schedule adds up.