Write a follow-up cadence
Five touches over three weeks, each adding a new reason to reply.
- 1.Open ChatGPT or Claude.Either works. The skill is just text.
- 2.Inspect the real preview, then unlock the full file.One click; no install, no setup.
- 3.Paste it as your first message.The assistant now knows how to do this one job.
- 4.Give it your specifics, get the result.Roughly 5 min, every time you need it.
Give it context. Get back a work product.
Illustrative sample using the same output shape. Verify live facts in the tool you run it in.
We had a good first call with a VP Engineering at a Series B devtools company. They asked for security details and said budget timing is next quarter.
Writing follow-ups that sound busy but add no new reason for the buyer to respond.
Five-touch cadence
- Day 1: Send the security summary and ask whether their security lead should be included.
- Day 5: Share a short customer proof point tied to engineering adoption.
- Day 12: Offer a lightweight technical working session instead of pushing a generic demo.
Graceful close
- If next quarter is the real window, ask permission to send a concise prep note two weeks before planning starts.
- No guilt, no 'checking in,' no fake urgency.
Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Fill the blanks first.
Add context before you run it. These fields update the preview and ChatGPT/Claude buttons instantly.
Permanent agent install needs the full body.
This page is only showing a preview. Unlock the full skill to install it in Claude Code, Claude Projects, or a Custom GPT.
# Write a follow-up cadence You are a tasteful sales follow-up writer. I will give you the prospect, what happened, and what I want. Build a five-touch cadence that earns the next reply. ## Inputs Ask for the original email, prospect role, context, value prop, timeline, and any relationship history. ## Output Create five touches over three weeks: | Touch | Timing | Channel | Purpose | Message | |---|---|---|---|---| Each touch must add a new reason to reply: useful context, relevant proof, a concise question, a forwardable summary, or a graceful close. ## Rules [Preview stops here. Unlock the Pro library for the full rules, guardrails, examples, and copyable file.]
This preview is cut from a real Pro workflow. Unlock the founding Pro library for the full file, rules, examples, and installable skill.
- ✓ Input checklist
- ✓ Step-by-step workflow
- ✓ Quality bar
- ✓ Guardrails
- ✓ Output format
- ✓ Example run
- ✓ Install formats