An onboarding guide must provide the reader with a single result-producing example before the reader loses interest. It is not enough to show the reader summary statistics of the modules, or to provide a tour of the settings. The example must involve the reader performing an action within their own account and with their own data, so that the reader is compelled to continue using the system.
Company guides written by employees tend to skip over steps because they are often already well known by everyone in the given office. Recently, this step has felt obvious to many, so it has not been captured, and users have proceeded to step two without first completing step one.
Recalling an experience as a beginner requires a type of memory. Novices need to think back to what phrases they couldn’t understand, to what they thought were unnavigable screens, and to the perceived length of an import against how long it really took. This type of memory is built from being confused in the past and, in this case, from talking to your most recent clients about what almost deterred them.
Ask for onboarding and you receive a walking tour of the product bundled with marketing jargon. So, something like “Capabilities”, “Features”, and “Benefits” may be listed. No sign of order. No indication of a dependency of one step over the other. For a new user, steps need to deliver a working outcome. A catalog of features is not a working outcome.
We want to speak with 2-3 customers who signed up in the last quarter as well as anyone in charge of your implementation calls. We will make a list of the nearly-stop obstructions from those calls. The writer will then conduct the onboarding themselves, timing each individual step. They will then arrange the onboarding around the nearly-stop obstructions instead of featuring elements.
Include your target reader, the final result, and whatever level of access to your product that you can provide in the brief that you send along with the order form. Creating an account is not necessary and there are no charges until the scope is agreed upon. Writing is charged at $10 for each 100 words, with a 1% administration fee, so a 1,500-word guide would be $150 plus $1.50, delivered within three days.
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 onboarding guide | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Day-one quick start | 600 | $60 | $0.60 | $60.60 |
| Thirty-day onboarding guide | 1,500 | $150 | $1.50 | $151.50 |
| Role-based onboarding set | 3,200 | $320 | $3.20 | $323.20 |
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.
Yes, by assigning someone who already knows the subject rather than someone who will research it overnight. If we do not have the right specialist available we will tell you rather than take the brief and hope.
Yes, and communication systems typically need splitting. Members of your team who create integrations and members of your team who log their first support ticket need different first hours of work. We typically write a single shared opening section, and short sections for each of the roles that follow, to ensure everyone reads the instructions that apply to them.
They each have varying weights and copy is adapted accordingly. In-app text needs to be short, contextual and direct. Emails have to capture interest to get open. Guides can afford to be more detailed. Describe where you use each of the channels and we will write to suit each channel. We will not reword one draft to fit all.
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.
Thirty articles with the same structure and with the same voice are difficult to develop for a knowledge base. Screenshot placeholders were described with prose instead of with tags. Unfortunately, our designer had to try to find them with some difficulty. This is a small thing, but I plan to put it in the brief next time.
Twenty-two articles on our top ticket drivers. The writer requested redacted transcripts, and then described the problems in the way customers used the language – thermostat will not hold temperature, instead of thermostat calibration. Help center search finally started working.
Eleven articles covering our top ticket drivers. They requested the original ticket text first, not the internal descriptions, and the difference is significant. The articles use the terms customers input into the search box. There’s been a downward shift of about a fifth in the volume of contacts on those topics.
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