Knowledge

Knowledge Base

Every complaint about AI content — generic, confidently wrong, could-be-anyone's-product — is a grounding problem. The model didn't know enough about you. The Knowledge Base is the fix: one place holding everything GoShipFast knows about your product, which every other feature reads before it writes.

When an article gets drafted, a topic pick chosen, a customer brief authored, or a marketing plan generated, this is what grounds it. Better knowledge in, better everything out.

What's inside

Knowledge inside a brand has three tabs. Two are generated reports with their own pages — Market Analysis and Marketing Plan. The third, Files, is the raw material:

• Uploads — drag and drop PDFs, images, and text files: pitch decks, product specs, positioning docs, testimonials, past writing you're proud of.
• URLs — add any page; an auto-discover subpages toggle crawls and ingests an entire docs site or blog in one add.
• Folders — organize however you think.

Every item is processed for the AI's use (statuses: pending → processing → ready, or failed) and labeled by source: user upload, AI generated, crawled, or system default. A detail dialog shows type, versions, and processing metadata; a trash with restore protects against fat fingers.

Your site itself was crawled into knowledge at brand creation — the base layer that makes a brand-new brand already know its own product. Knowledge processing is free; it's setup, not production.

The third report

Alongside market analysis and marketing plan, onboarding generates a content analysis: what your site already covers, classified by article type (how-tos, comparisons, listicles, use cases…), with coverage percentages, gaps, and a suggested roadmap. Its main consumer is the weekly topic engine, which uses it to fill gaps instead of repeating you. It refreshes as your published content grows.

What to feed it

In rough order of impact:

1. Positioning you've actually written — the "why us" doc, the pitch deck. The AI can infer positioning from your site, but your own words are the difference between generic and yours.
2. Customer language — testimonials, reviews, support threads. This is where authentic article phrasing and sharp lead-brief rules come from.
3. Product depth — docs, specs, changelogs. This makes articles technically substantial instead of surface-level.
4. Your best past writing — the clearest style signal you can give.

Ten minutes of curation here upgrades every artifact the system produces after. It's the highest-leverage maintenance in the product.