Users are in a bad mood when they access help articles. They have either burned time trying to sort out a bug that is the reason why they got to the help article in the first place, or they have been repeatedly frustrated and have given up. They don’t want to scroll past explanations of features in your application that you think are valuable and that help them understand what the bug is fixing.
These should be written upside down contrast with typical marketing text. Answer first, steps second, context only if it alters what the user should do next. Everything else is wasted space and is unneccesary information that will just anger the user and force them to scroll.
The help article has to be identical to the interface. If your settings screen has a label Members and the article has a label Users, a number of readers will report the ticket. ‘Users’ is gone. That kind of super literal accuracy only happens when you have the product open in another tab while you work.
Generated documents show examples of interfaces that differ from yours. The menu is misplaced while a toggle carries a name that is unfamiliar to your company. The reader assumes they are reviewing a different version. An issue of minor concern has just been converted to a support request.
Thirty of your most common ticket subjects are what we ask for. That list is the article backlog regardless of whether anyone has actually written it or not. The writer of our article does each task in the product and captures the wording on each of the associated screens. The writer notes where there are actual issues with the interface.
Hand over the drafts to a support agent and have them send the article instead of typing a reply for a week. Whatever is still added by hand after that is what the article is lacking. The review will provide more information than someone who already has the answer would give after a careful reading.
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 documentation | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single help article | 450 | $45 | $0.45 | $45.45 |
| Feature help set | 1,600 | $160 | $1.60 | $161.60 |
| Help center section | 3,000 | $300 | $3 | $303 |
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.
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.
We place each image on the page, and add captions. However, to have unprocessed data and the current theme, the source images need to be screencaptures and made by your team. In the event that you want us to do that, please give a dummy user account to the writer with dummy data as required.
Keep track of what articles influence what screens. This will allow you to know the articles to recheck when a screen has been changed. We include the mapping between articles and screens with the provided set. It is usually a short amount of text to update an affected article rather than a full rewrite.
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.
Ordering is clearly very good, and the screenshots are clearly explained. The guide assumes the customer has admin access, which a good number of them do not. We wrote a pre-req box ourselves in ten minutes. Everything else was complete.
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