# Building an outbound sequence that books meetings

> A working outbound cadence for SaaS: trigger selection, list building, a 14 touch multichannel sequence, copy rules and the reply rates to expect at each step.

Source: https://saas-marketing.net/playbooks/saas-outbound-sales-sequences/
Topic: SaaS Sales
Type: playbook
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/playbooks/saas-outbound-sales-sequences/

## Short answer

A working SaaS outbound sequence runs 14 touches across email, phone, LinkedIn and video over 21 business days, against a list built from a specific trigger rather than a firmographic filter. Expect cold email reply rates in the low single digits, connect rates on dials around 5 to 10 percent, and roughly 20 to 30 percent of booked meetings to no-show. Trigger quality matters more than sequence length: a 9 touch cadence on a signal-rich list beats a 30 touch cadence on a bought one.

## Key takeaways

- Trigger selection determines outcome more than copy, cadence length or tooling combined.
- A 14 touch sequence over 21 business days across four channels is the workable default for mid-market SaaS.
- Cold email reply rates of 2 to 5 percent are normal in 2026, and anything above 8 percent usually means a very narrow list.
- Roughly 20 to 30 percent of booked meetings do not happen, so plan capacity on meetings held rather than booked.
- Each touch needs one job. An email that introduces, proves and asks for a meeting does none of the three well.
- Mailbox infrastructure is a prerequisite, not an optimisation. Sending from your primary domain at volume is how you lose it.

---

Most outbound programmes are built backwards. Someone buys a tool, imports 8,000 contacts that match a job title and a headcount band, writes six emails, and then spends four months tuning subject lines while the real problem sits upstream in the list. Copy tuning on a bad list is rearranging deck chairs. This playbook starts where the influence is.

## Trigger selection beats everything else in the sequence

A trigger is an event that makes the problem you solve urgent this month rather than someday. Firmographics tell you someone could buy. Triggers tell you they might buy now.

Here is how the common triggers rank in practice, with the signal each one gives you and what it costs to detect.

The strongest trigger on that list is your own product data, and it is the one most outbound teams ignore because it lives in a different system. A free-tier user at a 400-person company who invited three colleagues last week is a warmer contact than anyone you will find on LinkedIn, and routing them properly is a joint sales and growth problem rather than an SDR one.

My position: a nine touch cadence against 150 contacts who all share a real trigger will beat a thirty touch cadence against 5,000 firmographic matches, on meetings held, on opportunity quality and on how long your SDRs stay in the job. Volume outbound against untriggered lists is a declining asset and has been for three years.

Write the first line of the email using only the trigger. If that line would read identically for 500 other companies, it is not a trigger, it is a filter. Delete it and find a real event.

## Building and enriching the list so the first line writes itself

List building has four steps and the third is the one people skip.

**From trigger to sequenceable list**

The evidence field is the whole trick. When your enrichment stores "posted a Senior RevOps Manager role on 14 August, requirement list mentions manual Salesforce reporting", the first line of your email writes itself and it is true. When it stores only company name and industry, your rep writes a generic opener and the sequence is dead before touch two.

## The 14 touch cadence, day by day

Four channels over 21 business days. Each touch has one job. The most common copy failure is an email that tries to introduce, prove and close in the same 200 words.

| Day | Channel | Job of this touch | Notes |
| --- | --- | --- | --- |
| 1 | Email | Earn a reply with one specific observation | Under 90 words. No links, no attachment |
| 1 | LinkedIn | Follow, no connection request yet | Passive familiarity |
| 2 | Call | Named reference to the email | Voicemail only if under 20 seconds |
| 4 | Email | One proof point from a comparable company | Name the company if you have permission |
| 6 | LinkedIn | Connection request, no pitch in the note | Blank or one line referencing the trigger |
| 8 | Call | Different time of day from touch 2 | Track which windows connect |
| 9 | Email | Reframe. A different problem angle | Assume angle one was wrong |
| 11 | Video | 45 second Loom showing their situation on screen | Highest reply rate per touch, highest cost |
| 12 | Call | Reference the video by name | The video makes this call warmer |
| 14 | Email | Forward your own thread with two lines up top | Keeps context, low effort, works |
| 16 | LinkedIn message | Short, one question, no attachment | Only if connected |
| 18 | Call | Final dial attempt | Leave a closing voicemail |
| 20 | Email | Permission to close the file | The highest reply rate email in the sequence |
| 21 | CRM | Disposition and recycle date | Not a touch, but the step that compounds |

Two of those deserve comment. The day 11 video is the highest performing single touch in most programmes I have seen, and also the most expensive, at roughly six to eight minutes of rep time including the screen setup. Use it only on accounts worth the time, which usually means your top tier.

The day 20 breakup email consistently outperforms every other email in the sequence on reply rate. That says something uncomfortable: a good share of your replies are people responding to the removal of pressure rather than to your value proposition. Write it plainly, offer to close the file, and do not add a fake deadline.

The recycle date matters more than any single touch. A contact who said "not now, ask me in Q1" and gets asked in Q1 converts at multiples of a cold contact. Most teams lose this entirely because the disposition field is free text.

A fully loaded SDR in a major market runs 85,000 to 130,000 dollars a year with tooling on top. At roughly 0.75 meetings held per 100 contacts sequenced and a realistic 1,200 contacts a month per rep, you are buying around 9 meetings held monthly per rep. Run that against your close rate and ACV before you hire the second one. For products under about 8,000 dollars ACV the maths usually does not work.

## Copy rules that survive contact with a real inbox

Six rules, and they are not stylistic preferences.

- Under 90 words for touch one. Anything longer gets skimmed on a phone and archived
- One ask per email, and in touch one the ask should be a question, not a calendar link
- No images, no tracking pixels on first send, no attachments. All three hurt deliverability and the pixel data is unreliable anyway
- Write the subject line as if you already know them. Three to five words, lowercase, no colons and no brackets
- Name the trigger in the first sentence, specifically enough that it could not be a mail merge
- Never claim a mutual connection, a previous conversation or a referral that did not happen

The most useful editing pass is reading the email aloud. If it does not sound like something you would say to someone standing next to you, rewrite it. Tools like Lavender score this automatically, and the scores are directionally useful without being gospel.

Concrete example of the difference. Weak opener: "I noticed you're in the RevOps space and thought our platform could help streamline your reporting." Strong opener: "Saw the Senior RevOps Manager role you posted on the 14th. The requirement list mentions manual Salesforce reporting three times, which usually means someone is rebuilding dashboards every Monday."

For more worked examples, the [cold email teardowns](/examples/saas-cold-email-teardowns/) page breaks down real sequences line by line, and the [cold email guide](/guides/cold-email-for-saas-sales/) covers the copy mechanics in more depth than this playbook has room for.

## The maths from contacts to closed deals

Do this arithmetic before you commit headcount, and use your own close rates rather than these.

Start with 1,000 contacts sequenced in a month. At a 4 percent all-in reply rate that is 40 replies, of which roughly a third are positive, so 13 positive replies. Say 10 convert to booked meetings. At a 25 percent no-show rate, 7 to 8 meetings held. At a 40 percent meeting-to-opportunity rate, 3 opportunities. At a 25 percent close rate, 0.75 closed deals per 1,000 contacts.

At a 30,000 dollar ACV that is 22,500 dollars of new ARR per 1,000 contacts sequenced. One rep working 1,200 contacts a month generates roughly 27,000 dollars of ARR monthly, or 324,000 annually, against a loaded cost of maybe 140,000. That works. Run the same maths at a 6,000 dollar ACV and it does not.

**0.75** Closed deals per 1,000 contacts sequenced, using mid-market SaaS conversion assumptions shown on this page

The number that moves this model most is not reply rate. It is the meeting-to-opportunity rate, which is determined by whether the meeting was booked with someone who had a real problem. Trigger quality shows up here, two steps downstream from where you set it. A well-structured [discovery call script](/templates/saas-discovery-call-script/) protects the same number from the other side.

## Infrastructure, tooling and the boring prerequisites

Three things have to be right before the first send, and none of them are optional.

Sending domains. Buy two or three variants of your domain, point them at your main site, and send cold volume from those. SPF, DKIM and DMARC configured on each. Warm each mailbox for two to three weeks before real sends, and cap at 30 to 50 sends per mailbox per day. This is the single most common reason a programme underperforms for reasons nobody can see, and it deserves its own read rather than a paragraph here.

Sequencing tooling. Outreach and Salesloft are the mature enterprise options, Apollo covers list building and sequencing together at lower cost, and Clay sits upstream doing enrichment and trigger detection. The [sales engagement platforms comparison](/tools/sales-engagement-platforms/) covers the trade-offs. Do not buy the expensive one until you have proved the motion manually with 200 contacts and a spreadsheet.

Call recording and review. Gong or an equivalent, with a weekly review of two calls per rep. Without it, coaching is opinion. The wider operating system this sits inside belongs in your [SaaS sales playbook](/templates/saas-sales-playbook-template/), and the tactical selling side is covered in [SaaS selling strategies](/guides/saas-selling-strategies/).

One more piece of hygiene. If you are also running paid search against the same accounts, keep the exclusion lists tidy so you are not paying to advertise to people already in an active sequence. The [SaaS negative keyword list](/templates/saas-negative-keyword-list/) is a decent starting point for that cleanup, and the strategic context for the whole motion sits in the [SaaS sales strategies](/saas-sales/) hub.

Next step: pick one trigger, build a list of 150 contacts who all share it, and run the 14 touch cadence manually for three weeks before you buy anything. If that batch does not produce meetings, more tooling will not fix it.

## Frequently asked questions

### What is a good reply rate for cold email in B2B SaaS?

Two to five percent across a full sequence is normal in 2026, counting all replies including negatives. Positive reply rates sit around 1 to 2 percent. Narrow trigger-based lists of under 200 contacts can reach 8 to 15 percent. If a vendor quotes you 20 percent reply rates on cold outbound at volume, ask how they define a reply and how many contacts the sample covered.

### How many touches should an outbound sequence have?

Fourteen across four channels over about 21 business days works for mid-market SaaS. Below eight touches you leave meetings on the table because most replies arrive after touch four. Above twenty you are mostly annoying people who already decided. Length is a weak lever compared with the quality of the trigger that put the contact on the list.

### What triggers work best for SaaS outbound?

In rough order of strength: a relevant new hire or leadership change in the buying role, a funding round in the last 90 days, a job posting describing the problem you solve, a technology install or removal detected on their stack, and a competitor contract approaching renewal. Generic firmographic targeting with no event attached performs several times worse.

### How many contacts do you need to book one meeting?

A common working model is 100 contacts sequenced, 3 to 5 replies, 1 to 2 positive, and 1 meeting booked. With a 25 percent no-show rate, expect about 0.75 meetings held per 100 contacts. At a 20 percent meeting-to-opportunity rate and a 25 percent close rate, one closed deal needs roughly 2,500 to 3,500 contacts sequenced.

### Should outbound email come from the company domain?

No, not at volume. Use separate sending domains that redirect to your main site, with their own warmed mailboxes, SPF, DKIM and DMARC configured, and a per-mailbox cap of around 30 to 50 sends a day. Sending cold volume from your primary domain risks the deliverability of your invoices, password resets and lifecycle email.

### Does cold calling still work for SaaS in 2026?

Yes, at lower connect rates than a decade ago. Expect 5 to 10 percent connect rates on direct dials and much lower on switchboard numbers. Calls work best as the second touch after an email has landed, because named recognition raises both pickup and tolerance. A call with no email before it is the hardest version of the job.

### What should the first outbound email say?

One observation about their situation, one sentence on the pattern you see at similar companies, and one small ask. Under 90 words. No attachments, no images, no calendar link in touch one. The job of email one is to earn a reply, not to explain your product, and the most common failure is trying to do both.
