Developer Relations strategy

Hi! I’m Amir (@ashevat).

Agenda:

1. Why Developers

2. How we do DevRel

3. Stats to date

4. Learnings

Why Developers

Why do Developer Relations?

In more than 90% of the use cases you do you need Developer Relations.

Why do Developer Relations?

We started out without DevRel and found out we need one.

What can you do with the Slack Platform?

How we do DevRel

Dev Tools Partnership Advocacy Content & Community

Mission: Best in class developer tools and experience for the

Slack Platform

Mission: Top partners releasing quality and popular Slack apps.

Mission: Scale our reach with content and community

engagement

Slack Developer Relations Team

Inspire

Educate

Enable

Feedback

Developer Engagement Model

Have API Key

Building

Published

Installed

Used

Interested

Dev Funnel

User Funnel

How we do DevRel

70% of our focus is partnerships

How we do DevRel

We focus on the funnel of developers and partners.

Stats

To date,17K integrations have been

installed 3.6M times

What does a new platform feature usage look like?

Events API - used by more than 400 developers and installed on 30k teams.

Review process

Only 2% pass the review the first time.

Lessons Learned

● Segment your developers● Work the breadth and depth ● Focus on high value developers/partners● Measure the right thing● Advocacy Vs. Evangelism ● Where you are in the org matters● Where the $$ comes from matters● Always think FIIFM for the developer

Lesson learned

https://www.flickr.com/photos/124247024@N07/14090438714/

https://www.flickr.com/photos/jdhancock/8671399450/

Yeah!We did it!

Botness

Thanks!

For more information go to: slack.com/info