Selling to Developers: Your Documentation Is a Competitive Advantage
Tags: devrel, writing, leadership
Published: 2023-02-27 12:33:23

Usually people think of technical documentation as helping existing users. Documentation lets customers find answers to questions themselves. It reduces load on your support team. But when you are selling to developers, your technical documentation is a **_sales tool_**.

Your ability to win customers will depend on how developers perceive your documentation, and thus your product. Bad documentation leads to lost sales. But great documentation can make you stand out in the market and help you win over developers and close deals.

## Don't make me talk to a human

Developers have become an important buyer in modern tech organisations. Unlike many other buyers, the customer journey software engineers take is **self-serve**. This means:

1. They do not want to talk to a sales person
2. They want to try it before they buy it

In one survey, **57% of developers said they wouldn't reach out for a sales demo** [^1].

Looking at the best companies that sell to developers, they make it easy for customers to buy how they want. **89% of developer-first Cloud 100 companies offer a freemium product or a free trial** [^1]

They give their prospects the ability to try out their product and form an opinion themselves. This is where your documentation comes in.

## Building trust

Documentation builds trust with developers. If they buy your product, they will be spending hours or even months interacting with your service/API/SDK. Good documentation reassures developers. It lets them know they will not have to contact a support agent when they have an issue or something is unclear in your product. It is also an indirect sign of your product quality. If your documentation is sub-par, is your product that good either? [^3]

[Stripe](https://stripe.com/docs) is the canonical example of a company with world-class technical documentation. So much so, that it has almost become a meme at this point. Every developer-tools company wants to have docs like Stripe. Their whole brand of being developer-friendly is built upon excellent documentation (and a product to match, of course). Building a payments integration can be hard. But they know that Stripe is a solid service that will guide them through the process.

If your documentation is unclear, hard to read, full of obvious mistakes or outdated screenshots, developers will turn away.

## Guiding towards the "Aha-moment"

Another key function of your documentation is guiding developers on how to get started. It is important to help your users get to the point in your product where they have the _"aha-moment"_ where they understand the value you can provide.

For any even slightly complex product, it is hard to get your users to this point through only an onboarding flow. You need tutorials and guides that help new users navigate your product.

In other words, you need good docs.

> Docs are like air. It's impossible for a developer to be successful without them

\- _Andrew Baker, Twilio Director of Developer Education [^2]_

[Twilio](https://www.twilio.com/docs) is another company that prides itself on having high quality documentation. They provide ["Quickstart"](https://www.twilio.com/docs/sms/quickstart) guides to introduce developers to various parts of their product. They have [goal-based tutorials](https://www.twilio.com/docs/tutorials) that walk through real examples of building a full Twilio-integration for different use cases.

Everything is pushing a developer new to the platform towards success.

## Docs in sales

When I said developers never want to talk to salespeople, this is only partly true. Large enterprises with a complex list of requirements will still expect to talk to a human. But only after their developers have first developed an understanding of your offering on their own.

Even Atlassian, which at times claimed to have no sales staff, does sales:

> If you're a large enterprise customer that has more complexity, or
> potentially more value to us, we have a team that can help steer you in the
> right direction and answer a more complicated set of questions that you have.

\- _Jay Simmons, Atlassian President [^4]_

Our customers tell us documentation is something their sales representatives reference constantly on calls. We have even heard of companies giving early access to feature documentation privately to some customers, before releasing the feature publicly.

Documentation helps close deals.

## Wrapping up

If you are selling to developers, your documentation has to be a high priority. Developers want to try out products themselves, and you have to be able to support them with proper guides, tutorials, and references. Having world-class documentation will make you stand out in the market.

Here are a few takeaways about how to improve your docs:

* Make sure someone is responsible for the quality of your documentation
* Have proper analytics to measure how people are consuming your documentation
* Consider [docs-as-code](https://www.doctave.com/blog/2021/08/30/why-you-should-consider-docs-as-code.html) if you want your developers to be able to contribute to docs easily


[^1]: [_OpenView: The developer-focused go-to-market playbook_](https://offers.openviewpartners.com/developerfocusedgtmplaybook)
[^2]: [_Lessons from Twilio: How To Build Developer Loyalty with Docs and Dev Ed_](https://www.decibel.vc/content/how-to-build-developer-loyalty-with-docs-and-dev-ed)
[^3]: [_Broken windows theory_](https://en.wikipedia.org/wiki/Broken_windows_theory)
[^4]: [_How Atlassian built a $20 billion company with a unique sales model_](https://www.intercom.com/blog/podcasts/scale-how-atlassian-built-a-20-billion-dollar-company-with-no-sales-team)