A cold email is a short argument, not a pitch
A cold email that gets replies is built like a short argument: one claim, one piece of evidence, one ask. Every additional sentence past that is competing with the reader's decision to stop reading, which happens fast — a cold email is usually read in the time it takes to glance at a phone screen, so the structure has to hold up to that, not to a careful read.
Subject line: earns the open, nothing more
The subject's only job is to be specific enough and relevant enough that the recipient opens the message. It cannot do the convincing — that's the body's job — so a subject that tries to make the whole pitch in eight words usually ends up vague instead of persuasive. Name a specific, true thing about the recipient or their situation and stop.
Opening line: proves you did the reading, fast
The first sentence has one job: show the reader this wasn't sent to a thousand people unchanged. A specific, checkable detail about their company, role, or recent activity does this in one sentence. Generic flattery ("I love what you're doing at [Company]") fails this job because it's exactly as true of every recipient, which the reader can tell instantly.
The claim: one thing, stated plainly
The body makes exactly one claim about what you can do for the recipient, in plain language, without an invented statistic. "We cut onboarding time for a similar team from six weeks to ten days" is a claim a reader can evaluate. "We use AI-powered solutions to transform your workflow" is not a claim at all — it's a sentence that avoids saying anything specific.
The ask: one action, low effort
End with exactly one ask, sized to the relationship. "Worth a 15-minute look?" is a smaller ask than "Can we get 30 minutes on your calendar this week?" and a smaller ask converts better on a first touch, because it doesn't require the reader to make a real scheduling decision yet — just a yes/no on interest.
A complete example with the reasoning inline
Subject: Noticed [Company] is hiring 3 support engineers Hi [Name], -- addresses a person, not "Team" Saw the three open support roles on your -- opener: specific, checkable detail careers page — a sign ticket volume is growing faster than your team. We help teams in that spot cut onboarding -- one plain claim, no invented stat time for new hires from six weeks to ten days. Worth a 15-minute look before your next -- one small, low-effort ask hire starts? Sam -- signature: name, company, one link MailPilot team mailpilots.in
Five sentences total. Nothing is there to look impressive — everything is there because removing it would weaken the argument.
What not to do
Do not add a second claim "just in case the first one doesn't land" — it dilutes the argument instead of strengthening it. Do not open with a compliment that's equally true of every recipient. Do not stack multiple asks (a call, a reply, a demo link) — each additional option makes the easiest response "ignore this."
What each line is doing, as a table
| Line | Job |
|---|---|
| Subject | Earn the open with a specific, checkable detail |
| "Hi [Name]," | Addresses an individual, not a list |
| Opener | Proves the message was researched, in one sentence |
| Claim | States one plain, defensible thing you can do for them |
| Ask | One small, low-effort next step |
| Signature | Confirms identity, nothing more |
If a line in your draft doesn't map to one of these jobs, it's probably filler, and removing it will usually help the reply rate rather than hurt it.
The sentence that's safe to cut first
When a draft runs long, the sentence most often safe to delete is the second claim — the one added "just in case" the first one doesn't land for this particular recipient. It rarely strengthens the pitch; it usually just gives the reader two things to be unconvinced by instead of one, and it's the clearest sign a draft hasn't been edited down from a first pass yet.
Reading your own draft as a stranger would
Before sending, read the draft as if it arrived from someone you'd never heard of, with no context about your company. If the opener, claim, and ask don't hold up without that missing context, the message is relying on brand recognition it doesn't have yet — a trap especially easy to fall into for anyone close to the product being pitched.
Where MailPilot fits
Getting the structure right only matters if the message actually reaches the inbox. MailPilot checks SPF, DKIM, and DMARC on your sending domain and measures real inbox placement per provider, so a well-built email isn't undone by a configuration problem you can't see from the sent folder.
Ready to reach the inbox every time?
Automated email warmup across real peer mailboxes. Live inbox placement monitoring. Free 7-day trial - no credit card required.
Start free trial