I sent 500 cold emails in my first three months as a founder.
Got 6 replies.
1.2% response rate.
For every 100 emails I sent, 99 people ignored me. One person responded, usually to say “not interested.”
I knew the problem wasn’t my product. Early customers loved it. The problem was my outreach.
Generic templates weren’t working. But I didn’t know what would.
So I ran an experiment.
I split my prospect list in half. 250 emails using my generic template. 250 emails using a new research-based approach.
The results:
Generic template: 3 replies (1.2% response rate)
Research-based approach: 39 replies (15.6% response rate)
13x improvement.
Same product. Same prospects. Different framework.
To be clear, I learned this framework from Samantha Mckenna (You should follow her – see has great sales tips to build your business)
Here’s the framework—and how you can replicate these results.
Why Generic Cold Emails Don’t Work for Technical Products
Let’s start with why most cold email advice fails for technical B2B founders.
The Standard Template
This is what every “cold email expert” tells you to do:
Subject: Quick question
Body:
Hi [Name],
I noticed you work at [Company]. We help [industry] companies with [generic benefit].
Would you be open to a quick 15-minute call to learn more?
Best,
[Your Name]
What’s wrong with this?
Nothing, technically. It follows all the “rules”:
- Short (under 100 words)
- Personalized (uses their name and company)
- Clear CTA (asks for a call)
But for technical products, it fails.
Here’s why.
The Problem with Templates for Technical B2B
Problem #1: Short = not enough context
Generic advice says “keep emails under 75 words.”
That works for simple products: “We help you schedule social media posts.”
But for technical products?
- “We optimize distributed ML training” needs explanation
- “We enable real-time BIM collaboration” requires context
- “We automate carbon accounting” demands specifics
75 words isn’t enough to demonstrate you understand their world.
Problem #2: Basic personalization isn’t enough
“Hi [Name], I noticed you work at [Company]…”
Cool. You looked at their LinkedIn. So did 50 other salespeople this week.
That’s not personalization. That’s mail merge.
Real personalization means:
- You understand their specific challenges
- You’ve researched their approach
- You have insights relevant to THEM
Problem #3: No value before the ask
Most cold emails ask before they give:
“Would you be open to a call?”
The prospect thinks: “Why would I give you 15 minutes when you haven’t given me 15 seconds of value?”
For technical products, you need to demonstrate expertise BEFORE asking for their time.
The Data
I tested this over two years. Here are my results:
Cohort A: Generic Templates
- 250 emails sent
- 3 replies received
- 1.2% response rate
- 0 meetings booked
- 0 deals closed
Time per email: 30 seconds (mail merge)
Total time: 2 hours
Time per reply: 40 minutes
Cohort B: “Show Me You Know Me” Framework
- 250 emails sent
- 39 replies received
- 15.6% response rate
- 18 meetings booked
- 4 deals closed ($15K, $12K, $10K, $8K)
Time per email: 7 minutes (research + personalization)
Total time: 30 hours
Time per reply: 46 minutes
The insight:
Time-per-reply is roughly the same. But you get 13x more replies.
Would you rather spend 2 hours to get 3 replies, or 30 hours to get 39 replies?
The answer is obvious when you look at outcomes, not inputs.
The “Show Me You Know Me” Framework
Here’s the three-part structure that works.
Part 1: Observation (Prove You Researched)
Purpose: Show you’ve done your homework on THEM specifically.
Not this (generic):
“Hi [Name], I noticed your company is in the construction tech space…”
This (specific observation):
“Hi [Name], saw your team just launched the BIM integration feature last month. The real-time clash detection is a smart approach—I’ve seen other teams struggle with lag in traditional workflows.”
Why this works:
It shows:
- You understand their product (not just their industry)
- You’re in their space (you know what “real-time clash detection” means)
- You’ve done actual research (not generic template)
The prospect thinks: “This person actually knows what we do.”
That’s the psychological shift. They go from “another spam email” to “someone who might be worth my time.”
How to Find Observations
Where to look:
1. Recent product launches
- Company blog
- Product updates page
- LinkedIn company posts
- Product Hunt
Example observation:
“Saw you shipped the [specific feature] last week. The [technical approach] is interesting—most teams go with [alternative approach] but I can see why [your approach] makes sense for [use case].”
2. Technical challenges mentioned
- Engineering blog
- Conference talks (YouTube)
- GitHub issues (if open source)
- Stack Overflow (if they’re active)
Example observation:
“Read your post on [technical challenge]. The [specific solution] you described is clever. We’ve seen three other teams tackle this differently—curious if you’ve experimented with [alternative approach]?”
3. Industry trends they’re participating in
- Their LinkedIn posts
- Twitter threads
- Podcast appearances
- Webinars they’ve hosted
Example observation:
“Heard you on the [podcast name] talking about [specific topic]. Your point about [specific insight] resonated—especially the part about [detail].”
4. Recent funding or hiring
- Crunchbase announcements
- LinkedIn job postings
- Hiring pages
Example observation:
“Noticed you’re hiring for [specific role]. That usually means [inference about their priorities]. Curious if you’re dealing with [related challenge]?”
Time investment: 5-10 minutes per prospect
The key: Make it specific enough that it couldn’t apply to 100 other companies.
Part 2: Insight (Teach Them Something)
Purpose: Give value BEFORE asking for anything.
Not this (just pitching):
“We help companies like yours with [generic benefit]. Would you be open to a quick call?”
This (teach something valuable):
“I’ve seen three other construction tech companies tackle real-time sync at scale. The pattern that works: edge caching + event sourcing for conflict resolution. Cuts sync time from 2-3 seconds to <200ms, even at 200+ concurrent users.”
Why this works:
You’re giving, not taking.
Most cold emails ask for something (your time, attention, a meeting).
This email GIVES something (insight, pattern, data).
The psychology: Reciprocity. You gave them value. They feel slight obligation to reciprocate.
But more importantly: You’ve demonstrated expertise.
You’re not just another salesperson. You’re someone who actually knows their space.
Types of Insights That Work
Insight Type #1: Technical pattern they might not know
Structure:
“The companies that scale [specific challenge] successfully use [specific approach]. Here’s why: [brief explanation].”
Example:
“The companies that solve latency at scale use a combination of edge caching + CDN distribution. Sounds obvious, but most miss the edge caching part and only rely on CDN. Result: they still have 500ms+ latency at the edge. With both: sub-100ms globally.”
Why it works: Specific enough to be useful. Brief enough to spark curiosity.
Insight Type #2: Industry benchmark
Structure:
“I’ve reviewed [number] implementations of [solution]. The ones that work have [specific characteristic].”
Example:
“I’ve reviewed 15 ML training pipelines at scale. The ones that hit <48 hour training times all use gradient compression + asynchronous SGD. The ones relying on synchronous approaches plateau at 3-5 days regardless of hardware.”
Why it works: Data > opinion. You’re not selling. You’re sharing patterns.
Insight Type #3: Common mistake to avoid
Structure:
“Three companies I talked to tried [approach X]. All hit the same wall. Here’s what worked instead…”
Example:
“Three companies tried to scale carbon accounting by hiring more data entry people. All hit the same bottleneck: data quality, not data volume. The ones that solved it invested in automated data validation upfront. Reduced errors by 80%, eliminated the hiring need.”
Why it works: You’re helping them avoid a mistake. That’s valuable.
The Balance: Insight Without Selling
Bad insight (too salesy):
“Our platform helps you solve this with our proprietary AI algorithm…”
Good insight (genuinely helpful):
“The companies that solve this use [approach]. No specific tool required—you could build it yourself or use existing solutions. The key is [specific principle].”
The difference: You’re teaching a principle, not selling your product.
The result: They trust you. And when they need help implementing, they think of you.
Part 3: Soft Invitation (No Hard Ask)
Purpose: Give them an easy out while opening the door.
Not this (hard ask):
“Are you available for a 30-minute demo on Tuesday at 2pm?”
This (soft invitation):
“If you’re curious about how [similar company] implemented this, happy to share what we learned. No pitch, just comparing notes.”
Why this works:
No pressure. People hate being sold to. This doesn’t feel like a sales pitch.
Curiosity-based. “I want to learn” is more compelling than “I need to sell you something.”
Easy yes. Low commitment. They can say yes without feeling trapped.
Types of Soft Invitations
Option 1: Offer a resource
“Not sure if this is relevant to your roadmap, but I put together a quick framework for this. Mind if I send it over?”
Why it works: They’re getting something (framework). Low commitment (just reading).
Option 2: Suggest comparing notes
“If you’re dealing with [challenge], might be worth comparing notes. We’ve seen a few different approaches work—happy to share what we’ve learned.”
Why it works: Collaborative tone (not vendor/buyer). Mutual benefit implied.
Option 3: Ask a qualifying question
“Curious if [challenge] is something you’re actively working on, or if it’s on the backlog for later?”
Why it works: It’s a question, not an ask. Starts a conversation.
Option 4: Permission-based
“Not sure if the timing is right, but if this is a priority for you, I’d be happy to set up a quick call to walk through how [similar company] approached it.”
Why it works: Gives them control. They decide if timing is right.
The Psychology
Hard ask triggers defense: “Are you available Tuesday at 2pm?” → “I’m busy. This is a sales pitch. Ignore.”
Soft invitation triggers curiosity: “Want to see the framework?” → “Hmm, might be useful. What’s the framework?”
The goal: Start a conversation. Not book a meeting immediately.
Once the conversation starts, THEN you can suggest a call.
The Complete Template (With Examples)
Here’s how all three parts come together.
Template Structure
Subject: [Observation about them]
Hi [Name],
[OBSERVATION – 1-2 sentences proving you researched]
[INSIGHT – 2-3 sentences teaching something valuable]
[SOFT INVITATION – 1 sentence, low commitment]
Best,
[Your Name]
Length: 100-150 words
Time to write: 5-10 minutes
Example 1: Construction Tech
Subject: Real-time BIM sync at scale
Hi Sarah,
Saw your team launched the real-time BIM integration last month. The approach to clash detection is smart—I’ve seen other teams struggle with lag when scaling beyond 50 concurrent users.
Quick insight: The three construction tech companies I’ve worked with that solved the scaling challenge all used edge caching + event sourcing. Cuts sync time from 2-3 seconds to <200ms, even at 200+ users. The key is conflict resolution at the edge before it hits your main database.
Not sure if scaling is on your roadmap yet, but happy to share how [Company X] implemented it if helpful. No pitch—just comparing notes on what works.
Best,
Nifemi
Why this works:
✅ Observation: “launched the real-time BIM integration last month” (specific, recent)
✅ Insight: “edge caching + event sourcing” (technical pattern, actionable)
✅ Invitation: “happy to share… just comparing notes” (low pressure)
Result from this exact email: 3 sent, 2 replied, 1 meeting booked
Example 2: AI/ML Product
Subject: Model drift monitoring for production ML
Hi Mike,
Noticed you’re hiring ML infrastructure engineers—looks like you’re scaling the platform. I’ve been tracking how teams handle model drift monitoring at scale (my background: deployed 30+ production ML systems at [Company]).
Pattern I’ve seen: Teams that catch drift early use statistical process control + automated retraining triggers. Sounds obvious, but most teams miss the SPC part and end up either retraining too often (expensive) or too late (bad predictions). The sweet spot is setting confidence intervals on prediction distributions.
If you’re working on drift detection, I put together a quick framework comparing the three approaches I’ve seen work. Happy to send it over—no strings attached.
Best,
Nifemi
Why this works:
✅ Observation: “hiring ML infrastructure engineers” (specific signal)
✅ Insight: “statistical process control + automated retraining triggers” (specific approach)
✅ Invitation: “framework… no strings attached” (resource offer, non-threatening)
Result from similar emails: 5 sent, 3 replied, 2 meetings booked
Example 3: Climate Tech
Subject: Carbon accounting edge cases
Hi Lisa,
Read your post on the challenges of Scope 3 emissions tracking—the supply chain visibility problem resonates. I’ve reviewed 8 carbon accounting implementations and that’s consistently the #1 bottleneck.
Here’s what worked for the companies that solved it: hybrid approach using API integrations for tier-1 suppliers + industry averages for tier-2+, with explicit confidence intervals on estimates. Gives you speed without sacrificing accuracy. The key is being transparent about confidence levels rather than pretending all data is equally reliable.
Not sure if you’re tackling Scope 3 yet, but thought the approach might be useful. Mind if I share the case study from [Company Y]?
Best,
Nifemi
Why this works:
✅ Observation: “Read your post on…” (shows engagement with their content)
✅ Insight: “hybrid approach… confidence intervals” (specific solution)
✅ Invitation: “Mind if I share the case study?” (permission-based)
Result from similar emails: 4 sent, 3 replied, 1 meeting booked
The Research: Why This Gets 13x Higher Replies
Let me show you the actual data.
My Testing Methodology
Cohort A: Generic Templates
The template:
Hi [Name],
I help [industry] companies improve [generic benefit]. We work with companies like [competitor name] to solve [vague problem].
Would you be open to a quick 15-minute call to see if this might be relevant for [Company]?
Best,
Nifemi
Emails sent: 250
Responses: 3
Response rate: 1.2%
Meetings booked: 0
Deals closed: 0
Time per email: 30 seconds (mail merge with [Name], [Company], [Industry])
Total time: 2 hours
Cohort B: “Show Me You Know Me” Framework
Emails sent: 250
Responses: 39
Response rate: 15.6%
Meetings booked: 18
Deals closed: 4 ($15K, $12K, $10K, $8K = $45K total)
Time per email: 7 minutes (5 min research + 2 min writing)
Total time: 30 hours
The Math
Generic approach:
- Time investment: 2 hours
- Replies: 3
- Time per reply: 40 minutes
- Meetings: 0
- Revenue: $0
SMYKM approach:
- Time investment: 30 hours
- Replies: 39
- Time per reply: 46 minutes
- Meetings: 18
- Revenue: $45K
Time-per-reply is almost identical (40 min vs 46 min).
But you get 13x more replies and 18x more meetings.
ROI calculation:
- 30 hours invested
- $45K revenue generated
- $1,500 per hour of outreach time
Try getting that ROI with generic templates.
What Drove the Results
Factor #1: Time invested per email
I know what you’re thinking: “7 minutes per email doesn’t scale!”
But let’s do the math differently.
Generic approach:
- 250 emails × 30 sec = 2 hours
- 3 replies
- Time per reply = 40 min
SMYKM approach:
- 250 emails × 7 min = 30 hours
- 39 replies
- Time per reply = 46 min
The time-per-reply is basically the same.
You’re not wasting time. You’re investing it wisely upfront to get 13x more responses.
Factor #2: Quality of conversations
This is the part most people miss.
Generic template replies:
- “Not interested”
- “Send me more info” (then ghost)
- Tire-kickers and low-quality leads
SMYKM replies:
- “Yes, let’s schedule a call”
- “This is exactly what we’re working on”
- “Can you send that case study? And let’s set up time to discuss”
High-quality, engaged prospects who actually want to talk.
Factor #3: Conversion to meetings
Generic approach:
- 3 replies → 0 meetings → 0 deals
SMYKM approach:
- 39 replies → 18 meetings → 4 deals
The conversion rates:
- Replies → Meetings: 46% (18/39)
- Meetings → Deals: 22% (4/18)
Why the high conversion?
Because you’ve already demonstrated:
- You understand their space (observation)
- You have relevant expertise (insight)
- You’re not just pitching (soft invitation)
By the time they get on the call, they WANT to talk to you.
How to Scale This (Without Spending Hours Per Email)
I hear this objection all the time:
“This doesn’t scale. I can’t spend 7 minutes researching every single prospect when I need to send 500 emails per month.”
Fair point.
Here’s how to scale it: Batch research + segmentation.
Step 1: Segment Your List
Group prospects by:
- Similar company type (construction tech, AI/ML, climate tech)
- Similar challenge (scaling infrastructure, integration complexity, compliance)
- Similar recent action (product launch, funding round, hiring)
Example segments:
- Construction tech companies that launched BIM features in last 6 months
- AI/ML companies hiring infrastructure engineers
- Climate tech companies raising Series A
Why segment? You’ll do ONE round of research that applies to the whole segment.
Step 2: Research the Segment (Not Each Prospect)
Spend 1-2 hours researching the SEGMENT:
- Common challenges they ALL face
- Technical patterns that work across the segment
- Industry benchmarks applicable to all
- Recent trends affecting the segment
Output: 3-5 insights that apply to everyone in the segment.
Example for “Construction tech with BIM features” segment:
Research findings (1-2 hours):
- Common challenge: Real-time sync at scale (lag beyond 50 users)
- Technical pattern: Edge caching + event sourcing works
- Benchmark: <200ms is the standard users expect
- Trend: Moving from cloud-only to edge computing
Now you have segment-specific insights.
Step 3: Create Segment-Specific Template
Write ONE template for the entire segment:
Template for “Construction tech + BIM” segment:
Subject: Real-time BIM sync at scale
Hi [Name],
[CUSTOM: Specific observation about THEIR company – 2 min research]
Quick insight: The three construction tech companies I’ve worked with that solved scaling challenges for real-time BIM collaboration all used edge caching + event sourcing. Cuts sync time from 2-3 seconds to <200ms, even at 200+ concurrent users.
[CUSTOM: Adjust invitation based on their situation]
Best,
Nifemi
What’s custom (per email):
- Line 1: Specific observation about them (2-3 minutes)
- Invitation: Slightly adjusted based on their context (1 minute)
What’s templated (same for all):
- The insight paragraph (pre-written)
- Subject line (same for segment)
Time per email: 3-4 minutes (vs 7 for fully custom, 30 sec for generic)
Step 4: Send and Track
Send 50 emails to the segment.
Track:
- Response rate (aim for 10-15%)
- Which custom observations work best
- Which insights get the most engagement
Iterate:
- If response rate is <8%, the segment insight isn’t landing
- If response rate is 12-18%, you nailed it—keep going
- If response rate is >20%, double down on this segment
Common Mistakes (And How to Fix Them)
Mistake #1: “Observation” Is Still Generic
Bad:
“I see you’re in the construction tech space…”
Why it’s bad: Could apply to 1,000 companies. Not specific.
Good:
“Saw your team launched the BIM integration last month. The real-time clash detection approach is interesting…”
Why it’s good: Specific to THEM. Recent. Shows actual research.
The test: Could this sentence apply to 50 other companies? If yes, it’s too generic.
Mistake #2: Insight Is About YOUR Product
Bad:
“We help companies solve this with our platform that uses AI to optimize workflows…”
Why it’s bad: Sounds like a pitch. You’re selling, not teaching.
Good:
“The companies that solve this use edge caching + event sourcing. The key is handling conflict resolution at the edge before it hits your main database.”
Why it’s good: Teaching a pattern, not selling your solution.
The test: Could they implement this insight WITHOUT your product? If yes, it’s a good insight.
Mistake #3: Asking for Too Much Too Soon
Bad:
“Are you available for a 30-minute demo next Tuesday at 2pm?”
Why it’s bad: High commitment. Specific time. Feels pushy.
Good:
“Mind if I send over the case study? And if it’s useful, happy to set up a quick call to walk through it.”
Why it’s good: Low commitment first (case study). Call is secondary, optional.
The test: If you were the recipient, would this feel like pressure or curiosity?
Mistake #4: Too Long / Too Rambling
Bad:
[400-word email explaining your entire product, company history, and philosophy]
Why it’s bad: Nobody reads 400-word cold emails. Delete.
Good:
[100-150 words: Observation + Insight + Invitation]
Why it’s good: Respects their time. Gets to the point. Still provides value.
The test: Can you read this out loud in under 45 seconds? If no, it’s too long.
When to Use This Framework (And When Not To)
Use “Show Me You Know Me” When:
✅ Selling to technical buyers (they value depth and expertise)
✅ Complex product (requires education and context)
✅ Long sales cycle (3-12 months, relationship-based)
✅ High deal value ($10K+, worth the research time)
✅ You have time to research (5-10 min per prospect, or batch research)
Why it works here: Technical buyers want to work with experts, not salespeople. Demonstrating expertise upfront is your competitive advantage.
Don’t Use “Show Me You Know Me” When:
❌ High-volume transactional sales (<$1K deals, need 1000+ emails/month)
❌ Non-technical buyers (they want simplicity, not technical depth)
❌ Short sales cycle (<30 days, decision happens fast)
❌ You’re sending >500 emails/month (can’t personalize that many)
Why it doesn’t work: Volume game requires speed over depth. Use generic templates and win on numbers.
Alternative: For high-volume, use segmentation approach (batch research + light personalization). Gets you to 5-7% response rate, which is enough for volume plays.
Conclusion: Research > Templates
Here’s what I learned from sending 500 cold emails:
Generic templates: Easy. Fast. Don’t work.
Research-based outreach: Harder. Slower. 13x better results.
The framework:
- Observation: Prove you researched (specific, recent, relevant)
- Insight: Teach them something (pattern, benchmark, mistake to avoid)
- Soft Invitation: Low-commitment next step (resource, case study, permission)
The results:
- 1.2% response rate → 15.6% response rate
- 0 meetings → 18 meetings
- $0 revenue → $45K revenue
The time investment:
- 7 minutes per email (or 3-4 min with segmentation)
- Time-per-reply: basically the same as generic templates
- But 13x more replies to work with
The math: Would you rather spend 2 hours for 3 replies, or 30 hours for 39 replies?
For technical B2B founders, research beats templates every time.
Ready to Systematize Your Outreach?
If you want to implement this framework:
Jetwheel Essentials helps you systematize your outbound:
- Track follow-ups automatically
- Template library (with personalization prompts)
- Response rate tracking
- Never lose context on prospects
Try Jetwheel Essentials ($99/mo) →
If you want expert help with your messaging:
Strategic coaching includes:
- Messaging audit and refinement
- ICP identification and targeting
- Email template development
- Outreach strategy optimization
Book a Strategy Call →
If you want the templates:
Download the “Show Me You Know Me” email template library:
- 10 industry-specific examples
- Research checklist
- Segmentation guide
Get the Template Library →