← All Skills
Reply Handling

Reply Drafting

The campaign's only job was to get a reply. What happens next decides whether that curiosity becomes a meeting or evaporates. This skill sets seven rules: reply fast, deliver the promise immediately instead of gatekeeping it behind a call, soften the time ask, and offer two exact slots with a clickable calendar link. Worked examples cover a hard yes, an info request, a technical question, soft interest, and an objection.

Pipeline Playbooks · Open Source, MIT Licensed

Rules and worked examples for the reply that turns an interested prospect into a booked meeting, fast, generous with the promised asset, and never gatekept behind a call.

When to use this

  • Any reply classified as interested or objection needs an answer
  • Answering a pricing question or a technical question
  • Handling pushback without sounding like a sales script
  • Sanity-checking a reply draft before it goes out

What it covers

  • Seven core rules: speed, delivering the promise, softening the ask
  • Proposing two exact time slots instead of "when works for you"
  • Making the calendar link a clickable hyperlink on natural anchor text
  • Matching the prospect's length and energy, 100 words as the ceiling
  • Never over-templatizing, every reply answers their actual words
  • Worked examples: hard yes, info request, technical question, soft interest, objection
  • Common mistakes: gatekeeping, slow replies, bare URLs, essay replies

Install just this skill

Every skill folder is self-contained. Run this from your project root to pull just this one into .claude/skills/reply-drafting/:

$ npx degit joelwylie7/cold-email-playbooks/.claude/skills/reply-drafting .claude/skills/reply-drafting

Want the whole system, not just one skill?