Key takeaways
- RevOps owns the sequence library, the data and the definitions; SDR managers own coaching.
- Compare sequences within one segment, step by step, not rep against rep.
- Change one thing at a time and give each test enough contacts and time.
- Retire sequences on a schedule so the library stays small and comparable.
What does RevOps own in an outbound programme
RevOps owns the structure that every SDR works inside: the sequence library, the rules for who enters which sequence, the data and the reporting. SDR managers own message quality and coaching, and the SDRs own the research and the conversations.
Writing this split down prevents the most common problem: every rep running a private version of the same sequence, which makes results impossible to compare.
Which measures show whether a sequence works
Positive replies and meetings held show whether a sequence works; opens and clicks are weak signals at best. Track, for each sequence and each step, the measures below, all defined the same way for every team.
- Positive replies, defined in writing, so a polite no is not counted as interest.
- Meetings booked and meetings held.
- Pipeline created from those meetings.
- Bounces, opt-outs and complaints, as a health check on data and targeting.
- The step at which replies arrive, to show which touches earn their place.
How do you compare performance across SDRs fairly
Compare like with like: the same sequence, the same segment and the same period. A rep working enterprise accounts in a new territory will never match a rep working inbound leads, and ranking them side by side teaches nothing.
When one sequence does well for some reps and badly for others, the gap is usually coaching. When one rep does well on one sequence and badly on another, look at the content and the targeting.
How should RevOps run sequence experiments
Run one change at a time, with a start date, an end date and a written hypothesis. Split contacts at random between the old and new version within one segment, and wait until both have had time to finish the sequence.
Keep a changelog of every test and its result. Winning versions go into the shared library for everyone, and losing ones are recorded so nobody runs the same test again next quarter.
How often should sequences be reviewed
Review sequence health weekly, steps monthly and the whole library quarterly. The weekly look catches broken data and rising bounces early; the monthly review rewrites weak steps; the quarterly review retires sequences that no longer fit a segment or offer.
Who owns what in outbound sequences
One common split of responsibilities between RevOps and SDR management.
| RevOps | SDR manager | |
|---|---|---|
| Sequence library | Builds, versions and retires sequences | Requests changes and new sequences |
| Entry rules | Defines which contacts enter which sequence | Makes sure reps follow the rules |
| Message quality | Keeps approved versions in one place | Coaches reps on research and personalisation |
| Reporting | Sets definitions and builds the reports | Uses reports in one-to-ones and team reviews |
| Experiments | Designs tests and records results | Suggests ideas from what reps hear |
Where Pebbles Ai fits
- CapabilityOutreach contentOn Team plans and above, colleagues send campaign content for review and comment on it in the editor, and the team keeps an approved library of what has been checked.
- FoundationCompany IntelCompany Intel holds your business knowledge and brand voice, which every assistant works from, so drafts across the team start from the same positioning.
Common questions
Should SDRs be allowed to edit shared sequences?
Let them personalise individual messages but not change the shared steps. Suggestions go to RevOps, which tests them and updates the library for everyone.
How many active sequences should an SDR team run?
As few as cover your segments and situations, often one or two per segment plus a handful for inbound and re-engagement. A long tail of rarely used sequences makes results impossible to compare.
What is the difference between RevOps and sales ops for outbound?
Sales ops traditionally runs the sales team's tools and processes. RevOps spans marketing, sales and customer success, so it can connect sequence results to the wider revenue picture.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
