Messaging Hierarchy
Positioning is the strategy; messaging is the words. Most teams skip the layer in
between and let every surface invent its own - so the website promises one thing,
the ads a second, and the sales deck a third, and the buyer never hears the same
story twice. This skill builds the messaging hierarchy (the "messaging
house"): one value proposition on top, three message pillars holding it up, proof
points under each pillar, and per-channel copy derived from - never inventing
beyond - that structure. Build it once, and every channel says the same thing in
its own register.
This skill takes the output of [[positioning-statement]] as its input and produces
the brief that [[landing-page-copy]] turns into hero and page copy. It is the
spine of the [[launch-plan-sequencer]] and the source the [[sales-enablement-kit]],
[[plg-motion-designer]], and [[launch-day-runbook]] pull their language from - so
the same promise survives from the strategy doc to the go-live announcement.
When to use this skill
Reach for it the moment positioning is fixed and you need words, and whenever
someone notices the website, ads, and sales aren't saying the same thing. If
positioning itself is still wobbly (you can't name the audience, the alternative,
or the one differentiator), stop and run [[positioning-statement]] first - a
messaging house on a cracked foundation just scales the confusion.
The hierarchy, top to bottom
Everything below the value prop must ladder up to it. If a pillar doesn't
support the value prop, or a proof point doesn't support its pillar, cut it.
- Value proposition - one sentence. The single promise to the single
audience, in their words, that no chosen competitor can say as credibly.
- Message pillars - three (occasionally two or four) themes that prove the
promise is true. Each is a reason-to-believe, not a feature. "Faster" is a
pillar; "webhooks" is not.
- Proof points - under each pillar, the concrete, checkable evidence:
metrics, capabilities, customer outcomes, integrations, certifications. This
is where features finally appear - in service of a pillar.
- Per-channel copy - the same hierarchy expressed in each surface's voice
and length budget: a 6-word hero, a 90-character ad, a one-line sales opener.
The ordered workflow
Work top-down. Do not write a single ad until the value prop and pillars are set.
- Ingest positioning. Pull the four load-bearing inputs from
[[positioning-statement]]: target customer, the alternative they'd otherwise
use (the "instead of"), the one differentiator, and the category frame. If any
is missing, get it before proceeding.
- Draft the value proposition. One sentence: for [audience] who [need],
[product] is the [category] that [single differentiated benefit] - unlike
[alternative]. Write it in the customer's language, not yours. Kill adjectives
that any competitor could also claim ("powerful," "seamless," "intuitive").
- Derive 3 message pillars. Ask: "What three things must a skeptic believe
for the value prop to be true?" Those are your pillars. Name each as a benefit
the buyer feels, not a feature you ship. Three is the target - two is thin,
five is a list nobody remembers.
- Load proof points under each pillar. 2-4 per pillar. Each must be
checkable - a number, a named capability, a customer result, a logo, a
compliance fact. If you can't substantiate it, it's a claim, not a proof point;
cut it or go get the evidence.
- Run the ladder-up test. For every proof point ask "which pillar?" and for
every pillar ask "does this prove the value prop?" Orphans get cut or
re-homed. The house must be fully connected.
- Project onto channels. Express the same hierarchy per surface, longest to
shortest: website (value prop = hero, pillars = section headers, proof points =
body) → sales ([[sales-enablement-kit]]) → ads → product/PLG
([[plg-motion-designer]]) → social. Shorter channels carry fewer pillars, never
different ones.
- Write the one-page brief and hand off. Emit the messaging house as a single
page (see template) and hand it to [[landing-page-copy]] for the hero/landing
words and to [[sales-enablement-kit]] for the deck and talk track.
Quality bar
A messaging hierarchy is done when:
- The value proposition is one sentence and survives being read aloud. No
semicolons stapling two promises together.
- Every pillar is a reason-to-believe the buyer cares about, not a feature
name, and there are three (two or four only with cause).
- Every proof point is checkable - a number, capability, outcome, or fact a
buyer could verify. Nothing aspirational hiding as evidence.
- The house is fully connected: no orphan pillar that doesn't support the
value prop, no orphan proof point that doesn't support a pillar.
- A teammate could regenerate the hero, an ad, and a sales opener from the
one-pager alone and they'd all say the same thing in different lengths.
- It uses the customer's words, validated against real call transcripts /
reviews / support tickets where possible - not internal jargon.
- It reuses the existing GTM skills rather than re-deriving them: pricing
language defers to [[pricing-strategy]] / [[saas-pricing]], competitor framing
to [[competitive-intelligence]], overall plan to [[go-to-market-planner]].
Do NOT
- Do NOT start here without positioning. No fixed audience / alternative /
differentiator means no value prop. Run [[positioning-statement]] first.
- Do NOT write the landing page in this skill. This produces the framework
and brief; the actual hero/page words are [[landing-page-copy]]'s job. Stop at
the one-pager.
- Do NOT let pillars be feature lists. "SSO, audit logs, SOC 2" is three
proof points under one pillar ("Enterprise-ready"), not three pillars.
- Do NOT ship un-evidenced superlatives. "The fastest," "the only," "#1"
without a checkable proof point is a liability, not a message.
- Do NOT let channels diverge. A different length per channel is correct; a
different message per channel is the exact failure this skill exists to
prevent.
- Do NOT re-invent pricing, competitive, or plan content. Cross-link to
[[pricing-strategy]], [[saas-pricing]], [[competitive-intelligence]], and
[[go-to-market-planner]] instead of duplicating them.
Runnable artifact - the consistency linter
This self-contained Python script holds the messaging house as data and checks the
structure the eye misses: orphaned pillars/proof points, the wrong number of
pillars, channels that go off-message, and proof points that read as un-checkable
superlatives. Fill in HOUSE, run it, and fix what it flags before you write a
word of channel copy.
#!/usr/bin/env python3
"""messaging_lint.py - lint a messaging hierarchy for structural integrity.
Usage: python3 messaging_lint.py (edit HOUSE below first)
No dependencies. Pure stdlib.
"""
import re
import sys
# ---- FILL THIS IN (from your positioning-statement output) ------------------
HOUSE = {
"value_prop": (
"For revenue teams drowning in CRM busywork, Pulse is the sales workspace "
"that auto-logs every call and email \u2014 unlike Salesforce, no manual data entry."
),
"pillars": [
{
"name": "Zero manual entry",
"proof": [
"Auto-captures calls, emails, and meetings into the CRM",
"Reps save ~5 hours/week vs. manual logging (Q2 customer survey, n=120)",
],
},
{
"name": "Live, trustworthy pipeline",
"proof": [
"Pipeline updates in real time, not at week's end",
"Forecast accuracy within 8% across 40 design partners",
],
},
{
"name": "Enterprise-ready",
"proof": [
"SOC 2 Type II certified",
"SSO, SCIM, and role-based access control",
],
},
],
# Each channel lists which pillars it carries. Must be a SUBSET of pillars,
# never a pillar that doesn't exist in the house.
"channels": {
"website": ["Zero manual entry", "Live, trustworthy pipeline", "Enterprise-ready"],
"ads": ["Zero manual entry"],
"sales_deck": ["Zero manual entry", "Live, trustworthy pipeline", "Enterprise-ready"],
"social": ["Zero manual entry", "Live, trustworthy pipeline"],
},
}
# -----------------------------------------------------------------------------
SUPERLATIVES = re.compile(
r"\b(fastest|best|only|#1|number one|leading|world.?class|revolutionary|"
r"seamless|powerful|cutting.?edge|unmatched|ultimate)\b",
re.IGNORECASE,
)
CHECKABLE = re.compile(r"\d|SOC|SSO|SCIM|ISO|HIPAA|GDPR|%|hours?|x\b")
def lint(house):
errors, warnings = [], []
vp = house.get("value_prop", "").strip()
pillars = house.get("pillars", [])
names = [p["name"] for p in pillars]
# 1. Value proposition: one sentence, present, no double-promise.
if not vp:
errors.append("value_prop is empty.")
else:
sentences = [s for s in re.split(r"(?<=[.!?])\s+", vp) if s.strip()]
if len(sentences) > 1:
errors.append(f"value_prop is {len(sentences)} sentences; tighten to one.")
if ";" in vp:
warnings.append("value_prop uses ';' \u2014 likely two promises stapled together.")
# 2. Pillar count: 3 ideal, 2\u20134 allowed, else flag.
if not 2 <= len(pillars) <= 4:
errors.append(f"{len(pillars)} pillars; target 3 (2\u20134 only with cause).")
elif len(pillars) != 3:
warnings.append(f"{len(pillars)} pillars \u2014 3 is the sweet spot. Justify {len(pillars)}.")
if len(set(names)) != len(names):
errors.append("duplicate pillar names \u2014 each pillar must be distinct.")
# 3. Proof points: present, checkable, not bare superlatives.
for p in pillars:
proof = p.get("proof", [])
if not 2 <= len(proof) <= 4:
warnings.append(f"pillar '{p['name']}': {len(proof)} proof points (want 2\u20134).")
for pt in proof:
if SUPERLATIVES.search(pt) and not CHECKABLE.search(pt):
errors.append(f"un-checkable superlative under '{p['name']}': \"{pt}\"")
# 4. Channels: every carried pillar must exist in the house (no off-message).
for ch, carried in house.get("channels", {}).items():
for pillar in carried:
if pillar not in names:
errors.append(f"channel '{ch}' carries unknown pillar '{pillar}' (off-message).")
if not carried:
warnings.append(f"channel '{ch}' carries no pillars \u2014 it will say nothing.")
return errors, warnings
def main():
errors, warnings = lint(HOUSE)
for w in warnings:
print(f"WARN {w}")
for e in errors:
print(f"ERROR {e}")
if errors:
print(f"\n{len(errors)} error(s), {len(warnings)} warning(s). Fix errors before writing copy.")
sys.exit(1)
print(f"\nMessaging house is structurally sound ({len(warnings)} warning(s)). "
"Hand the one-pager to landing-page-copy.")
if __name__ == "__main__":
main()
Worked example output for the HOUSE above:
Messaging house is structurally sound (0 warning(s)). Hand the one-pager to landing-page-copy.
If you instead set the ads channel to a pillar that doesn't exist (e.g. "ads": ["Cheapest"])
and add a proof point like "The only real-time CRM", the linter prints:
ERROR un-checkable superlative under 'Live, trustworthy pipeline': "The only real-time CRM"
ERROR channel 'ads' carries unknown pillar 'Cheapest' (off-message).
2 error(s), 0 warning(s). Fix errors before writing copy.
Fill-in template - the one-page messaging house
Hand this completed page to [[landing-page-copy]] and [[sales-enablement-kit]] as
the single source of truth.
MESSAGING HOUSE - <Product>
Inputs (from positioning-statement):
Audience: <who, specifically>
Instead of: <the alternative they'd otherwise use>
Differentiator: <the one thing only you can claim>
Category: <the frame>
VALUE PROPOSITION (one sentence):
For <audience> who <need>, <product> is the <category> that
<single differentiated benefit> - unlike <alternative>.
PILLAR 1: <benefit the buyer feels>
- proof: <checkable evidence>
- proof: <checkable evidence>
PILLAR 2: <benefit the buyer feels>
- proof: <checkable evidence>
- proof: <checkable evidence>
PILLAR 3: <benefit the buyer feels>
- proof: <checkable evidence>
- proof: <checkable evidence>
PER-CHANNEL PROJECTION (same message, different length):
Website hero (<= 8 words): <value prop, compressed>
Website sections: <pillar 1> | <pillar 2> | <pillar 3>
Ad headline (<= 90 chars): <strongest single pillar>
Sales opener (1 line): <value prop in the rep's voice>
PLG / in-product nudge: <pillar most felt during activation>
Social one-liner: <value prop, conversational>
Deferrals:
Pricing language ......... see pricing-strategy / saas-pricing
Competitor framing ....... see competitive-intelligence
Overall GTM plan ......... see go-to-market-planner
Deliverable
A one-page messaging house: the inputs from [[positioning-statement]], a
one-sentence value proposition, three pillars each with 2-4 checkable proof
points, and a per-channel projection that keeps website, ads, sales, PLG, and
social on the same message in different lengths - linted for structural integrity
and ready to hand to [[landing-page-copy]] and [[sales-enablement-kit]].
1---2name: messaging-hierarchy-23description: Use when turning a positioning statement into actual copy - building the value proposition, message pillars, proof points, and per-channel messaging that keep the website, ads, and sales deck all saying the same thing. Triggers on "write our value proposition", "message pillars", "messaging framework", "messaging house", "key messages", "proof points", "our website and sales say different things", "per-channel messaging", "on-message copy". Takes the positioning-statement as input and feeds landing-page-copy. Do NOT use when you have not yet fixed positioning - use positioning-statement first. Do NOT use when you need the actual hero/landing page words - use landing-page-copy. Do NOT use to sequence launch phases - use launch-plan-sequencer; for the hour-by-hour go-live - use launch-day-runbook; for the sales deck/talk track - use sales-enablement-kit; for the in-product activation flow - use plg-motion-designer.4metadata:5 source: https://skillmd.com/skills/skillmedev/messaging-hierarchy-26 title: "Messaging Hierarchy"7---89# Messaging Hierarchy1011Positioning is the strategy; messaging is the words. Most teams skip the layer in12between and let every surface invent its own - so the website promises one thing,13the ads a second, and the sales deck a third, and the buyer never hears the same14story twice. This skill builds the **messaging hierarchy** (the "messaging15house"): one value proposition on top, three message pillars holding it up, proof16points under each pillar, and per-channel copy derived from - never inventing17beyond - that structure. Build it once, and every channel says the same thing in18its own register.1920This skill takes the output of [[positioning-statement]] as its input and produces21the brief that [[landing-page-copy]] turns into hero and page copy. It is the22spine of the [[launch-plan-sequencer]] and the source the [[sales-enablement-kit]],23[[plg-motion-designer]], and [[launch-day-runbook]] pull their language from - so24the same promise survives from the strategy doc to the go-live announcement.2526## When to use this skill2728Reach for it the moment positioning is fixed and you need words, and whenever29someone notices the website, ads, and sales aren't saying the same thing. If30positioning itself is still wobbly (you can't name the audience, the alternative,31or the one differentiator), stop and run [[positioning-statement]] first - a32messaging house on a cracked foundation just scales the confusion.3334## The hierarchy, top to bottom3536Everything below the value prop must *ladder up* to it. If a pillar doesn't37support the value prop, or a proof point doesn't support its pillar, cut it.38391. **Value proposition** - one sentence. The single promise to the single40 audience, in their words, that no chosen competitor can say as credibly.412. **Message pillars** - three (occasionally two or four) themes that *prove the42 promise is true*. Each is a reason-to-believe, not a feature. "Faster" is a43 pillar; "webhooks" is not.443. **Proof points** - under each pillar, the concrete, checkable evidence:45 metrics, capabilities, customer outcomes, integrations, certifications. This46 is where features finally appear - in service of a pillar.474. **Per-channel copy** - the same hierarchy expressed in each surface's voice48 and length budget: a 6-word hero, a 90-character ad, a one-line sales opener.4950## The ordered workflow5152Work top-down. Do not write a single ad until the value prop and pillars are set.53541. **Ingest positioning.** Pull the four load-bearing inputs from55 [[positioning-statement]]: target customer, the alternative they'd otherwise56 use (the "instead of"), the one differentiator, and the category frame. If any57 is missing, get it before proceeding.582. **Draft the value proposition.** One sentence: *for [audience] who [need],59 [product] is the [category] that [single differentiated benefit] - unlike60 [alternative].* Write it in the customer's language, not yours. Kill adjectives61 that any competitor could also claim ("powerful," "seamless," "intuitive").623. **Derive 3 message pillars.** Ask: "What three things must a skeptic believe63 for the value prop to be true?" Those are your pillars. Name each as a benefit64 the buyer feels, not a feature you ship. Three is the target - two is thin,65 five is a list nobody remembers.664. **Load proof points under each pillar.** 2-4 per pillar. Each must be67 *checkable* - a number, a named capability, a customer result, a logo, a68 compliance fact. If you can't substantiate it, it's a claim, not a proof point;69 cut it or go get the evidence.705. **Run the ladder-up test.** For every proof point ask "which pillar?" and for71 every pillar ask "does this prove the value prop?" Orphans get cut or72 re-homed. The house must be fully connected.736. **Project onto channels.** Express the *same* hierarchy per surface, longest to74 shortest: website (value prop = hero, pillars = section headers, proof points =75 body) → sales ([[sales-enablement-kit]]) → ads → product/PLG76 ([[plg-motion-designer]]) → social. Shorter channels carry fewer pillars, never77 different ones.787. **Write the one-page brief and hand off.** Emit the messaging house as a single79 page (see template) and hand it to [[landing-page-copy]] for the hero/landing80 words and to [[sales-enablement-kit]] for the deck and talk track.8182## Quality bar8384A messaging hierarchy is done when:8586- The **value proposition is one sentence** and survives being read aloud. No87 semicolons stapling two promises together.88- Every pillar is a **reason-to-believe the buyer cares about**, not a feature89 name, and there are **three** (two or four only with cause).90- **Every proof point is checkable** - a number, capability, outcome, or fact a91 buyer could verify. Nothing aspirational hiding as evidence.92- The house is **fully connected**: no orphan pillar that doesn't support the93 value prop, no orphan proof point that doesn't support a pillar.94- A teammate could **regenerate the hero, an ad, and a sales opener** from the95 one-pager alone and they'd all say the same thing in different lengths.96- It uses the **customer's words**, validated against real call transcripts /97 reviews / support tickets where possible - not internal jargon.98- It **reuses the existing GTM skills** rather than re-deriving them: pricing99 language defers to [[pricing-strategy]] / [[saas-pricing]], competitor framing100 to [[competitive-intelligence]], overall plan to [[go-to-market-planner]].101102## Do NOT103104- **Do NOT start here without positioning.** No fixed audience / alternative /105 differentiator means no value prop. Run [[positioning-statement]] first.106- **Do NOT write the landing page in this skill.** This produces the *framework107 and brief*; the actual hero/page words are [[landing-page-copy]]'s job. Stop at108 the one-pager.109- **Do NOT let pillars be feature lists.** "SSO, audit logs, SOC 2" is three110 proof points under one pillar ("Enterprise-ready"), not three pillars.111- **Do NOT ship un-evidenced superlatives.** "The fastest," "the only," "#1"112 without a checkable proof point is a liability, not a message.113- **Do NOT let channels diverge.** A different *length* per channel is correct; a114 different *message* per channel is the exact failure this skill exists to115 prevent.116- **Do NOT re-invent pricing, competitive, or plan content.** Cross-link to117 [[pricing-strategy]], [[saas-pricing]], [[competitive-intelligence]], and118 [[go-to-market-planner]] instead of duplicating them.119120## Runnable artifact - the consistency linter121122This self-contained Python script holds the messaging house as data and checks the123structure the eye misses: orphaned pillars/proof points, the wrong number of124pillars, channels that go off-message, and proof points that read as un-checkable125superlatives. Fill in `HOUSE`, run it, and fix what it flags before you write a126word of channel copy.127128```python129#!/usr/bin/env python3130"""messaging_lint.py - lint a messaging hierarchy for structural integrity.131Usage: python3 messaging_lint.py (edit HOUSE below first)132No dependencies. Pure stdlib.133"""134import re135import sys136137# ---- FILL THIS IN (from your positioning-statement output) ------------------138HOUSE = {139 "value_prop": (140 "For revenue teams drowning in CRM busywork, Pulse is the sales workspace "141 "that auto-logs every call and email \u2014 unlike Salesforce, no manual data entry."142 ),143 "pillars": [144 {145 "name": "Zero manual entry",146 "proof": [147 "Auto-captures calls, emails, and meetings into the CRM",148 "Reps save ~5 hours/week vs. manual logging (Q2 customer survey, n=120)",149 ],150 },151 {152 "name": "Live, trustworthy pipeline",153 "proof": [154 "Pipeline updates in real time, not at week's end",155 "Forecast accuracy within 8% across 40 design partners",156 ],157 },158 {159 "name": "Enterprise-ready",160 "proof": [161 "SOC 2 Type II certified",162 "SSO, SCIM, and role-based access control",163 ],164 },165 ],166 # Each channel lists which pillars it carries. Must be a SUBSET of pillars,167 # never a pillar that doesn't exist in the house.168 "channels": {169 "website": ["Zero manual entry", "Live, trustworthy pipeline", "Enterprise-ready"],170 "ads": ["Zero manual entry"],171 "sales_deck": ["Zero manual entry", "Live, trustworthy pipeline", "Enterprise-ready"],172 "social": ["Zero manual entry", "Live, trustworthy pipeline"],173 },174}175# -----------------------------------------------------------------------------176177SUPERLATIVES = re.compile(178 r"\b(fastest|best|only|#1|number one|leading|world.?class|revolutionary|"179 r"seamless|powerful|cutting.?edge|unmatched|ultimate)\b",180 re.IGNORECASE,181)182CHECKABLE = re.compile(r"\d|SOC|SSO|SCIM|ISO|HIPAA|GDPR|%|hours?|x\b")183184185def lint(house):186 errors, warnings = [], []187 vp = house.get("value_prop", "").strip()188 pillars = house.get("pillars", [])189 names = [p["name"] for p in pillars]190191 # 1. Value proposition: one sentence, present, no double-promise.192 if not vp:193 errors.append("value_prop is empty.")194 else:195 sentences = [s for s in re.split(r"(?<=[.!?])\s+", vp) if s.strip()]196 if len(sentences) > 1:197 errors.append(f"value_prop is {len(sentences)} sentences; tighten to one.")198 if ";" in vp:199 warnings.append("value_prop uses ';' \u2014 likely two promises stapled together.")200201 # 2. Pillar count: 3 ideal, 2\u20134 allowed, else flag.202 if not 2 <= len(pillars) <= 4:203 errors.append(f"{len(pillars)} pillars; target 3 (2\u20134 only with cause).")204 elif len(pillars) != 3:205 warnings.append(f"{len(pillars)} pillars \u2014 3 is the sweet spot. Justify {len(pillars)}.")206 if len(set(names)) != len(names):207 errors.append("duplicate pillar names \u2014 each pillar must be distinct.")208209 # 3. Proof points: present, checkable, not bare superlatives.210 for p in pillars:211 proof = p.get("proof", [])212 if not 2 <= len(proof) <= 4:213 warnings.append(f"pillar '{p['name']}': {len(proof)} proof points (want 2\u20134).")214 for pt in proof:215 if SUPERLATIVES.search(pt) and not CHECKABLE.search(pt):216 errors.append(f"un-checkable superlative under '{p['name']}': \"{pt}\"")217218 # 4. Channels: every carried pillar must exist in the house (no off-message).219 for ch, carried in house.get("channels", {}).items():220 for pillar in carried:221 if pillar not in names:222 errors.append(f"channel '{ch}' carries unknown pillar '{pillar}' (off-message).")223 if not carried:224 warnings.append(f"channel '{ch}' carries no pillars \u2014 it will say nothing.")225226 return errors, warnings227228229def main():230 errors, warnings = lint(HOUSE)231 for w in warnings:232 print(f"WARN {w}")233 for e in errors:234 print(f"ERROR {e}")235 if errors:236 print(f"\n{len(errors)} error(s), {len(warnings)} warning(s). Fix errors before writing copy.")237 sys.exit(1)238 print(f"\nMessaging house is structurally sound ({len(warnings)} warning(s)). "239 "Hand the one-pager to landing-page-copy.")240241242if __name__ == "__main__":243 main()244```245246Worked example output for the `HOUSE` above:247248```249Messaging house is structurally sound (0 warning(s)). Hand the one-pager to landing-page-copy.250```251252If you instead set the ads channel to a pillar that doesn't exist (e.g. `"ads": ["Cheapest"]`)253and add a proof point like `"The only real-time CRM"`, the linter prints:254255```256ERROR un-checkable superlative under 'Live, trustworthy pipeline': "The only real-time CRM"257ERROR channel 'ads' carries unknown pillar 'Cheapest' (off-message).2582592 error(s), 0 warning(s). Fix errors before writing copy.260```261262## Fill-in template - the one-page messaging house263264Hand this completed page to [[landing-page-copy]] and [[sales-enablement-kit]] as265the single source of truth.266267```268MESSAGING HOUSE - <Product>269Inputs (from positioning-statement):270 Audience: <who, specifically>271 Instead of: <the alternative they'd otherwise use>272 Differentiator: <the one thing only you can claim>273 Category: <the frame>274275VALUE PROPOSITION (one sentence):276 For <audience> who <need>, <product> is the <category> that277 <single differentiated benefit> - unlike <alternative>.278279PILLAR 1: <benefit the buyer feels>280 - proof: <checkable evidence>281 - proof: <checkable evidence>282PILLAR 2: <benefit the buyer feels>283 - proof: <checkable evidence>284 - proof: <checkable evidence>285PILLAR 3: <benefit the buyer feels>286 - proof: <checkable evidence>287 - proof: <checkable evidence>288289PER-CHANNEL PROJECTION (same message, different length):290 Website hero (<= 8 words): <value prop, compressed>291 Website sections: <pillar 1> | <pillar 2> | <pillar 3>292 Ad headline (<= 90 chars): <strongest single pillar>293 Sales opener (1 line): <value prop in the rep's voice>294 PLG / in-product nudge: <pillar most felt during activation>295 Social one-liner: <value prop, conversational>296297Deferrals:298 Pricing language ......... see pricing-strategy / saas-pricing299 Competitor framing ....... see competitive-intelligence300 Overall GTM plan ......... see go-to-market-planner301```302303## Deliverable304305A one-page messaging house: the inputs from [[positioning-statement]], a306one-sentence value proposition, three pillars each with 2-4 checkable proof307points, and a per-channel projection that keeps website, ads, sales, PLG, and308social on the same message in different lengths - linted for structural integrity309and ready to hand to [[landing-page-copy]] and [[sales-enablement-kit]].