agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/messaging-matrix/SKILL.md

messaging-matrix

Skill13 starsChanged 22 days agoMITView on GitHub

Use this skill when one message does not fit every buyer and you need messaging by persona, industry or stage: \"build a messaging matrix\", \"tailor our pitch for each persona\", \"different messages for CFO and CTO\", \"sales messaging framework\". Maps each persona to its top pains, the outcome they care about, proof that persuades them, objections and the words to use and avoid, then writes ready-to-use lines for cold email, LinkedIn, calls and landing pages.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when the same pitch goes to a CFO, a team lead and an engineer.

    line 16
  2. Distinctive:

    Call: "I work with CFOs who'd rather not hire another analyst to get to a 5-day close."

    line 57
  3. Distinctive:

    Every persona row has a different first sentence.

    line 62
  4. Distinctive:

    MUST keep the core value proposition consistent across rows.

    line 69
  5. Distinctive:

    MUST use only approved proof points.

    line 70
  6. Distinctive:

    NEVER create rows for segments without distinct pains.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this when the same pitch goes to a CFO, a team lead and an engineer. It produces a matrix that keeps the core value proposition but changes the pain, proof and words for each reader.

Inputs

  • The core value proposition and pillars.
  • Personas (economic buyer, champion, user, technical evaluator).
  • Proof points, tagged by what they prove.

The play

1. Build the grid

Rows are personas; columns are:

ColumnWhat goes in
Measured onThe metric they own
Top painThe pain in their words
OutcomeThe result they want
Pillar to lead withWhich of your pillars fits best
ProofThe proof point that persuades this role
ObjectionTheir most likely pushback and the answer
UseWords that resonate
AvoidWords that make them tune out

2. Pick the lead pillar per persona

A CFO hears cost and risk; a team lead hears time and quality; an engineer hears how it works and what it touches. Same product, different first sentence.

3. Write the lines

Per persona: an email opener, a LinkedIn opener, a 20-second call opener and a landing page headline. Lines reuse the matrix words exactly.

4. Add industry or stage variants only when they change the pain

A variant earns a row when the pain or the proof genuinely differs (healthcare compliance, a seed-stage team without a RevOps person). Otherwise, the persona row is enough.

Example row

PersonaMeasured onTop painOutcomeLead pillarProofObjection → answerUseAvoid
CFOClose time, audit findings, headcount cost"We hire analysts to do reconciliation"5-day close without new hiresAutomation of reconciliationContoso: 9 → 4 days, one analyst redeployed"Another tool to buy" → replaces 2 tools and manual hoursclose, audit trail, headcountrevolutionary, synergy, seamless

Lines for the CFO:

  • Email: "Most finance teams your size close in 8-10 days, and most of it is reconciliation."
  • Call: "I work with CFOs who'd rather not hire another analyst to get to a 5-day close."
  • Landing page: "A 5-day close, without another analyst."

What good looks like

  • Every persona row has a different first sentence.
  • Proof is matched to persona.
  • The matrix fits on one page; reps actually use it.
  • The common mistake is building a 12-column matrix for 15 micro-segments that nobody opens again.

Rules

  • MUST keep the core value proposition consistent across rows.
  • MUST use only approved proof points.
  • NEVER create rows for segments without distinct pains.

Example prompts

  • "Build a messaging matrix for CFO, Controller and AP Manager from our value prop."
  • "Our SDRs use the same pitch for everyone. Create persona lines for email and LinkedIn."
  • "Add healthcare and fintech variants to our messaging matrix where they truly differ."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free