# Message Map: What It Is and How to Build One (+Free Template)

> What a message map is, how it differs from a messaging framework, a step-by-step build method, a worked example, and a free template.

- Source: https://calven.ai/resources/product-marketing/message-map
- Author: David Kolinek
- Published: 2026-07-05
- Last updated: 2026-07-15
- Tags: messaging, message map, positioning, product marketing, PMM

---

A message map is the document that turns your positioning into the words your whole go-to-market team reuses. The format is the easy part. A blank map takes ten minutes to draw, and every template site hands you one. The map is only as good as the buyer language inside it, and that is the part no format supplies. Below is a definition that resolves the map-versus-framework confusion, the components, a build method that starts where it should, a worked example, and a free template.

## What is a message map?

A message map is an internal document that lays out a product's positioning as a hierarchy: one core message at the top, a handful of supporting pillars beneath it, and proof points under each, usually cut by buyer persona. It is a reference the whole team draws from, not customer-facing copy. Pragmatic Institute calls it [an internal document that acts as a messaging structure](https://www.pragmaticinstitute.com/resources/articles/product/a-practitioners-guide-to-product-message-maps/) for product communications. Crayon defines it as an overview of your company's positioning. Cascade Insights describes it as [positioning laid out in the format of a map](https://www.cascadeinsights.com/message-maps-frameworks-and-more-decrypting-the-differences-for-the-b2b-marketer/).

The three definitions agree on the load-bearing word: positioning. The map does not invent your message. It organizes the positioning decision you already made, and organizing is [a core product marketing deliverable](/resources/product-marketing/what-is-product-marketing). The core message at the top is [your positioning made concrete](/resources/product-marketing/how-to-write-a-positioning-statement), turned from an internal strategy paragraph into a line a seller can actually say.

Map, framework, house, matrix: these are largely the same idea drawn different ways, and arguing about the name distracts from whether the language inside is right. The shared skeleton is a hierarchy of core message, pillars, and proof points. Cascade Insights has the clearest breakdown of the near-synonyms:

| Term | What it emphasizes (per Cascade Insights) |
|---|---|
| Message map | [Positioning laid out in the format of a map](https://www.cascadeinsights.com/message-maps-frameworks-and-more-decrypting-the-differences-for-the-b2b-marketer/): a visual hierarchy |
| Messaging framework | [Value props, pillars, and proof points in a grid-like format](https://www.cascadeinsights.com/message-maps-frameworks-and-more-decrypting-the-differences-for-the-b2b-marketer/) |
| Message house | [Messaging organized in the outline of a house](https://www.cascadeinsights.com/message-maps-frameworks-and-more-decrypting-the-differences-for-the-b2b-marketer/) |
| Message architecture | [The key messages each persona or stakeholder needs to hear](https://www.cascadeinsights.com/message-maps-frameworks-and-more-decrypting-the-differences-for-the-b2b-marketer/) |
| Messaging matrix | [Distinct messaging by persona and channel](https://www.cascadeinsights.com/message-maps-frameworks-and-more-decrypting-the-differences-for-the-b2b-marketer/) |

A map implies the visual, hierarchical snapshot; a framework is usually the more detailed grid it summarizes. Pick the layout your team will actually keep open.

## What goes in a message map?

Four layers, top to bottom: a core message, message pillars, proof points, and a persona cut. Each layer supports the one above it, which is what makes it a map rather than a list of claims.

| Component | What it is | The discipline |
|---|---|---|
| Core message | The single sentence everything ladders up to. Your positioning made concrete. | One sentence. Not a paragraph. |
| Message pillars | The value-prop themes that support the core message. | Three is the disciplined default. |
| Proof points | The evidence under each pillar: metrics, customer quotes, case studies, third-party validation. | Evidence, not a feature list. |
| Persona cut | How each pillar reframes for a specific buyer. | The map's job, not an afterthought. |

Three pillars is the well-sourced default. Pragmatic Institute builds its guide around the rule of three, and three is what most disciplined teams ship. Some go to five. Treat that as a ceiling you reach when the product genuinely needs it, not a target, because a fourth weak pillar dilutes the three strong ones. Proof points are where maps most often go soft: Pragmatic recommends [ordering them by revenue impact](https://www.pragmaticinstitute.com/resources/articles/product/a-practitioners-guide-to-product-message-maps/), which forces the question a feature list never asks, namely which evidence actually moves a deal.

## How to build a message map, step by step

Build it from the buyer's words in, not the org chart out. The order below is deliberate: the first step does most of the work, and skipping it is why so many maps look complete and still fail.

> Let your customer do the work for you – steal their language (in the nicest possible way, of course).
>
> — Emma Stratton, Founder and CEO, Punchy

1. **Start with customer language.** Before you write a single pillar, pull the exact words buyers use from real conversations: call transcripts, win/loss notes, customer interviews, review sites. Not the words your team wishes buyers used. The words they actually said, verbatim, including the unglamorous ones. Crayon's method starts with personas for the same reason. Everything downstream inherits the quality of what you capture here.
2. **Lock the core message.** Your positioning made concrete, in one sentence a seller can say out loud without wincing.
3. **Draw the three pillars from the themes in the language.** Cluster what buyers actually care about into three, and let those clusters become your pillars. Not your feature categories. Not your engineering roadmap.
4. **Attach proof points.** Evidence under each pillar, ordered by what moves revenue.
5. **Cut by persona.** Reframe each pillar in the terms the specific buyer uses, because the CFO and the practitioner value the same product for different reasons and in different words.

A map assembled from internal jargon is decoration. It will be well-formatted, internally consistent, and useless, because the buyer never sees themselves in it.

Step one is also where AI helps most. Rather than combing through call recordings by hand, point a model at your transcripts through a sales-intelligence MCP and have it surface the buyer's exact phrasing, clustered into the themes that become your pillars. A prompt to start from:

**Extract buyer language from sales calls**

```text
# Role
You're a product marketing analyst building a message map from the voice of the customer. You work only from what buyers actually said, in their own words, never ours.

# Context
I'm writing the pillars of a message map and need the raw language first: the exact words buyers use for their problems, the outcomes they want, and the alternatives they weigh. I'll cluster your output into three to five themes and turn those into pillars, so the honesty of the source language matters more than polish.

# Source data
Pull the transcripts of our sales calls across the whole company, the most recent 12 months (or the last few hundred calls, whichever is larger). Favor prospect and customer conversations over internal ones. [Use your sales-intelligence MCP here, e.g. "use the Gong MCP" or "use the Chorus MCP", to fetch the transcripts.]

# Task
From those transcripts, pull verbatim buyer language into four buckets:
1. Problem: how buyers describe the pain they're trying to solve, including the blunt, off-message wording.
2. Outcome: the result they say they want, in their terms.
3. Objections: their hesitations, risks, and reasons to say no.
4. Alternatives: what they call the competitors, incumbents, and the status quo (spreadsheets, "doing nothing").

# Output format
Give me one table per bucket, with three columns: the verbatim quote; the speaker's role and segment (for example "VP Marketing, mid-market"); and the call date. Below the tables, cluster the recurring phrases into three to five themes, and for each theme list the three most representative quotes. End with one line on which theme came up most often.

# Rules
Quote verbatim, never paraphrase or clean up grammar. Never invent a phrase, a speaker, or a source that isn't in the transcripts, and if a bucket is thin, say so. Prefer patterns that many buyers repeat over a single vivid quote.
```

Swap the bracketed placeholder for whichever tool holds your calls. The same prompt works against any sales-intelligence MCP, so "use the Gong MCP" becomes "use the Chorus MCP", and so on.

**Free template:** [Message Map Template](https://docs.google.com/document/d/1y9cZ1MxDvYMdZWccop8I85s2Ggi2cswxRqnrxyAR0S0/edit?usp=sharing)

A blank message map skeleton: the core message, three pillars with a supporting line each, proof points under every pillar, a persona cut, and a prompt plus a quality check under each blank.

The template gives you the empty hierarchy. What it can't give you is the positioning decision the core message is supposed to make concrete. That decision has to be made before the map has anything true to organize, and it is a different, harder piece of work.

**Further reading:** [Obviously Awesome: How to Nail Product Positioning — April Dunford](https://www.amazon.com/Obviously-Awesome-Product-Positioning-Customers/dp/1999023005) (Book)

The positioning decision that has to be settled before a message map has anything true to organize.

## A filled-in message map example (reconstructed from public messaging)

No company publishes its internal message map. Like a positioning statement, it is a strategy artifact, not marketing copy. What follows is a reconstruction assembled only from one company's public homepage and product messaging, not a leaked internal document. It shows the shape filled in: a core message, three pillars, proof points, and one persona cut.

**Illustrative example: Notion**

| Layer | Content |
|---|---|
| Core message | The connected workspace where teams and agents think together. |
| Pillar 1: One workspace, not twelve tools | Docs, wikis, projects, and databases in one place, so context stops fragmenting across apps. Proof: replaces separate doc, wiki, and project tools `[illustrative]`. |
| Pillar 2: Bend it to how your team works | Flexible building blocks assemble into whatever a team needs instead of a rigid template. Proof: databases, custom views, and templates configurable without code `[illustrative]`. |
| Pillar 3: AI that knows your context | AI that answers from your own workspace, not the open internet. Proof: search and generation grounded in your existing docs and data `[illustrative]`. |
| Persona cut (team lead) | Stop paying for and stitching together five tools. One workspace your team will actually keep open. |

Read it top to bottom and the ladder holds: each proof point supports its pillar, each pillar supports the core message, and the persona cut restates the whole thing in a buyer's terms. Every metric here is marked `[illustrative]` on purpose. In a real map, each one would carry a source or be cut, because an unsourced proof point is a claim, not proof.

## Who captures the buyer language, if not you?

Every step of the method above depends on one thing the format can't supply: the exact language your buyers use, captured from real conversations rather than invented at a whiteboard. Getting that language out of hours of call recordings and interview notes and into a usable record is the job of Calven's [Voice of Customer Agent](/platform/research#voice-of-customer). Today it reads uploaded transcripts, interviews, and win/loss notes and folds the signals into an evidence-backed knowledge base with the quotes attributed to their source. The skill that captures the exact terminology buyers use, the one most directly tied to filling a map, is on the near roadmap. A map also goes stale the moment the product, market, or competitors move, so that capture has to be continuous, the kind of monitoring [AI is starting to take on in product marketing](/resources/ai-for-pmm/how-ai-is-changing-product-marketing), not the annual refresh that always slips and leaves sellers quoting pillars the buyer no longer recognizes.

That record is meant to feed the [Messaging Agent](/platform/messaging#messaging) Calven is building to write and maintain the messaging framework, grounded in real customer language instead of internal jargon. That agent isn't shipped yet, and saying so matters: the buyer's language is the work, and it's worth capturing well whether an agent or a person does the listening.