Taxonomy is the element of a knowledge base that is the easiest to neglect, but will ultimately be the greatest source of failure. For every forty good articles filed under six categories that nobody would think to search by, we might as well have no articles at all. That’s a search that reverts zero results, and an auto-generated support ticket.
We think of structure first before proceeding with writing. Things such as constructing categories by the vocation of the users, matching the titles of articles to the words typed, and making a selection by whether or not to construct an article for some of the queries, are all deliberate decisions.
A knowledge base suffers from clarity primarily because of findability. An article is well-explained when the answer it contains is expected by the reader and this happens when the article is titled and categorized correctly, as well as when the first line of the article is aligned with the question. If articles are written in isolation, then the end result is a library where each individual piece is clear, but a collection is not.
Generated knowledge bases contain volume but lack structure. Four different articles may answer the same question multiple times and searchers have to navigate multiple results. Searchers end up opening the wrong article. Sifting through duplicates becomes the user’s burden and the damage isn’t fixing the duplicates but eliminating them. Answering the same question multiple times generates a knowledge base quickly. Sifting through duplicate answers is the burden of the user. Eliminating duplicates is the most important first step to a knowledge base.
Please provide the search queries that resulted in zero results, tickets that come up repeatedly, and a training session walkthrough from your staff when a customer joins your group. These things show both what the users want and what your staff assumes is known. This outline is the gap you’re looking to fill.
Knowledge bases help out more during pre-sale activities than many teams realize. Product evaluators check on the knowledge base to see if the product is complete. Knowledge bases help Sales deflect support requests by providing Sales with the links to the answers. Knowledge bases help create the first line of support deflection even after deal closure. Amplify knowledge bases by publishing long-form articles, as there are long-tail queries that your marketing pages will never capture.
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 knowledge-base content | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single knowledge-base article | 400 | $40 | $0.40 | $40.40 |
| Six-article cluster | 2,200 | $220 | $2.20 | $222.20 |
| Launch knowledge base | 4,000 | $400 | $4 | $404 |
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.
Help articles solve only one task that a user is stuck on. Knowledge Base work involves any article along with organization/structure like categories, articles, titles, duplications, article retirements. If you have twenty articles scattered with no organization, request this service. If you only need a single article, order help documentation.
Yes. It is also often more cost effective. We go over what you already have and mark what parts we will retain, merge, or put to rest. We deal with what we write and you pay us for what we write. We will never charge you for what we suggest removing.
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.
I sent a folder of interface screenshots and asked for callout text. Every caption matches what is actually visible in the image. Sounds basic. I have paid three other people for this and had to correct half the captions each time.
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