When you assume…

Don’t make the same mistake as I did.

I helped launch a CLI interface to a product mostly used by people who don’t write code… and, therefore, spend little to no time on the command line.

I won’t repeat the proverb about assumptions, but it holds true here.

How you market your “developer product” depends on its intended audience—which may not be exclusively developers.

When we first work with a client, we try to figure out where they are on the developer marketing continuum. Developer-focused products need to attract developers directly, because they’re the buyers. On the opposite end are developer-enabled products that require developers to implement, but may have other buyers.

That continuum question is also where my recent post for Nordic APIs starts. In Developer Marketing for API Companies, I also cover how to find your real competitor and what it means to solve developer problems.

We may be able to help you navigate these sometimes tricky questions. But we wouldn’t want to assume. When you’re ready, reach out to the EveryDeveloper team to discuss.