← All posts

Cold email that gets a reply, line by line

A cold email template annotated line by line, plus the four-minute research that makes it work and the CAN-SPAM, PECR and GDPR rules that apply to you.

Guides

Cold email is the slowest channel you have and the only one nobody can take away from you. No algorithm ranks it, no marketplace prices it, and it works the same in a bad quarter as a good one. It is also the one most freelancers do badly enough to conclude it doesn't work.

The market has made it less optional. Fiverr's annual active buyers fell to 2.7 million in Q2 2026, down 21.9% year over year, while annual spend per remaining buyer rose 15.6% to $368. Fewer buyers, each spending more. Waiting for a marketplace to route one to you is a worse plan than it was two years ago.

The prospect we'll follow

One target, carried through the post: a company that shipped something in the last two months and said so publicly. A launch, a funding round, an open role in your discipline. Generic on purpose; the property that matters is that the change created work nobody owns yet.

That is why it works at all: you aren't persuading someone to want something, you're arriving while they already have a problem and no plan for it.

Four minutes of research, and it has to show

Set a timer. If you can't find something specific in four minutes, close the tab: the problem is the list, not the email.

Job postings first. A company hiring a content lead has admitted a gap and attached a budget to it. The strongest public signal there is, and it tells you in their words what the work is.

Anything dated. A changelog entry, a launch post, a conference talk, from the last sixty days. The reference has to prove the email was written this week rather than pulled from a list bought last year.

One number. Their pricing tiers, their headcount, the size of their docs. A number in your first line cannot be faked at scale.

You are not looking for something to compliment. You are looking for evidence of a job nobody owns, and buyers tell those apart instantly.

Subject lines that survive a phone preview

Most cold email is first seen in a phone list view, at a glance, while the recipient deletes things. Subject and preview both truncate, so the meaning has to live in the first few words.

Patterns that survive:

  • your docs / API reference — a noun from their world, nothing else
  • the content lead role — something they published

Patterns that don't: anything starting with your name or discipline, anything containing "opportunity" or "reaching out," anything in title case, anything with an emoji.

The opening line is not about you

The first line has one job: prove the email was written for one person.

"I'm a freelance technical writer with eight years of experience" fails it in nine words. So does any sentence whose subject is I.

Two that work. Observation plus implication: "You've got 40-odd documented endpoints and the last three ship notes aren't in the reference yet" — a fact only someone who looked would know, naming the gap without calling it a problem. Their own words back: "You wrote in the launch post that support tickets tripled after the release." Nothing flatters a person like being read.

Then one sentence of relevance rather than credentials: what you've done that is structurally the same as their situation, in a clause.

The ask has to be small, and specific

"Do you have 15 minutes for a call?" is not a small ask. It is a calendar entry, a context switch, and a commitment to an unknown conversation.

Smaller asks, roughly in order of how easily they get answered: a yes/no question answerable in four words; a redirect ("is this you, or does someone else own it?"); a named, priced piece of work; or permission to send something.

Naming a price cuts reply volume and raises reply quality. Nobody replies to a number out of politeness, so the replies come from people with a budget and a problem.

The template, annotated

Short enough to read on a phone without scrolling. Every line has a job.

Subject: your API reference

Hi [name],

You've got around 40 documented endpoints and the last three ship
notes haven't made it into the reference yet.

I write developer docs — most recently a reference rebuild for a
payments API with a similar surface area.

If it's useful: I'll go through the reference and send you a list of
what's missing and what's wrong, priced at €400 for about a day's
work. If the list is short, you've spent €400 finding that out.

Is docs yours, or is there someone else who owns it?

[your first name]
[business name] · [full postal address] · [website]
Reply "no thanks" and I won't email you again.

Subject. Four words, all of them theirs. Change per recipient; it must never be reusable.

"Hi [name]." First name only, no honorific. If you don't have a name, you haven't done the four minutes.

The observation. Two checkable facts, both about them. Cut this and the email becomes a template again. If the second fact is weaker, drop it; one strong observation beats two soft ones.

The relevance line. One sentence, one comparable, no adjectives. Say "a payments API" if you can't name the client. Never link a portfolio; a link is a task, and this email is trying not to give them tasks.

The offer. Small, priced, and framed so a bad outcome is still a fine outcome for them. The last sentence does the most work in the email, because it removes the risk of the purchase instead of arguing for its value. Price it at a day you won't resent. If you never want to sell a paid audit, replace the block with "want me to send the three gaps I found?" and give them away.

The question. The email ends on the easiest thing to answer. Never end on "let me know if you're interested," which requires them to have a position. "Is this yours?" requires only that they know their own org chart.

Sign-off and footer. First name only. The postal address and opt-out line are not decoration; the legal section explains why. Keep them plain — a styled newsletter footer is what makes an email look bulk-sent. Nothing else belongs here: no calendar link, no attachment, no tracking pixel.

Follow up twice, and add something each time

Two follow-ups. Not seven, not one. The rule that matters more than the count: every follow-up must contain information the previous email didn't. "Just bumping this up your inbox" admits you have nothing to say and are asking for attention anyway.

Four working days later:

Two of the gaps, in case they're useful either way: the webhooks page
still describes the v1 payload, and there's no error-code reference.
Both are about an hour to fix if someone owns them.

That is the whole email. It gives away real work and drops the cost of replying to nearly zero.

Ten working days after that:

Assuming this isn't a priority right now, which is fair enough. I'll
leave it — if the docs come up later, the offer stands.

Then stop. The second gets replies because it releases them, usually as "can we talk in January" — a real lead with a date attached.

The rules that actually apply to you

United States: CAN-SPAM

CAN-SPAM is an opt-out regime; you don't need permission before you send. The FTC's compliance guide is explicit that "the law makes no exception for business-to-business email," so it covers your prospecting exactly as it covers a retailer's newsletter.

What it requires: accurate From, Reply-To and routing information; a subject line that isn't deceptive; identification of the message as an ad; your valid postal address; a working opt-out; and honoring opt-outs within 10 business days. The mechanism must keep working for at least 30 days after you send, and you can't charge a fee or demand information beyond an email address to process one. The guide puts the penalty at "up to $53,088" per email in violation. Per email, not per campaign.

The "identify it as an ad" rule catches people: a one-to-one email whose primary purpose is commercial still counts. A sentence naming the offer, plus the address and opt-out line, satisfies it.

United Kingdom: PECR, with UK GDPR underneath

PECR draws the line at the subscriber, not the message. The ICO's electronic mail marketing guidance says "you can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)" without prior consent.

The trap is the next sentence: "sole traders and some partnerships are treated as individuals – so you can only email or text them if they have specifically consented." Plenty of the small businesses a freelancer would approach are sole traders. Ltd or LLP in the name and a company number on the site: fair game. A designer trading under their own name: not.

Either way you must not conceal your identity and must give a valid contact address for opting out. And because firstname@company.com identifies a person, UK GDPR governs the processing underneath: you need a lawful basis, normally legitimate interests, and you must honor an objection.

European Union: it varies by member state, and that isn't a hedge

Article 13(1) of the ePrivacy Directive requires prior consent for direct marketing email. Article 13(5) applies that to natural persons and leaves member states to decide how far to protect business subscribers. So B2B cold email is lawful in some member states and not in others.

Germany is the one to know. Section 7(2) of the UWG prohibits "advertising using an automated calling machine, a fax machine or electronic mail without the addressee's prior express consent," and draws no distinction between consumers and businesses. Enforcement comes from competitors and industry associations, not only from a regulator.

The GDPR sits under all of it. Recital 47 accepts that "the processing of personal data for direct marketing purposes may be regarded as carried out for a legitimate interest," which gives you a basis where ePrivacy permits the send. Article 21(2) then gives the recipient an unqualified right to object. When they say stop, you stop, permanently.

The rule set that covers you almost everywhere

Real name and real business postal address in every email. One plain opt-out sentence. A suppression list you check before every send. Opt-outs honored the day they arrive rather than inside any statutory window. No bought lists, no scraped personal addresses. Check the country before emailing into Germany or Italy.

None of that costs you replies; most of it makes the email read like a person rather than a sequence. And if your list runs across the US, UK and EU, check that your own tools do too — a lot of freelancer software is built North America first, which is the comparison the HoneyBook alternative page is about.

Volume, honestly

No reply rate appears in this post. Every figure available is a vendor aggregate drawn from lists nothing like yours, and a rate measured on a purchased list of ten thousand tells you nothing about twenty researched emails.

Measure your own. Three numbers: sent, replied, and replies that became paid work. You need roughly a hundred sends before the last two mean anything, and a hundred at four minutes of research plus three of writing is about twelve hours of unbillable time.

So price it. Twelve hours at your actual effective hourly rate, meaning the fee divided by every hour a project consumed rather than the rate you quote, is what the campaign has to beat. The effective hourly rate calculator gives you that figure from a project you've already finished, and tracking prospecting time in the same timer as client work is what stops outreach looking free.

Below about twenty sends you can't tell a bad email from a bad week. Past roughly ten a day the research degrades and reply rate falls faster than volume rises. This doesn't scale linearly for one person.

When a reply arrives the bottleneck moves to the gap between "send me something" and a document in their inbox. What goes in that document is its own subject; the mistakes that lose the deal after the reply are in the stage-by-stage post.

The next 30 minutes, and the next month

In the next 30 minutes: build a list of ten companies that shipped something in the last sixty days or have an open role in your discipline. Ten, not two hundred, and don't write anything yet.

This month: send twenty emails, five a week, each with its own first line. Log the date, the observation you used, and the reply. Twenty tells you whether your first lines are specific enough, which is the only variable worth tuning first. Then send eighty more before judging the channel.

Worklyn turns a reply into a priced proposal and then into a contract and an invoice without retyping anything, so the hours you spent earning the reply aren't spent again on paperwork.

Worklyn is one calm workspace for the work and the money — worklyn.co