Cold Email Drafting v1.0.0

Cold Email Drafting

Write cold outreach emails that get replies instead of deletions. Built from real campaigns: 44 local businesses emailed across 6 waves, ~30 cold calls, and the hard lessons that came out of them. The core insight: sell the outcome, never the mechanism.

The 3 rules that matter most

1. Sell the outcome, never the tool. Don't lead with "AI", "automation", "software", or any mechanism. Lead with the pain disappearing: missed calls, cold quotes, no-shows, empty chairs. Reveal the how only when asked.
2. One email, one ask. Every cold email ends in a single low-friction call to action. Never "reply or call or book or check the site".
3. Make the first line undeniable. The preview line decides whether the email gets opened. Reference something specific about their business — a review, a location, a recent post. Generic flattery is worse than none.

Anatomy of a cold email that works

Subject:  3-7 words, specific, no clickbait
Preview:  First line visible in inbox — make it personal
Body:     Hook (their pain) → Proof (one line) → Offer (free/low-risk) → Ask (one CTA)
Sign-off: Name + one contact method

Keep the body under 120 words. If it scrolls on a phone, it's too long.

Subject lines

Good patterns:

• Question about a specific pain: "Quick question about missed calls at {shop}"
• Plain and direct: "15-min idea for {business name}"
• Reference trigger: "Saw your review about {thing}"

Bad patterns (never use):

• "Revolutionize your business with AI"
• "Quick question" (alone — overused)
• Anything with !!!, ALL CAPS, or "free $$$"

The body formula: Hook → Proof → Offer → Ask

Hook (1-2 sentences). Name a pain they feel weekly. Be concrete: > "Most shops I talk to lose 2-3 jobs a month to calls that go to voicemail > after hours."

Not: "In today's competitive landscape, businesses need digital solutions."

Proof (1 sentence). One specific, believable claim. Small and true beats big and vague: > "We set this up for a shop in [town] and they caught 11 after-hours calls > in the first month."

Never invent numbers. If you have no proof yet, say what the pilot measures instead of claiming results.

Offer (1-2 sentences). Make it free and time-boxed. The free pilot framing lowers the ask to almost zero: > "I'm running a free 14-day pilot for 3 local shops — no card, no contract. > If it doesn't pay for itself you keep the setup notes either way."

Ask (1 sentence). One CTA, low friction: > "Worth a 10-minute call Tuesday or Thursday?"

Not: "Let me know a time that works for you or feel free to check out our website or reply with questions."

Personalization that actually scales

Tier your effort. 80% of replies come from the top tier:

• Tier 1 (5 min each): Reference a specific review, their busiest hours, a service they clearly offer, or something from their site/socials.
• Tier 2 (1 min each): Industry + town + one plausible pain point.
• Tier 3 (bulk): Industry-level pain only. Expect low reply rates; use only for list-building, not for your best prospects.

The free-pilot email (full template)

Subject: missed calls at {business}?

Hi {name},

Noticed {business} closes at {time} — most {industry} shops I talk to lose
a few jobs a month to after-hours calls that hit voicemail and never call
back.

I'm running a free 14-day pilot for 3 local {industry} shops: every call
gets answered, quotes go out same-night, nothing falls through. No card,
no contract — if it doesn't pay for itself you keep the setup notes.

Worth a 10-minute call Tuesday or Thursday?

{your name}
{phone}

Follow-up sequence

Most replies come from follow-ups 2 and 3, not email 1. Never send more than 4 touches.

• Touch 1 (day 0): The cold email above.
• Touch 2 (day 3): One-line bump. "Bumping this in case it got buried — still have one pilot slot open this month."
• Touch 3 (day 7): New angle, new value. Share one concrete tip they can use without you: "Quick win either way: calls between 6-8pm convert 2x — worth checking your voicemail log for that window."
• Touch 4 (day 14): The breakup. "Closing the loop — I'll stop bugging you. If missed calls ever become a headache, my number's below."

Each touch is a fresh email, not a reply-all chain. Keep the thread clean.

What NOT to do

• Never attach files, flyers, or PDFs to a cold email. Spam filters eat them and nobody opens them. Link nothing in email 1.
• Never lie about how you found them ("we've been following your work" — you haven't).
• Never fake a prior relationship ("Re:", "Following up" on first contact).
• Never promise specific results you can't guarantee ("double your revenue").
• Keep lists clean: public business emails only, no personal addresses, no re-sending to people who said no, honor every unsubscribe immediately.
• If your open rate craters, stop and fix deliverability (SPF/DKIM/DMARC, warmed domain, plain-text format) before sending more volume.

Handling replies

• "How much?" → "The pilot's free for 14 days. After that it's {price}/mo, cancel anytime. But let's see if it works for you first — 10 minutes Tuesday?"
• "How does it work?" → Now you may reveal the mechanism, briefly, in plain language tied to their pain. Two sentences max, then back to the ask.
• "Not interested." → "No worries — thanks for the reply. Door's open if that changes." Then never email them again.
• "Send me info." → Send 3 bullet points, not a deck. End with the call ask again.

Adapting the formula to other offers

The structure survives any product. Swap the variables:

• Pain: what costs them money or sleep weekly?
• Proof: smallest true claim you can make.
• Offer: what can you give away free for 14 days that proves value?
• Ask: what 10-minute commitment moves this forward?

Test one variable at a time: subject lines first (they gate everything), then the hook, then the offer. Change nothing else while a test runs.

Quick self-check before sending

• [ ] Under 120 words?
• [ ] First line references something specific about them?
• [ ] Zero mention of your tech/method in the hook?
• [ ] Exactly one call to action?
• [ ] No attachments, no links in touch 1?
• [ ] Would you reply to this?