250 accounts and 500 people, about 315 verified work emails and 945 emails sent from inboxes on your own domain.
Give this to your agent
Using RouterGrowth, run this workflow: Find startups hiring backend engineers in Berlin and London and email their CTO. 250 accounts, 2 contacts 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 on the hiring signal: company.jobs x 250 jobs. Open roles matching the title and location; each job is a company already spending on the problem. 2. Qualify on firmographics: company.enrich x 250 companies. Headcount, industry and location to keep the accounts that fit. 3. Find the people: people.search x 500 profiles. 2 contacts per account by title and seniority, with current role. 4. Get the contact: contact.find x 350 (500 tried, 70% found), contact.verify x 350 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 250 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 945 (315 contacts x 3 steps). Sequence from inboxes on a domain you own, one call per email. 7. Read the replies: email.messages x 95 inbox reads. Poll the inboxes, classify replies, hand the warm ones to a human. Before sending: email.domain x 1, email.inbox x 2, on a domain I own. Budget for one run: about $14.98 plus $6.98 one-time setup. Run routergrowth inspect on any capability before the first call to confirm the quote.
Works in Claude, ChatGPT, Claude Code, Codex and Cursor. New workspaces start with $1 of credit. Get a key or read the setup guide.
Why it works
A startup hiring backend engineers is behind on its roadmap, and the CTO is weighing build against buy on everything that is not the core product.
A company that posts a role has already admitted it has the problem and has budgeted for it. The open role is the trigger, the job description is the context, and the person who owns that team is the buyer. These workflows source accounts from live job postings, qualify on firmographics, find the hiring manager and reach out while the role is open.
The first line, as your agent would write it
Two backend roles open since last month: is the team still building its own billing, or would you rather they spent those weeks on the product?
The workflow
7 stages and 2,990 calls on one key. Every call is quoted and reserved before it runs, and a lookup that finds nothing releases the hold.
Open roles matching the title and location; each job is a company already spending on the problem.
Headcount, industry and location to keep the accounts that fit.
2 contacts per account by title and seniority, with current role.
Charged on a match only: a miss is free, so the estimate is a ceiling.
One page per account and a few recent posts per person, so the opener is about them.
Poll the inboxes, classify replies, hand the warm ones to a human.
Sending infrastructure you own: a verified domain and enough inboxes for the daily limit. Charged once, reused on every run.
The receipt
About $14.98 for the whole run, plus $6.98 once for the sending inboxes. No subscription and no seats: each call is paid from a prepaid balance at the price shown before it runs.
| Capability | Calls | Cost |
|---|---|---|
| company.jobs$0.0035 per result | 250 | $0.88 |
| company.enrich$0.0071 per match | 250 | $1.77 |
| people.search$0.002 per call of up to 200 + $0.0004 per person | 500 | $0.19 |
| contact.find$0.0187 per match | 350 | $6.54 |
| contact.verify$0.002 per verdict | 350 | $0.70 |
| web.scrape$0.0056 per page | 250 | $1.40 |
| email.send$0.0035 per email | 945 | $3.31 |
| email.messages$0.002 per read | 95 | $0.19 |
| One run | 2,990 | $14.98 |
Assumptions: 2 contacts per account unless the brief says otherwise, a 70% email find rate, 90% of found addresses passing verification, 3 emails per contact and a 30% LinkedIn accept rate. Prices are the catalog's list prices when this page was built. Change the volumes and the assumptions in the workflow generator, or see how plans lower the price of every call.
# RouterGrowth workflow: Find startups hiring backend engineers in Berlin and London and email their CTO. 250 accou
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 on the hiring signal (company.jobs x 250)
routergrowth run -c company.jobs -i '{}'
# 02 Qualify on firmographics (company.enrich x 250)
routergrowth run -c company.enrich -i '{"domain":"<domain>"}'
# 03 Find the people (people.search x 500)
routergrowth run -c people.search -i '{}'
# 04 Get the contact (contact.find x 350, contact.verify x 350)
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 250)
routergrowth run -c web.scrape -i '{"url":"<url>"}'
# 06 Run the outreach (email.send x 945)
routergrowth run -c email.send -i '{"inbox_id":"<inbox_id>","to":"<to>"}'
# 07 Read the replies (email.messages x 95)
routergrowth run -c email.messages -i '{"inbox_id":"<inbox_id>"}'
FAQ
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.
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.
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.
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.
About $14.98 for one run of 2,990 calls, plus $6.98 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.
Keep going
Reading this as an agent? This workflow as markdown: /workflows/hiring-backend-engineers.md · every workflow: /workflows.md
Paste the prompt into your agent. The first calls run on the $1 that comes with signup.