π Playbook: How I send cold emails to developers
Everyone hates cold emails. Developers hate them even more. Here's how I get solid open rates and CTRs
TL;DR
At least 2 things in life are certain:
Developers hate marketing in all its forms
Developers REALLY hate receiving cold emails
So when one of my cold email experiments performed consistently well with developers, I was thrilled.
Itβs an approach that combines multiple steps and several assumptions. But the underlying keys to success really come down to doing two things well:
Identifying relevant targets before sending out any emails.
Communicating with email recipients in a normal, effective way.
Hereβs the whole playbook broken down step by step.
The playbook
Use GitHub to find relevant targets
This playbook revolves around GitHub, which is the worldβs largest social network for technical people. I first tried it as part of the go-to-market play for Preevy - an open-source tool that we built at Livecycle.
Unlike other social networks, GitHub isnβt built for direct communication or chat. Itβs designed to get people to look at projects and contribute code. GitHub users can also leave a βstarβ on projects theyβre interested in. Itβs equivalent to an βupvoteβ or a βlikeβ on other platforms. And from a marketing and outreach perspective, GitHub is a powerful source of information.
So, once Preevy had reached a hundred stars or so, I used GitHub to better focus my upcoming marketing efforts. I did this by analyzing our list of βstargazersβ. By understanding who was interested in our tool, I could do a better job of targeting similar people going forward.
I started by looking at commonly-starred GitHub repositories. I used a tool called Clickhouse to identify the other GitHub projects our group of stargazers had starred most frequently. These commonly-starred repositories represented an expanded pool of potential stargazers (and users) of Preevy.
Focus on the people who want to be contacted
This expanded pool of targets was a focused list of qualified personas - people who (likely) possessed the technical skill, experience, and interest to be relevant for Preevy.
My next step was to try and see if I could further focus on the people in this pool who also showed qualified intent.
In general, when you only qualify the persona, youβre just assessing if the people are technically qualified to do what you ask of them. When you qualify intent, youβre making sure the people are willing and interested to do so. Qualifying both persona + intent = youβre in really good shape.
In my case, the βintentβ I needed was the willingness to open an email. To qualify this intent, I reduced my list of targets to those who had exposed email addresses on their GitHub profile page. I assumed that by publically listing their email address, these users were announcing that they were open to being contacted, out of the blue.
Exporting lists of stargazers from GitHub
Once I had my list of qualified targets in mind, I needed to export the list and their email addresses. But this was easier said than done.
Going through GitHub profiles one by one would take far too long, so I used the GitHub GraphQL API Explorer to batch the process and speed things up.
The GitHub GraphQL API provides native support for exporting lists of stargazers, and the Explorer is a convenient way for actually executing it.
It wasnβt glamorous, but it was the path of least resistance to extract the info I needed.
To see exactly how I used the API to export the user data from GitHub, check out this technical playbook with the details.
Give before asking for something in return
With the help of the GitHub API, I was able to generate a long list of qualified names and email addresses kept neatly in a spreadsheet.
But before actually reaching out to these people, I did one more thing to increase my chances for success.
I found a way to βgiveβ before asking for something in return.
The vast majority of cold outreach is just someone asking you for something - Try this. Buy this. Subscribe to this. Itβs far more uncommon for someone to offer you something. This is why many of us are pleasantly surprised when someone offers us a compliment or positive feedback. We instinctively donβt expect it.
In my experience, when you first offer and give, the recipient is more willing to listen and reply. And even if you end up asking them for something later on, they are more likely to respond positively once theyβve connected with you in this positive way.
The easiest and quickest way for me to βgiveβ to my list of target users was to follow them on GitHub.
Like other social networks, GitHub allows you to follow other users. Unlike other social networks though, GitHub users have far fewer followers on average. When you follow someone, it means that you are taking the time to acknowledge them and their work. And chances are, theyβll see the notification and appreciate the thought.
By first following these users, I created an opportunity to focus my cold email on what Iβve given them (βjust followed you on GitHub!β) and not what I want in return (βcheck out my open source project!β).
But once again - easier said than done.
Following thousands of GitHub users one by one, by hand, would take forever. I sped things up by using a Python script to automate this process (Iβll be posting the details in a separate, technical playbook - stay tuned).
Before long, I had a spreadsheet with my targets and I had followed them all on GitHub. Now I was ready to reach out.
Send a human-sounding email
My first few rounds of emails were sent via HubSpot. But I was soon blocked from sending more. HubSpot picked up that this was cold outreach, and while there was nothing technically (or legally) wrong with what I was doing, they werenβt into it. They didnβt love the fact that I was marking these people as βmarketing contactsβ (a HubSpot prerequisite when sending emails such as these) when the recipients hadnβt yet opted in.
Not wanting to compromise our HubSpot account, I moved over to other email marketing platforms.
I am currently sending most of my emails via AdRoll. Iβm not thrilled with their platform, but it does the job. For now. Maybe weβll cover some of these solutions in another post.
But for now, letβs turn to the email itself. It looked something like this:
Subject: hi - just followed you on github!
Hey [first name]
π
I just followed you on GitHub - Looks like you're a Docker/open-source fan, so we have that in common. I'm always on the lookout for smart people I can connect with and learn from, so I figured I'd reach out.
I also thought youβd be interested in some of the tools my team is working on:
"Preevy" - We've built an open-source CLI that makes it easy for developers to provision shareable preview environments for any Docker-Compose application the the cloud.
Docker Extension - We're launching a Docker Desktop extension that lets you share your local development environment with remote team members and Get instant feedback without the hassle of commits, deployments and CI builds. You can also create a preview environment in the cloud at any time if needed.
If it sounds interesting, weβd be thrilled to have you try it for yourself. Here are the relevant links:
Obviously, no pressure or strings attached. We're just looking for some smart people who can benefit from our tools.
And if there is anything we can do in return (star a repo, give feedback, send you free swag etc. etc.) let me know and we'll do our best to make it happen!!
Thanks for your time! π€© π
Cheers,
Zevi
A few notes regarding the email:
It wasnβt stylized or decorated. I wanted it to look authentic and personal
I intentionally used lower-case letters for the subject line so it would look more like a real person wrote it
I started by emphasizing what we have in common, and then presented what weβre working on in a non-salesy way
I ended the email by offering to help in any way possible, with a few specific examples
The results
This approach has been working pretty well for me:
~60% unique open rate
~30% unique click rate
Hundreds of GitHub stars
Dozens of nice replies and collaboration opportunities
Here are a few of the human responses that Iβve received. Note how some people even complimented me on my marketing!
Summary
To sum up my key suggestions for cold-email outreach:
Try to double and triple qualify your targets (look for intent, not just persona)
Give before you ask for something in return
Communicate like a human
Donβt try to sell anything, but clearly present your offering
Automate and scale the process as much as you can, but not at the expense of the above steps.