playbooks

home / skills / gtmagents / gtm-agents / messaging-framework

messaging-framework skill

/plugins/sales-enablement/skills/messaging-framework

This skill helps craft compelling enablement messaging frameworks for sales, marketing, and success teams with structured value, proof, and objections.

npx playbooks add skill gtmagents/gtm-agents --skill messaging-framework

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.1 KB
---
name: messaging-framework
description: Use to structure value propositions, proof points, and objection responses
  for enablement assets.
---

# Enablement Messaging Framework Skill

## When to Use
- Creating new sales plays, launch content, or talk tracks.
- Refreshing messaging for competitive shifts or product updates.
- Enabling partners or success teams with consistent narratives.

## Framework
1. **Audience & Pain** – define persona, current pains, and desired state.
2. **Value Pillars** – articulate 2-3 core benefits with supporting proof.
3. **Proof & Stories** – attach metrics, customer quotes, ROI snippets, demos.
4. **Objection Handling** – map common objections to concise responses.
5. **CTA & Next Step** – specify recommended actions (demo, workshop, business case).

## Templates
- Message house worksheet (persona, pain, value, proof, CTA).
- Objection/response matrix.
- Story library index referencing assets.

## Tips
- Tailor variations per segment/industry but keep pillars consistent.
- Partner with product marketing for latest proof points.
- Revisit after every major launch or pricing change.

---

Overview

This skill helps you build consistent, high-impact enablement messaging by structuring value propositions, proof points, and objection responses. It packages a repeatable framework and templates to speed creation of sales plays, launch content, and partner enablement assets.

How this skill works

You define the target audience and their pain, then capture 2–3 value pillars with supporting proof. The skill organizes proof and customer stories, maps common objections to concise responses, and recommends a clear CTA or next step. Templates include a message house worksheet, objection/response matrix, and a story library index to keep assets reusable.

When to use it

  • Drafting new sales plays, launch collateral, or sales talk tracks
  • Refreshing messaging after product updates or competitive shifts
  • Enabling partners, customer success, or field teams with consistent narratives
  • Preparing battlecards and objection-handling guides for reps
  • Creating business-case materials and demo scripts tied to outcomes

Best practices

  • Start with a clear persona and explicit pain-to-desired-state statement
  • Limit to 2–3 value pillars and link each to specific proof or metric
  • Keep objection responses short, outcome-focused, and testable in roleplay
  • Maintain a central story library and update it with every major launch
  • Collaborate with product marketing to validate proof points and ROI

Example use cases

  • Build a message house for a vertical-specific sales play in one session
  • Create an objection/response matrix for a pricing change rollout
  • Assemble a story library of customer quotes and ROI metrics for demos
  • Produce partner enablement packs that preserve core pillars but include regional examples
  • Refresh field collateral after competitive positioning changes

FAQ

How many value pillars should I include?

Keep it to 2–3 pillars so messaging stays focused and memorable.

How often should I revisit messaging?

Revisit after major launches, pricing changes, or when win/loss patterns shift.