Structure · Sequence / Cadence Design
Design a Multi-Channel Outbound Cadence (Email + LinkedIn + Call)
Architect a 17-day email + LinkedIn + call cadence with clear channel sequencing rules and SDR-friendly task design.
managerfounderAdvanced⏱ 3-4 hours
When to use
Use this when you're building outbound for an SDR or BDR team and email-only isn't converting on your highest-tier accounts. It's the prompt for top-of-funnel tier-1 ABM lists where you need orchestrated touches across channels. Build one cadence per persona-account tier combo.
The prompt
You are an outbound sales architect who's built multi-channel cadences for SDR teams selling agency services into the Fortune 5000. Agency: [AGENCY_NAME] — [SERVICES] | ICP: [ICP_DESC] | Trigger to start cadence: [TRIGGER] | Tools: [SEQUENCE_TOOL] + [DIALER] + LinkedIn Sales Nav | SDR capacity: [DAILY_TASK_LOAD] tasks per rep per day Design a 17-business-day multi-channel outbound cadence (email + LinkedIn + call) that respects SDR task load and orchestrates channels intentionally — not randomly. - 8-10 total touches across 17 business days - Channel split target: 50% email, 30% LinkedIn, 20% call - Calls must follow an email (warm the inbox first) — never lead with a cold call - LinkedIn touches: 1 connection request, 1 engagement (like/comment), 1 DM - Email touches: progressive — intro → value → multi-thread → break-up - Each day must have no more than 1 task per contact (SDR sanity) - Stop conditions: any positive reply, meeting booked, explicit decline, unsubscribe Return a numbered table with columns: Touch # | Day | Channel | Action | Goal | Depends On (previous touch). Below the table, give a channel-split summary (% email/LI/call) and a 2-sentence rationale for why calls follow emails.
Variables
- [AGENCY_NAME] — Your agency's name
- [SERVICES] — Service lines
- [ICP_DESC] — Ideal customer profile, including persona and account tier
- [TRIGGER] — What triggers a contact into the cadence (intent signal, list import, job change)
- [SEQUENCE_TOOL] — Outreach, Salesloft, Apollo
- [DIALER] — Aircall, Orum, Nooks, or built-in
- [DAILY_TASK_LOAD] — Realistic daily task capacity per SDR (e.g., 80)
Example input
Agency: Helix Performance — paid media + CRO for enterprise SaaS | ICP: CMOs at $500M+ ARR SaaS in N.America | Trigger: account showed 6sense intent on 'paid social agency' | Tools: Outreach + Orum + LI Sales Nav | SDR capacity: 70 tasks/day
Example output
Touch # | Day | Channel | Action | Goal | Depends On
1 | Day 1 | Email | Intro email referencing intent signal | Open the door | —
2 | Day 2 | LinkedIn | Connect request, no note | Build presence | T1
3 | Day 4 | Email | Value-add: benchmark report | Show expertise | T1
4 | Day 5 | Call | Reference yesterday's email | Get a live conversation | T3
5 | Day 8 | LinkedIn | Engage with recent post | Stay top-of-mind | T2
6 | Day 10 | Email | Multi-thread to Director of Demand | Widen account coverage | —
7 | Day 12 | LinkedIn | DM with case study link | Personalize at scale | T2
8 | Day 15 | Email + Call (same day) | Final value attempt | Force decision | T6
9 | Day 17 | Email | Break-up | Clean exit | T8
Channel split: ~44% email, 33% LI, 22% call.
Why calls follow emails: warming the inbox first gives the SDR a reference point ("I just sent you...") that 3-4x's connect rates vs cold-dialing.Pro tips
- Never have an SDR call a contact who has zero prior touches — connect rates plummet.
- Use Outreach/Salesloft 'when prospect opens email' triggers to auto-task a call within 5 minutes — highest-converting moment.
- Cap this cadence at tier-1 accounts only. For tier-2/3 use the email-only 14-day cadence — calls don't scale economically below a certain account value.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS callRelated prompts