Brainfish for Product Marketing

Brainfish gives product marketing teams a single place to capture, organize, and surface customer-facing knowledge — launch FAQs, positioning, competitive notes, use cases, and feature education — and put it in front of customers and internal teams exactly when they need it.

This article covers how PMM teams use Brainfish in practice.

What PMMs use Brainfish for

• Launch enablement. Centralize launch assets (FAQs, talk tracks, objection handling, troubleshooting) so Sales, CS, and Support can self-serve on day one.
• Customer education. Publish feature explainers, use-case content, and ROI / upgrade content in a searchable, AI-answerable format.
• Sales enablement at scale. Consistent messaging, competitive notes, and battlecards available wherever your team works (Slack, Teams, Help Center, in-product widget).
• Insight loop. Brainfish captures what users search for and where confidence is low — feeding directly back into messaging and content gaps.

The PMM workflow

1. Seed Brainfish with the foundations

Start with:

• Positioning and messaging doc
• ICP and personas
• Top 5 use cases
• Top 10 customer objections + responses
• Competitive notes (your top 3–5 competitors)
• Pricing FAQ
• Release notes archive

Use Migrating and Bulk-Importing Content to bring existing PMM assets in from Notion, Google Drive, or a Drive export.

2. Structure with collections

Group content into collections that match how PMM works rather than how the docs site is laid out. Common collections:

• Positioning & Messaging
• Use Cases
• Competitive
• Pricing
• Launches (a new collection per launch, archived after)
• FAQs

See Collections 101 for how to set these up and choose internal vs public visibility per collection.

3. Build a launch collection per release

For each launch:

1. Spin up a Launch — {feature name} collection.
2. Drop in: feature overview, customer-facing FAQ, sales talk track, objection handling, support troubleshooting notes, known limitations.
3. Add the launch collection to the relevant agents under Agent → Knowledge Settings.
4. Link customers and internal teams to a single launch-collection URL in launch comms.

4. Capture questions as they happen

Three ways to convert real questions into knowledge:

• From Slack threads: tag @Brainfish in a thread — Brainfish drafts an article and queues it for review. See Generate, Review, and Publish Knowledge Base Article Suggestions.
• From sessions: if ambient observe-and-learn is enabled, Brainfish samples real user sessions and surfaces the most knowledge-worthy ones.
• From video walk-throughs: upload an internal product demo and Brainfish drafts customer-facing articles from it.

5. Surface in-product

Add Brainfish to the surfaces where users actually decide what to do next — onboarding flows, settings, complex feature areas, dashboards. See the Distribution section for how to deploy widget, sidebar, and Help Center agents.

6. Measure and iterate

Use Brainfish analytics to see:

• What users search for most.
• Where confidence is low (signal of missing content).
• Which articles drive the most resolution.
• Which features get the most questions — a leading indicator for messaging gaps.

Governance

• Ownership: PMM owns messaging and positioning content. Product / Support owns technical accuracy. Both review at release cadence.
• Cadence: Monthly for competitive; per-release for product changes; quarterly for everything else.
• Archive, don't delete. Outdated launch assets get archived to keep search results clean.

Get started fast

The fastest way to use Brainfish for PMM is via the Brainfish MCP server inside Claude. PMMs can dictate articles in natural language and have Claude publish them to Brainfish directly:

• See Brainfish MCP — Use Brainfish Inside Claude.

Related

• Brainfish MCP — Use Brainfish Inside Claude
• Generate, Review, and Publish Knowledge Base Article Suggestions
• Migrating and Bulk-Importing Content
• Microsoft Teams Integration and Slack integration — for internal sales/CS enablement.