What the Knowledge Base is
Understand what your Knowledge Base holds, how it is organized into files and fields, and what depends on it being right.
You want unpitch to write and judge your outreach against your actual business, not a plausible guess at it. The Knowledge Base is where that business context lives. It is the one place you tell unpitch what you sell, who buys it, what they compare you to, what backs your claims, and how you sound.
Open it from Knowledge Base in the left sidebar. The subtitle on the page says what it is: Structured business context with its supporting sources and review state.
One file per real thing
The Knowledge Base is not a folder of documents. It is a shelf of knowledge files, and each file describes exactly one real thing: one product, one buyer segment, one competitor, one customer story, one objection you keep hearing. The product calls a buyer segment an ICP segment, after ideal customer profile, and that name appears throughout.
Inside a file, a fixed set of named fields does the structuring for you. An Offering file has Capabilities, Non-capabilities, Pricing shape and Customer outcomes. An ICP segment file has Firmographics, Disqualifiers, Jobs to be done, Pains, Desired outcomes, Triggers, Circumstances and Switching forces. You fill the fields you can and leave the rest.
Two other things live on a file. Citations attach a page URL and the exact excerpt that supports a point, so a claim can be traced back to where it came from. Review state records whether a person has actually looked at a value or whether it is still something unpitch proposed.
The nine types
The New button opens a dialog headed Add structured knowledge, and every type there carries a caption telling you how many of it a workspace should have.
| Type | What it holds | Cardinality |
|---|---|---|
| Positioning | How you frame the choice: alternatives, differentiated value, fit, category | Foundation · one per workspace |
| Voice | How you sound, written as mechanics: traits, owned and banned lexicon, tone registers, gold examples | Foundation · one per workspace |
| Offering | What a product does, and, first-class, what it does NOT do | Library · one per real entity |
| ICP segment | A buyer segment: firmographics, jobs, pains, outcomes, triggers, switching forces | Library · one per real entity |
| Alternative | Something the buyer would choose instead, including doing nothing | Library · one per real entity |
| Proof | One piece of evidence and what it is good for | Library · one per real entity |
| Objection | One push-back, the concern under it, and the response you have validated | Library · one per real entity |
| Market change | A dated shift in the buyer's world, for a credible reason to write now | Library · one per real entity |
| Document | An indexed unstructured document to structure later | Material · add as needed |
Positioning and Voice are the two you can only have one of. If one already exists, its card in the dialog reads Open and takes you to it instead of making a second.
What confirming changes
unpitch can fill much of this by reading your public website, but what research produces is a proposal, not a fact. Every value it writes lands in a review queue, and the empty-state hint says it plainly: You control what is confirmed.
That queue is what the count on the sidebar Knowledge Base entry and the Needs review chip on the shelf are counting. Working it down is how researched context becomes context you stand behind.
Confirming is not a gate, though. Where a file type is already being read — today that is ICP segment files, and persona creation reads them — every non-empty value reaches the build whether you reviewed it or not. Review changes how much weight it carries. An unreviewed value the research inferred is carried as a declared assumption; one quoted straight off your site is not flagged at all, so it arrives as settled fact.
There is no completeness score and no health ring, and an empty field is a legitimate end state. The only nudge is a quiet line at the foot of a file naming which fields are still empty. Fill what you actually know.
What reads it today
Open a file and the Field guide on the right tells you, for the file type you are in, what belongs in the field your cursor is in and which parts of unpitch consume that type. Two captions matter there. Used by lists what reads this type today. Coming lists what will and does not yet.
Today the only live consumer is Persona creation, on ICP segment files: when you accept a persona recommendation, the matching ICP segment file is what grounds the persona that gets built. Everything else is listed as Coming. Filling in Positioning, Offering, Voice, Proof, Objection, Alternative or Market change is worth doing as your own record and as preparation, but it does not change what the product produces yet.
If research read something about your business wrongly, review is where you catch it. Nothing downstream will hold that value back for you.
One Knowledge Base per workspace
The shelf, the review queue and the badge all belong to the active workspace. Switch workspaces and you switch all three. If a file you expected is missing, check which workspace you are in before you go looking for it.
Reading a persona
Open the detail panel, read each of its sections, and decide whether a persona is the right reader for the draft in front of you.
Letting unpitch research your business
Fill most of your Knowledge Base from your public website, watch the scan run, and know what happens when you want to run it again.