---
name: designing-outbound-sequences
description: >-
  Designs multichannel outbound sequences as a matrix of tier and persona by
  buyer state, setting touch count, spacing, channel mix, message structure,
  exit rules, and reply-rate instrumentation. Use when the user says build a
  sequence, cadence design, outbound sequence, how many touches, email cadence,
  cold email framework, cold call script, sequence matrix, multichannel
  outreach, follow-up cadence, sequence A/B test, reply rate benchmark, or asks
  why our sequences are not getting replies. Use this skill whenever the task
  is deciding what to say and when to say it in outbound, even if the user only
  asks for "an email". Do NOT use for choosing which accounts and contacts to
  target (see building-icp-and-target-lists), for signal-triggered plays and
  response SLAs (see running-signal-based-plays), or for SPF/DKIM/DMARC and
  spam-rate remediation (see protecting-email-deliverability).
metadata:
  version: "1.0"
---

# Designing outbound sequences

Produce a sequence matrix — touch count, spacing, channel, message structure,
exit rule, and measurement plan — for each tier-and-persona combination. One
job: sequence design. Building the target list, firing signal plays, and
configuring sending infrastructure are out of scope.

## Workflow

Copy this checklist into your reply and tick items as you complete them:

```
- [ ] 1. Confirm inputs: tiers, personas, buyer state, daily rep capacity
- [ ] 2. Set touch count and timeframe per segment from the matrix
- [ ] 3. Assign channel per touch to a buyer job
- [ ] 4. Write email copy to the 4T structure
- [ ] 5. Write the call opener, problem proposition, objection path
- [ ] 6. Set exit, pause, and suppression rules
- [ ] 7. Define instrumentation and the reply-rate review loop
- [ ] 8. Validate against the pre-launch gate, fix, re-validate
```

**1. Confirm inputs.** You need the account tier (1:1 / 1:few / 1:many), the
persona, the buyer state (cold, partial intent, warm inbound), and how many
manual touches a rep can actually execute per day. A single rep can execute
10–15 quality touches per day
([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)); a matrix
that exceeds that number is a fiction and will be executed as templates. If any
input is missing, state the assumption you are using rather than stalling.

**2. Set touch count and timeframe.** Use this matrix as the default. It is a
sensible default, not a mandate — adapt where you can name the reason.

| Buyer state / segment | Touches | Timeframe | Channels |
|---|---|---|---|
| Cold, no signal — SMB | 6–8 | 10–14 days | Email, phone |
| Cold, no signal — mid-market / enterprise | 12–18 | 20–40 days | Email, phone, social |
| Partial intent (content download, site visit) | 8–12 | 17–21 days | Email, phone, social, video |
| Warm / inbound inquiry | 8–12 | 10–15 business days | Email, phone, meeting link |

(all rows: [Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence))

The general planning range for most B2B outbound is 6–12 touches over 2–4 weeks
([Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence)),
and effective sequences are also described as running 4–7 touchpoints
([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)). When those
ranges conflict for a segment, pick the *longer* timeframe rather than the
higher touch count, because the named failure mode is compressing too many
touches into too few days
([Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence)).

**3. Assign each touch a buyer job.** Every touch must do a different job for
the buyer, not repeat the last one louder. The reference progression: touch 1
problem awareness (email: specific pain point plus social proof); touch 2 value
education (phone call referencing the email); touch 3 social connection
(connection request with context); touch 4 ROI framing (email: case study or
benchmark)
([Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence)).
Extend the pattern for longer enterprise sequences by adding new stakeholders
rather than new adjectives.

**4. Write email copy to the 4T structure.** Use it for every cold email;
this step is low-freedom because the failure modes are consistent
([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)):

- **Truth** — open with an observable fact about the prospect (a company
  development, job change, hiring pattern, technology choice) that connects to
  the problem you solve.
- **Think** — raise an *unconsidered* problem as a neutral observation, not a
  leading question engineered to extract a yes.
- **Third-party credibility** — cite similar companies and specific outcomes
  instead of asserting that your product works, which removes seller bias.
- **Talk** — close with a low-friction ask ("Would it be worth a quick look?")
  rather than "Let's schedule a call."

Copy rules, all from the same framework
([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)): keep the
email under 80 words, because longer messages signal mass marketing; make the
subject line reference the Truth directly and prefer specificity over wordplay
("Your SDR expansion" beats "Quick question about your sales team"); use
customer language ("buried under email") over marketing language ("streamline
workflow"). Reject superficial personalization — first-name and company merge
fields, generic industry references, compliments on a recent post, and
templates with swapped variables all count as none.

**5. Write the call touches.** Structure every dial as context-first opener →
problem proposition → objection handling, because "the key to cold calling is
to get them to forget that it's a cold call"
([30MPC](https://www.30mpc.com/newsletter/the-ultimate-30mpc-cold-calling-framework)).

- **Opener.** Lead with context before your name — competitors you work with,
  peers in their region, a connection to their investor — and establish
  in-network peer status within the first 5 seconds. Never open with "How's
  your day?" or "Bad time?"; the second "puts you in a position of inferiority"
  ([30MPC](https://www.30mpc.com/newsletter/the-ultimate-30mpc-cold-calling-framework)).
  If you use a permission opener, tailor it to a specific trigger and state how
  long you need, because the untailored version "blindsides the prospect because
  you could literally be calling about anything," and context cannot be canned
  ([30MPC](https://www.30mpc.com/newsletter/the-ultimate-30mpc-cold-calling-framework)).
- **Problem proposition instead of a value prop**, in three parts: a triggering
  problem repainted "as if you were describing a movie scene" (who was there,
  what challenge, how they felt); a one-sentence solution in the form "we do X
  so that the problem goes away," where X is your single biggest
  differentiator; and an interest-based CTA, because meetings feel heavy and a
  small ask raises the odds of an initial yes. Buzzwords such as "single source
  of truth" or "all-in-one platform" fail, because people act to remove pain
  faster than to gain benefits
  ([30MPC](https://www.30mpc.com/newsletter/the-ultimate-30mpc-cold-calling-framework)).
- **Objection handling** — handle the reaction to the interruption before the
  objection itself: agree with the objection, incentivize the conversation with
  a diagnostic question, then sell the test drive rather than the purchase
  ([30MPC](https://www.30mpc.com/newsletter/the-ultimate-30mpc-cold-calling-framework)).

Size call volume honestly: cold-call connect rates run 5.5–6%, needing 16–18
dials per conversation, with 15–18% of connects converting to meetings
([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)).

**6. Set exit, pause, and suppression rules.** These are non-negotiable, because
they are what keeps a sequence inside the spam-rate ceiling that governs
whether anything is delivered
([Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence)):

- No open after 3 emails → pause and verify the contact data before continuing.
- Opens but no reply after 5+ touches → switch channel or pause 30 days; treat
  it as engagement decay, meaning the message is not resonating.
- Unsubscribe or spam complaint → remove immediately and suppress permanently.
- Positive intent signal → exit the sequence and move to personalized follow-up.
- Time re-engagement off intent signals such as pricing-page visits rather than
  fixed day intervals.

**7. Instrument reply rate.** Report reply rate per sequence, per persona, and
per segment size — never a single blended number, because campaign size alone
moves reply rate 2.8x (5.8% under 50 recipients versus 2.1% over 500)
([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)). Calibrate
against: average B2B cold reply rate 1–3%, platform-wide average 3.43%, highly
targeted campaigns 17–18%, and warm introduction rates of 30–50%
([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)). Do not
build the review loop on open rate: Google does not track open rates and cannot
verify third-party open reporting, so low opens are not a reliable indicator
([Google](https://support.google.com/a/answer/81126)).

**8. Validate before launch, then loop.** Run this gate on the drafted
sequence. If any line fails, revise and run the whole gate again. Only launch
when every line passes.

```
- [ ] Touch count and timeframe inside the segment's matrix row
- [ ] Daily touch load per rep <= 15
- [ ] Every touch mapped to a distinct buyer job
- [ ] Every email under 80 words with a Truth-anchored subject line
- [ ] No subject line begins with "Re:" or "Fwd:" unless a real reply
- [ ] Zero merge-field-only personalization
- [ ] Exit, pause, and permanent-suppression rules configured in the tool
- [ ] Reply-rate reporting split by persona and segment size
```

## Output format

Use this exact structure for the deliverable, because sequence tooling and the
weekly review both read it positionally. Copy wording per touch is yours.

```markdown
# Sequence matrix — <segment>

| Tier | Persona | Buyer state | Touches | Days | Channel mix | Owner |

## Sequence: <tier> / <persona>
| # | Day | Channel | Buyer job | Asset / message | Notes |
| 1 | 0 | Email | Problem awareness | subject + body | 4T, 74 words |

### Copy
Touch 1 — Subject: <...>
Truth: ... / Think: ... / Third-party: ... / Talk: ...

### Call touches
Opener: ... | Problem proposition: ... | Top objection path: ...

## Exit rules
<rule -> action>

## Instrumentation
| Metric | Split by | Target | Review cadence |
```

## Gotchas

- Reply-rate benchmarks are not comparable across list sizes. Comparing a
  50-recipient 1:1 sequence at 6% against a 2,000-recipient 1:many sequence at
  2% is measuring list size, not copy quality
  ([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)).
- Never prefix a subject line with "Re:" or "Fwd:" to fake a thread. Google
  explicitly prohibits it unless the message is an actual reply or forward, and
  it is a spam-classification trigger, not a clever trick
  ([Google](https://support.google.com/a/answer/81126)).
- Adding touches inside the same window is the classic degradation: compressing
  too many touches into too few days is the named failure mode, so extend the
  timeframe instead
  ([Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence)).
- "No open after 3 emails" is a data problem before it is a copy problem. Verify
  the address before touch 4; continuing to send to unverified contacts raises
  spam complaints, which is the metric that actually caps the program
  ([Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence)).
- The "Bad time?" opener feels polite and performs badly, because it is always a
  bad time for a busy prospect and the question concedes inferiority before the
  pitch ([30MPC](https://www.30mpc.com/newsletter/the-ultimate-30mpc-cold-calling-framework)).
- Vagueness, not length, kills the problem proposition: the biggest mistake is
  not being specific enough, and the bar is that the listener can visualize the
  problem ([30MPC](https://www.30mpc.com/newsletter/the-ultimate-30mpc-cold-calling-framework)).
- A "Think" line phrased to extract a yes reads as a trap and suppresses
  replies; keep it a neutral observation about an unconsidered problem
  ([11x](https://www.11x.ai/guides/josh-braun-cold-outreach-method)).
- Each CAN-SPAM violation can carry penalties up to $53,088 per the FTC, so an
  unsubscribe path that is not wired into the sequence tool is a legal exposure,
  not a hygiene gap
  ([Apollo](https://www.apollo.io/insights/what-is-the-ideal-number-of-touches-in-an-outbound-sales-sequence)).