DEV Community

Kornel Varga
Kornel Varga

Posted on

Paste-Ready Cold Outreach Rewrite Patterns (2 Before/After Examples)

Most cold outreach fails in the first two lines.

Not because the offer is bad. Because the message still reads like a template after you swap the company name. Busy people can smell that in under a second — and they archive it without feeling rude.

This post is a rewrite clinic, not another “10 platforms to find clients” list. You’ll get two fictional before/after examples, the pattern behind each, and a 60-second checklist you can run on your own draft tonight.

Steal the structure. Don’t copy the sentences into a real send.

What “paste-ready” actually means

A paste-ready pattern is one you can drop a specific observation into without rewriting the whole note. Three pieces:

  1. Observation — one detail only true for that company (or that person).
  2. Proof crumb — one concrete thing you’ve done that maps to their situation (not a résumé dump).
  3. Tiny ask — something answerable in one reply: yes / no / “send the checklist.”

If any of those three is missing, you’re usually writing a brochure, not a message.

Pattern 1 — Observation → tiny ask (agency / SMB)

Before (fictional):

Hi Sarah,

My name is Alex and I’m a full-stack developer with 5+ years of experience building modern web apps. I help businesses grow with custom software. I’d love to offer my services to BrightPath Studio. Let me know if you’re hiring freelancers!

Best,
Alex

What’s wrong (structurally):

  • Opens with a bio about you
  • Claim is generic (“grow with custom software”)
  • Ask is vague (“hiring?”)
  • Line 1 still works after swapping the company name

After (same fictional sender):

Hi Sarah — noticed BrightPath’s case studies lean hard on WordPress rebuilds for local clinics.

I just finished a similar clinic site migration (booking + forms, no redesign drama). Would a 10-minute teardown of your current clinic intake flow be useful — even if you’re not hiring right now?

Either way, happy to send the 3-bullet checklist I used.

Why the rewrite lands:

  • Sentence one is only true for them
  • The ask is small and binary
  • Bio moved out of the opener
  • Easy out (“even if you’re not hiring”)

Filter: if line 1 still works after swapping “BrightPath” for another company, delete it and write a new observation.

Pattern 2 — Warm intro ask (network note, not “hire me”)

Before (fictional):

Hey Mike,

Hope you’re doing well! I’m currently looking for freelance React work and was wondering if your company needs any developers. I’ve attached my portfolio. Would love to chat about opportunities.

Thanks!

What’s wrong:

  • Status update about your job search
  • High-friction ask (hire / opportunities)
  • Attachment before consent
  • No reason Mike should spend social capital for you

After:

Hey Mike — quick one.

I’m taking on 1–2 React cleanup projects this month (performance + flaky test debt). Do you know anyone at an agency or product team who’d want a short teardown of a slow dashboard — no pitch call required unless they ask?

If nobody comes to mind, all good. If someone does, a one-line intro is plenty.

Why it works:

  • Lower ask (intro vs hire)
  • Clear, narrow scope
  • Easy out for Mike
  • No attachment ambush

Filter: write the ask in one plain sentence first. If it needs three clauses, cut until it doesn’t.

A 60-second rewrite checklist

Run this before you hit send:

  1. Delete the bio paragraph. Put one specific observation first.
  2. Make the ask answerable in one reply (yes / no / “send the checklist”).
  3. Remove anything that still works after a company-name swap.
  4. Cap under ~80–100 words so busy people can say yes without scheduling guilt.
  5. If you attached a PDF, remove it — offer to send after they reply.

You don’t need a new “system.” You need a draft that survives a skim.

Common failure modes (quick)

  • Spray-and-pray first lines — “I came across your website and was impressed.” Impressed by what?
  • Stacked asks — intro + hire + portfolio review in one note. Pick one.
  • Proof without a map — “I’ve built 40 apps” doesn’t tell them why their dashboard is relevant.
  • Follow-up that restarts the pitch — a good follow-up adds one new observation or one smaller ask, not the same bio again.

Free templates (optional)

Want the five paste-ready message patterns (observation, reactivation, teardown, referral, content reply) with blanks to fill?

https://dev.to/kornel_varga_62cb594bf3fd/5-outreach-messages-that-dont-sound-like-spam-free-templates-2ieo

Same rule: fill every blank or don’t send. Optional free download pack (no reply-rate promises): https://kornelvarga.gumroad.com/l/rqmtr

Want one rewrite?

If you paste a real draft in the comments (scrub names and numbers), I’ll rewrite one for free — no guarantees on replies, just a cleaner structure you can send.

That’s it. Observation, proof crumb, tiny ask. Then stop typing.

Top comments (0)