# Reach clinic managers at clinics hiring nurses

150 accounts and 150 people, about 95 verified work emails and 285 emails sent from inboxes on your own domain.

Family: [Hiring signals](https://www.routergrowth.com/workflows/hiring-signals.md) · HTML page: https://www.routergrowth.com/workflows/hiring-nurses

## Give this to your agent

```text
Using RouterGrowth, run this workflow: Find clinics hiring nurses in Texas and Florida and email their practice manager. 150 accounts, 1 contact each, three-step sequence.
Show me the price before every call, and stop after each stage with a sample of the results so I can adjust.

1. Source the businesses: local.places x 8 map searches. Google Maps places for the category and area, with site, phone and rating.
2. Qualify on the signal: company.jobs x 150 companies. Keep the accounts where the trigger is real; the rest never reach outreach.
3. Find the people: people.search x 150 profiles. 1 contact per account by title and seniority, with current role.
4. Get the contact: contact.find x 105 (150 tried, 70% found), contact.verify x 105 verdicts. Charged on a match only: a miss is free, so the estimate is a ceiling.
5. Context for the first line: web.scrape x 150 pages. One page per account and a few recent posts per person, so the opener is about them.
6. Run the outreach: email.send x 285 (95 contacts x 3 steps). Sequence from inboxes on a domain you own, one call per email.
7. Read the replies: email.messages x 29 inbox reads. Poll the inboxes, classify replies, hand the warm ones to a human.

Before sending: email.domain x 1, email.inbox x 1, on a domain I own.

Budget for one run: about $4.68 plus $4.66 one-time setup. Run routergrowth inspect on any capability before the first call to confirm the quote.
```

## Why this works

A clinic that cannot fill nursing shifts loses revenue every day a room stays closed. The practice manager owns both the schedule and the vendors that could fix it.

The first line, as your agent would write it:

> You have had an RN role open in Tampa for six weeks. How are you covering those shifts in the meantime?

## The workflow, stage by stage

Source the businesses → Qualify on the signal → Find the people → Get the contact → Context for the first line → Run the outreach → Read the replies

| # | Stage | Calls | Cost |
|---|---|---|---:|
| 1 | Source the businesses | `local.places` x 8 | $0.03 |
| 2 | Qualify on the signal | `company.jobs` x 150 | $0.53 |
| 3 | Find the people | `people.search` x 150 | $0.06 |
| 4 | Get the contact | `contact.find` x 105, `contact.verify` x 105 | $2.17 |
| 5 | Context for the first line | `web.scrape` x 150 | $0.84 |
| 6 | Run the outreach | `email.send` x 285 | $1.00 |
| 7 | Read the replies | `email.messages` x 29 | $0.06 |
| + | One-time setup | `email.domain` x 1, `email.inbox` x 1 | $4.66 once |

One run: $4.68 for 982 calls. Assumptions: 2 contacts per account unless the brief says otherwise, 70% email find rate, 90% verification pass, 3 emails per contact, 30% LinkedIn accept rate. Prices are the catalog's at the time this page was built; `routergrowth inspect` returns the exact quote before a call.

### Source the businesses

Google Maps places for the category and area, with site, phone and rating.

### Qualify on the signal

Keep the accounts where the trigger is real; the rest never reach outreach.

### Find the people

1 contact per account by title and seniority, with current role.

### Get the contact

Charged on a match only: a miss is free, so the estimate is a ceiling.

### Context for the first line

One page per account and a few recent posts per person, so the opener is about them.

### Run the outreach

Sequence from inboxes on a domain you own, one call per email.

### Read the replies

Poll the inboxes, classify replies, hand the warm ones to a human.

## Run it from the command line

```bash
# RouterGrowth workflow: Find clinics hiring nurses in Texas and Florida and email their practice manager. 150 acco
npm install -g routergrowth && routergrowth setup

# one-time setup
routergrowth run -c email.domain -i '{"domain":"<domain>"}'
routergrowth run -c email.inbox -i '{}'

# 01 Source the businesses  (local.places x 8)
routergrowth run -c local.places -i '{"query":"<query>"}'

# 02 Qualify on the signal  (company.jobs x 150)
routergrowth run -c company.jobs -i '{}'

# 03 Find the people  (people.search x 150)
routergrowth run -c people.search -i '{}'

# 04 Get the contact  (contact.find x 105, contact.verify x 105)
routergrowth run -c contact.find -i '{"first_name":"<first_name>","last_name":"<last_name>","company_domain":"<company_domain>"}'
routergrowth run -c contact.verify -i '{"email":"<email>"}'

# 05 Context for the first line  (web.scrape x 150)
routergrowth run -c web.scrape -i '{"url":"<url>"}'

# 06 Run the outreach  (email.send x 285)
routergrowth run -c email.send -i '{"inbox_id":"<inbox_id>","to":"<to>"}'

# 07 Read the replies  (email.messages x 29)
routergrowth run -c email.messages -i '{"inbox_id":"<inbox_id>"}'
```

## Questions

### How do I find companies that are hiring for a specific role?

company.jobs returns live job postings for a title and a location, with the company behind each one. Your agent runs it once per segment, removes duplicates and keeps the companies that fit your size and industry before any contact is looked up.

### Why is an open role a buying signal?

A posted role is a budgeted problem. The company has decided to spend on it, written the requirements down in the job description and named a team that owns it. The leader of that team is the buyer, and the description gives you the first line.

### Who should I contact at a company that is hiring?

The person the new hire will report to, plus one level up. people.search finds them by title and seniority at the company, and contact.find returns a work email that is charged only when one is found.

### How fresh is the hiring data?

Each run reads postings that are live when it runs. A workflow you schedule weekly only needs the new roles, so the second run costs a fraction of the first.

### What does this workflow cost to run?

About $4.68 for one run of 982 calls, plus $4.66 once for the sending inboxes. Each call is quoted before it runs and a lookup that finds nothing is not charged, so the figure is a ceiling. There is no subscription: the run is paid from a prepaid balance.

## Related

- [Reach operations leaders at logistics firms hiring dispatchers](https://www.routergrowth.com/workflows/hiring-dispatchers.md)
- [Email finance leaders at UK companies hiring accountants](https://www.routergrowth.com/workflows/hiring-uk-finance.md)
- [Reach sales leaders at companies hiring SDRs](https://www.routergrowth.com/workflows/hiring-sdr-teams.md)
- [Reach CTOs at startups hiring backend engineers](https://www.routergrowth.com/workflows/hiring-backend-engineers.md)
- Guide: [How to find high-intent leads from hiring signals](https://www.routergrowth.com/use-cases/find-high-intent-leads.md)
- Guide: [Buying signals: score accounts on hiring, funding and tech changes](https://www.routergrowth.com/use-cases/company-buying-signals.md)
- Skill: [Cold email pipeline](https://www.routergrowth.com/skills/cold-email-pipeline.md)
- Skill: [Hiring-signal outbound](https://www.routergrowth.com/skills/hiring-signal-outbound.md)

Adjust the volumes and assumptions: https://www.routergrowth.com/free-gtm-tools/workflow-generator#q=Find%20clinics%20hiring%20nurses%20in%20Texas%20and%20Florida%20and%20email%20their%20practice%20manager.%20150%20accounts%2C%201%20contact%20each%2C%20three-step%20sequence.