← all playbooks

Turn a company's public team page into a qualified candidate list

Everyone named on the page as a row: name and title as printed, a LinkedIn profile where one person clearly matched, dated work history, and a score against your brief with the evidence quoted. Pages that could not be read are reported, never guessed at.

use when
a company's own team page already lists the people you want, and the databases hardly know the firm exists
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 read the people off this team page and tell me which of
them fit my brief.

Page: <TEAM_PAGE_URL>
Brief: <PASTE THE BRIEF, OR GIVE A FILE PATH / URL>

How I want it run:
- Read the names and job titles exactly as the page prints them. Do not
  open with a database search. The page is the roster.
- Public pages only. If the page needs a login, or the names sit inside
  images, stop and tell me. Do not look for another way in.
- Find each person's LinkedIn profile. Fill it in only when the name, the
  employer and the role all agree. Otherwise leave it blank.
- Pull dated work history before you score anyone. A bio on a team page is
  marketing copy, not a career.
- Score against <MUST_HAVES> and quote the evidence.
- Contact details only for the people who pass: personal email and
  LinkedIn, never work email.

Run five people first and tell me what the full run costs before you do the
rest. Do not contact anyone.

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

What you need first

  • The address of a public team, people or leadership page
  • The brief you are hiring against, even if it is one paragraph
  • 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

    Open the page and check it can be read

    credits

    The page is fetched once as text. A fetch is charged per page and can be charged even when the site blocks it, so a blocked page is not retried blindly. If the roster sits behind a login, or the names are inside images, the agent stops there and tells you.

  2. 2

    Read the names and titles off the page

    credits

    The roster comes back as rows of name and job title, kept exactly as printed, because the company's own page is more current than a database. A team split across department pages is mapped first, so the whole roster is read.

  3. 3

    Resolve each person to a LinkedIn profile

    credits

    Team pages rarely print profile links. A research run takes the rows and looks up each person, capped on effort and on the number of people so the spend is bounded. Anyone still missing gets a web search on quoted name, employer and role, charged per search whether or not it finds them.

  4. 4

    Keep only the clear matches

    free

    A profile link is filled in when the name, the employer and the role all agree. Two possible people, or a profile at another employer, leave the cell blank with a note. A wrong link is worse than none, because every later lookup then returns a stranger.

  5. 5

    Pull the dated work history

    credits

    The page gives a title and the profile gives a career. Employers, titles and dates are pulled for everyone with a confirmed link, and a provider answer with no work history in it counts as a miss.

  6. 6

    Qualify against the brief

    credits

    Each person is scored against your must-haves on the dated history, with the evidence quoted. Sector experience is never taken from a team-page blurb. People with no confirmed profile are listed as unscored, not dropped.

  7. 7

    Find contact details for the people who pass

    credits

    Personal email and LinkedIn only, through the personal-email providers in a set order that stops at the first hit. A miss usually costs nothing. The work address printed on the page is not used for a candidate approach.

  8. 8

    Hand over the list and what could not be read

    free

    A CSV with one row per person on the page, and a note of every page or person the agent could not read or match. Nothing is sent and nothing is written to your ATS.

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$3.131 credits$11110 credits
100$13130 credits$46460 credits
500$63630 credits$2282280 credits
1,000$1251250 credits$4554550 credits

Free before anything is charged

  • Keep only the clear matches
  • Hand over the list and what could not be read

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 work history and 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 company has already published its own roster

When you know which firm you want people from, the usual move is a company search in a people database. For a large employer that works. For the firms whose team pages recruiters tend to paste, the boutique consultancy, the owner-led engineering practice, the small specialist, the databases are thin or out of date. Some of the team is missing and the titles lag behind.

Meanwhile the company has printed the answer itself. A team page is the firm's own statement of who works there and what each person does, and it is more current than a database row. So this play does not search for the roster. It reads it, and then does the two things a page cannot: it works out which profile belongs to each name, and it finds out what each person has really done.

It is the narrow sibling of source from named competitors, which searches inside the companies you name. Use that one for larger firms. Use this one when the page is better than the data.

What you get back

A CSV with one row per person on the page: name and title as printed, the LinkedIn profile and how it was matched, the dated work history, the score against your brief with the evidence quoted, and a personal email for the people who passed.

With it comes a short note of what could not be read: pages behind a login, names held in images, and people listed without a title. Nothing is sent and nothing is written to your ATS.

Variations worth knowing

One firm, several pages. Bigger teams are split by department or spread over numbered pages. The site is mapped first, so the whole roster is read and not only the first screen.

Names you typed yourself. If a page cannot be read, paste the names and titles. Everything after the page read runs the same way.

Profile links only. If all you want is a link against each name, add the LinkedIn profile URL to a list is that job by itself.

Where this goes wrong

Login walls and picture rosters. They are reported and left alone. The play reads public text and nothing else.

A page with nobody on it. A stock-photo or contact page lists no one. The agent falls back to a search inside that company's domain and tells you.

Bios read as experience. A blurb that claims deep sector expertise is copy. Sector experience is only ever taken from dated history.

People who have left. A page can lag behind a resignation. The dated history shows the current employer, and a mismatch with the page is flagged, not hidden.

Leadership-only pages. Large companies publish the top table and not the team. You get those names and no more, so a company search is the better tool there.

Questions

Why read the page when a company search in a people database would do?

For a large employer a database search is fine. The firms whose team pages recruiters paste are usually small or owner-led, and those are exactly where the databases are thin or out of date. The page is the company's own statement of who works there, so it is treated as the roster. If a page turns out to list nobody, the agent falls back to a search inside that company's domain and says that it did.

What happens if the page is behind a login, or the team is shown as pictures?

It is reported and the play stops for that page. Only public text is read. The agent does not try to get round a login and it does not guess names from photographs. You can paste the names and titles yourself, and everything after the page read runs the same way.

Will it find the right profile for someone with a common name?

Only when it is clear. A link is kept when the name, the employer and the role agree, and the employer is a strong anchor here because everyone on the page shares it. If two people could be the match, the cell stays blank and both are listed. A blank is cheap to fill later. A wrong link quietly poisons the work history and the contact details bought after it.

What does it cost when the page turns out to be useless?

The page fetch, and nothing after it. A fetch is charged per page, and that can include a page the site blocks. The profile lookup is a research run that is charged when it completes, for what it came to, and the agent sets a fixed effort level and a cap on the number of people so that figure is bounded. Work history and contact details are bought for five people first, and for the rest only once you have seen the cost and approved it.

Can I hand over several pages at once?

Yes. A roster spread over several department pages of one firm is mapped and read as one team. Pages from different companies are kept as separate blocks in the output, so you can see how deep each firm's bench is. Start with one page, look at the result, then add the rest.