# Source senior backend engineers at fintech companies

200 accounts and 200 people, about 126 verified work emails and 378 emails sent from inboxes on your own domain.

Family: [Outreach by audience](https://www.routergrowth.com/workflows/audiences.md) · HTML page: https://www.routergrowth.com/workflows/audience-candidate-sourcing

## Give this to your agent

```text
Using RouterGrowth, run this workflow: Find senior backend engineers at fintech startups in London and email them about our team. 200 contacts, 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 accounts: company.search x 20 searches. Companies matching the industry, size and location, ten or so per search.
2. Qualify on firmographics: company.enrich x 200 companies. Headcount, industry and location to keep the accounts that fit.
3. Find the people: people.search x 200 profiles. 1 contact per account by title and seniority, with current role.
4. Get the contact: contact.find x 140 (200 tried, 70% found), contact.verify x 140 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 200 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 378 (126 contacts x 3 steps). Sequence from inboxes on a domain you own, one call per email.
7. Read the replies: email.messages x 38 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 $6.96 plus $4.66 one-time setup. Run routergrowth inspect on any capability before the first call to confirm the quote.
```

## Why this works

Senior engineers ignore recruiters and answer engineers. A message about the system they would work on gets a reply where a job description does not.

The first line, as your agent would write it:

> You have spent four years on payments infrastructure. We are rebuilding ours around a ledger. Curious what you would do differently this time?

## The workflow, stage by stage

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

| # | Stage | Calls | Cost |
|---|---|---|---:|
| 1 | Source the accounts | `company.search` x 20 | $0.05 |
| 2 | Qualify on firmographics | `company.enrich` x 200 | $1.42 |
| 3 | Find the people | `people.search` x 200 | $0.08 |
| 4 | Get the contact | `contact.find` x 140, `contact.verify` x 140 | $2.90 |
| 5 | Context for the first line | `web.scrape` x 200 | $1.12 |
| 6 | Run the outreach | `email.send` x 378 | $1.32 |
| 7 | Read the replies | `email.messages` x 38 | $0.08 |
| + | One-time setup | `email.domain` x 1, `email.inbox` x 1 | $4.66 once |

One run: $6.96 for 1,316 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 accounts

Companies matching the industry, size and location, ten or so per search.

### Qualify on firmographics

Headcount, industry and location to keep the accounts that fit.

### 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 senior backend engineers at fintech startups in London and email them about our team.
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 accounts  (company.search x 20)
routergrowth run -c company.search -i '{"query":"<query>"}'

# 02 Qualify on firmographics  (company.enrich x 200)
routergrowth run -c company.enrich -i '{"domain":"<domain>"}'

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

# 04 Get the contact  (contact.find x 140, contact.verify x 140)
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 200)
routergrowth run -c web.scrape -i '{"url":"<url>"}'

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

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

## Questions

### How do I find investors to email?

company.search returns funds by focus and stage, people.search finds the partners at each one and contact.find returns a work email that is charged only when found. The agent reads each fund's site for the first line.

### How do I build a media list?

news.search finds who has written about your topic recently, with the outlet and the article. The agent keeps the reporters on the beat, finds their address and cites their own piece in the pitch.

### Can I use this for recruiting?

Yes. people.search filters by title, seniority, company and location, which is candidate sourcing. The email goes out from an inbox you own, and replies come back to the same thread.

### Is every address verified before sending?

contact.verify checks each address and returns valid, invalid or unknown. The workflows send only to the valid ones, which protects the domain you send from.

### What does this workflow cost to run?

About $6.96 for one run of 1,316 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

- [Recruit agency partners that serve your buyers](https://www.routergrowth.com/workflows/audience-agency-partners.md)
- [Email partners at seed funds that invest in B2B software](https://www.routergrowth.com/workflows/audience-seed-investors.md)
- [Connect with angel investors who back developer tools](https://www.routergrowth.com/workflows/audience-angel-investors.md)
- [Build a media list of reporters who cover AI agents](https://www.routergrowth.com/workflows/audience-media-list.md)
- Guide: [Lead enrichment: email finder, verification and company data in one API](https://www.routergrowth.com/use-cases/contact-enrichment.md)
- Guide: [Waterfall enrichment without the waterfall bill](https://www.routergrowth.com/use-cases/waterfall-email-enrichment.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%20senior%20backend%20engineers%20at%20fintech%20startups%20in%20London%20and%20email%20them%20about%20our%20team.%20200%20contacts%2C%201%20contact%20each%2C%20three-step%20sequence.