You've built something people actually use. Your GitHub stars keep climbing. Your Slack community is active. But your revenue looks like a sad spreadsheet.
This is the open source paradox - you have massive distribution, real problem-solving value, and genuine user loyalty. Yet monetizing that without alienating your community feels impossible. Most open source founders resort to conference talks, hoping for sponsorships, or they half-heartedly add a SaaS tier that nobody wants.
Cold email works for open source companies because it does one thing well: it lets you talk directly to the people who already benefit from your work. You're not cold-calling strangers. You're reaching out to companies and teams that have installed your software, found it valuable enough to keep running, and probably spent engineering time integrating it. They just haven't thought about paying yet.
Who You're Actually Emailing (It's Not Who You Think)
Most open source founders target the wrong person. They email the CTO or the engineer who uses the tool. Wrong move. That person loves your project. They'll defend it in Slack. But they can't approve budget.
You need to email the person whose job depends on the thing your open source project enables. If your project is a database tool, email the VP of Infrastructure or the Engineering Manager responsible for database performance. If it's a security scanner, email the security team lead or the CISO. If it's a monitoring tool, email the platform or DevOps lead.
The key distinction: find people whose KPIs are directly affected by whether your tool works well or fails. Those people have budget authority or budget influence. They also have pain points your project already solves - they just haven't connected those dots yet.
LinkedIn is your best lead source here. Search for companies using keywords like "[your project name] open source" in job postings, or filter for companies in your target space and look for the people in those specific roles. You'll find 50-200 qualified prospects in any major market pretty quickly.
The Email Structure That Actually Converts
The email needs to do two things: acknowledge that they're already getting value from your project, and introduce a paid offering that removes friction or adds capabilities they need.
Here's the actual structure:
- Line 1 (the hook): Reference something specific about their use of your project or their role
- Line 2-3: Name the problem they're experiencing (usually around ops, scale, or reliability)
- Line 4: One sentence about what you've built to solve that
- Line 5: Social proof (a company using the paid version, a metric, a customer quote)
- Line 6: Low-friction ask
Here's a real example for a DevOps monitoring tool:
Hey [Name], Saw that [Company] is running [Project] across your infrastructure - managing state for about 2K+ resources based on your job postings. Most teams using [Project] at scale hit the same wall: the open source version works great until you need centralized dashboards, role-based access, or audit trails for compliance. After that, it's a gnarly DIY project. We built [Product] to handle that - basically [Project] with the enterprise plumbing already done. [Customer Name] uses it to cut their ops overhead by about 20 hours/month per team. Worth a quick call to see if it makes sense for you? [Name]
Notice what's here: specific reference to their use, a concrete problem (scale + compliance), one sentence on the solution, one customer proof point, and a simple ask. No hype, no "revolutionizing," no buzzwords.
The Subject Line That Works for Open Source
Your subject line should signal that you know something specific about them, not that you're pitching. Open source decision-makers get a lot of generic vendor emails. Stand out by being specific.
The best structure: "[Company Name] + [Project Name]" or "Question about [Project Name] at [Company Name]."
Question about [Project] at [Company Name]
This works because it's not obviously a pitch. It looks like someone asking a technical question. Your open rate will be 35-45%, which is solid for cold email. Industry benchmarks for tech email hover around 25-30%, so you're beating that by actually sounding like a person.
If you want to be slightly more direct without being pushy:
[Company Name]'s [Project] setup
Same principle - specific and factual, not a sales pitch.
Timing and Volume Matter
Send these emails Tuesday through Thursday, ideally between 9 AM and 11 AM in your prospect's timezone. Open source developers and ops teams check email in bursts, usually in the morning. Friday emails get buried in their weekend prep.
Start with 20-30 emails in your first batch. Wait for responses (give it 7 days before follow-up). Your response rate should be around 8-15% initial replies - some interested, some just answering your question, some saying "not right now but interesting." Track that number. If you're below 8%, your targeting or your email opener needs adjustment.
Once you have your first batch dialed in, scale to 50-80 emails per week. Open source is a niche - your addressable market isn't infinite. But at that volume, you should be scheduling 2-4 calls per week with qualified prospects.
What Happens When They Reply
Most replies will be one of three types:
- "Yeah, we use it, but we're not paying for tools right now" - These are warm leads. Ask one qualifying question (usually around timeline or pain level) and keep them warm. Reply in 3 months.
- "We're interested, let's talk" - Schedule the call the same day. These are rare and hot.
- "Not relevant for us" - Say thanks, no hard feelings. Remove them. Don't follow up on obvious rejects.
The call itself should be short. Fifteen minutes. Your job is to understand whether they actually have the problem your paid product solves, and whether they have budget. Don't try to sell the full feature set. Just explore the problem.
The Follow-Up Sequence
Send one follow-up 4 days after the first email if there's no reply. That's it. Two emails total. Open source communities are tight - people notice spam. One follow-up shows persistence without being annoying. Two emails is your limit.
Here's a real second-email template:
[Name], Quick follow-up on my last note - no pressure at all if the timing isn't right. I'm curious: if [specific pain point] wasn't an issue, would [Project] be enough for your needs? Or is there something else that's been a headache? Just trying to understand if this is even worth exploring. [Your name]
This reframes the conversation as you trying to solve their actual problem, not you trying to sell them something. It also creates an easy out - they can just say "nope, we're good" without guilt.
Why This Matters for Open Source Specifically
Open source founders have two advantages over other B2B cold email campaigns: you already have proof of product-market fit (your usage numbers), and your prospects already know your product works (they're running it). You're not fighting skepticism about whether the tool is legitimate. You're fighting inertia and budget.
That changes the entire dynamic. Your email isn't about convincing them the problem matters or that you've solved it. It's about making it easier to pay you than to keep managing the pain themselves.
The actual work is targeting the right person and keeping your email conversational. If you do that, you'll see results within 30 days.
When Cold Email Stops Working
You'll know you've hit the natural limit of your market when your response rate drops below 5% and your qualified calls drop to zero for two weeks straight. That usually happens after you've reached 300-500 prospects - which represents your addressable market of companies who use your project and have budget.
At that point, you've either converted them or you haven't. Cold email is efficient for the first phase of monetization, but it's not infinite. After you've worked through your high-intent prospects, you'll need other channels - content, partnerships, word-of-mouth from your community.
But for your first 10-20 paid customers? Cold email is faster and more reliable than hoping your community converts on their own.
The Gap Between Knowing This and Running It
Reading this is one thing. Actually building lead lists for 50+ people per week, writing personalized emails that reference specific details about their infrastructure, handling replies the same day, and tracking response rates across campaigns - that's a different project. Most open source founders built their project because they liked building, not because they like sales operations. There's a reason most of them don't do this, even though it works.
If you want to run a cold email campaign for your open source monetization but don't want to manage the infrastructure, lead research, and day-to-day execution yourself, that's exactly what BEC Growth handles for open source companies. They manage the lead list, write the emails, track the replies, and schedule your calls - you just take the meetings.