A B2B cold email that gets a reply does four things in 100 words or fewer. It names a problem the reader already has. It shows one result from a past client that the reader could check. It asks for 15 to 20 minutes of their time rather than trying to sell the service. And it reads like one person wrote it to one other person.
Most example lists online stop at templates full of [First Name] and [Company]. Below are four complete emails for the businesses that struggle with this most: a marketing agency, a software development shop, a consultancy and a sales-led SaaS company. Each appears twice: the draft a founder typically sends, then my rewrite, with a note on every line that changed.
Every email in this article is constructed for it. The people, companies and numbers inside the emails are invented, so read them as patterns, never as copies of real campaigns.
How were these examples built?
Smirnov Consulting Group is a Prague-based B2B outbound lead generation agency that runs cold email and LinkedIn campaigns for founder-led B2B companies and books qualified sales calls. A lot of that work is fixing first drafts before anything goes out. The "before" emails below are composites of the mistakes those drafts repeat.
The "after" versions follow the rules my team and I write by, with invented details so no client's data is on display. In your own email, every number must be one you can prove the moment a prospect asks.
Why does a services company need a different cold email?
A software product can point to a free trial. A service cannot. When an agency, a dev shop or a consultancy writes to a stranger, there is nothing to click and try. The only thing that makes the promise believable is what happened for past clients.
So for a service, proof has to sit inside the message, because a stranger will not go digging through your website before they trust you. I wrote separately about turning a whole case study into one sentence. Here it is a single line in every rewrite.
A real proof line is short. If I wrote one about our own work, it would read: a US marketing agency, 277 sales calls and 34 contracts in 60 days. Type of client, result, timeframe. A prospect can ask about any of the three.
What rules do all four rewrites follow?
Five checks. Every "after" email passes all of them, and every "before" fails at least three.
-
Sell the call, and only the call. In a first message, asking for a short video call usually works. Trying to sell the service inside the email usually does not. The email has one job: earn 15 or 20 minutes.
-
No pitch up top. A pitch in the opening lines is the quickest route to being ignored. If line two lists your services, the reader files you under "vendor" and moves on.
-
One checkable proof point. A type of client, a result and a timeframe, in one sentence.
-
Short and human. I will take a short email in a human voice over a polished template that reads like a robot wrote it, every time.
Hunter's State of Email Outreach 2026 report, built on 31 million emails its users sent in 2025, found comparatively high reply rates for emails of 61 to 80 words, and also for 181 to 200. That is a tool vendor's own user data, and the second band is a reminder that short only helps when nothing useful gets cut. Every rewrite below lands between 60 and 80 words.
-
Written for one segment. Sending the same generic sales message to everyone made my list of the 15 most common LinkedIn mistakes, and in email it fails the same way. Buyers are already judging the sender before they read the copy.
Why the call and not the sale? Because nobody signs from an email. For a UK software and IT consulting firm we ran outreach for, cold email alone produced 41 positive replies, 13 calls and 2 signed deals in 1 month. Every one of those deals went through a conversation first.
If your buyers are so cold that even 15 minutes feels like a lot, a smaller first offer can come before the call. I laid out the lighter asks, from a checklist to a pilot separately.
Example 1: a marketing agency writing to a head of marketing
Constructed example. Sender: Tom, founder of an 11-person content agency that works only with B2B software companies. Prospect: Laura, head of marketing at a 60-person HR software company that just posted a job ad for a content marketer.
Before
Subject: Partnership opportunity
Hi Laura,
I hope this email finds you well. My name is Tom and I am the founder of a full-service digital marketing agency with over 10 years of experience.
We offer SEO, content marketing, social media management, email marketing, web design and branding. Our team of certified experts takes a data-driven approach to deliver measurable results.
I came across your company and was really impressed with what you are building.
We have helped many companies like yours grow their traffic and leads, and I would love to show you how we could do the same for you.
Would you be available for a 30-minute call next week to discuss your marketing goals?
Best regards, Tom
The rewrite, line by line
| Before | After | Why it changed |
|---|---|---|
| Subject: Partnership opportunity | Subject: your content hire | "Partnership" announces a pitch before the email is even opened. The new subject names something true about her week. |
| I hope this email finds you well. My name is Tom... | Saw you are hiring a content marketer. | The opener is about her. His name is already in the From line. |
| (nothing) | In software companies your size, that hire usually inherits a blog whose traffic never turns into demo requests. | The problem, stated as a guess she can confirm or correct. Either answer is a reply. |
| We offer SEO, content marketing, social media... | We only do content for B2B software companies. | A single specialty tells her he has probably seen her problem before, which a list of six services never does. |
| We have helped many companies like yours... | For a 40-person payroll software company, blog pages went from 3 demo requests a month to 21 in 7 months. | "Many companies like yours" cannot be checked. A client type, a before and after, and a timeframe can. |
| I came across your company and was really impressed... | (cut) | It could go to anyone, and she knows it. |
| Would you be available for a 30-minute call...? | Worth 15 minutes before the new hire starts, so they do not begin from zero? | A 15-minute ask instead of 30, a reason why now, and a benefit for the person she is about to hire. |
After
Subject: your content hire
Hi Laura,
Saw you are hiring a content marketer. In software companies your size, that hire usually inherits a blog whose traffic never turns into demo requests.
We only do content for B2B software companies. For a 40-person payroll software company, blog pages went from 3 demo requests a month to 21 in 7 months.
Worth 15 minutes before the new hire starts, so they do not begin from zero?
Tom
What I left out on purpose: a portfolio link, a calendar link, a P.S. listing the other services. Each one hands her another decision, and this email needs exactly one: yes or no to 15 minutes.
Example 2: a dev shop writing to a head of engineering
Constructed example. Sender: Anna, head of sales at a 35-person custom software shop that rebuilds old internal systems for logistics companies. Prospect: Martin, head of engineering at a freight company whose careers page has listed the same two backend roles since April.
Before
Subject: Software development services
Dear Martin,
We are a leading software development company with 150+ talented engineers and 300+ successful projects delivered for clients around the world.
Our expertise covers web and mobile apps, cloud, AI, blockchain, data engineering and UI/UX design. We work with startups and enterprises in fintech, healthcare, retail and logistics.
We offer flexible engagement models, including dedicated teams, staff augmentation and project-based work.
Please find our company presentation attached. I would be happy to arrange a call to discuss how we can support your digital transformation.
Kind regards, Anna
The rewrite, line by line
| Before | After | Why it changed |
|---|---|---|
| Subject: Software development services | Subject: the two backend roles | A fact about his own company that he will recognize, in place of a category name. |
| We are a leading software development company... | Your two backend roles have been open since April. | Headcount is about Anna. The open roles are about Martin, and he can check the claim in a second. |
| (nothing) | At freight companies that usually means the old dispatch system eats the team's week, and new hires avoid it. | The guess behind the trigger. If it is wrong, he will say so, which is still a conversation. |
| Our expertise covers web and mobile apps... | We rebuild old dispatch and billing systems for logistics companies, one module at a time, so nothing goes offline. | One job for one industry, plus an answer to the fear that stops him buying: downtime. |
| (nothing) | For a 300-truck carrier, billing moved off a 14-year-old system in 5 months, with zero downtime. | The proof matches the fear the line above answered. |
| We offer flexible engagement models... | (cut) | How the work is contracted is a question for the second call. |
| Please find our company presentation attached. | (cut) | A file from a stranger is one more reason not to engage. It can go in the reply if he asks. |
| ...how we can support your digital transformation. | Open to a 20-minute call to see if the same order of work fits your system? | "Digital transformation" means nothing to an engineer. "The same order of work" points back to something he just read. |
After
Subject: the two backend roles
Hi Martin,
Your two backend roles have been open since April. At freight companies that usually means the old dispatch system eats the team's week, and new hires avoid it.
We rebuild old dispatch and billing systems for logistics companies, one module at a time, so nothing goes offline. For a 300-truck carrier, billing moved off a 14-year-old system in 5 months, with zero downtime.
Open to a 20-minute call to see if the same order of work fits your system?
Anna
The line I would defend hardest is "one module at a time, so nothing goes offline". A head of engineering is rarely against a rebuild. He is against the week everything breaks.
Example 3: a consultancy writing to a CEO
Constructed example. Sender: Petra, partner at a 6-person operations consultancy that fixes inventory planning for wholesale distributors. Prospect: David, CEO of an industrial parts distributor that announced a second warehouse on LinkedIn in March.
Before
Subject: Quick question
Hi David,
Congratulations on the new warehouse! That is a great achievement.
I'm Petra, a partner at a boutique consultancy. We partner with ambitious leaders to achieve operational excellence through tailored, end-to-end solutions.
Our proven methodology combines strategy, process improvement, change management and digital tools, and our clients typically see significant improvements in efficiency and profitability.
I'd love to learn more about your priorities for the rest of the year and share some ideas. Do you have time for a quick chat?
Best, Petra
The rewrite, line by line
| Before | After | Why it changed |
|---|---|---|
| Subject: Quick question | Subject: stock across two sites | "Quick question" has been used so often it reads as a trick. The new subject is the topic, plainly. |
| Congratulations on the new warehouse! | Congrats on opening the second warehouse in March. | Keep the trigger, drop the applause. One line, then move on. |
| (nothing) | The first year with two sites is usually when stock piles up in the wrong one, and cash goes with it. | The problem the trigger creates, in a CEO's terms: cash. |
| We partner with ambitious leaders... | We fix inventory planning for distributors with 2 to 5 warehouses, and nothing else. | "Operational excellence" could be sold to a hospital. This line could only be sent to David and a few hundred people like him. |
| Our proven methodology... significant improvements... | For an electrical parts distributor with 3 sites, that freed EUR 1.1M of cash tied up in stock within 6 months. | A euro figure with a timeframe gives him something to check, where "significant improvements" only asks for trust. |
| I'd love to learn more about your priorities... quick chat? | Worth 20 minutes to look at where yours is sitting? | The old ask makes him explain his business to a stranger. The new one is a yes or no about one topic. |
After
Subject: stock across two sites
Hi David,
Congrats on opening the second warehouse in March. The first year with two sites is usually when stock piles up in the wrong one, and cash goes with it.
We fix inventory planning for distributors with 2 to 5 warehouses, and nothing else. For an electrical parts distributor with 3 sites, that freed EUR 1.1M of cash tied up in stock within 6 months.
Worth 20 minutes to look at where yours is sitting?
Petra
Consultancies hide behind "we" more than anyone. The rewrite still says "we", but it comes from a partner writing in her own name about one narrow problem. A CEO answers a person with a specific skill far sooner than a firm with a methodology.
Example 4: a sales-led SaaS company writing to an operations director
Constructed example. Sender: Jonas, founder of a resource planning tool for agencies with 30 to 200 people, sold through a call rather than self-serve sign-up. Prospect: Priya, director of operations at a 90-person design agency.
Sales-led SaaS sits closer to services than most founders admit: the product still gets sold on a call. For a UAE tech startup we worked with, the numbers that mattered were 684 demos in 4 months and $1.31M ARR. A demo is a meeting with a screen share.
Before
Subject: Revolutionize your resource planning
Hi Priya,
Are you struggling with resource planning? Our AI-powered, all-in-one platform helps agencies plan capacity, track time, forecast revenue and manage projects in one place.
Key features: drag-and-drop scheduling, real-time utilization dashboards, 50+ integrations, automated timesheets and custom reports.
Trusted by 500+ agencies worldwide.
Start your free 14-day trial today, or book a demo with the link below.
Cheers, Jonas
The rewrite, line by line
| Before | After | Why it changed |
|---|---|---|
| Subject: Revolutionize your resource planning | Subject: Friday staffing | Big verbs in a subject line read as marketing. A small, familiar moment reads as a note from someone who knows the job. |
| Are you struggling with resource planning? | Do your project leads still plan next week's staffing in a spreadsheet on Friday afternoon? | Nobody admits to "struggling". A specific scene is easy to answer yes or no. |
| Our AI-powered, all-in-one platform... | We built a planning tool for agencies of 30 to 200 people so that spreadsheet can go. | Who it is for and what disappears, in one line. |
| Key features: drag-and-drop scheduling... | (cut) | Features belong in the demo, where she can see them work. |
| Trusted by 500+ agencies worldwide. | At a 70-person branding agency, billable utilization went from 64% to 73% in the first quarter. | Utilization is the figure an operations director gets measured on, so moving it says far more than any customer count. |
| Start your free 14-day trial, or book a demo | Want to see how they set it up? 15 minutes on a call is enough. | Two options split the decision. A trial also asks her to do the setup work alone. |
After
Subject: Friday staffing
Hi Priya,
Do your project leads still plan next week's staffing in a spreadsheet on Friday afternoon?
We built a planning tool for agencies of 30 to 200 people so that spreadsheet can go. At a 70-person branding agency, billable utilization went from 64% to 73% in the first quarter.
Want to see how they set it up? 15 minutes on a call is enough.
Jonas
How do the four rewrites compare?
| Example | Pattern | Words before | Words after | Trigger | Proof line | Ask |
|---|---|---|---|---|---|---|
| Marketing agency | Trigger plus case result | 111 | 68 | Job ad for a content marketer | 3 to 21 demo requests a month in 7 months | 15 minutes |
| Dev shop | Trigger plus problem and fix | 84 | 79 | Two roles open since April | Billing migrated in 5 months, no downtime | 20-minute call |
| Consultancy | Trigger plus case result | 80 | 74 | Second warehouse opened | EUR 1.1M of cash freed in 6 months | 20 minutes |
| Sales-led SaaS | Question-led problem and result | 57 | 63 | None, a scene they recognize | Utilization from 64% to 73% in the first quarter | 15-minute call |
Word counts exclude the subject line, greeting and sign-off. The SaaS "before" is the shortest email in the set, and its rewrite is longer, yet the draft still fails. It pitches by line two, proves nothing checkable, and splits the ask in two.
Referral emails and free-resource emails follow the same five checks. The ask changes; the proof line stays.
What does a follow-up to one of these look like?
Constructed example. Anna's follow-up to Martin, a few days after the first email got no answer.
Subject: Re: the two backend roles
Hi Martin,
One detail on the carrier I mentioned: we moved invoicing first, because it causes the least damage if something goes wrong. It is usually the safest place to start.
If a call is too much right now, I can send the one-page migration order we used. Want it?
Anna
Two things make it work. It adds new information instead of "just bumping this up", and it offers a smaller ask for someone not ready for a call. A reminder with nothing new in it gives Martin nothing to answer.
What should you fix first if none of your emails get replies?
Sometimes the email is fine and the problem sits one layer down: a stranger cannot tell what you sell or who it is for. No rewrite fixes that, because the rewrite has nothing specific to say.
A client once put our work in one line on a call: "You know what you actually are? You're translation experts. You translate what we do into what people actually want to buy." That translation is what happened in every "after" above. Tom's fix was a narrower offer: content for B2B software companies, measured in demo requests.
If you cannot write your own version of Tom's "We only do content for B2B software companies", the packaging needs work before the copy does. I made the full case for one offer aimed at one audience elsewhere. Once the packaging is clear and the email still runs long, a delete pass on the copy is the next step.
Questions founders ask about cold email examples
What reply rate is normal for B2B cold email?
Hunter's 2026 report on 31 million emails sent by its users in 2025 puts the average response rate for sales outreach at 3%. That is one vendor's user data, so treat it as a rough reference. Judge your own campaign on positive replies and booked calls, because an "unsubscribe me" also counts as a reply.
How many follow-ups should a cold email have?
In the same Hunter data, sending three messages instead of one lifted total replies from 3.3% to 6.8%. So plan two follow-ups after the first email. Each one should add something new, such as a second proof point or a smaller ask, never a plain reminder.
Can I copy these examples as templates?
Copy the structure and keep your own words. If a hundred founders send Tom's email with their name swapped in, it becomes the generic message these rewrites were built to replace. The parts that make it work belong to you alone: your segment, your trigger and your client result.