Writing an optimal knowledge brief

Website scraping and PDFs give Converd raw material. The brief is the editorial layer: what must never be wrong, what nuance legal or sales cares about, and which links or facts are canonical when the site has conflicting copy on old blog posts or landing variants.

Think of it as the notes a sharp product marketer would leave for a new hire on their first day—except the hire is an agent that can speak to thousands of visitors without getting tired.

You do not need a novel. You need scannable blocks the model can retrieve under pressure. A layout that works well for most SaaS teams:

• Company snapshot — one tight paragraph: who you serve, the problem you own, and the outcome you sell. No adjectives without proof.
• Product map — each product or plan in a short subsection: who it is for, what is included, what is explicitly not included, and the migration path if someone is on the wrong tier.
• Pricing and packaging — numbers, billing rhythm (monthly vs annual), trials, refunds, and tax or currency caveats. If something requires a quote, say so plainly and say what qualifies someone for sales.
• Security, privacy, and data — hosting region, retention, subprocessors if visitors ask, and where your DPA or SOC report lives.
• Implementation reality — typical time-to-value, required integrations, and what good onboarding looks like in week one. This prevents optimistic hallucinations.
• Objections you hear weekly — the three to seven doubts that stall deals, each with a factual, calm response and (when possible) a link to a doc or comparison.

The brief is not the place for slogans that replace information. Prefer testable statements: limits, SLAs, feature names as they appear in the app, and named integrations. If your marketing page says “enterprise-grade” but your brief does not define what that means, the agent will improvise.

Disambiguate similar terms

If you call the same thing “workspace,” “account,” and “organization” in different parts of the site, pick one primary term in the brief and map the others. Visitors mirror the language they see; the brief keeps the agent consistent.

Call out stale pages

If a URL is outdated but still indexed, note it in the brief: “Ignore pricing on /old-pricing; use /pricing only.” That single line saves more confusion than a full paragraph of adjectives.

Brochures and whitepapers are great for depth, but the brief should still contain the answers visitors repeat—pricing tiers, limits, compliance statements—in plain text. PDFs are support evidence; the brief is the index that tells the agent which evidence applies to which question.

When you add a file, add one line in the brief describing what authority it has: “Security overview PDF is current as of March 2026; overrides older blog posts on encryption.”

Tie updates to real events: a launch, a price change, a renamed feature, a new integration. After each crawl or major site edit, skim the brief for contradictions. The fastest way to erode trust is an agent that sounds confident about last quarter's packaging.