Pay writers for tutorials that answer your buyers' setup searches

Commissioned tutorials work like this: you pay outside practitioners to write step-by-step guides for the setup and configuration tasks your buyers search for, and you host the guides on your own site. DigitalOcean runs this as a paid writers' program limited to open-source software. An outside analysis credits its 6,000+ tutorials with over 5 million monthly visits. That figure is an estimate, and it measures traffic, not signups or revenue.

How it works

The mechanism has five parts. The DigitalOcean case page holds the full record.

1. Set a topic boundary. DigitalOcean only accepts tutorials about open-source software. A rule like this keeps writers on tasks your product can actually run. It also stops the library from drifting into general content that ranks but never converts.
2. Recruit outside writers and pay them. DigitalOcean's announcement about its paid writers' program says Community members get paid for tutorials on deploying, configuring and developing open-source software. DigitalOcean raised the typical payout for a new tutorial to $300, paid by PayPal or as DO credit.
3. Edit to one template. Every guide should follow the same structure: prerequisites, numbered steps, commands that can be copied, and a closing check that the setup works. Consistency is what lets a reader trust the next guide they land on.
4. Let search do the distribution. An outside analysis of DigitalOcean's developer content describes the writers' program as the way the company scaled output, and it estimates the tutorials drive over 5 million monthly visits.
5. Turn trust into trial. In a public comment thread on DigitalOcean's container service, one commenter says that finding a DigitalOcean tutorial tells them they are in good hands. Another says the tutorials are why they became a customer. These are two anecdotes, not a conversion rate.

DigitalOcean's company timeline lists the Community launch in the same entry as its Series A, though the page shows no year. The funding round is context, not a result of the tutorials. If your buyers already gather in a forum, the community-led growth playbook covers how to recruit writers from that group.

What it takes

Our estimate: about 40 hours of work, and about 90 days before you can read a signal. The hours go into keyword research for setup queries, a writer brief and style template, recruiting and vetting a handful of writers, and technical editing of a first batch of around ten guides. Editing takes the most time, because every command has to be tested. Search pages take weeks to get indexed and settle in rankings, so a read before about three months will mostly show noise.

What to measure

Start with organic sessions to the new tutorials, compared with your organic baseline before launch. Rising sessions only mean the guides rank. They do not mean the guides earn money, and that was the exact limit of the DigitalOcean traffic figure.

The metric that matters is signups from tutorial landing sessions, counted per tutorial. A good reading is a steady trickle of signups spread across many guides. A bad reading is traffic that grows while signups stay flat.

Divide what you spend, payouts plus editing time, by those signups. Then compare that cost with paid search for the same queries. Track the activation rate of tutorial-sourced signups against other organic signups as well. People who arrive mid-setup may activate faster, or they may finish the guide and leave. Finally, check what share of guides rank for their target query on a fixed date. A low share points to weak topic choice, not weak writers.

When it backfires

• Traffic with no buyers. The library ranks for topics your product does not serve. DigitalOcean's open-source boundary is one guard against this.
• Uneven quality. The trust commenters describe depends on guides that work. A few broken commands can damage the whole library.
• Editing becomes the bottleneck. Writers deliver faster than your team can test, and drafts pile up unpublished.
• Stale guides. Software versions change, steps break, and rankings fall unless someone owns updates.
• Attribution gaps. Readers who sign up days later through another channel make the program look weaker than it is. Plan your tracking before you publish.

Run it as an experiment

Hypothesis: commissioned setup tutorials will produce signups at a lower cost per signup than paid search for the same queries.

Comparison: we recommend a holdout design with a fixed window. Choose about 20 target queries of similar volume and assign half at random to get tutorials. Leave the other half unpublished as your control. Compare organic signups from the two sets over a 90-day window that starts when each guide is indexed.

Log the following for each guide: the target query, publish date, payout, editing hours, sessions, signups, and activated signups. Score and queue topics with the growth experiment backlog template, and write up results using the growth experiment guide.

Decision rule: expand if cost per activated signup beats paid search across the batch. Cut the program if signups stay flat while sessions rise.

How strong the evidence is

The grade is practitioner report. The outcome numbers come from a third-party write-up, and the company did not publish them. DigitalOcean carries the case alone. Its own blog confirms the program and the $300 payout, but the 5 million visit figure is an outside estimate. That figure covers visits rather than signups or revenue. The customer evidence is two public comments. Nothing here shows what the program cost in total or what it returned.