Documentation is read by real people who can determine if something is correct or incorrect almost immediately. A parameter name that does not match is not strictly a style concern. It is at least fifteen minutes of wasted time and the completion of a support ticket from a now a little ticked off person who has to read the rest of the page questioning its validity, as well.
The writer works with the product in front of them. They do each step and run each sample and provide anything that does not work as a case to the engineers, rather than explaining it in prose, which only smoothes over the answer.
Docs are a buying surface whether or not you treat them as one. Developers evaluate documentation before they evaluate the product, and usually before team members in sales even hear about the product. If the quickstart works, your tool makes it onto the shortlist. However, once the tool Bookmarks a step, and fails, developers immediately exit the page and nothing in your funnel is able to capture data on the step, why the developer failed, and what tutorial they were following.
This is where harm from generated text can easily be measured. Models create endpoints, parameters and flags that look exactly right and which simply do not exist. A developer following one of those spends half an hour to show that your documentation was incorrect, then brags about it to his colleagues.
To begin, the writer builds something small and real using your API or product, taking notes to capture every moment of confusion. These notes will be the outline for the rest of the article. Because the goal of the engineers’ survey is to capture the technical accuracy of the API/product, and not the finished article, they keep their feedback short and to the point. This approach helps to maintain a readable article.
Quietly, docs and marketing grow more distant. The website calls it a workspace, docs call it a project, and in the end support has to be the interpreter for the customer. We consider your terminology list as a contract, and if none is available, we create one from what the actual interface says, then show the places your marketing contradicts this.
One rate, whatever the format: $10 per 100 words. You are paying for the writer’s time and judgement, so the price scales with the words rather than with a package tier.
| Typical documentation | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Quickstart guide | 800 | $80 | $0.80 | $80.80 |
| Feature documentation set | 2,000 | $200 | $2 | $202 |
| Full product docs section | 4,000 | $400 | $4 | $404 |
The writer receives 100% of the writing price. Our 1% fee is added on top of it, and 0.5% is donated to tree planting. Full pricing breakdown.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
Yes. Send two or three pieces you like the sound of, or your style guide. Matching an established voice is ordinary work for a writer and close to impossible for a model that has never read your back catalogue.
Those who work on documentation will take care of your issues. They will not build your API, but they will monitor a repository, run a sample, read the response payload and report any discrepancies that exist between the behavior and the documentation. Stack name included in your brief, and we will match the right writer to your document.
We can provide Markdown or MDX that can be added into most static docs platforms via front matter if you provide the schema. Repository access and pull requests can be offered for long-term projects. Files via email are the easiest way to complete a one-off request.
Completely. Copyright transfers to you on delivery, with no attribution requirement and no licence back to us. Nothing written for you is resold, repurposed or republished.
Reviews from completed, paid orders in this category.
I’ve written and purchased a lot of feature copy, and most of it is vibes instead of verbs, which is a huge loss. This was not the case. It clearly stated what a feature did and what the change was in the system. It got our sales team reading it on the phone.
The customer we used in this example sent us a nice email saying it was the least stressful case study she’s had to do. This has never happened to us. I have to say the article is awesome, too. The customer liked the interview, but what I will remember is the process.
I sent a folder of interface screenshots and asked for callout text. Every caption matches what is actually visible in the image. Sounds basic. I have paid three other people for this and had to correct half the captions each time.
We do not ask you to take the no-AI promise on trust. Each draft is run through these platforms and the reports are attached to your delivery email.
Originality.aiAI detection + plagiarism
GPTZeroAI detection
TurnitinAI detection + similarity
CopyleaksAI detection + plagiarism
Winston AIAI detection
ZeroGPTAI detection
SaplingAI detection
Content at ScaleAI detection
Send the brief, get a human draft back within 3 days. No account, no subscription, no AI.
$10 per 100 words · all of it to the writer · 0.5% to trees