Knowledge base software holds written answers in one searchable place: how-to articles, policies, product guides, troubleshooting steps and common questions. It can be internal, for staff, or public, for customers who want to help themselves before contacting support.
This guide is for businesses replacing scattered documents, wiki pages and old help centres, or setting up a knowledge base for the first time. Most tools let you write and publish articles. The differences are in how well search works, how easy it is to keep content current, and what it costs as more people read and write.
Why a knowledge base demo can mislead you
A demo shows a small, tidy set of well-written articles with clear titles. A search for an exact phrase finds the right one at once. Real readers search with typos, different words and half a question, and real knowledge bases fill up with outdated and duplicate articles within a year.
The surprises come after launch. Search only matches exact words. Reports on failed searches are on a higher plan. Every person who edits needs a paid seat. Importing your existing documents breaks formatting and images. Articles go stale because nobody is reminded to review them.
So write down who will read and write your articles, and how they look for answers, and ask every vendor the same questions in writing.
Must ask
- How good is search? Ask whether it copes with typos, synonyms and different wording, whether it searches inside attachments, and whether it shows which searches found nothing.
- How easy is it to write and edit articles? Ask whether staff without technical skills can format text, add images, tables and videos, and reuse one block of content in several articles.
- How are permissions handled? Ask whether some articles can be internal only, whether different teams or customer groups can see different content, and whether readers need to log in.
- How is content kept up to date? Ask about review dates, an owner for each article, reminders, draft and approval steps, and version history showing who changed what.
- How do we bring in what we have now? Documents, wiki pages and an old help centre. Ask whether formatting, images, links and categories come across, and whether help with the import is free.
- How is the price worked out? Ask whether you pay per editor, per reader, per knowledge base or by page views, and which plan covers your must-haves for everyone who needs access.
- Can we get all our articles out, at any time? Ask about the format, whether images, categories and version history are included, and whether there is a fee.
Worth asking
- Does it connect to our help desk or chat? Ask whether support staff can find and send articles from inside a ticket, and whether customers see suggested articles before they contact you.
- Does it offer AI answers or summaries? If so, ask whether answers come only from your own articles, whether they show their sources, and whether this costs extra.
- Can it handle more than one language? Ask how translations are managed, and how they are kept in step when the original article changes.
- What reports are included? Ask about most-read articles, failed searches, and whether readers can rate an article or say it didn't help.
- How much can we brand a public knowledge base? Ask about your own domain, design and removing the vendor's branding, and which plan includes them.
- Where is our data stored and who can see it? Internal articles often hold sensitive procedures. Ask which country, how access is controlled and whether single sign-on is included.
The hidden costs
The price per editor is only part of the bill. Ask about each of these in writing:
- Seats for occasional editors who only update a few articles.
- Reader or page view limits on a public knowledge base.
- Single sign-on and advanced permissions on higher plans.
- AI search or answers, often charged as an add-on.
- Extra knowledge bases for different products, brands or teams.
- Import help from your current documents or tool.
- Custom domains and branding removal for a public help centre.
- Price increases at renewal. Ask for a cap in writing.
How to compare the answers
Put every vendor's written answers side by side, question by question. Then work through them in this order:
- Must-haves first. If search reports or internal-only articles are only on a higher plan, compare that plan's price.
- Then the partial answers. Ask exactly what is missing, and whether it needs an add-on, a workaround or a separate tool.
- Then the two-year total for the editors and readers you expect, not just today's numbers.
- Then a real trial. Import twenty of your own articles and ask three colleagues or customers to find answers using their own words.
Only then book detailed demos, and ask each vendor to search your own articles, not their sample help centre. If you want to see who sells this kind of software, see companies that sell knowledge base software. NeutralPick lets you send every vendor the same questions and compare their written answers side by side, for free, with no paid ranking.