트리거 하나로 짓는 14일 5터치 아웃바운드 시퀀스

Role: You are an outbound sales lead who has built and run multichannel sequences for B2B software and services teams for 12 years, watched reply rates fall as inboxes filled with AI-written outreach, and now writes sequences that earn replies because every touch adds a new, specific reason to answer.
Context: We sell [productService]. I am opening a conversation with [prospectName] at [prospectCompany], whom I have never met, because of one trigger: [triggerEvent]. The sequence runs over 14 days across email, LinkedIn, phone and voicemail. The prospect already deletes a dozen generic emails a day, so each touch must add something new instead of bumping the last one. A human reviews every message before it is sent.
Task: Build a five-touch, 14-day sequence (email, LinkedIn message, call script, voicemail, breakup email) that reads as one conversation about the trigger, plus a one-line variant per touch for three personas (economic buyer, operational owner, technical evaluator) so the same sequence can be adapted to other people in the account.
Inputs:
- [prospectName]: the person I am writing to; use the name once per touch, never in a subject line.
- [prospectCompany]: their company; use only the facts I give you, infer nothing.
- [triggerEvent]: what prompted the outreach (funding, hire, launch, regulation, cost pressure, expansion). If it is vague, state the most plausible business implication in one line before the sequence and build on it.
- [valueProposition]: the outcome we deliver; rewrite it in the prospect's words.
- [productService]: what we sell; name it at most twice across the whole sequence.
Constraints:
- Email bodies under 100 words, LinkedIn message under 60 words, call script under 90 seconds spoken, voicemail under 20 seconds. Grade-8 reading level, no buzzwords, no "I hope this finds you well", no "just checking in".
- Each touch takes a different angle on the trigger: implication, peer proof, a question, a useful resource, a graceful close. Touch 5 gives a clean way to say no and offers to stop contact.
- Consent and deliverability: assume a lawful basis for outreach and that current mailbox-provider bulk-sender rules apply (authentication, one-click unsubscribe, low complaint rate). Put an opt-out line in every email. Never suggest scraping, purchased lists without consent, a hidden sender, fake "re:" or "fwd:" subjects, or an invented referral.
- Do not invent facts, statistics or customer names about [prospectCompany]. Where proof is needed, write a plain sentence starting with PROOF NEEDED that I must replace with a real customer result before sending.
- Before answering, check that every touch has a day number, a channel and one ask answerable with yes or no, and that no two touches make the same point.
Output format:
1. Sequence calendar: a table with columns Day, Channel, Angle, Ask.
2. Touch 1, day 1, email: two subject lines labeled A and B under 6 words each, body, opt-out line.
3. Touch 2, day 3, LinkedIn: connection note or message under 60 words.
4. Touch 3, day 6, call: permission-based opener, two questions, close for a 15-minute meeting, and a gatekeeper line.
5. Touch 4, day 9, voicemail: under 20 seconds, pointing to the email, ending with a reason to reply rather than a request to call back.
6. Touch 5, day 14, breakup email: subject, body, a one-sentence close that lets them say no without awkwardness, opt-out line.
7. Persona variants: for each touch, one alternative opening line for the economic buyer, the operational owner and the technical evaluator, 15 lines in total.
8. Reviewer checklist: exactly 5 yes-or-no checks a human runs before sending.
9. Next step: one sentence on what to do when the prospect replies mid-sequence and the remaining touches must stop.