# Reach data leaders at companies that use Segment

200 accounts and 400 people, about 252 verified work emails and 756 emails sent from inboxes on your own domain.

Family: [Technology signals](https://www.routergrowth.com/workflows/technology-signals.md) · HTML page: https://www.routergrowth.com/workflows/technology-segment-data

## Give this to your agent

```text
Using RouterGrowth, run this workflow: Find companies that use Segment and email their head of data or analytics lead. 200 accounts, 2 contacts each.
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 the signal: company.technologies x 200 companies. Keep the accounts where the trigger is real; the rest never reach outreach.
3. Find the people: people.search x 400 profiles. 2 contacts per account by title and seniority, with current role.
4. Get the contact: contact.find x 280 (400 tried, 70% found), contact.verify x 280 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 756 (252 contacts x 3 steps). Sequence from inboxes on a domain you own, one call per email.
7. Read the replies: email.messages x 76 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.11 plus $6.98 one-time setup. Run routergrowth inspect on any capability before the first call to confirm the quote.
```

## Why this works

A Segment customer has already decided customer data matters and has someone who owns it. That person evaluates anything that sits downstream of the event stream.

The first line, as your agent would write it:

> Since you route events through Segment, the hard part is usually what happens after the warehouse. Where do those events stop being useful?

## The workflow, stage by stage

Source the accounts → 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 accounts | `company.search` x 20 | $0.05 |
| 2 | Qualify on the signal | `company.technologies` x 200 | $4.20 |
| 3 | Find the people | `people.search` x 400 | $0.15 |
| 4 | Get the contact | `contact.find` x 280, `contact.verify` x 280 | $5.79 |
| 5 | Context for the first line | `web.scrape` x 200 | $1.12 |
| 6 | Run the outreach | `email.send` x 756 | $2.65 |
| 7 | Read the replies | `email.messages` x 76 | $0.15 |
| + | One-time setup | `email.domain` x 1, `email.inbox` x 2 | $6.98 once |

One run: $14.11 for 2,212 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 the signal

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

### Find the people

2 contacts 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 companies that use Segment and email their head of data or analytics lead. 200 accoun
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 the signal  (company.technologies x 200)
routergrowth run -c company.technologies -i '{"domain":"<domain>"}'

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

# 04 Get the contact  (contact.find x 280, contact.verify x 280)
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 756)
routergrowth run -c email.send -i '{"inbox_id":"<inbox_id>","to":"<to>"}'

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

## Questions

### How do I find companies that use a specific technology?

The agent sources companies in your segment with company.search, then company.technologies reads the stack detected on each one's site. The companies running the technology you named stay in the list; the rest never reach the contact stage.

### What are technographics used for in sales?

Qualifying before you spend on contacts. What a company runs tells you whether it can use your product, which integration to mention and who owns the decision.

### How accurate is technology detection?

It reads what is visible on the company's public site and pages, so front-end and marketing tools are detected reliably and internal systems less so. Treat a match as a strong signal and confirm it in the first reply.

### Can I build a list of the customers of a competitor?

When the competitor's product leaves a trace on its customers' sites, yes: name it in the brief and the same workflow keeps the companies where it is detected.

### What does this workflow cost to run?

About $14.11 for one run of 2,212 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.

## Related

- [Reach data engineering leaders at Snowflake customers](https://www.routergrowth.com/workflows/technology-snowflake-data-eng.md)
- [Reach finance leaders at companies that use Stripe](https://www.routergrowth.com/workflows/technology-stripe-finance.md)
- [Reach e-commerce marketers at brands on Klaviyo](https://www.routergrowth.com/workflows/technology-klaviyo-ecommerce.md)
- [Reach agency owners building on WooCommerce](https://www.routergrowth.com/workflows/technology-woocommerce-agencies.md)
- Guide: [Buying signals: score accounts on hiring, funding and tech changes](https://www.routergrowth.com/use-cases/company-buying-signals.md)
- Guide: [Lead enrichment: email finder, verification and company data in one API](https://www.routergrowth.com/use-cases/contact-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%20companies%20that%20use%20Segment%20and%20email%20their%20head%20of%20data%20or%20analytics%20lead.%20200%20accounts%2C%202%20contacts%20each.