What 100 Cold Emails Taught Me About Building in Public as a Solo Founder

Building in public felt like shouting into the void until I started cold emailing about LeadFlow. Those first 100 emails taught me more about my product and market than six months of Twitter threads.

The Cold Email Experiment

I built LeadFlow to automate lead qualification for B2B companies. After launching quietly and getting crickets, I decided to email 100 potential users directly. Not to sell, but to share what I was building and ask for feedback.
The response rate surprised me: 23% replied. More importantly, 8 people booked calls, and 3 became early customers.

What Actually Worked

Be specific about the problem you solve. My early emails were vague: "I'm building a lead automation tool." The emails that got responses were concrete: "I noticed your team manually scores 200+ leads weekly. I built something that cuts that to 10 minutes."
Show, don't just tell. I included a 30-second Loom video showing exactly how LeadFlow works. Videos got 40% more replies than text-only emails. People want to see the product, not read about it.
Ask for problems, not validation. Instead of "Would this be useful?", I asked "What's your biggest bottleneck in lead qualification?" This shift generated real conversations about pain points I hadn't considered.

The Unexpected Benefits

Cold emails became my best customer research tool. I learned that my target market actually had three distinct use cases I never anticipated:

• Sales teams wanting to prioritize outbound lists
• Marketing teams qualifying inbound leads
• Customer success teams identifying expansion opportunities

This insight led me to rebuild LeadFlow's onboarding flow around these specific workflows.

Building Social Proof Through Outreach

Each email response became content for building in public. I'd tweet (with permission): "Just talked to a sales director who spends 8 hours/week manually scoring leads. Anyone else dealing with this?"
These specific, problem-focused tweets got 10x more engagement than generic "building in public" updates. People don't care that you shipped a feature. They care that you solved a problem they recognize.

The Template That Worked

Here's the cold email structure that got responses:
Subject: Quick question about lead qualification at [Company]
Hi [Name],
I noticed [specific observation about their company/role]. I'm building LeadFlow to help B2B teams qualify leads automatically.
[30-second demo video]
I'm curious: what's your current process for prioritizing leads? And what's the biggest bottleneck?
Not selling anything, just trying to understand the problem better.
Best,
Tobias
Key elements: Personalized opening, clear product explanation, visual proof, specific question, and explicit "not selling" disclaimer.

When Cold Emails Backfire

About 20 emails went to the wrong people entirely. I targeted "Head of Sales" titles but reached people managing inside sales teams, not lead qualification. This taught me to research individual responsibilities, not just titles.
Two people replied asking me to stop building competitor products. These conversations revealed I was positioning LeadFlow too broadly. I refined my messaging to focus on "automated lead scoring" instead of generic "lead automation."

The Real ROI

Those 100 emails generated $12,000 in first-year revenue from early customers. But the bigger win was product direction. Customer conversations shaped my roadmap more than any user research session.
Your next step: Pick 20 people who should care about your problem. Email them tomorrow. Ask about their current process, not whether they'd buy your solution.
The worst outcome isn't rejection. It's building something nobody wants in silence.