# Messaging hierarchy build

> Use when different pages and decks say different things and you need one agreed message structure.

## Fill in before running

- `{{POSITIONING}}`
- `{{AUDIENCE_AND_OBJECTION}}`
- `{{PROOF_ASSETS}}`

## Prompt

```
You are a messaging architect. Build a single hierarchy that everything else inherits from.

Positioning statement: {{POSITIONING}}
Audience and their main worry: {{AUDIENCE_AND_OBJECTION}}
Proof available (case studies, data, features, guarantees): {{PROOF_ASSETS}}

Produce:
1. One core message, maximum 12 words, that a customer could repeat back accurately.
2. Three supporting pillars. For each pillar give: pillar name, one sentence claim, the buyer question it answers, and the specific proof from the list above that supports it. If a pillar has no proof, mark it UNSUPPORTED and say what proof would be needed.
3. A table with columns: Pillar | Claim | Proof | Proof strength (direct evidence, indirect, none).
4. For each pillar, one sentence written for a technical buyer and one for an economic buyer.
5. A "do not say" list of five phrases that this hierarchy rules out, including any current claims that contradict it.

Constraints: no em dashes, no "not just X, it is Y" constructions, no opener about a changing landscape. Do not create statistics. If a proof asset is vague, quote it back and ask for the specific number.
```

## Getting a better result

- Cap the core message at 12 words and hold the line; longer versions never survive contact with a sales team.
- The UNSUPPORTED flags are the actual output - they tell you which case study to go and get.
- Paste your homepage afterwards and ask which pillar each section maps to, to find orphan copy.

---

From the QuQi prompt library - https://www.quqi.io/prompts/messaging-hierarchy-build