Building an outbound sequence that books meetings

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.

Trigger	What it signals	Detection cost	Typical reply lift vs cold
New hire in the buying role	New owner rebuilding their stack in the first 90 days	Low. LinkedIn plus enrichment	3x to 5x
Job posting describing your problem	They are staffing around a pain you automate	Low. Job board scraping	3x to 4x
Funding round in last 90 days	Budget exists and headcount is growing	Low. Public sources	2x to 3x
Technology install or removal	Stack change in progress, adjacent needs open	Medium. Tech detection vendors	2x to 3x
Product usage signal on your own free tier	Already experiencing the problem inside your product	Low if instrumented	5x to 10x
Competitor contract renewal timing	A window where switching is possible	High. Interviews and inference	3x to 6x
Firmographic match only	Nothing	None	1x baseline

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.

Building and enriching the list so the first line writes itself

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

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.

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.

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 page breaks down real sequences line by line, and the cold email guide 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.

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 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 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, and the tactical selling side is covered in 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 is a decent starting point for that cleanup, and the strategic context for the whole motion sits in the SaaS sales strategies 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.