Context
Use this to prevent random copywriting and enforce one narrative spine across touchpoints.
Procedure
- Define category context and the problem frame.
- Draft one-line value proposition with measurable promise.
- Add three supporting claims tied to concrete proof.
- Add objection counters and trust anchors.
- Map CTA logic (primary, secondary, fallback).
- Review for channel portability (web, email, paid, sales).
Output Format
# Messaging Hierarchy
## Level 1: Category Frame
- We help [ICP] solve [problem category].
## Level 2: Core Value Proposition
- [Primary promise + measurable result]
## Level 3: Supporting Claims
1. Claim:
Proof:
2. Claim:
Proof:
3. Claim:
Proof:
## Level 4: Trust + Objection Handling
- Objection:
Rebuttal:
- Trust Signals:
## Level 5: CTA Stack
- Primary CTA:
- Secondary CTA:
- Low-intent CTA:
QA Rubric (scored)
- Hierarchy integrity (0-5): each level has clear purpose.
- Proof alignment (0-5): every claim has evidence.
- Clarity and brevity (0-5): concise and non-jargon.
- Activation readiness (0-5): usable by design and growth teams.
Examples (good/bad)
- Good: “Cut time-to-insight by 40% with pre-modeled analytics workflows.”
- Bad: “The best platform for every business.”
Variants
- Enterprise variant: adds procurement and compliance language.
- SMB variant: highlights speed, implementation ease, and ROI clarity.