Help article readers are usually frustrated, and right so. They reached out for help, and nothing from their troubleshooting was successful. If you were working on a help article, would you open with “Hello”? Of course, not. There is no time to waste on formalities. Use your opening sentence(s) to answer any of their burning questions.
The article doesn’t waste time telling the reader about what they are trying to accomplish. It kicks right off with step one, and this is where most of the guides stop. It, however, saves the extra touch and goes through what to do when step four does not look like the screenshot.
Help content exists post-sale, and its worth is measured in tickets that are never escalated. This means that accuracy takes precedence over perfection. For example, an article with the wrong menu name creates the contact that it was written to eliminate, plus an additional contact about the documentation being wrong.
A model is complete enough to describe an interface without having to resort to your iPad. It is specific enough to tell a user to navigate to Settings, then Integrations, with a lot of certainty, even though your menu says something entirely different. The model also includes a nonexistent toggle that does not exist and a permission that is not mentioned. Bad instructions are worse than none at all.
The writer will lead you through the product, step by step, in a real world scenario once the description of your product is complete. Every label is taken directly from the screen. Should a step rely on a permission or plan that the reader may not have, that condition is shown before the step rather than noted after the step.
Support agents should review the draft before publishing. This is important because support agents have knowledge specific to how customers misunderstand the same instructions in three unique ways. We provide help desk entries in your template with each section clearly and concisely formatted with bulleted and/or numbered steps and any additional call-outs. Publishing is as simple as pasting our help desk template.
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 help center article | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Short how-to article | 500 | $50 | $0.50 | $50.50 |
| Standard help article | 900 | $90 | $0.90 | $90.90 |
| Troubleshooting guide | 1,500 | $150 | $1.50 | $151.50 |
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.
It makes a large difference. A sandbox or trial account lets the writer walk the flow and copy labels exactly. Without one, we work from recordings and screenshots you supply, and the draft comes back with more questions attached to it.
Yes. Send four or five articles you consider good, plus any rules you have about imperatives, headings, screenshot use and how you refer to the product. Consistency across a help center matters more than any single article being clever.
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 provided our sales team’s top five objections and asked if the pricing FAQ could address them without being defensive. It seems to accomplish this. In particular, the answer to the refund question is provided in two sentences and does so without beating around the bush.
I thought there would be a cheesy moment when the person had a flash of inspiration, but instead came back with three paragraphs talking about what the clinic does on a Tuesday morning. Our nurses said it was a perfect representation of what we do. That was the test, so I was pleasantly surprised.
Everyone said we should tell our story. The writer asked what a customer needs to believe before buying, and made a 280 word response. Our founder did the mildly offended response for about a day and now uses that in interviews.
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