Your cold emails are probably boring
Most cold emails read like job postings written by a robot. They lead with what you do, why your solution is amazing, and what the prospect should do about it. And they get deleted.
The reason is simple: nobody cares about your service when they first hear from you. They care about a problem that looks like theirs, or a result that feels possible.
A story does what a pitch doesn't - it makes the prospect see themselves in the situation before you solve it. That's the whole point of storytelling in cold email.
The three-part storytelling structure
A working storytelling cold email has three moves, in this order:
- The setup - A specific situation that mirrors your prospect's world
- The tension - The problem or bottleneck that showed up
- The shift - The one thing that changed, leading to a result
Notice what's missing: you. Your product. Your credentials. Those come after the story lands.
Here's what a real one looks like for a service business targeting agencies struggling with project delivery:
Hi [Name], We worked with a 12-person agency last year doing $800K in annual revenue. They were taking on 8-10 projects a month, but scope creep was killing their margins. Every project took longer than estimated because clients kept adding requests mid-delivery. They couldn't hire faster - new people just made it worse. So instead, they built a one-page scope document that got signed before kickoff. Killed the back-and-forth. Within 3 months, they cut project timelines by 20% without losing a single client. We've seen the same playbook work for similar teams. Curious if scope is a similar friction point for you? Best, [Your Name]
This hits all three parts. The setup puts you in an agency's shoes. The tension is real and specific (not "agencies struggle" - it's scope creep eating hours). The shift is one action, with one result.
Why the specificity matters
Generic stories don't work. "A client we worked with" is not a story. "A 12-person agency doing $800K revenue with 8-10 projects per month" is a story because it's specific enough that the right prospect recognizes themselves.
When writing your story, include:
- Company size or revenue range (if it applies to your niche)
- The specific problem, not the category - not "inefficiency" but "scope creep creating 20+ hour overruns per project"
- One measurable outcome - 20%, 3 months, 30 fewer hours, whatever it was
The more specific you are about the before state, the more people in that exact situation will feel like you're talking directly to them.
The story-to-ask transition
Most people mess this up by jumping straight from the story to a hard ask. "Want to see if we can do the same for you?" or "Let's schedule a call" feels jarring because you haven't connected your story to the prospect yet.
Add one transitional line that bridges the gap. It should do two things: acknowledge that their situation might be different, and create curiosity about whether the story applies.
Better versions of the bridge:
"We've seen this same bottleneck come up with teams in your space. Worth a quick conversation to see if it's relevant for you?"
Or:
"Does any of that sound familiar, or is the constraint somewhere else for you?"
The second one is stronger because it doesn't assume - it actually asks. It tells the prospect you're willing to learn whether your story applies.
Where the story goes in your email
Put it second. Your first 1-2 lines should acknowledge something true about their world or recent activity - not a hard pitch, just a reason you're writing.
Then the story. Then the bridge. Then ask for a conversation or a reply.
Your email should not be longer than 80-100 words total. The story can be 40-60 of those words if it's tight. You're not writing a case study; you're proving you understand their world in the space of a paragraph.
Common mistakes that kill the story
The story is too broad. "We worked with a company" could apply to anyone. Tighten it to a specific niche, size, or revenue range so only the right people see themselves in it.
The story has too many details. You don't need to mention their industry, their budget, their team structure, and their location. Pick 2-3 details that make the situation specific without making the email longer.
The result is vague. "They saw improvements" doesn't work. "They cut project timelines by 20%" does. If you don't have a number, describe the specific change: "Scope creep stopped being a weekly conversation" is better than "things got better."
You mention the outcome but not what caused it. The prospect needs to understand the mechanism - what changed that led to the result. In the example above, it wasn't luck. It was a scope document signed before kickoff.
Testing and iterating your story
Your first story probably won't be the one that works best. You're going to send 50-100 emails with a story before you see enough data to know if it's landing. Once you get replies, look for patterns.
Are people replying saying the story is exactly their situation? That's a keeper. Are they saying the problem is different for them? Adjust the story to a different bottleneck in your niche and test that version in a new batch.
The best stories come from actual customers you've worked with. If you have 3-5 good customer results, extract the story from each one and test them as separate email sequences. Let your data tell you which situation resonates most with your market.
When to use storytelling vs. other frameworks
Storytelling works best when you're reaching out to people who might not know they have a problem yet, or when your solution is more about behavior change than a tool swap. It works less well if you're selling to someone actively looking for a solution right now - they're usually ready for a more direct ask.
If you want to see how storytelling fits into a broader cold email framework, check out the storytelling cold email guide or compare it with other cold email sales frameworks to see what works best for your offer.
The gap between knowing and doing
Reading this and writing one story email is one thing. Building a storytelling campaign that runs consistently, testing multiple story angles, handling replies, and scaling it to 50+ emails per week is another. Most service business owners build one email sequence, send it, get inconsistent results, and assume cold email doesn't work for them.
The real unlock happens when you have someone managing the full machine - testing story variations, running A/B tests on different customer situations, handling the replies that come in, and feeding results back into what story you test next. That's where cold email stops being a random tactic and becomes a predictable way to sign clients.