Write one offer worth testing
In a cold email experiment, the offer is the thing you're testing. Write one promise in plain words, and don't touch it until the verdict is in.
Your segment is set and your delivery is proven. Now the only open question is whether these people care about what you offer. This chapter covers how to write that offer so a reply, or silence, actually tells you something: one promise, a four-beat email, a clear question at the end, and copy that stays the same from the first send to the last.
The offer is the thing you're testing
Every experiment in this guide tests one hypothesis: this segment, this persona, this offer. Chapter 2 fixed the first two. The email carries the third.
That changes how you write. You aren't trying to squeeze replies out of a list. You're trying to find out if one promise matters to one group of buyers. If the email makes three promises, a reply can't tell you which one landed. Silence can't tell you which one failed.
So write one promise per experiment. Before you write any copy, put the hypothesis in one sentence:
Segment: bootstrapped B2B SaaS, 2–20 people, no sales hire.
Persona: the founder, who also runs billing.
Problem: paying customers drop off when a card fails at renewal.
Promise: we win those customers back without anyone chasing them by hand.
If you can't fill in all four lines, you aren't ready to write. If you want to promise two things, that's two experiments. Run the stronger one first.
Sellvance runs each offer as its own experiment: one segment, one message, one verdict. You find out whether the offer works before you write the next one.
See how offer validation worksThe four-beat email
A cold email gets a few seconds. Four beats fit into that: a subject that gets it opened, their problem, your answer, and a question. Pain, then solution, then the ask. Nothing else.
Subject
Short, and it shouldn't look like a pitch. If the subject reads like outreach, the email is deleted before anyone sees the body. A good subject looks like it came from someone who knows their world: "billing question", "founder to founder", "${first_name}, one quick thing".
Avoid the company name plus a benefit ("Grow ${brand_name}'s revenue"). It reads like a subject line generator wrote it.
Their problem
This is the part they actually read. Open with their problem, in the words they'd use for it. No self-introduction, no "I'm the founder of…", no "hope you're well".
Fit the pain to the role. A founder worries about losing paying customers. A head of growth worries about a number on a dashboard. Same product, different first paragraph. Pick the one that matches the persona in your hypothesis.
Your answer, plus one line of proof
Now they're thinking: "OK. Who are you, and why should I trust you?" Say what you built in a sentence or two. Then add one line of credibility: a customer, a result, where you've done this before.
If you have no proof yet, say so. "We're new, so I'd rather learn than pitch" is honest and it's fine. A made-up customer count or case study is not. It also ruins the test: you'd be measuring the fake proof, not the offer.
A specific, open question
End with a question only someone in their seat can answer. "How do you find out today that a renewal failed?" is easy to answer and shows you know the work. "Worth 15 minutes next week?" asks a stranger for their calendar before they care.
One question. Specific enough to show you know the field, but not so obscure they need to look something up.
One offer, written two ways
Here is the same offer from the hypothesis above. The first version is how most cold emails read. The second follows the four beats.
Before
Subject: Boost ${company_name}'s revenue with smarter billing
Hi ${first_name}, hope you're well!
I'm the founder of [Product], an innovative payment recovery platform that leverages machine learning to optimize subscription revenue for SaaS companies of all sizes.
Would you be open to 15 minutes next week?
- The subject is a pitch, and it uses the legal entity name.
- Paragraph 1 is about the sender, not the reader.
- "Leverages", "optimize", "platform": abstract words, one long sentence.
- The ask is a meeting with a stranger.
After
Subject: {billing question|renewals question|${first_name}, one quick thing|founder to founder}
Hi ${first_name},
When a card fails at renewal, most billing tools send one email. Then the customer just drops off. Nobody at ${brand_name} chose to lose them. The card expired.
We built a tool that retries failed cards at better times. It also texts the customer a link to update the card. We're new, so no big logos yet. I'd rather learn from founders than pitch.
How do you find out today that a renewal failed?
Sam
The Five-Point Check
Run every draft through these before it goes into a campaign. If one fails, rewrite.
- Does the subject reveal a pitch? If yes, rewrite it.
- Does paragraph 1 open with their pain, or with you? It has to be their pain.
- Are sentences longer than about 10 words on average? Split them.
- Any abstract words you can swap for concrete ones? Swap them.
- Is the ask a specific, open question, or a generic meeting request? Make it a question.
Writing rules
Most B2B email reads like a policy document. Cold email should read like a note from a peer. These rules get you there.
- Write at a grade 6–7 reading level. Most corporate email lands at grade 10–12. Paste your draft into a readability checker and cut until it drops.
- About 10 words per sentence. Mix short and medium. One long sentence is where readers stop.
- Active voice. "We built this to" beats "The solution was designed to".
- Concrete words. "Servers", not "infrastructure". "Setup", not "implementation". "Use", not "leverage".
- No "hope you're well". Or any other line that could open any email to anyone.
- Use the brand name, not the legal name. Databases store the registered entity: "Northwind Software Solutions LLC". The company calls itself "Northwind". Using the legal name tells the reader you scraped a registry. Pull the brand name from their website before you write.
- Short sign-off. Your first name is enough.
Choosing the ask
The question at the end is part of the offer. Pick one type before you launch and keep it for the whole experiment.
Open question
Asks about their work, not your product. Easy to answer, and the answer tells you about the problem even when they don't buy.
- "How do you find out today that a renewal failed?"
- "Who chases failed payments on your team?"
Yes/no question
Costs the reader one word. Works when the problem is obvious and you only need to know if they have it.
- "Is this something you deal with?"
- "Should I send the two-line version of how it works?"
Meeting ask
Asks for time before the reader has a reason to give it. On a cold list, it mostly tests how busy people are.
- "Open to a call on Thursday?"
Spintax: vary the subject, not the promise
A cold email should read like it was written for one person. The same subject line on every email reads like a template. Spintax helps with that. You write options inside curly braces, split by pipes, and each message gets one at random.
- Write 3–5 full subject variants by hand. That's enough for the subject to stop reading like a template. Read each one and make sure it passes the "doesn't look like a pitch" test on its own.
- Avoid heavy word-level spin in the body. Blocks like {help|assist|support} multiply into combinations nobody has read, and some will sound strange.
- Every variant makes the same promise. If one subject hints at revenue and another at saving time, you're running two offers in one campaign. The verdict can't separate them.
- Personalize with real data, not synonyms. Merge fields like ${first_name} and ${brand_name}, or AI-written first paragraphs, vary the body in ways that matter to the reader.
Copy that doesn't hurt delivery
Chapter 1 proved your emails arrive. The copy can still undo that. An email that lands in spam gets no reply, and that silence looks exactly like a market that doesn't care.
Plain Text, No Tracking Pixels
No HTML layout, no images, no open tracking. Gmail warns recipients about tracking pixels and puts "Report spam" front and center. Plain text looks like a person wrote it, because a person did.
No Links in the First Email
If recipients mark the email as spam, every domain linked in it takes the hit. That can include your main website. Keep links out of cold emails and send them in replies.
No Spam Trigger Words
"Free", "guaranteed", "act now", "limited time", "click here". Also skip all caps, exclamation marks and fake urgency. Run a spam check on the final copy before launch.
An Unsubscribe Option
Required in the EU (GDPR) and Canada (CASL), and useful everywhere. Gmail and Outlook show "unsubscribe" before "report spam". An unsubscribe costs you nothing. A spam report damages the mailbox.
A Bare Signature
Name, title, company. No logo, icons, phone number or links. The same rich block in every email is a pattern filters look for.
Hold the copy fixed while the test runs
Once the first email goes out, the copy is locked. Any edit starts a new experiment.
Three days in, nobody has replied, and the subject suddenly looks weak. Change it, and the first 60 sends tested one email while the rest tested another. The result describes neither.
What counts as "the copy" for this rule:
- The subject variants.
- The promise, the proof line and the question.
- The number of steps and the follow-up emails.
- The instructions you give an AI writer, if one drafts the messages.
If you find a real mistake, like a broken merge field or a wrong claim, stop the campaign. Fix it, and start counting again from zero on companies that haven't seen the old version. Then let the new version run to its planned sample. Chapter 4 covers how to set that sample before you send.
The Experiment Playbook walks through one full experiment: the hypothesis, the offer, the sample size, and the rules for when to stop. Use it as the checklist before you lock your copy.
Read the Experiment PlaybookAI can draft. Someone still reviews.
An AI writer can fit the first paragraph to each company. That's fine. The promise, the proof line, the question and the instructions stay fixed. The AI changes the wording around the offer, not the offer.
Review keeps that true:
- Read the first batch in full before anything is sent. Twenty drafts is enough to spot a pattern.
- Check facts about the company. If the draft says they sell to agencies, confirm it. A wrong detail is worse than none.
- Check it's still the same offer. Drafts drift. Look for extra promises, invented proof, or a meeting ask where you wanted a question.
- Run the five-point check and the brand name rule on each one.
- Fix the instructions, not single drafts. If several drafts share a problem, change the prompt and review a new batch. Do this before launch. After launch, it's a new experiment.
Sellvance's AI writes each message from your offer and the lead's company data, then a second AI pass reviews it before it's approved. You can read, edit or reject any draft before it goes out.
See how messages are written and reviewedPut One Offer in Front of the Right People
Sellvance writes and reviews each message around your offer, then the Signal Check tells you whether it arrived and whether anyone cared.
Start your first experiment