> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Messaging Frameworks

> Codify positioning, value props, and key messages once. Apply them across every Chat, Message Test, and AI workflow.

Messaging Frameworks are how you stop messaging from drifting. Codify your positioning, value props, key messages, and proof points once, and GetWhys applies them automatically when your team drafts, evaluates, or generates content — inside the product and through MCP across the rest of your AI stack.

## Why this exists

Most PMM teams have a messaging document. The problem isn't writing it — it's keeping the rest of the org on it. Outdated decks circulate. Sales improvises. AI tools generate copy from whatever they happened to scrape last quarter. By the time someone notices the drift, six different versions of the value prop are already in market.

A Messaging Framework in GetWhys is the source of truth your team and your AI workflows are constrained to. Update it once and downstream content gets the update.

## What goes in a Framework

A Messaging Framework is a free-form document. Common contents:

* Product positioning and category
* Primary value proposition
* Secondary value props by persona or use case
* Proof points (case studies, stats, customer quotes)
* Competitive differentiation
* Key messages by funnel stage
* Words and phrases to use, and ones to avoid

Markdown and rich text are both supported. The format is up to you — what matters is that it's opinionated enough to be useful as a constraint.

## Organization-level vs. Project-level

<Tabs>
  <Tab title="Organization Frameworks">
    Live under **Customization** and apply to all work in your account by default.
  </Tab>

  <Tab title="Project Frameworks">
    Live inside a Project and override the organization frameworks for any work done in that Project. Use Project Frameworks when a specific campaign or launch has its own positioning that differs from the main framework.
  </Tab>
</Tabs>

## Creating a Framework

For an Organization Framework: go to **Customization → Messaging Frameworks → Add Framework**. For a Project Framework: open the Project, go to **Settings → Messaging Frameworks → Add Framework**. Give it a title, write the content, and save.

## Drafts

Save a Framework as a draft while you're still iterating. Drafts don't get applied to Chat or Message Testing until published — useful for getting alignment internally before flipping the switch.

## Using Frameworks in Chat

Type `@` in any Chat input to mention a Framework. The full content gets pulled into the prompt as context, so Chat knows exactly which positioning to apply.

You can also let GetWhys apply Frameworks automatically. When you're in a Project that has a Project-level Framework, Chat will reference it without you needing to mention it.

## Using Frameworks across your AI stack

Frameworks are exposed through the MCP integration. Any AI tool your team uses (Claude, Cursor, Typeface, custom agents) can pull the Framework directly. The same positioning constraint applies across every workflow, automatically. See [MCP integration](/integrations/mcp).

## For PMM and marketing leaders

This is the governance layer for messaging consistency. Your team and your sellers are shipping content faster than anyone can review. The Framework is what stops the drift — set once, applied everywhere, updated when the positioning evolves.

## Bulk upload

You can bulk upload Frameworks from the Frameworks page if you have existing documents to import. Supported formats are listed on the upload screen.

## Tip

<Tip>
  Frameworks work best when they're opinionated. "We're the most flexible BI tool" gives Chat something to work with. A laundry list of every possible benefit gives Chat nothing to anchor on.
</Tip>