Most cold emails open with the sender’s credentials, their client roster, or a compliment about the recipient’s company. The buyer has seen thousands of those. What they almost never see is someone naming the exact thing keeping them up at night, the problem they’d never write a LinkedIn post about.
Why “Unsayable Pains” Unlock Cold Inboxes
Gap Selling, Keenan’s framework for modern B2B sales, makes a precise claim: buyers don’t buy products, they buy the distance between their current state and their desired state. The more vividly you can describe the current state, including the parts that feel embarrassing or politically sensitive, the more you collapse the gap between cold stranger and trusted advisor.
The problem is that most sellers only talk about the desired state (“imagine if your team could…”). The current state, especially the parts that sting, is left unspoken. That’s the opening. When you name the current state precisely, and do it without judgment, the buyer’s brain registers: this person actually gets it.
The Three Categories of Unsayable Pain
Not every pain qualifies. The ones that work best share three properties: they’re real, they’re specific to a role, and they’re things the buyer would be embarrassed to admit to their board or their peers. Here are the three categories with one example each.
1. Metric shame. Numbers the buyer is responsible for that are underperforming relative to benchmarks they know well. Example opening: “Most SaaS teams I talk to in the $2M–$5M ARR range are sitting on churn rates they’d prefer not to show in a deck right now.” The phrase “prefer not to show” does the work. It’s not an accusation, it’s a knowing nod.
2. Team dysfunction. Internal coordination failures that would embarrass leadership if visible externally. Example: “A lot of product teams scaling from 8 to 20 people hit a point where standups stop working and no one wants to be the one to say it.” Again, framed as a pattern, not a personal failure.
3. Strategic drift. The gap between what a company says its priorities are and what the team is actually working on. Example: “Most founders I speak with in the DTC space have ‘profitability’ as their stated priority for 2026 but their ad spend tells a different story.” This one is sharper and requires more confidence to send, reserve it for CEOs and founders, not middle managers.
The rule: never say “you have this problem.” Say “most companies at your stage are dealing with this right now.” One word, “most”, converts a personal accusation into industry-wide empathy, and that shift is the difference between a delete and a reply.
How to Build the Full Opener
The Mutual Pain hook has a three-part structure: observation, specificity marker, and the soft door. Here’s how they fit together.
Observation names the pain without attributing it. One sentence, industry-level.
Specificity marker signals you’re not sending a blast, you know something particular about their situation. This is where you slot in a data point, a recent company event (a funding round, a job posting, a product launch), or a revenue tier.
Soft door is the question or statement that invites a response without demanding one. Not “would you have 15 minutes?”, too transactional. Better: “Curious whether this has been on your radar or if you’ve solved it already.”
Put together, for a freelance data analyst targeting e-commerce brands:
“Most DTC brands scaling past $3M are running attribution models that were built for a world before iOS 14, and the gap between what the dashboard shows and what’s actually driving revenue is getting harder to explain to the board. Curious whether this is something your team has worked through or if it’s still live.”
That’s 52 words. It names a real, specific, politically sensitive problem. It doesn’t pitch anything. And it ends with genuine curiosity, not a calendar link.
The Accusatory Trap and How to Avoid It
The version that backfires sounds like this: “Your retention numbers are probably suffering because you’re not doing X.” Three problems: it presumes guilt, it telegraphs the pitch, and it starts with “your”, which makes it about them personally rather than about a category of problem.
The fix is simple. Replace “your” with “most” or “a lot of.” Replace active diagnosis with hedged observation. Replace the word “because” with “and.” Compare:
- Accusatory: “Your onboarding is probably losing users because you haven’t mapped friction points.”
- Mutual Pain: “Most SaaS tools in the project management space are losing users in the first 7 days, and the friction points usually aren’t where teams think they are.”
Same information. Completely different emotional register.
Testing Your Hook Before You Send at Scale
Before sending a Mutual Pain hook to 100 contacts, test it on 10. Measure not just reply rate but reply quality. A good hook generates replies that say “how did you know?” or “yes, this is exactly what we’re dealing with.” A bad hook generates “thanks, not interested” or no reply at all.
Run A/B tests with subject line variants too. For Mutual Pain emails, subject lines that reflect the pain (“the churn problem no one talks about”) consistently outperform benefit-promise subject lines (“3x your retention in 60 days”).
What to Do When They Bite
When a reply comes in, resist the urge to immediately pitch. The first reply is earned trust, not a buying signal. Respond with a question that goes one level deeper into their specific situation. If you named metric shame and they confirmed it’s real, ask: “Is it the data side or the team buy-in side that’s been harder to crack?” That question does two things: it proves you understand the problem at depth, and it surfaces the specific angle your service addresses best.
Applying This as a Freelancer
As a solo operator, you have an advantage the large agencies don’t: you can write emails that sound like a person, not a company. The Mutual Pain hook is designed for exactly that register, personal, observational, slightly confessional. Use the specificity marker to reference something you genuinely noticed about their business: a job posting that signals a gap, a product update that implies a scramble, a hiring freeze that suggests budget pressure. The more specific the observation, the less it reads as a template, and the more it reads as the opening line of a real conversation.
