# What is a business knowledge base? | Bamboo Digital > A business knowledge base is a written brain: your rules, policies, voice, and numbers stored as plain files an AI reads before it drafts anything. Canonical: https://bamboodigital.io/guides/what-is-a-business-knowledgebase --- [Guides](https://bamboodigital.io/guides) / Foundation Knowledge base # What is a business knowledge base? A written brain for your company: product rules, compliance requirements, lead times, policies, pricing logic, and your voice with customers, stored as plain files that an AI always reads before it drafts anything. It is what lets AI answer from your facts instead of guessing. ## What actually goes in one. - **Product facts and rules.** What fits what, what works with what, specs, and the edge cases only you know. - **Compliance folders.** Marketplace rules, regulatory requirements, anything where a wrong answer has a penalty. The system reads these before every relevant reply. - **Operational truth.** Supplier lead times, reorder points, return and warranty policies, dealer terms, pricing logic. - **Your voice.** Real examples of how you write to customers, so drafts sound like you, not like a bot. - **SOPs.** How work gets done here, written once, reused forever. ### It is a file you own. Here is one. One page from a working knowledge base: plain files your AI actually reads, and so can you. Pick a business Parts and gearOnline storeHome services Ask it something a customer would Does this fit my 2023 Talaria Sting?Will it work on a Rawrr Mantis?It is out of stock. How long? This is one page from a business's files. It opens like any document, and the AI reads it before it answers. File knowledge base / products / fitment-mx2-handlebar.md ``` # Fitment: MX-2 handlebar kit updated: 2026-06-28 · source: supplier spec sheet v4 + owner confirmation 2026-06-21 ## Fits - Sur-Ron Light Bee X (2021-2026): direct bolt-on - Talaria Sting R (2023-2026): requires riser adapter RA-11 - E-Ride Pro SS: direct bolt-on, confirmed by teardown photo (files/teardown-eride.jpg) ## Does NOT fit - Talaria Sting L1e (road model): stem diameter differs. Do not suggest workarounds. - Rawrr Mantis: untested. If asked: say untested, offer to check with supplier (2-3 days). ## Reply rules - Always name the exact model and year back to the customer before confirming fit. - If the bike is not listed here, the answer is "not written down yet," never a guess. - Lead time if out of stock: 12-18 days (supplier-lead-times.md). ``` Composites of real client files, anonymized. This is the whole trick: plain files, readable by you, binding on the AI. When a customer asks "Does this fit my 2023 Talaria Sting?", the draft reply is built from this file and cites it, or says the answer is not written down yet. There is no third option. Without one AI answers from general training - Guesses about your products - Sounds certain either way - No source you can check With one AI answers from your files - Reads your rules before drafting - Cites the file it used - “Not written down yet” is an allowed answer The same claim the FAQ below makes in words: a chatbot is an interface, the knowledge base is the ground truth behind it. ## Why plain files matter. A knowledge base built as plain files on your computer has three properties a platform never gives you. **You can read it:** open any file and see exactly what the AI knows. **You can fix it:** a correction becomes a permanent rule in seconds. And **you own it:** no export fees, no lock-in, it works whether or not your consultant sticks around. ## How it changes what AI can do. Without a knowledge base, AI answers from general training data: fluent, confident, and guessing about your business. With one, the question "does this part fit?" is answered from your fitment file, with a citation, or the honest reply that the answer is not written down yet. That gap, cited versus guessed, is the entire difference between AI you can trust with customers and AI you cannot. ## From knowledge base to agentic knowledge base. The knowledge base is the foundation. An **agentic knowledge base** is the next step: the same written brain, plus agents that read it and act on it. Instead of asking one question at a time, the agents run **agentic workflows**, multi-step jobs like "draft this week's customer replies" or "flag what is below reorder point and draft the purchase orders," grounded in your files and handed back for your approval. The files keep the agents honest; the agents turn the files into work done. That is what we build. Each part of the business gets its own layer on that same foundation: [agentic operations](https://bamboodigital.io/guides/what-is-agentic-operations) for the daily running, [agentic sales](https://bamboodigital.io/guides/what-is-agentic-sales) for the pipeline, [agentic finance](https://bamboodigital.io/guides/what-is-agentic-finance) for the numbers, and [agentic marketing](https://bamboodigital.io/guides/what-is-agentic-marketing) for being found. They are built one at a time, in the order your business actually feels the pain. ## Not the same as an "agent knowledge base." The AI industry uses a similar phrase for a very different thing, and the difference is the whole point. **An agent knowledge base is developer infrastructure**: a retrieval layer wired into a platform so a bot can look things up. Engineers build it, it lives inside somebody else's product, and the people who actually run the business never see it. Ask to read it and the answer is a database schema. **An agentic knowledge base is a business asset.** Plain files you can open at your kitchen table, correct in seconds, and take with you if we never speak again. The agents read those files before they act, and every draft comes back citing which file it came from. The test is simple: if you cannot open it, read it, and fix a wrong answer yourself, it is not your knowledge base, it is someone's backend. ## The honest caveat. A knowledge base is only as good as its upkeep. It gets built in weeks, but it stays right because corrections flow back into it during review. Budget the 2 hrs/wk of review time, or expect it to drift. Apply it ## This is what month one builds. The knowledge base, wired to your real tools, with drafts you approve. [What you get](https://bamboodigital.io/how-it-works) · [Book a discovery call](https://bamboodigital.io/start) [Book a discovery call](https://bamboodigital.io/start) [See what changes in 30 seconds](https://bamboodigital.io/start#quiz) --- Site overview for agents: https://bamboodigital.io/llms.txt Every article, full text: https://bamboodigital.io/llms-full.txt All URLs: https://bamboodigital.io/sitemap.xml