Text is scanned in bits and pieces. A user clicks on page forty from a search result, and reads two paragraphs then leaves the page. This is the unit of use. Each page must be able to stand alone from the others for the set to be of use. Similar words and/or meanings for the same things must be used across the set.
Our feedback includes your product, your existing docs, and a call with whoever knows the edge cases. For behaviors that are unclear, the writer will ask the question rather than describe what they think the behavior of the feature may be. Documentation of guesses will come back to you in the form of support tickets.
Most of the work in writing consists of being consistent. If you call a setting a workspace on one page, a project on another, and an environment on a third, your reader is going to think you have three distinct things. Writers employ the term glossary. They create a running list of these definitions and then compare that glossary to your interface strings. They will then tell you the discrepancies that you have come to ignore.
A model will describe a feature you do not have because the sentence shape is correct and nothing informed it your app lacks a bulk export. The most annoying aspect is the keys. They are generated config keys. They look like your real keys and they fail silently. Eventually, they find their way to support.
The writer separates your material into tasks, concepts, and references to manage the drafting of the documents. Most doc sets fail because the tasks, concepts, and references get mixed within one page. Thus, a user looking for a parameter is forced to review a philosophy of the product. Separating the tasks, concepts, and references is the first structural decision that drives the design of everything else.
Documents degrade in quality unless someone owns them. We give our deliverables in the format of your choice, with the source files, glossary, and a short note on which pages will be edited in the next release. This helps your team maintain our written work without having to understand our logic. You are not purchasing a locked deliverable.
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 technical documentation | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single reference | 800 | $80 | $0.80 | $80.80 |
| Standard doc set | 2,000 | $200 | $2 | $202 |
| Full documentation | 5,000 | $500 | $5 | $505 |
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.
Yes — 2 rounds are included, for 14 days after delivery, handled by the writer who wrote the piece rather than by someone new to the brief.
Fill in the order form with your brief and email address. No account needed. You get a confirmation by email, then the finished piece as a document within 3 days.
Generally not. We provide source files in your chosen markup so your team makes the commits. This keeps the review and CI processes under your team’s control. If you prefer us to open pull requests, please include the name of the repository as well the access level in the brief, and we will let you know what is possible.
Let the author know as soon as you can. Changes in a draft require no effort; changes requested after the draft was submitted consume one of your two rounds of revisions, which will remain open for 14 days. We recommend that you document a pinned release for products that ship on a weekly basis.
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.
We have never recorded our three architecture talks but we have now. One of the teams who take note of things and join in a session and then compile a summary of the two positions once we’ve made our decision. Saw that as a good opportunity to strengthen their practice so no longer have any new hires asking questions. Parent 1: rewr22567 Parent 2: autograder
Most writers omit error response text, or post the status codes with no surrounding context. Ours explained what they thought the caller did wrong with a short response per status. Because of this explanation, our support queue for that endpoint has gone quiet.
Before drafting, the client sent over eleven questions. Two of the questions asked about failure states that we had never documented before. Responding to these questions took me a morning to complete, but now the internal notes have improved. The guide is the second best thing that came from this order.
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