How RevOps consultancies reach software companies hiring their first RevOps person

Why this trigger

A company that posts its first RevOps role is telling you, in its own words, that the CRM has become a problem. The job post usually lists what is broken. Pipeline stages nobody trusts, forecasts built in spreadsheets, a sales tool nobody fully set up. The person who wrote that post, usually the head of sales, owns the problem until the hire starts, and the hire will take months.

That window is your opening. Either you help before the hire arrives, or you make the new hire productive in week one instead of quarter two.

Step 1, build the trigger list

Search the job boards once a week for "Revenue Operations", "RevOps", "Sales Operations" and "Sales Ops" roles. Keep companies where it is the first such role, which you can usually tell from the post itself ("you will build our RevOps function", "first hire in the team") or because nobody at the company has a RevOps title yet. Write down the website and one detail from the post.

website,job_detail
northloop.example,clean up our HubSpot pipeline stages
fairgrid.example,own forecasting and CRM hygiene

The job_detail column is a short phrase in their words. It goes into the email, so keep it lowercase and natural.

Step 2, find the people

Company domains   paste the websites from your trigger list
Job titles        VP Sales, Head of Sales, Chief Revenue Officer,
                  CRO, VP Revenue, Sales Director,
                  CEO, Founder, Co-Founder
Employees         11-50, 51-200
Must have         email

Keep founders in for companies under 50 people. They often still own the CRM. Above 50, the head of sales is the right person and the founder is a second contact at most.

To see which CRM each company runs, use the Technology filter with Hubspot or Salesforce on a second pass and split the list in two. The emails below have one line that changes with the CRM, so two campaigns read better than one.

Without the job boards

You can approximate the trigger with filters alone, at lower precision.

Industry          Software & Internet
Employees         51-200
Technology        Hubspot   (or Salesforce)
Job titles        as above

Then search the same companies for Revenue Operations and Sales Operations titles, and drop the companies where someone already holds one. Those are not first hires.

Step 3, bring in the custom column

Export the list, add job_detail by company website, and upload it as the campaign audience with Upload CSV, keeping job_detail as a custom field.

Step 4, the math

companies per week         60
people per company        2.5
new people per week       150   (30 per weekday)
emails per person           3
emails per weekday        ~90   once follow-ups overlap
per mailbox per day         5
mailboxes needed           18

The mailbox math is the same as in the Academy lesson on mailboxes and limits. Our own Microsoft mailboxes are set to 5 cold emails a day each, and we would start any new segment there.

Step 5, the sequence

Email 1, variant A

Subject  your RevOps hire

{Hi|Hey} {{first_name|there}},

Saw the RevOps role at {{company|your company}}, and the line about wanting someone to {{job_detail|sort out the CRM}}.

Most first RevOps hires spend their first quarter cleaning data before they can build anything. [What you do, in one sentence, for example: we do that cleanup in the weeks before they start, so they begin with a CRM they can trust.]

Worth a 20 minute look at what that would involve for you?

{{sender_first_name}}

Quoting their own job post is the strongest first line you can write here. Read it with the fallback too. "Wanting someone to sort out the CRM" is still true for almost every company hiring this role.

Email 1, variant B

Subject  before the RevOps hire starts

{Hi|Hey} {{first_name|there}},

Who owns the forecast at {{company|your company}} until the RevOps person starts?

Usually it is the head of sales, in a spreadsheet, on Sunday night. [What you do, in one sentence.] Happy to show you what the first two weeks would look like.

{{sender_first_name}}

Email 2, three days later, same thread

{{first_name|Hi}}, one more thought. If you would rather wait for the hire, we also [your onboarding offer, for example: work alongside them in their first month so the cleanup does not land on them alone].

Which would be more useful, before or after they start?

{{sender_first_name}}

A choice between two yeses is easier to answer than a yes or no.

Email 3, five days after that, same thread

Last note. If the role is filled or on hold, no worries. If you want, I can send the checklist we use for the first 30 days of a new RevOps hire. Reply "checklist" and it is yours.

{{sender_first_name}}

Only offer the checklist if you have one. It is a small, real thing to give, and a "checklist" reply is a keyword for the subsequence below.

Step 6, the subsequence for yes

Add one subsequence called Interested. Keywords are checklist, interested, tell me more, sure, yes, open to it, let's talk, send it, timing. First email in the next sending window.

Subject  Re: {{thread_subject}}

Here is the checklist [link to your checklist]. Most of it is the cleanup that has to happen before anything else works.

If you want to go through it for {{company|your setup}}, I have 20 minutes {Wednesday|Thursday} afternoon. Does that work?

{{sender_first_name}}

The bracketed link must be replaced before launch. The editor flags anything that looks like a placeholder, and the campaign will not start quietly with it in.

Step 7, reply handling

• "We just hired someone." Congratulate them and ask for the new person's name. The new hire is a better prospect than the sales leader now.
• "We do it in-house." Ask what they will measure the new hire on in the first 90 days. If you have an answer to that, there is a conversation. If not, move on.
• "What does it cost?" Give a real range in one line, then the call. Hiding the price in this audience costs replies.
• "Remove me." The Unsubscribe label catches it.

What to watch

This list is small and changes every week, so judge it per month rather than per week. If people answer with "we just hired someone" a lot, your trigger list is too old. Only use posts from the last 14 days. If variant A clearly beats B, it means the job post line is doing the work, so spend your time on better job_detail phrases rather than new email copy.

For reference, our own healthiest campaign reached a 3.5% reply rate per person contacted, out-of-office notices included, with 0.05% bounces, sent from mailboxes at 5 cold emails a day to a valid-only list. That was a different segment and offer, so treat it as a sanity check, not a target. The lesson on reading the numbers says which change to make for which result.