# Connect with CROs posting about building RevOps

100 accounts and 200 people, 200 LinkedIn connection requests and about 126 verified work emails for the follow-up.

Family: [LinkedIn outbound](https://www.routergrowth.com/workflows/linkedin-outbound.md) · HTML page: https://www.routergrowth.com/workflows/linkedin-revops-hiring

## Give this to your agent

```text
Using RouterGrowth, run this workflow: Connect on LinkedIn with CROs and VPs of Sales who posted about building a RevOps function, then message the ones who accept and email the rest. 200 people, personalized from their posts.
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 10 searches. Companies matching the industry, size and location, ten or so per search.
2. Qualify on firmographics: company.enrich x 100 companies. Headcount, industry and location to keep the accounts that fit.
3. Find the people: people.search x 200 profiles. 2 contacts 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, linkedin.profile x 200 profiles read. Charged on a match only: a miss is free, so the estimate is a ceiling.
5. Context for the first line: web.scrape x 100 pages, social.posts x 600 posts. 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), linkedin.invite x 200 requests, linkedin.message x 60 (30% accepted). Connection request first, email to the rest; both from accounts you own.
7. Read the replies: email.messages x 38 inbox reads, linkedin.messages x 20 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 $9.58 plus $4.66 one-time setup. Run routergrowth inspect on any capability before the first call to confirm the quote.
```

## Why this works

A CRO announcing a RevOps build is about to buy the stack that function runs on.

The first line, as your agent would write it:

> Saw you are building RevOps from zero. Are you hiring the first person before or after choosing the tools?

## 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 10 | $0.02 |
| 2 | Qualify on firmographics | `company.enrich` x 100 | $0.71 |
| 3 | Find the people | `people.search` x 200 | $0.08 |
| 4 | Get the contact | `contact.find` x 140, `contact.verify` x 140, `linkedin.profile` x 200 | $3.30 |
| 5 | Context for the first line | `web.scrape` x 100, `social.posts` x 600 | $1.76 |
| 6 | Run the outreach | `email.send` x 378, `linkedin.invite` x 200, `linkedin.message` x 60 | $3.60 |
| 7 | Read the replies | `email.messages` x 38, `linkedin.messages` x 20 | $0.12 |
| + | One-time setup | `email.domain` x 1, `email.inbox` x 1 | $4.66 once |

One run: $9.58 for 2,186 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

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

Connection request first, email to the rest; both from accounts you own.

### Read the replies

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

## Run it from the command line

```bash
# RouterGrowth workflow: Connect on LinkedIn with CROs and VPs of Sales who posted about building a RevOps function
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 10)
routergrowth run -c company.search -i '{"query":"<query>"}'

# 02 Qualify on firmographics  (company.enrich x 100)
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, linkedin.profile x 200)
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>"}'
routergrowth run -c linkedin.profile -i '{}'

# 05 Context for the first line  (web.scrape x 100, social.posts x 600)
routergrowth run -c web.scrape -i '{"url":"<url>"}'
routergrowth run -c social.posts -i '{"platform":"<platform>","handle":"<handle>"}'

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

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

## Questions

### Can an AI agent send LinkedIn connection requests?

Yes, from your own account. You connect it once through a hosted sign-in, then linkedin.search, linkedin.invite and linkedin.message run as you, inside daily caps the platform enforces.

### How many invitations can it send a day?

Up to 30 a day per account, 20 in the first week, and 180 a week. The limit is enforced on every call, so a workflow of 300 people is spread over a couple of weeks.

### What should the connection note say?

One line about something the person posted. social.posts reads their recent posts so the agent can write a note that could only have been sent to them.

### What happens after someone accepts?

linkedin.messages shows who accepted and who replied. The agent messages the people who accepted and, in the workflows that say so, emails the ones who did not.

### What does this workflow cost to run?

About $9.58 for one run of 2,186 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

- [Connect with people who just started a sales leadership role](https://www.routergrowth.com/workflows/linkedin-new-role.md)
- [Connect with speakers at sales and marketing conferences](https://www.routergrowth.com/workflows/linkedin-event-speakers.md)
- [Connect with agency founders posting about client acquisition](https://www.routergrowth.com/workflows/linkedin-agency-founders.md)
- [Connect with sales leaders posting about hiring SDRs](https://www.routergrowth.com/workflows/linkedin-hiring-sdrs.md)
- Guide: [LinkedIn automation for AI agents: search, invite, message and read replies from one prompt](https://www.routergrowth.com/use-cases/linkedin-automation-for-ai-agents.md)
- Guide: [LinkedIn lead generation: turn competitor commenters into a qualified lead list](https://www.routergrowth.com/use-cases/competitor-commenters-to-leads.md)
- Skill: [Multichannel intent outbound](https://www.routergrowth.com/skills/multichannel-intent-outbound.md)
- Skill: [Cold email pipeline](https://www.routergrowth.com/skills/cold-email-pipeline.md)

Adjust the volumes and assumptions: https://www.routergrowth.com/free-gtm-tools/workflow-generator#q=Connect%20on%20LinkedIn%20with%20CROs%20and%20VPs%20of%20Sales%20who%20posted%20about%20building%20a%20RevOps%20function%2C%20then%20message%20the%20ones%20who%20accept%20and%20email%20the%20rest.%20200%20people%2C%20personalized%20from%20their%20posts.
