👓 Debug 001: When Sales Meets Open Source

Hey folks! 👋

Welcome to the inaugural edition of Debug, where I answer your growth and go-to-market questions!

In Debug 001 I’m answering a question from a founder considering hiring an SDR to tap into commercial opportunity in their open-source user base.

Want me to answer your question?

Just reply to this email or send a new email to [email protected].

Give me as much detail as you’re comfortable sharing, and let me know if you want the Q&A to be anonymised.

Instant Setup, Instant Results: Hire a Synthflow AI Agent Today

Your Next Best Hire: A Synthflow AI Voice Agent. With human-like interaction, it manages calls, qualifies leads, and more, 24/7. Cost-effective plans starting at $29/month, and integrates with top CRMs. Start your free trial and welcome your new team member!

Please support our sponsors!

DEBUG

The founder of a dev tool with an open core model (i.e. they’re building a commercial offering around an open-source core) asks:

We're a dev-tool company with a successful open-source offering.

We have a very large community of users with 1000+ companies using us in production.

We have some data about which companies these are from signals like Clearbit, no contact-level data.

We are now contemplating an SDR-ish position to reach out to these companies and get them closer to our commercial product.

These are devs. Typically allergic to anything that feels like sales. How should we be thinking about this position?

Anonymous dev tool founder

I love this question - it’s a common challenge for open source founders working in the dev tool space.

Here’s my take.

You’ve got this amazing open source community, with over 1000 companies using your tool in production.

That’s a huge asset, and you’re right to want to bring some of those users closer to your commercial product.

But you’re also totally right about developers - most of them hate anything that smells like traditional sales.

So when you’re thinking about this SDR-type position, I’d reframe it a bit: this isn’t sales.

Think of this role as a developer advocate for the business side.

The key is to build trust and create value in every single interaction.

Instead of reaching out with, “Hey, wanna hop on a demo?” it’s more like:

“Hey! Notice you’ve been using our open-source tool for X months now, which is awesome. I’d love to learn how it’s going and see if there’s anything we can do to help you scale or solve XYZ challenge.”

The idea is to approach it as a peer - even as a member of the community - not someone on the outside trying to sell them something.

Maybe they need help implementing a feature, or migrating to your commercial version.

Those conversations naturally open a door for you to talk about your paid offering in a way that doesn’t feel salesy.

It’s also worth considering: who is this person you’re hiring?

The ideal candidate might not be your typical SDR.

You want someone who speaks devs’ language - maybe even a former developer themselves.

It doesn’t have to be someone with recent hard-core coding experience, but they need that credibility and an ability to build rapport without coming off as pushy.

Other tactical ideas to make this work:

Leverage your data smartly. If you’re using tools like Clearbit to figure out which companies are adopting your tool, prioritise outreach based on product signals. For example: if you notice that a company has grown its deployment significantly or started using an advanced feature, that’s a good signal!

Make it collaborative. Sometimes an email or message that says, ‘Hey, we’d love your feedback on where we should go next with our roadmap!’ is a non-threatening way to kick off a conversation while learning about their pain points.

Create a feedback loop. As this hire profiles users and has conversations, they’re going to uncover insights. Feeding that back into your product team can help refine both your free tool and how you position your commercial offering.

So, TL;DR:

This isn’t a traditional SDR.

It’s someone rooted in community and trust-building.

Approach the people you reach out to like partners in the journey - not contacts on a list - and you’ll get them to lean in, not tune out.

Hope that helps!

Want me to answer your question?

Just reply to this email or send a new email to [email protected].

Give me as much detail as you’re comfortable sharing, and let me know if you want the Q&A to be anonymised.

Enjoying this content? Subscribe to get every post direct to your inbox!

THAT’S A WRAP

Before you go, here are 3 ways I can help:

Take the FREE Learning Velocity Index assessment - Discover how your team's ability to learn and leverage learnings stacks up in the product-led world. Takes 2 minutes and you get free advice.

Book a free 1:1 consultation call with me - I keep a handful of slots open each week for founders and product growth leaders to explore working together and get some free advice along the way. Book a call.

Sponsor this newsletter - Reach over 8000 founders, leaders and operators working in product and growth at some of the world’s best tech companies including Paypal, Adobe, Canva, Miro, Amplitude, Google, Meta, Tailscale, Twilio and Salesforce.

That’s all for today,

If there are any product, growth or leadership topics that you’d like me to write about, just hit reply to this email or leave a comment and let me know!

And if you enjoyed this post, consider upgrading to a VIG Membership to get the full Product-Led Geek experience and access to every post in the archive including all guides.

Until next time!

— Ben

RATE THIS POST (1 CLICK - DON'T BE SHY!)

Your feedback helps me improve my content

Login or Subscribe to participate in polls.

Reply

or to participate.