Skip to main content
Org knowledge is the structured go-to-market configuration Swan reads before it researches a company, writes outreach, or qualifies a prospect. It answers the questions every rep would ask before working a deal: what do we sell, who do we compete against, and who is actually a good fit. Org knowledge has three parts: Swan uses org knowledge as background context on nearly every run: it shapes how outreach is written, how companies and contacts get classified against your ICP, and how research is framed. If you don’t define target market segments, companies stay unclassified — Swan can still work, but it can’t filter by ICP fit, and any automation that depends on ICP matching won’t have anything to match against.

​
How it differs from memory and skills

Org knowledge is deliberately structured (fields like industry, revenue range, and employee count on a segment) rather than freeform. For freeform notes that don’t fit a structured field — a nuance about a specific deal, a standing preference, a fact that doesn’t belong on a value-prop page — use org memory instead. For step-by-step instructions on how to do something, use a skill.

​
Keeping it sharp

Org knowledge is only useful if it stays current and specific. Vague value-prop copy (“we help businesses grow”) gives Swan nothing to work with when it’s writing a cold email or deciding whether a company fits. Concrete detail — who you actually sell to, what breaks without you, which competitors come up in deals and why you win — makes a measurable difference in output quality. A few practical limits to know:
  • You can define up to 8 target market segments per org.
  • Value prop and competition are each a single free-text document — there’s no length cap enforced on them, but treat them as a page, not a book.

​
Who can edit it

Reading org knowledge is available to every role, including Viewers. If you ask Swan to update the value prop, competition, segments, personas, or funnel stages, the agent requires Admin permissions and declines requests from Members and Viewers. Manual edits in the dashboard do not currently have the same role restriction: authenticated Members and Viewers can also submit org-knowledge changes there. Swan can update org knowledge itself: an Admin can talk it through a change conversationally (“we just added a new competitor, add them to our competition doc”) and Swan will write the update directly. You can also edit these fields yourself in the dashboard, under Knowledge.

​
Common questions

Can I just upload a document instead of writing out my value prop and competition by hand? You can share documents and context in chat, and Swan will use that to draft or update the value prop and competition text for you — but the stored knowledge itself is still plain text, not an attached file. Does org knowledge affect every conversation, or only outreach? It’s used broadly — outreach writing, research, and company/contact classification against your ICP all draw on it, not just sequences. I’m not an Admin. Can I still suggest changes? Yes. You can send the suggestion to an Admin, or make a manual change in the dashboard. Swan itself tells Members and Viewers it can’t make the edit and to contact an Admin. What happens if I go over 8 segments? Creating a segment beyond the 8th is rejected. Delete or consolidate an existing segment first, or reconsider whether you need that many. Is there a separate place for notes that aren’t part of the formal ICP or value prop? Yes — use org memory for durable facts that don’t fit a structured field.