Selling to Developers? Use These 3 Data Strategies
We’ve said it before, and we’ll say it again: Developers are a tough crowd. They hate being sold to, and it’s pretty easy for traditional marketing campaigns to fall flat with them because they’d much rather get a recommendation from a colleague. Failed campaign after failed campaign has led to many software company executives throwing up their hands and declaring all sales and marketing to be pointless.
That’s just wrong. Selling to developers isn’t impossible—it’s just difficult.
I cover why exactly it’s difficult and examples of exceptional developer-focused marketing in my new playbook. Part of selling to developers involves balancing two things: building out a strong organic marketing function and targeting your audience with the right message at the right time throughout their buyer journey.
Easier said than done, right?
Yep. I see it all the time. Part of what’s blocking marketers from widening the top of the funnel (driving more developers to sign up for their free tools) for their developer-focused businesses is ensuring they have the right data and measurement capabilities in place to understand how much impact their activities have on the business.
💻Traditional B2B tactics don’t work when selling and marketing to developers. @stripe, @snyksec, and @datadoghq understand this, and it’s why they’re so successful. Here’s a list of resources to help you get there too: https://t.co/nVx9Atr4nX
— OpenView (@OpenViewVenture) July 8, 2021
That’s mostly because these marketers, community managers, and developer relations experts have the most luck with organic marketing. In this industry, organic marketing is one of the most challenging to measure.
Organic marketing means investing in channels like referrals, organic search, organic social (community), and direct traffic to your website (brand). New users from paid marketing, banner ads, events or SDRs (aka the most measurable channels) don’t count as organic. We measure the fruits of these efforts with a new metric called Natural Rate of Growth.
In a digital, multi-touchpoint world, it’s getting more challenging to measure which users hear about your brand from which channels. That’s why tools like Orbit, Tribe, and Mighty have gained traction so quickly.
That’s all good, and it’ll be a huge boon for community managers in time, but these tools still don’t solve some of the core data strategy issues I see developer-focused software companies fighting. These quick tips should help your team align around what needs to be done and what’s a nice-to-have so that selling to developers feels less like a battle.
Tip #1: Treat data like a product
Some of the brightest minds in tech have struck off on their own to create software that solves a real problem in the market. They’re great builders, but they’re not necessarily great at looking at their product from a commercial standpoint. That is, they know what’s required to make the product delightful, but they don’t know how to communicate that delight or measure it effectively.
Usually these businesses are running analytics off of a production (or production replication) database designed to actually run the product itself—it has no outputs or measures that align to the go-to-market side of the house. These teams are usually tying data back to CRM accounts using the account name or core email address.
It’s a hot mess. Don’t be a hot mess.
Sit down with the leaders and ops-focused employees on the revenue side of the house and ask them what product data they’re interested in, how they would use it (short term and long term), and how they define data-driven decisions. Assign a product manager to this, develop an MVP and a roadmap. Dedicate 10–20% of your resources to getting this up and running, and then support its growth long term.
When your go-to-market team has access to data in the way that they understand it (i.e. real users, their product usage, and real long-term cohorts to study) you’ll be surprised at how well teams align in your next roadmap planning meeting.
Tip #2: Map your customer’s journey
Hopefully by now you have every little bit of your product wired up to be measured. There’s nothing worse than marketing an awesome new feature everyone wants, and then realizing you can’t tell how they’re using it.
It’s great when you can understand how a user is interacting with your software, but it’s fantastic when you can understand how they found you, what their decision-making process looked like to give you a try, and then how they discovered value.
Only some of this is supplied by server-side product analytics. The rest hinges upon tools often overlooked by the developer-focused founder community. I’m talking about good ol’ Google Analytics. More often than not, Google lets me know what type of content is working, what isn’t, and what needs to be updated. You’d be shocked at how many companies don’t understand SEO and how Google works, so they just ignore it.
Tip #3: Don’t overthink it
One of the greatest product-led operators out there said something that really stuck with me. Fareed Musavat, former Head of Product at Slack, said that he believes companies should only track 5–10 events in their product. As a data professional, I was shocked to hear this.
Then I thought about it a little longer. I worked with early-stage companies that were sitting on mounds of data and assumed they needed to hire a machine learning scientist to make sense of it all (they were B2B startups with 50+ customers—we’re not talking social networks here).
Fareed is right: You’ve got to keep it simple. Use the ideal customer’s journey to be your guide with lots of inputs from your go-to-market team. There’s so much off-the-shelf technology out there that helps you get the work done, as well as amazing communities of professionals who have done it before.
The only thing holding you back is your attitude toward leveraging data to sell to your core customers. But when you think about it, doesn’t having the right message at the right time really provide a great experience for you? Isn’t it awesome when a business knows you might be stuck on something, or helps you unlock a feature you didn’t know you needed?
I love these experiences, and I want more software businesses to have them.
Get the Developer-Focused Go-to-Market Playbook—a brand-new resource from OpenView.
Editor’s note: This article was originally published on TechCrunch.
Header image: #WOCinTechChat.
It’s no secret that it can be a little tricky getting from design creation to design delivery.