I Asked 50+ Developers How They Buy Software. Here’s What I Learned.
Anyone who has ever tried to sell software to developers probably learned pretty quickly that traditional B2B marketing tactics just plain don’t work. Developers are a tough crowd, their time is extremely valuable, and they’re allergic to anything that even remotely feels, tastes, or smells like marketing.
Companies like Stripe, Snyk, and MongoDB are nailing it when it comes to marketing to developers. But what’s the secret sauce? To find out, I interviewed more than 50 developers in DevOps, DevSecOps, and generalist back-end roles about how they prefer to discover, try, and purchase software.
From these conversations, I learned a ton about what devs are looking for in a software website, in developer documentation, in onboarding, and even in sales interactions. Below, I’ve broken them down into the four biggest mistakes that I see expansion-stage businesses making. And below that I’ve included a SlideShare with more in-depth information to help founders, product managers, and all creators focused on growth take my learnings from these interviews and build better experiences for developers. They’re busy folks, after all.
1. Messaging is more important than you think
I’m more of a jump-in-and-get-started type, but I was surprised to see the busy engineers I interviewed going through product websites and asking questions like “So how does this work?”, “Will this work for my business’s existing stack?”, and the classic “How does this benefit me?”
As businesses become more product-focused, I’ve noticed that websites have a tougher time answering those simple questions. In the SlideShare at the bottom of this post, you’ll see some examples of companies that are doing a great job.
2. Developers are super smart, but they still need to be told what to do in your app
Oh, boy. It’s wild how many software-engineer-focused products just land them on a blank screen after signup and expect them to click around and figure out how to connect it to their Kubernetes instance, or whatever.
3. If your product’s value isn’t apparent very quickly, you’re in trouble
Do you need your prospective buyer to connect your tool into their AWS account and then load in a ton of data in order for them to see the product in action? If so, expect a very small conversion rate.
4. Some developers like to talk to salespeople—just not right away
Not all developers are sitting in front of a dark mode screen ignoring all other humans. They’re going to have questions about the product, and they might even want to connect with sales if they really love it. But for prospects who are too busy to hop on a call, it definitely doesn’t hurt to have self-service options for both sales and support.
I’m always looking for new products to tear down and new developers to chat with about their preferred buying habits. If this deck resonates with you, reach out on LinkedIn or via email. Hope it’s helpful!
Keep reading about marketing to developers
What started out as an adaptive move to help Logz.io align with buyer behavior turned out to be a powerful way for them to open up the market and take advantage of incremental opportunities.