New users need to have little to no pre-existing knowledge about your product, meaning you need to guide them through every step of the initial setup. If you instruct users to carry out a step that requires a dependency to be installed, chances are people will quit at the second step.
Recovery paths matter as much as the steps. How a user acts when a command returns an error indicates a support ticket versus a closed ticket.
Whether a setup guide is successful is judged by whether the reader is able to tell whether they are still following it. Most setup guides fail to state the expected outcome after each step, and as such, most readers lose track after seeing an unexpected result. Without any information to the contrary, someone who has deviated from the guide is left to guess whether they should continue, try again, or even restart the whole guide, and most of the time they simply give up.
A generated setup guide skips the mundane prerequisite setup. It begins its instructions for the interesting part at step 1, with the requirement that the user has a toolchain and permissions that the user may not have, since those may never have been in the prompt. As a result, the guide fails to set up the first machine that was not already configured.
To our knowledge, there exists no guide that calls for this level of recursion on a task. The only way to know what steps are actually required is to set everything up and see where failures occur. As each of these sections of the instructions was found to be necessary, we had to search, guess, even ask, for the next step. The second person has to, unfortunately, process the instructions completely cold, as the first author’s assumptions mean every section is now invisible.
As of now, it’s best to have a teammate review the setup with your draft open. We provide a document that’s convenient for this, with numbered steps, an expected result checkbox for each step, and a space to explain how the step actually went. Comments are provided as line references to avoid general comments.
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 setup guide | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Short guide | 1,200 | $120 | $1.20 | $121.20 |
| Standard guide | 2,500 | $250 | $2.50 | $252.50 |
| Comprehensive guide | 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.
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.
Not too great. We can transcribe a walkthrough, but that’s easily done. The valuable part of that is the writer facing the same issues as your customers. If access is really not possible, we will tell you what the guide can’t claim to have verified.
A failure that can occur at a specific step in the process should be treated differently from a failure that can occur at any step in the process. Hiding a common error in a troubleshooting appendix means the reader runs into it, thinks it is a problem, and then quits before they find your appendix.
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.
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.
Mostly excellent. Your improvements to the auth section are better than what our engineers wrote. Your pagination endpoints, however, were explained in the spec according to how they behave rather than how they are, which required two revisions. Our spec is incorrect in that area as well.
Our release notes went unread, but they serve the purpose of listing what breaks and what doesn’t when considering whether to upgrade. Two customers actually took the time to send thank yous in the same week, something that had never happened before.
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