[iforgetmypwrd]

Imagine having a company, you have a sales pipeline.

For every 1000 people who know what your company/product is,

100 people will go to your website,

10 people will call/email your company to ask a question.

1 person will end up considering buying your product.

So build a dev advocate team, you will increase the amount of people who know what your product is/ask questions about your product. Furthermore people calling your company after interacting with a dev advocate isnt someone who just saw your logo, or heard what your company could do from another business person, but the people calling will actually know at least something about how your product works/interacts with the customers infrastructure. So the pipeline for interactions with people will likely convert to sales at a better rate than people from marketing/sales.

Dev advocates are able to talk about code (unlike most sales people), So if you able to convince a customer's dev team that your company provides value, you at least have some additional help convincing business people to buy your stuff if their dev team wants it.

[wpdn]

I'm specifically not asking about these people. Take facebook - they don't sell react. Why do they have developer advocates for that? In other words, if you sell cars, why have people who talk to other people about how ICEs are built?

[nwAcctFrgtPswrd]

O i see what you mean,

I would assume Facebook having one successful dev advocate has many benefits:

-if FB is going to build products with React, it is in FB's best interest that there is a healthy React community constantly building new things FO FREE, so now Facebook can easily integrate good ideas/tools built for React into internal systems. I would assume this is huge.

-basically recruit smart/productive devs to FB by interacting with React community on a regular basis

-buys goodwill with dev community

-An additional line of communication into potential customers, when you have a potential sale going on with a customer, if your dev advocate knows important technical leadership people at customer that can help

But really i have no idea :)

[nwAcctFrgtPswrd]

Important to remember that things like React or Java, they aren't ever finished, they are constantly being worked on and improved on, so while there is a central brain trust (React has the React team at FB, Java has the Java Executive Committee comprised of devs from Oracle and other big companies like IBM, Twitter, others. these devs are eventually going to retire and will need to be replaced by community experts) these open source communities are still very much dependent on dev community assistance/feedback for the successes of these languages/frameworks to keep the gears churning.

[wpdn]

Yep, this is close to what I was thinking too. I was wondering if this doesn't have the drawback of core team having to constantly deal with people from outside coming with their use-cases that have nothing to do with what the team's vision is. You know, "i was thinking it would be nice to have bells and whistles when you click this button" type of people. I would really love to get some insight into the efficiency of this (developer-advocacy-in-general) - seems like it's really worth it for companies.

[wpdn]

I just thought of another possible explanation - apps and integrations are probably a big part of the revenue ecosystem so e.g. in case of react, if your product is built on it and your integrations/apps/whatever engine is also react-centered, it's kind of cheap to introduce new people to these concepts. I guess.