The Knowledge Base is your personal reference content. Your frameworks. Your playbooks. Your canonical answers. Your common objection responses. The coaching engine draws from this during live meetings so the guidance you see is grounded in your own thinking, not a general model and not the open internet.
Why bother building one
A general model can give you a decent answer. Your own notes can give you the right answer. The engine pulls from your Knowledge Base at the moment of need, so the coaching card you see mid-call is already in your voice. The second time a prospect pushes on price, the response is the one you worked out the first time.
What belongs in it
- Objection-handling notes.
- Pricing playbooks.
- Discovery questions you want to ask.
- Product one-pagers.
- Competitive teardowns in your framing of the comps.
- Personal commitment templates. Your floor numbers. Your boundaries.
- Previous meeting notes you want to pull forward into the next one.
What does not belong in it
- Confidential customer data you do not have the right to retain. The entry stays on your machine, but “on your machine” is not the same as “allowed to retain.”
- Anything you would not want surfaced at an awkward moment. If a note would be embarrassing to see on a coaching card mid-meeting, it belongs somewhere else.
How to add an entry
- Open Dashboard > Knowledge Base > New entry.
- Give it a title, an optional category, and tags. Tags are how you scope entries to meetings later.
- Write the body in Markdown.
- Click Save.
The entry is indexed locally for fast retrieval within seconds. Save it, start a meeting, and it is in play.
How entries get into a meeting
- By tag. A meeting profile can scope which tags are in play. A sales profile might pull only entries tagged pricing or objections.
- By project. Tie entries to a project, link projects to meetings, and the right content shows up on the right call.
- Default. If you set no scoping rules, everything in your Knowledge Base is available to the engine.
Testing an entry
Click Preview on any entry to see which recent meetings or rehearses would have surfaced it. If it never fires on calls where you expected it, the body is probably too vague. Add a few concrete phrases and preview again.
Editing, deleting, archiving
Entries are yours. Edit any field at any time. Delete and it is gone. Archive to keep an entry on hand without making it available for retrieval. We do not hold a cloud copy and we do not keep version history on our side.
Where entries show up
- Live coaching. Cards may quote your content when the context matches. The quote appears inline on the card so you can tell the guidance is grounded.
- Rehearse mode. A rehearse pulls from your Knowledge Base to draft the four sections. The more relevant entries you have, the sharper the draft.
- Meeting Brief. The Brief synthesizes the entries that fit the attached documents and the meeting profile.
- Ask Meetings. Entries are searchable alongside your meeting transcripts. A question like “what is my floor on a 50-seat annual deal” can hit a Knowledge Base entry directly.
Where your Knowledge Base lives
Everything is local. We do not read it. We do not sync it. There is no cloud mirror. If you want a backup, click Export to get a Markdown bundle you can store wherever you want. Restoring is a drag-and-drop back into the Knowledge Base tab.
Where to go from here
- Live coaching. How the overlay works during a meeting and how your Knowledge Base entries show up on coaching cards.
- Rehearse mode. Pre-call prep that pulls from your Knowledge Base to draft structured guidance.
- Meeting Brief. Document-grounded prep that folds in the Knowledge Base entries that fit.