TL;DR
- Most small teams go from zero to a live knowledge base with 5 articles in one afternoon (4 to 6 hours).
- The one decision that locks in a year of cost is your tool choice. Flat-rate (Helpable, $49/month) wins under 25 people; per-agent (Zendesk, $19/agent/month) wins above 50.
- Skip the "categories first" planning trap. Mine your support inbox, write the 5 most repeated questions, ship, then let zero-result analytics tell you what to write next.
Building a knowledge base takes one afternoon when you skip the planning trap that derails most attempts. The six steps below (pick a tool, mine your support inbox, write five articles, organize, publish on a custom domain, set a maintenance loop) get a small team to a live help center in 4 to 6 hours. This guide names the decisions that matter, gives prices for 5 leading tools, and shows the templates that cut writing time per article from 90 minutes to 20.
Step 1: Decide who it's for (15 minutes)
The single decision that shapes everything else: external (customers), internal (employees), or both. Get it wrong here and you redo the structure later.
The decision tree:
- Customers email the same questions weekly. Build an external knowledge base.
- New hires ask the same questions weekly. Build an internal knowledge base.
- Both are true. Build both, in one tool with access controls.
External knowledge bases need SEO (schema, sitemap, custom domain), public access, plain language, and a chat widget for "ask anything". Internal knowledge bases need a login wall, role-based permissions, integration with Slack or your identity provider, and a writing style that assumes shared context.
Most SaaS teams past 10 people end up needing both. You do not need two separate tools. Helpable, Document360, and Zendesk all let one platform host both with access rules deciding what is public. For the longer breakdown, see internal vs external knowledge base.
Step 2: Pick a tool (30 minutes)
This is the one decision that locks in cost for 12 months. Most teams over-research this and never start. Here is the short version: five tools, real prices, what they are built for.
| Tool | Starting price | Pricing model | Setup time | AI included | Best for |
|---|---|---|---|---|---|
| Helpable | $49 / month | Flat rate | 30 min | Yes | Under 25 people, EU compliance, fast setup |
| Zendesk | $19 / agent / month | Per agent | 1 to 2 days | Add-on ($50/agent) | Over 50 people, deep ticketing integration |
| Document360 | $149 / month | Per project | 2 to 4 hours | Add-on | Technical docs, dev teams |
| Notion | $10 / user / month | Per user | 1 hour | Limited | Internal only, no SEO, no widget |
| HubSpot Service Hub | $0 (free tier) | Per seat above free | 2 to 3 hours | Limited | Already on HubSpot CRM |
Three rules that filter most decisions:
- Under 25 people, pick flat-rate. Per-agent pricing scales linearly with hiring. At 10 agents, Zendesk plus AI add-on costs $1,390/month. Helpable Pro covers the same team for $149/month flat, with unlimited members included.
- EU compliance non-negotiable, pick EU-hosted. Helpable is the only flat-rate EU-hosted option in the table. Document360 and Zendesk are US-hosted by default.
- Already on Zendesk for ticketing, evaluate Zendesk first. Otherwise, evaluate it like any other vendor. Tight integration is real, but it is not free.
For a deeper head-to-head, see the best knowledge base software and free knowledge base software.
Step 3: Mine your support inbox (30 minutes)
Stop trying to invent articles. The articles are already in your support inbox.
Open your support email or chat archive. Sort by frequency. Write down the 15 most repeated questions. Those are your first 15 articles, in priority order.
If you use a help desk tool, most have a "saved replies" or "macros" feature. Those saved replies are nearly articles already. Copy each one out, add a title, and you have a draft.
The common mistake: starting with "Getting Started" content. Those articles are useful, but they are not the articles your customers actually need most often. Start with what arrives in your inbox right now. You can write the onboarding flow in week two.
Step 4: Write the first 5 articles (90 minutes)
Five articles is the minimum to make a knowledge base useful. Two articles is incomplete. Five is starting to deflect tickets.
Per article, aim for:
- Title that matches a real search query. "How do I cancel my subscription" beats "Subscription cancellation".
- Intro of two sentences that answers the question directly.
- 3 to 6 numbered steps with screenshots where the action is non-obvious.
- A related-article link at the bottom to encourage another page view.
Length: 200 to 400 words. Longer is not better. Customers skim.
AI writers cut this step in half. Helpable's AI Writer drafts each article from your existing support reply: paste the question and the saved reply, and the AI returns a structured article with intro, steps, and screenshot placeholders. Most teams report 20 to 25 minutes per article instead of 60 to 90 manually.
For full writing rules with good/bad examples and a copy-paste template, see how to write knowledge base articles.
Step 5: Organize and publish on your domain (45 minutes)
Pick three to five top-level categories. More than five and customers cannot find anything; fewer than three and the structure feels thin.
A category structure that works for most SaaS products:
- Getting Started (onboarding, first setup)
- Account & Billing (plans, payments, invoicing)
- Features (one section per major product area)
- Troubleshooting (error messages, common issues)
- API & Integrations (for technical readers)
Publish on your own subdomain (help.yourcompany.com). Three reasons:
- Domain authority feeds your brand, not your vendor's.
- Customers trust yourbrand.com/help over vendor.com/yourbrand.
- SEO equity carries over to your main domain through internal linking.
Submit your sitemap to Google Search Console the day you publish. First indexing usually takes 7 to 14 days. Helpable, Document360, and Zendesk all generate the sitemap automatically. With Notion or a generic CMS, you build that yourself.
For deeper structuring guidance with category-naming conventions, see how to organize a knowledge base.
Step 6: Set a maintenance loop (15 minutes setup, 30 minutes monthly)
The fastest way to kill a knowledge base is to publish 30 articles and stop touching it. Stale content actively damages trust: customers find an outdated screenshot, give up, and email support anyway.
The monthly loop, in 30 minutes:
- Review zero-result searches. Every search that returned no result is an article you should write next. This list is the single highest-value backlog any KB owner can maintain.
- Update the 5 most-viewed articles. If anything changed in the product (UI, pricing, flow), update screenshots and steps.
- Archive articles with under 10 views in 90 days. Dead weight crowds search results and hurts the experience.
Zero-result analytics is what most teams skip and what separates a working knowledge base from a graveyard. Most modern KB platforms surface it; Notion does not. See our SEO features for the full Helpable analytics breakdown.
What it looks like after 30 days
Based on Helpable customer data and industry benchmarks (Zendesk CX Trends, Document360 self-service stats):
- 15 to 25 articles published
- 30 to 50% reduction in tickets matching those articles
- Top 5 articles capture roughly 70% of all traffic (long-tail discovery picks up after month 3)
- AI chatbot answer rate of 60 to 70% with 15+ articles live
Six months in, most teams have 40 to 60 articles and an AI deflection rate above 70% (see knowledge base reduces support tickets for the math).
Checklist before you ship
- Tool picked and account configured
- Custom domain pointed (help.yourcompany.com)
- 5 articles drafted, reviewed, and published
- 3 to 5 categories defined
- Search bar tested with 10 sample queries from your real inbox
- Chat widget installed on main website (optional but recommended)
- Sitemap submitted to Google Search Console
- Schema markup verified using Google's Rich Results Test
After launch:
- Monthly review of zero-result searches
- Quarterly update pass on the top 10 most-viewed articles
- Annual structural review (categories, taxonomy, dead content)
Frequently asked questions
How long does it take to build a knowledge base?
With a modern tool and the six-step approach above, most small teams go from zero to a live knowledge base with 5 articles in 4 to 6 hours. Reaching 15 to 20 articles (the point where AI deflection becomes meaningful) takes another week of part-time work, around 5 to 8 additional hours.
Do I need a developer to build a knowledge base?
No. Modern tools like Helpable, Document360, and Zendesk are no-code. Setup is account creation, content writing, and pasting one script tag onto your website. Custom-domain DNS configuration takes one record change that most non-technical founders manage themselves.
Should I build a knowledge base or just an FAQ page?
Build a knowledge base if you have more than 10 repeated questions, expect to grow content over time, or want SEO benefit. An FAQ page works for simple cases (5 to 10 questions on a single page) but does not scale. See what is a knowledge base for the full comparison.
Can I migrate articles from another tool?
Yes. Most platforms accept Markdown or HTML imports. Helpable, Document360, and Zendesk all support bulk import via CSV or direct API. The harder part is rewriting articles for the new tool's structure, which usually takes 5 to 10 minutes per article.
How do I measure if my knowledge base is working?
Track three numbers: ticket deflection rate (ticket volume before vs after launch), self-service rate (article views divided by unique visitors), and zero-result searches (questions your KB does not answer yet). Most modern KB tools surface all three in analytics.
How many articles do I need before AI search works?
You can turn on AI from article 1, but the experience improves with depth. At 5 articles, AI handles narrow product questions. At 15 articles, AI deflects 60 to 70% of repeat questions. At 30 to 40 articles, AI deflection passes 80% for most SaaS support patterns. See why AI support fails without a knowledge base for the underlying mechanics.
Ready to start step 1?
If you are still picking a tool, the next step is the head-to-head review: see the best knowledge base software for full pricing and feature breakdowns of 8 platforms.
If you have a tool in mind, start a free 7-day Helpable trial and walk through these six steps end-to-end. EU-hosted, flat $49 per month, no credit card required. See Helpable pricing for the full plan breakdown.
Related articles
- What Is a Knowledge Base?
- How to Write Knowledge Base Articles
- How to Organize a Knowledge Base
- Best Knowledge Base Software for SaaS
- Internal vs External Knowledge Base
- Free Knowledge Base Software Compared
Last updated: May 2026