1
Michael
Grinich
CEO
WorkOS
Zeno Rocha
VP of Developer
Experience
WorkOS
Betsy Calender
Developer Success
Manager
WorkOS
The Founders Guide to
Developer-Led Growth
Doing Business with Developers
3
Why should you build
for developers?
4
Cloudflare
GitLab
GitHub
Heroku
MongoDB
Twilio
Stripe
Vercel
Segment
HashiCorp
Auth0
Retool
5
We have taken the entire
messy and complex world of
telephony and reduced it to five
API calls.
Jeff Lawson, Twilio's CEO
“
”
https://avc.com/2016/06/best-seed-pitch-ever
6
7
Developer-led Growth
Self-serve onboarding
Cheaper customer acquisition
Typically follow a usage-based model
8
Why sell
to developers?
9
Developers used to
influence, but not authorize,
technology purchases.
That's no longer the case.
10
58% of developers indicated
they have budget authority, not
merely budget influence.
Evans Data Corporation (2018)
“
”
https://techrepublic.com/article/developers-now-control-a-big-chunk-of-enterprise-budgets-heres-how-to-reach-them
11
# of software developers worldwide
https://www.statista.com/statistics/627312/worldwide-developer-population
23 24 28 29
in millions
2018 2019
2023 2024
12
US has the
largest population
of developers
India's developer
population will overtake
the US by 2024
https://www.daxx.com/blog/development-trends/number-software-developers-world
APAC region
shows the
strongest growth
LATAM has the second
strongest growth
13
Bottom Up Motion
Developer Input
Management
Evaluation
High
Ownership
Top Down Motion
Management Vision
Developer
Execution
Less
Ownership
14
Pricing
15
Pricing
Enable developers to sign up for free if possible.
Low starting point - easy to put in a credit card.
Usage based pricing - only get charged for what you’re using.
16
Upsell
Designed for expansion.
Build a suite of interrelated products.
Educate on other features they’re likely
to need next vs. just instigating a sales call.
17
Pitfalls
18
Pitfalls to avoid
Developers hate paying for something they’re not using.
Avoid introducing too much friction in the sign-up process.
Don’t use language like “unlock revenue”. Developers
notice when technical language is not quite right.
Marketing to Developers
20
How to build a
brand for developers?
21
Love
Praise
Promotion
Small Delight
Small Delight
Small Delight
Small Delight
Small Delight
=
22
Distrust
Indifferenc
e
Churn
Small Annoyance
=
Small Annoyance
Small Annoyance
Small Annoyance
Small Annoyance
23
Branding for developers
Developers are obsessed with precision.
An error in a line of code could be fatal.
The fastest way to lose credibility with developers
is to include errors in your writing.
24
Benefits
25
Focus on features, not benefits
Marketers use benefits, not features, to describe their product.
With developer audiences, this best practice is counterproductive.
Be straightforward about specs and feature comparisons against
other product lines or competitors.
26
What companies do
27
Just tell me
exactly what
this is
What developers see
28
Please don’t
send me
automated
marketing
emails
What developers see
29
How they can
guarantee
this?
What developers see
30
I’m sure
there’s a
catch here
What developers see
31
Yet another
fake promise
What developers see
32
Gated Content
33
Avoid lead magnets
Developers will always ignore your attempt to “convert” them.
They are not going to register for your special webinar.
When you gate white papers, guides, and other resources,
developer skepticism increases.
34
What companies do
35
I don’t
want read
a PDF
What developers see
36
This could
have been a
Github Repo
What developers see
37
or a blog post...
or a web page...
or anything but a
PDF
What developers see
38
Not
actually my
real name
What developers see
39
My fake
disposable
email address
What developers see
40
Unsubscribing
will be
impossible
What developers see
41
Channels
42
Meet developers where they are
Exchange cards with a developer and you'll never hear from them again.
A Twitter follow is way more effective than a business card.
Focus your efforts in channels that are authentic to developers.
43
Meet developers where they are
Hacker
News
Dev.to Twitter Stack
Overflow
44
Formats
45
Explore different mediums
Pick and choose the right medium for your targeted audience.
Some developers just want to get straight to the source code.
Others like to read blog posts or books, others prefer to watch
screencasts or pre-recorded presentations.
48
Voice & Tone
49
Earn trust by having technical
excellence
Developers are highly resourceful and skeptical of marketing.
Prove yourself as a trusted resource by having highly technical
content.
Demonstrate that you really know what you're doing and they will
reward you with their attention.
52
Leads
53
Don't try to hide your real
motives
A developer’s job is to build software workflows.
They reverse engineer your marketing funnel.
They’ll look at each field in your onboarding form
and wonder why it’s needed.
What companies do
54
55
More like trial for
30 days, spam for
365 days
What developers see
56
Why? Are you
going to run a
background check?
What developers see
57
Why can’t I use
my personal
email?
What developers see
58
Are you
going to call
me? Please
don’t call me!
What developers see
59
Am I going
to be treated
differently?
What developers see
60
Maybe lie
here to
avoid talking
to a sales
guy?
What developers see
61
Finally a
field that
makes
sense
What developers see
62
Word of Mouth
63
Trust on word of mouth growth
Developers are famously loyal.
The best marketing channel is having a truly great product.
Once a small base of developers loves and evangelizes your
product, you’re in a terrific position to grow.
Supporting Developers
65
How to support developers?
66
Tooling
67
Utilize a tool Developers are already
using
Shared Slack channels
Customer’s customer
Have proactive communication: Changelog, Blog updates,
Upcoming events/releases, and Error notifications
68
What companies do
Will I ever a
get a
response?
69
What developers see
I just want to
talk to a real
person
70
Feedback
71
Close the feedback cycle
Integrate user feedback directly into your ticketing system
Visibility
Responsive + Notifications
72
Close the feedback cycle
73
Dogfooding
74
Be developer zero
Constantly put yourself in the shoes of your developer users.
Avoid frustrations by having a strict review and QA process.
Before a new feature sees the light of day on your platform, your
team should have built a full app with it.
76
Visit our booth! #502
Thanks!
Zeno Rocha
@zenorocha
Michael Grinich
@grinich
Betsy Calender

The Founder's Guide to Developer-led Growth with WorkOS