Selling to Developers via Self-Serve Proof
Developers must prove products themselves, so invest in self-serve — sales can't convert them at the build stage
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 90%
Developers are a fundamentally different audience: they skip marketing, avoid sales, and — because they're personally accountable when a service fails — refuse to take anyone's word and must build a proof of concept themselves. That means companies requiring developers to build must invest heavily in self-serve experiences, treating the self-serve/growth function with the seriousness usually reserved for a sales team.
Origin
Laura Schaffer draws on her experience selling to developers at Twilio and rapid, including Fang and large retail companies whose engineers ran full POCs (even signing up with personal emails) without ever engaging sales.
Core principles
- 01Developers ~2-to-1 skip your marketing site and go straight to signup, context-free
- 02They're the 'IKEA buyers' who tear into building and only seek instructions when stuck
- 03Developers avoid sales at a whole other level, because a rep has other motivations
- 04A developer is personally accountable — if the service fails, it's on them, their job, their reputation
- 05High stakes mean they can't trust content or a rep; they must prove it by building
How to run it
- 1
Assume no marketing context reached them
Design signup and onboarding as if the developer skipped your marketing site, pricing, and product context entirely — because most do.
Pro tip Don't rely on 'they probably know this coming in' or 'it's on the marketing website' — none of it applies to this group.
- 2
Recognize why the stakes are high for them
Understand the developer is responsible when the service goes down, fails to integrate, or wakes a teammate's pager — it can cost their job and reputation.
- 3
Let them prove it themselves
Give them a self-serve path to build at least a proof of concept, because they won't commit on anyone's word — they must prove it works themselves.
- 4
Invest in self-serve like it's your sales team
If your product requires developers to build, resource the self-serve/growth function with seriousness akin to a Salesforce, because sales cannot convert developers at the build stage.
Watch out Developers will not accept sales coming in to convert them mid-build; pushing sales there backfires.
In the wild
A Fang company signed up for Twilio, built a POC, and launched to production over months without engaging sales once — surfacing only via support when a delivery feature was off. A large retail engineering team signed up with personal email addresses specifically so they wouldn't get bombarded by sales.
→ Illustrates that developers get deep into the self-serve experience and prove the product themselves before committing, so conversion depends on self-serve investment, not sales outreach.
Common mistakes
Porting non-developer growth/sales playbooks onto developers
People strong at growth or product with other audiences assume the learnings transfer, but developers are so different that it's a steep climb — assumptions about marketing context and sales receptivity break.
Trying to convert developers with sales during the build stage
Developers are personally accountable and can't trust a rep's motivations, so they avoid sales and must prove the product themselves; sales pressure at that stage fails.
Is it for you?
Best for
Founders and growth leaders building products that require developers to build or adopt them
Not ideal for
Products sold to non-technical buyers who expect and welcome sales-led, marketing-rich journeys
From the transcript
“developers like almost 2-1 do not look at your marketing website at all they go straight to your sign up flow”
“they're the the Ikea buyers”
“the engineering team signed up with their personal email addresses so they wouldn't get bombarded by by sales”
“they must do it they must prove it themselves”
“you must invest in self-serve experiences in order to effectively convert your audience”
From the episode
Career frameworks, A/B testing mistakes, counterintuitive onboarding tips, selling to developers
Laura Schaffer (VP of Growth at Amplitude)