Design an 8-touch follow-up cadence with channel variety
Most cadences are 4 emails in 8 days. This produces a real multi-channel cadence with varied angles, calibrated to a deal stage.
Build an 8-touch follow-up cadence over 21 days for this prospect.
Last touchpoint: {{LAST_TOUCH}}
Deal stage: {{DEAL_STAGE}}
Product: {{PRODUCT_CONTEXT}}
What I learned about them: {{NOTES}}
For each of the 8 touches, output:
- Day (relative)
- Channel (email, LinkedIn DM, voicemail, video, phone)
- Angle (insight-share, question, breakup, case study, social-proof, calendar nudge)
- The actual message (or call talk-track) — 60 words max
Distribute channels: no more than 3 emails in a row. Include one 'breakup' touch at #7. End at #8 with a re-open offer 30 days later. {{LAST_TOUCH}}{{DEAL_STAGE}}{{PRODUCT_CONTEXT}}{{NOTES}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{LAST_TOUCH}}{{DEAL_STAGE}}{{PRODUCT_CONTEXT}}{{NOTES}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Jasper
$39/moEnterprise-grade marketing AI with brand-voice controls.
Jasper is built for marketing teams that need on-brand output at scale. Strong template library, decent brand-voice fine-tuning, plugs into Surfer for SEO.
Copy.ai
$49/moSales + marketing workflows you can chain together.
Copy.ai pivoted hard into 'workflows' — chainable prompts that combine research, drafting, and personalization. Better than Jasper for outbound sales sequences.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.