A reply is a higher bar than an open. A prospect can open out of curiosity, scan two lines, and archive without thinking. To get a reply they have to do work — type, decide, send. That means everything in the email has to lower the cost of replying. Most cold emails do the opposite. They're long, vague about who they're for, vague about the ask, and written in a voice that signals “sales person you can ignore.” This post is the framework we use to build cold emails that earn the work of typing back.
Key takeaways
- A cold email has four parts and each fails differently. Diagnose by part, not as a whole.
- Reply-rate ceiling lives in the opener, not the subject. The subject earns the open; the opener earns the read.
- Body should justify your right to email at all, not pitch. Pitching is the ask's job.
- A specific small ask outperforms a calendar invite by a wide margin on first touch.
- Length is a vote on your respect for the prospect's time. Under 100 words is the working ceiling for first touches.
The four parts and what each is for
A cold email is doing four jobs in sequence: earn the open, earn the read, earn the trust, earn the reply. Each part of the email maps to one job, and confusing the jobs is the most common reason an email fails. The subject can't earn trust; the body can't earn the open; the ask can't replace the body. The framework below treats each part as its own deliverable.
- Subject line — earn the open.
- Opener — earn the read past the first line.
- Body — earn the trust that you're worth replying to.
- Ask — earn the reply itself.
Subject line: earn the open
The subject line's only job is to look like internal work or a coworker note, not marketing. The categories that consistently work are specificity, curiosity, mutual connection, and signal-based references. We covered fifty-plus subject line examples in this post; the short version is sentence-case, no buzzwords, name a specific noun the prospect could only confuse with their own situation.
Bad: Quick question — boost your team's pipeline with AI
Better: your SDR job posting (one question)
Opener: earn the read past the first line
The opener is the line that decides whether the prospect keeps reading or archives. It is also the part most often given to a template like “I hope this finds you well.” That phrase is so universal in outbound that it has become a tag for “this is a sales email, archive it.” The fix is to front-load the specific reason you're writing, not the pleasantries.
Bad opener: Hi Sarah, I hope you're having a great week. My name is X and I work at Y, where we help companies like yours...
Better opener: Sarah — saw you posted the SDR role last Tuesday. The bit about “owns the AE hand-off” is what caught my eye.
The better opener does three things. It names the prospect by first name (one word, no comma if you don't want one). It cites a specific public artifact (the job post) with a specific detail (the AE hand-off line) only a real reader would notice. It does not introduce you. Introductions are the body's job.
Common mistake: opener as auto-flatter
“Love what you're doing at Acme” is auto-flatter. It costs zero effort, gives zero signal, and the prospect knows it. If you don't have a specific reason to compliment, don't. The default state of a cold email should be neutral and direct, not gushing.
Body: earn the trust
The body is where most cold emails go to die. The temptation is to pitch — to list features, to drop logos, to explain how the product works. None of that earns trust. What earns trust is showing you understand the prospect's situation well enough to make a relevant suggestion or observation. That's it. The body's job is not to sell. It's to demonstrate the prerequisite to selling.
A working body has three pieces, in this order: a one-line hypothesis about the prospect's situation, a one-line connection to what you do, and one sentence of evidence that the connection isn't random. Anything more is usually padding.
Bad body:
At Prsona, we're a leading AI sales platform that helps top teams unlock 10x productivity in their outbound workflows. We integrate seamlessly with all major CRMs and offer enterprise-grade security. Our customers include high-growth companies across SaaS, fintech, and beyond.
Better body:
Guessing the SDR you're hiring will lean on the AE hand-off being documented somewhere — most teams I see at this stage are still doing it in Slack. We built the cold-email half of that pipeline at Prsona; happy to send a two-paragraph note on how a team like yours has set it up if useful.
The better version does not pitch. It diagnoses, names the specific situation, and offers a small thing of value. It also names the company without making the company the protagonist of the sentence.
The ask: earn the reply
The ask is the line that determines whether the prospect types back. The default ask in cold email is “15 minutes on my calendar next week?” That ask is wrong on first touch for almost every category. Calendar time is expensive. A stranger asking for it without first proving they're worth the time gets archived.
A small ask outperforms a calendar ask. The small ask is something the prospect can do in twenty seconds: reply yes, reply no, forward to the right person, tell you who owns it. The smaller the cost of the reply, the higher the reply rate.
- Worth me sending the two-paragraph note?
- Are you the right person, or is this someone else?
- Open to one suggestion?
- Want me to email back in two weeks once you've filled the role?
- Is this a now problem or a Q3 problem?
Worked example: rewriting a calendar ask
Bad: Do you have 15 minutes next Tuesday or Thursday for a quick call?
Better: If this is a now problem, happy to send the note. If it's a Q3 problem, I'll email back in August. Either way works.
The better version gives the prospect two acceptable answers, both of which are cheap to type. The Q3 framing also lets the prospect off the hook honestly, which paradoxically increases the chance they engage now if they actually have a now problem.
Length and the “under 100 words” rule
Cold email reply rate drops as length increases past about a hundred words. This is not because long emails are inherently bad, but because length on a first touch reads as “this person didn't respect my time enough to edit.” The exceptions are rare: highly technical asks, very senior prospects who specifically prefer detail, or a referral context where length reads as care. For everything else, the working ceiling is one screen on a phone, no scroll. That's about ninety to a hundred and ten words including the signature.
Voice and brand consistency
Two reps on the same team should sound like the same company. That doesn't mean identical templates — it means the same voice across senders. If one rep writes like a peer and the next writes like a marketing landing page, prospects notice and trust drops. Brand voice on outbound is the part most teams underrate and the part that compounds the most as a team scales. We built brand voice controlfor exactly this reason: a single team-wide voice guide that every rep's generated emails inherit, so the tenth rep sounds like the first.
The full worked example
Subject: your SDR hire — re: the AE hand-off
Sarah — saw you posted the SDR role last Tuesday. The bit about “owns the AE hand-off” is what caught my eye.
Guessing the SDR you're hiring will lean on that hand-off being documented somewhere — most teams I see at this stage are still doing it in Slack. We built the cold-email half of that pipeline at Prsona; happy to send a two-paragraph note on how a similar team has set it up if useful.
Worth sending? Or is this a Q3 thing.
Dalton
That's 87 words. Specific subject. Specific opener. Body that diagnoses without pitching. A small ask with two acceptable answers. The same email written with auto-flatter, feature dumps, and a calendar ask would be three times longer and would convert at a fraction of the rate.
How AI shifts the workflow
Writing one of these emails takes ten to twenty minutes if you do the research yourself. The research is the slow part — reading the LinkedIn, finding the job post, noticing the AE hand-off detail. Prsona's AI cold email generatorcompresses the research step. The output isn't meant to be sent verbatim; it's meant to give you a draft with the specific signals already pulled, so the rep edits and ships in two minutes instead of fifteen.
One last note on follow-ups
A first touch with a 15 percent reply rate doesn't mean 85 percent of the list is dead. Most replies arrive on touches two through five, not touch one. The framework above is for the first email, but the same four parts apply on every follow-up — and follow-ups have their own constraints, which we covered in the follow-up sequence post.
Want to see this in practice?
Try Prsona free— open any LinkedIn profile, generate a draft in your team's brand voice, and edit from there. Solo plan is free, 10 lifetime credits, no card.