# Sourcing developer marketing content

DevFeed: [Sourcing developer marketing content](<https://devfeed.tech/articles/sourcing-developer-marketing-content-41204.md>)

Original publisher: [Read original article](<https://www.craigkerstiens.com/2017/12/28/Sourcing-developer-marketing-content/>)

Author: Map

Published: 2017-12-28T20:55:56Z

Content type: article

Language: en

Sources: [Craig Kerstiens](<https://devfeed.tech/sources/craig-kerstiens.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Users](<https://devfeed.tech/topics/users.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [content](<https://devfeed.tech/tags/content.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-marketing](<https://devfeed.tech/tags/developer-marketing.md>), [email](<https://devfeed.tech/tags/email.md>), [marketing](<https://devfeed.tech/tags/marketing.md>), [technical](<https://devfeed.tech/tags/technical.md>)

## AI overview

The article shares ways for developer-focused companies to source high-quality marketing content from within their organizations. It recommends turning well-written engineering emails into blog posts and capturing interactions with newer product users to maintain a beginner mindset.

## Source excerpt

I spend a lot of time with dev tool and data companies. I think I've more or less banished myself to a life of working in the space, no consumer products for me. In that world a common topic that comes up amongst marketing teams is how do I get my team to contribute to content? Sometimes the person already has an idea of how they want the team to jump onto the bandwagon of their plan, sometimes they're entirely open minded. I won't get into pros and cons of various approaches here, rather after sharing some of my approaches in one on one settings I thought it could be useful to share more broadly here. Turn emails into blogs I'm a big fan of high quality content when it comes to developer focused products. Yes, you can publish x vs. y with FUD and get some traction with it. You can publish high level customer stories that don't get down into the details. But publishing high quality deep technical content that other engineers appreciate gives you a huge head start in getting buy in from your customers. The best thing about much of this type of content is you likely already have it sitting within your organization. Engineers spend a lot of time being thorough and articulate in their emails to their peers. If you see a well written email from one engineer to the engineers@ list and then others chime in either with questions, follow-up, or praise then it's likely a great candidate for a blog post. We recently had one of these at Citus where another engineer replied with "Nice blog post :)", a few weeks later we had a post for the rest of the world to read. The thing about emails though is the engineers won't usually take and turn them into a blog post. Get a technically minded person that likes to write and put some framing around it, pull out relevant details, and collaborate with the engineer. I've often found going from one of these emails to a fully published blog post can be anywhere from 2-8 hrs (including reviews and edits). Beginner mindset with tickets As your