Scale · Outbound at Volume

Build a Multi-Channel Outbound Operating System

Build the operating system that orchestrates email, LinkedIn, phone, and gifting touches into one synchronized cadence per account at volume.

foundermanagerAdvanced⏱ 10-15 hours of system design
When to use
Use this when reply rates on email-only are dropping and you need to layer LinkedIn + phone + occasional gifting without chaos. Also use when reps are running channels in silos with no shared cadence. Run before you buy another sequencer.
The prompt
You are a head of outbound at a digital marketing agency running 1,000+ touches/week without burning domains. You build multi-channel systems that feel coordinated to the prospect, not spammy.
Agency: [AGENCY_NAME] — [SERVICES] | ICP: [ICP] | Weekly target: [WEEKLY_VOLUME_TARGET] | Team: [TEAM_SIZE] | Stack: [TECH_STACK] | Sending domains: [DOMAINS] | Channels in use: [CHANNELS] | LI Sales Nav seats: [LI_SEATS]
Design a multi-channel outbound operating system that orchestrates [CHANNELS] into one per-account cadence. Specify channel sequencing rules, timing windows, the data model that ties touches to an account, and the reply-detection logic that pauses other channels when one converts.

- One account, one cadence — prospect must never get redundant pings from 2 reps.
- Channels must be sequenced (email day 1, LI day 3, phone day 5, etc.), not stacked.
- Reply on ANY channel pauses ALL channels for that account.
- Respect [TECH_STACK] capabilities — do not invent integrations that do not exist.
- Include a per-channel volume cap that prevents fatigue.
Output: (1) Channel cadence map (day-by-day), (2) Data model diagram, (3) Reply-detection logic flowchart in text, (4) Per-channel volume caps, (5) Tech-stack integration map, (6) Rep playbook for handling cross-channel signals.
Variables
  • [AGENCY_NAME] — Your agency name
  • [SERVICES] — What you sell
  • [ICP] — Ideal customer profile
  • [WEEKLY_VOLUME_TARGET] — Weekly account touches across all channels
  • [TEAM_SIZE] — Sales team headcount
  • [TECH_STACK] — Sending tool, CRM, dialer, LI tool
  • [DOMAINS] — Sending domains
  • [CHANNELS] — Email, LinkedIn, phone, video, gifting, ads
  • [LI_SEATS] — Number of LI Sales Nav seats
Example input
AGENCY_NAME: Forge Media | SERVICES: Paid social + creative for ecom | ICP: DTC brands $5-50M | WEEKLY_VOLUME_TARGET: 800 accounts | TEAM_SIZE: 3 SDR + 2 AE | TECH_STACK: Instantly + HubSpot + Aircall + HeyReach | DOMAINS: 4 alt | CHANNELS: email, LinkedIn, phone, video DM | LI_SEATS: 3
Example output
Cadence per account (14 days): D1 email touch 1, D3 LI connect + note, D5 email touch 2 + LI view, D7 phone attempt 1 + voicemail, D9 video DM on LI, D11 email touch 3 (break-up), D14 close-loop email. Data model: account is parent record in HubSpot; touches stored as activities tagged by channel; account state machine = New > Active > Replied > Booked > Dead. Reply detection: Instantly webhook on reply > HubSpot updates state to Replied > HeyReach + Aircall sequences for that account pause via Zap. Per-channel caps: email 3 touches max, LI 1 connect + 1 follow-up, phone 2 attempts, video 1. Tech-stack map: Apollo > HubSpot > Instantly (email) + HeyReach (LI) + Aircall task list (phone); Zapier glues replies back to state machine. Rep playbook: when LI accept comes in, send manual personalized note within 4hrs, log in HubSpot — that account exits cadence and goes to manual SDR follow-up.
Pro tips
  • Build the kill switch first — reply on any channel must pause everything else, or you will get reported.
  • Sequence channels, do not stack — a prospect getting email + LI + call on the same day feels stalked.
  • Cap phone attempts at 2 — anything more is wasted rep hours, not lift.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts