Marketing to Developers

Marketing to Developers, updated 6/20/16, 2:14 AM

personedocr
collectionsBusiness Ideas
visibility302

Marketing to Developers by Kevin Chau.

Publishing documents on edocr is a proven way to start demand generation for your products and services. Thousands of professionals and businesses publish marketing (brochures, data sheets, press releases, white papers and case studies), sales (slides, price lists and pro-forma agreements), operations (specifications, operating manuals, installation guides), customer service (user manuals) and financial (annual reports and financial statements) documents making it easier for prospects and customers to find content, helping them to make informed decisions. #SEO #leadgen #content #analytics

About edocr

I am an accomplished content marketing professional helping you to build your brand and business. In my current role, I fulfill a multi-faceted solution marketplace including: publishing and sharing your content, embedding a document viewer on your website, improving your content’s search engine optimization, generating leads with gated content and earning money by selling your documents. I gobble up documents, storing them for safekeeping and releasing the text for excellent search engine optimization, lead generation and earned income. 

Publishing documents on edocr.com is a proven way to start demand generation for your products and services. Thousands of professionals and businesses publish marketing, sales, operations, customer service and financial documents making it easier for prospects and customers to find content, helping them to make informed decisions.

Get publishing now!

Tag Cloud

Marketing to Developers
Kevin Chau
Developers are the worst customers, but the best evangelists.
They ask a lot of questions
And linger in the funnel
They create lots of pre-sale support questions
But they make great evangelists
So, how do you create customers out of devs?
Product
It all starts here
Developer Thought Process
Developer Thought Process
1. Does it solve my problem?
Developer Thought Process
1. Does it solve my problem?
2. Should I build it myself?
Developer Thought Process
1. Does it solve my problem?
2. Should I build it myself?
3. Does it fit into my existing workflow/architecture?
Features Upfront
?????????
No BS Pricing
Don’t do this.
Simple. Effective.
Developer Friendly API
• Multiple SDKs
• Tutorials
• Plentiful Docs
• Examples
Developer Friendly API
Ahem, Google.
Community
Build it
Hackathons
‘Technology’ Focused
• Get qualified customers using your product
• Low to no budget required to run
• Global audience and exposure
• Make industry friends and potential partnerships
Meetups
DevRel and CMgr Gold Mine
Tech Community Meetups
Send your DevRel here
Interest Group Meetups
Curated by your Community Manager
• Social outing
• Builds strength in community
• Builds the brand outside of
the product
• Real people using the
product
• Forms stronger core users
• Create thought leaders for
your product
Tech Community
Interest Group
Conferences
Not of the “I think we should have booth babes, but I’m an idiot.” variety
Simple as that.
Pitch for your developers and send them to
share their findings in doing what they do best.
Content
Thought leadership
Position yourself as a thought leader. Use
plenty of example code.
Kevin Chau
@kchau
kevinchau.me
!
Divshot
@divshot
divshot.com
staticapps.org
“Fin.”