# Persona-to-Message Map: Content Matching by Buyer Role

> A master mapping table that connects each buyer persona to the specific belief gap they hold at each deal stage, the content type that closes it, and the named asset to use. Built once by a manager or enablement lead, handed to the whole team to stop reps sending the same deck to every stakeholder.

Free template for sales managers. Topic: [Sales Content, Playbooks & Battlecards](https://www.peerlab.ai/library/topic/sales-content-playbooks-battlecards/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/persona-to-message-map-content-matching-buyer-role/

## How to use it

Start with the worked SaaS example to see the logic, then use the blank template to build your own map for your segment and ICP. Review it quarterly or whenever a new content asset lands, and use it as the source of truth when coaching reps on what to send and why.

## What's inside

- Explanation of the four map columns: persona, belief gap, content type, named asset, and fallback
- Definitions of the five buyer roles covered: economic buyer, champion, technical evaluator, end user, procurement
- Explanation of the four deal stages used: awareness/first contact, active evaluation, late-stage/commercial, post-decision/close
- Fully worked example map for a SaaS deal across all five roles and four stages
- Named fallback options for every cell where the primary asset may be missing
- Guidance on the most common failure modes this map is designed to prevent
- Notes on when a belief gap recurs across roles and how to handle it without duplicating effort
- Blank template version with fill-in prompts for teams to adapt to their own segment

## What this is and why it exists

Most content libraries have a supply problem disguised as a quality problem. The assets exist. Reps just send the wrong one to the wrong person at the wrong moment, usually because nobody ever told them which content was built for which belief.

This map fixes that. It is not a content audit tool and it is not a framework for evaluating individual decisions in a single conversation. It is an enablement-side master reference: one document, built by a manager or enablement lead, that every rep on the team can use to answer the question "what do I send this person, right now, to move this deal forward?"

The organising logic is the belief gap: the specific thing a buyer role does not yet believe, which is blocking them from moving forward. Content only works when it closes a belief gap. If the gap is "I don't know whether this will integrate with our stack," a business case PDF closes nothing. If the gap is "I can't justify the spend to my CFO," a technical architecture diagram closes nothing either.

---

## The five buyer roles

| Role | What they own | Typical blocker |
|---|---|---|
| Economic buyer | Budget and final sign-off | ROI credibility and risk |
| Champion | Internal case-making | Ammunition to sell upward |
| Technical evaluator | Architecture and security | Fit with existing systems |
| End user | Day-to-day adoption | Confidence it will actually work for them |
| Procurement | Contract and commercial terms | Risk, compliance, and precedent |

---

## The four deal stages

1. **Awareness / first contact.** They know you exist. They do not know if you are relevant.
2. **Active evaluation.** They are comparing you against alternatives, running assessments, involving more stakeholders.
3. **Late-stage / commercial.** They are close to a decision. The conversation has shifted to terms, risk, and internal approval.
4. **Post-decision / close.** They have chosen you verbally or conditionally. The job is to remove the last obstacles to signature and start onboarding.

---

## How to read the map

Each cell contains four things:

- **Belief gap:** the specific thing this person does not yet believe at this stage
- **Content type:** the format most likely to close that gap
- **Named asset:** the actual asset to use (name it exactly as it appears in your library)
- **Fallback:** what to use if that asset does not exist yet

---

## Worked example: SaaS deal (revenue intelligence platform, mid-market)

### Economic Buyer

| Stage | Belief gap | Content type | Named asset | Fallback |
|---|---|---|---|---|
| Awareness | "I don't know if this is a real problem worth solving" | Executive one-pager, benchmark data | *Revenue Leakage Benchmark Report* | Industry analyst stat in email, cited with source |
| Active evaluation | "I can't see the ROI clearly enough to defend this internally" | Business case / ROI calculator | *ROI Calculator: Pipeline-to-Revenue Impact* | Customer proof quote with hard number, forwarded via champion |
| Late-stage | "The number feels right but I'm worried about risk" | Risk mitigation summary, peer reference | *Enterprise Risk & Security Summary* + reference call | Written reference from named customer at similar company |
| Post-decision | "I need to justify this to the board / my peers" | Announcement-ready summary, success metrics | *Go-Live Success Metrics Sheet* | Bullet list of agreed outcomes from your proposal doc |

### Champion

| Stage | Belief gap | Content type | Named asset | Fallback |
|---|---|---|---|---|
| Awareness | "I'm not sure I can get anyone to care about this internally" | Discovery conversation, problem framing | Structured discovery call, no asset needed | Email with two questions that surface the problem |
| Active evaluation | "I need something I can actually forward upward" | Executive summary they can present themselves | *Champion Enablement Deck: One-Page Business Case* | Email summary you write for them to forward verbatim |
| Late-stage | "I need to handle the objections my CFO is going to raise" | Objection handling guide, FAQs | *CFO Objection FAQ: Revenue Intelligence* | Bullet list of the three most common CFO objections with responses |
| Post-decision | "I need this to go smoothly so it reflects well on me" | Implementation timeline, named contacts | *Onboarding Roadmap: 30-60-90 Days* | Email from your CSM introducing themselves before contract is signed |

### Technical Evaluator

| Stage | Belief gap | Content type | Named asset | Fallback |
|---|---|---|---|---|
| Awareness | "I don't know if this will work with what we already have" | Integration overview, tech stack compatibility list | *Integration Directory: CRM, MAP, and BI Connectors* | Bullet list of native integrations in email |
| Active evaluation | "I need to understand the architecture before I'll recommend it" | Technical deep-dive, security documentation | *Technical Architecture Overview* + *Security & Compliance Pack* | Live technical call with your solutions engineer |
| Late-stage | "I'm worried about implementation complexity and handoff" | Implementation spec, SLA documentation | *Implementation Specification v2.1* + *SLA Terms Summary* | Reference call with a technical contact at a live customer |
| Post-decision | "I need to know what happens if something breaks" | Support model documentation, escalation paths | *Support Tiers & Escalation Path Guide* | Written summary of your support SLA from the AE |

### End User

| Stage | Belief gap | Content type | Named asset | Fallback |
|---|---|---|---|---|
| Awareness | "I don't see how this changes my day-to-day" | Use case video, role-specific one-pager | *"A Day in the Life" Video: AE Role* | Short written walkthrough of a typical workflow improvement |
| Active evaluation | "I'm worried about the learning curve and disruption" | Trial access, guided walkthrough | Product trial + *Quick Start Guide: First 7 Days* | Recorded demo of the two or three features they will use most |
| Late-stage | "I've seen tools like this fail before" | Peer proof, adoption data | *Customer Story: [Named similar company], adoption rate* | Quote from a frontline user at a reference customer |
| Post-decision | "I need to know what training looks like" | Onboarding and training plan | *End User Training Programme Overview* | Scheduled intro call with your onboarding team before go-live |

### Procurement

| Stage | Belief gap | Content type | Named asset | Fallback |
|---|---|---|---|---|
| Awareness | Not typically involved yet | None required | N/A | N/A |
| Active evaluation | "I need to know if you meet our supplier requirements" | Security questionnaire response, compliance docs | *Pre-completed Security Questionnaire (ISO 27001)* + *Data Processing Agreement* | Direct intro to your legal/compliance team |
| Late-stage | "I need to benchmark this pricing and understand the terms" | Commercial summary, pricing rationale | *Commercial Terms Summary* + *Pricing Rationale Sheet* | AE-written email summarising the commercial structure and what is flexible |
| Post-decision | "I need to close this out cleanly and quickly" | Redline-ready contract, named legal contact | Standard MSA + *Procurement Fast-Track Contact Sheet* | Named contact at your legal team with a committed response SLA |

---

## Common failure modes this map prevents

**Sending the ROI deck to the technical evaluator.** They are not asking "is this worth it?" They are asking "will this work?" The business case lands as noise.

**Sending the architecture overview to the economic buyer.** This signals you do not understand their question. It can actively damage credibility.

**Sending nothing to the end user until late-stage.** By the time procurement is involved, end-user resistance can kill a deal from the inside. Early proof of usability matters.

**Using the champion as a postbox rather than an ally.** The champion enablement deck exists so they can make the case without you in the room. If you give them nothing to work with, you are depending on their memory and improvisation.

---

## Blank template

Copy this table structure for each buyer role in your segment.

**Role:** [Name the role]

| Stage | Belief gap | Content type | Named asset | Fallback |
|---|---|---|---|---|
| Awareness | | | | |
| Active evaluation | | | | |
| Late-stage / commercial | | | | |
| Post-decision / close | | | | |

**Instructions for filling it in:**

1. Name the belief gap in plain language, as the buyer would say it, not as you would describe it internally.
2. Choose a content type based on what format closes that specific gap, not what you have available. Identify the gap first, then find or build the asset.
3. Name the asset exactly as it appears in your library so reps can find it without asking.
4. Write a fallback for every cell. If you have no fallback for a gap, that is a content production priority, not a gap to leave blank.

---

## Maintenance

Review this map when: a new content asset is created, a stage is renamed or restructured, a new buyer persona is added to your ICP, or win/loss analysis reveals a pattern of wrong-content sends. Assign one owner. A map nobody maintains becomes a map nobody trusts.
