How do I build a knowledge base when I have nothing?

The question almost always arrives at the same moment. Someone wants to start a knowledge base, or bring in an AI that answers customer questions, looks at the documentation lying around, and sees nothing usable. An old manual from three versions ago. A FAQ with seven questions on the website. A shared folder nobody opens anymore.

That is usually where it goes quiet. Because documenting everything first feels like a project of months, and nobody has time for that project.

Good news: that project is not needed either.

You have more than you think

Go into your sent folder and search for a question you get often. You will find the same answer five times over, retyped from scratch by someone else each time. That is documentation. It just sits in the worst possible place: a mailbox exactly one person can open.

The same goes for your chat history, your quotes with the same explanation at the bottom, and the write-up someone posted internally last month for a new colleague. Your company writes answers all day long. It simply does not keep them.

So building a knowledge base from scratch is largely collecting what already exists, rather than inventing what ought to exist.

Start with the twenty questions that keep coming back

Ask everyone with customer contact to write down, for one week, which questions come in. No system, just a list. At the end of that week you have a ranking, and that ranking is your table of contents.

Take the top twenty from it. That is your first knowledge base. Not five, because then your customer misses too much. Not two hundred either, because then you never finish and within the year you are sitting on articles you never reviewed.

For each question, find the best answer that has already been sent and paste it into an article. Twenty articles of ten lines are worth more than three perfectly written pages, because your customer is now helped twenty times instead of three.

One question, one article, in your customer's words

Two rules keep your knowledge base usable while it grows.

The first: one article answers one question. An article called "Everything about your order" gets found by nobody and read in full by nobody. Split it up until each article explains one thing.

The second: use your customer's words in the title, even when those words are wrong internally. If everyone calls in about "extending the warranty" and you call that a service agreement internally, then your article is called "Extending your warranty". Your customer searches with the words they know. They do not know your internal name for it.

It sounds like a small thing and it makes the difference between a knowledge base that works and one that is full without solving anything.

Skip the structure debate

The classic trap is a meeting about categories while not a single article has been written. Out comes a tree of chapters and subchapters, designed for the knowledge base you hope to have in three years.

With twenty articles you need no tree. Five to eight categories are enough, and name them after what your customer is trying to do. Getting started, ordering and delivery, billing, fixing problems. Do not go deeper than a couple of clicks, and certainly do not organise it the way you are organised internally. Your customer does not know which department handles their question, and they should not have to.

Structure is easy to change afterwards. Articles that do not exist are not.

Publish before it is finished

Do not wait until all twenty articles are neatly done. Put them online as soon as they are correct, even if half of them still read like an answer pasted out of an email. An article that helps someone today is more useful than the same article looking better in six weeks.

And then say so. A knowledge base nobody knows about does nothing. Put the link in your signature, in your confirmation emails, on your contact page and in your chat window. Point to it yourself when you answer a question, even though it costs you one extra click. That is also your first test of whether the article is good enough.

Let the rest grow out of the questions that come in

Here is the reversal that makes the whole project workable. You do not have to predict the knowledge that is missing. Your customers point it out for you.

Every question that comes in and is not covered by your knowledge base is an article you are missing. The answer your colleague types on it is the content of that article. Tie those two together and your knowledge base grows along with the questions people actually ask, instead of the questions you expected to get.

That is also why the order "document everything first, add AI later" rarely works. You spend months writing ahead based on a guess. Starting with twenty articles and letting practice fill in the rest delivers a more complete result within a few weeks, and it is easier to keep up as well.

How Sarrai gets you going

Getting started is exactly what Knowledge KickStart exists for, and it is included in every plan.

If you have documents lying around, old ones included, throw them in. Word files, PDFs, a wiki export, your website. Sarrai pulls the topics out of them and writes draft articles, organised by topic instead of by file. You read them over and approve.

If you genuinely have nothing on paper, Sarrai runs a guided conversation with the person who knows. They explain how it works in plain language, and Sarrai writes the articles afterwards. Nobody has to fill a blank page.

After that the approval inbox takes over. Every question Sarrai cannot answer comes back as a proposal for a new article, based on the answer your employee gave. So your knowledge base keeps growing while you simply help your customers. How fast that start goes in practice is covered in How quickly can you get started with Sarrai.

Start small, start this week

Take one afternoon. Collect the ten questions that come in most often, find the answers you have already sent for them, and put them online. That is a real knowledge base, and it is useful from that moment on.

The rest comes from your customers. They are asking their questions anyway.