← all playbooks

Ask the people you placed for referrals into a live role

The people you placed who are worth asking, where each of them works today, the live role each one is best placed to refer into, and a short personal referral ask drafted and staged for your review.

use when
you have years of placements in your database and no habit of asking those people who else is good
starts from
Your database

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 ask the people we placed for referrals into my live roles.

Pull our placements from <CRM_NAME> for the last <YEARS> years. If the CRM
does not expose placements, use this export: <PLACEMENTS_FILE>

Leave out anyone placed in the last <MONTHS> months, they are still inside
the guarantee, and everyone on this list: <EXCLUSIONS>

For everyone left:
- Check whether they still work where we placed them. Mark the ones who
  have moved.
- Match each person to the one live role closest to their own discipline.
  My live roles: <READ THEM FROM THE CRM, OR PASTE THEM>
- Draft a short personal note from <RECRUITER_NAME> that mentions the
  placement and asks who they rate for that role. Ask about people they
  worked with before, never their current colleagues.
- Personal email or LinkedIn only. Use what is on file, look up the gaps.

Run five first and tell me what the full run costs before you do the rest.
Stage the drafts, do not send anything.

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

What you need first

  • Your placements: read from a connected CRM that exposes them, or an export with name, client, role and start date
  • At least one live role you want referrals for
  • A Hyreflow workspace with credits, for the employer check and any missing contact details
  • Optional: a connected sequencer with a paused campaign, if you want the drafts staged

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

    Read your placements

    free

    Where your CRM exposes placements the agent reads them directly: who, which client, which job and the start date. Where it only exposes pipeline stages, it reads who reached the placed stage, job by job. Otherwise you hand over an export.

  2. 2

    Take out the people you should not ask

    free

    Placements still inside the guarantee period and everyone on the exclusion list you supply. With lemlist connected, people who unsubscribed there come out too. The filter runs on your own data and costs nothing.

  3. 3

    Check where each person works today

    credits

    Each person's profile is checked against the employer you placed them with. The check reports a change of employer and nothing else, and it needs a LinkedIn profile to work from.

  4. 4

    Read your live roles

    free

    Open jobs are read from the same CRM, or taken from what you pasted, so every ask can name one real role.

  5. 5

    Match and draft the ask

    credits

    Each person is matched to the live role closest to their own discipline, and a short note is drafted: who you are to them, the one role, and a direct question about who they rate. No fee talk unless you add it.

  6. 6

    Fill in missing contact details

    credits

    Most placed candidates already have a personal email on file, and that is used as it stands. Only the gaps are looked up, in a set order that stops at the first hit, then checked for deliverability. A work address at your client is never used.

  7. 7

    Stage it for your review

    free

    Drafts go into a paused campaign as per-person text, or come back as a file to send from your own inbox. Starting a send is your action.

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
25$7.676 credits$14140 credits
100$31310 credits$58580 credits
500$1531530 credits$2882880 credits
1,000$3053050 credits$5755750 credits

Free before anything is charged

  • Read your placements
  • Take out the people you should not ask
  • Read your live roles
  • Stage it for your review

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 personal email. 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.
  • The scoring and drafting steps run on the metered agent, charged on what they read and write rather than per candidate, 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.

The warmest list you own, and the one nobody works

Everyone you placed took your call once, trusted you with a career move and got a job out of it. They know what good looks like in their discipline, they know who was good at their last two employers, and they have a reason to help you. No list you can buy is warmer than that.

Almost nobody works it. Referrals arrive when a placed candidate happens to think of you, which is rarely. Asking properly means pulling the placements, checking who is still where, choosing the right role to ask each person about and writing forty short personal notes. It is a job nobody gets round to, so it does not happen.

This play does that job. You read the drafts and press send.

What you get back

A table of placed people worth asking: name, the client and role you placed them in, whether they are still there, the live role matched to them and why, the personal email or LinkedIn profile to use, and the drafted ask. Separately, the people who were filtered out and the rule that removed each one. Drafts are staged and idle.

Variations worth knowing

Start with the leavers. People who have moved on since you placed them carry two networks and have left an open seat behind them. The job-change play covers that conversation in full.

One discipline at a time. Referrals work best where the role and the person's background match closely. Run it per desk, and skip anyone with no live role near their field.

Add your referral terms. If you pay for referrals, say so in the prompt and it goes in the note. The play does not invent an incentive you did not give it.

Where this goes wrong

Asking for their current colleagues. They work at your client. The ask is about people they rated elsewhere, and any name that comes back gets screened against your off-limits list like anyone else.

Asking too soon. Someone a few weeks into a job you found them is still settling in and still inside your guarantee. The filter takes them out. Leave it on.

Using the address on the placement record. Many CRMs hold the work email at the client, added after the start date. A referral ask sent through your client's mail server is a bad look. Personal email or LinkedIn only.

Records without a profile. The employer check works from a LinkedIn profile, and placements from years back often lack one. Resolve those first, or accept that those rows go unchecked.

Questions

Can it read placements from my CRM?

From some. JobAdder and Spott expose placements directly, so the agent reads them with the candidate, client, job and dates attached. TrackerRMS exposes them through its shortlist search, and is connected by the Hyreflow team, not self-serve. Loxo and Atlas expose the pipeline stage of each candidate on a job, so the placed stage can be read job by job, which is slower. For anything else, export the placements report you already run and hand over the file. The rest of the play is the same.

Why tie the ask to one live role?

Because 'do you know anyone looking' gets no answer. It is too big a question and nobody keeps a list. 'Who is the best site manager you worked with at your last firm' is a question a person can answer in one line, and it is obviously not a mailshot.

Is it a problem that they work at my client?

Asking them for names is fine. Asking them to refer their current colleagues is asking them to help you take staff from your own client. The draft asks about people they worked with before, and any name that comes back is screened against your off-limits rules like any other candidate.

What if they have left the job I placed them in?

Then one check has told you two things: a seat at your client has emptied, and the person has a second employer's worth of colleagues to recommend. Those rows are marked, because the conversation is different and usually deserves a call, not an email.

Can this run on a schedule?

Yes, once the manual run reads right. It converts into a scheduled workflow that picks up placements as they pass out of the guarantee period and leaves the list and the drafts waiting in your workspace. It never sends. Prove it by hand first: a referral ask is personal, and a badly worded one on repeat does damage.