Messaging Hierarchy — B2B SaaS

Variables to fill in: {{product_reality}}{{market_context}}{{business_goal}}

You are a positioning strategist who makes brands the obvious choice for the right customer. I need your help in the context of a B2B SaaS company marketing to a defined buyer persona with a long consideration cycle.

TASK: Build the message house the whole team can write from.

DELIVERABLE: Produce a messaging hierarchy: core promise, three pillars each with proof points and example copy, audience-specific variations, and banned-phrases list.

PROCESS:
1. Review the inputs below. If anything critical is missing or ambiguous, ask me up to three clarifying questions before producing the deliverable.
2. Extract from the inputs what the product truly does best and for whom — positioning built on wishes collapses.
3. Define the alternative: what customers would do without you is the frame that gives claims meaning.
4. Choose one position and pay its cost: what you will NOT claim, serve, or be.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- Positioning statements a competitor couldn't copy-paste onto their own site.
- Language a real customer would use, not category buzzwords.
- Every claim is paired with its proof.

INPUTS:
- What the product does, who loves it today, and why they say they love it: {{product_reality}}
- Competitors/alternatives and how the category talks: {{market_context}}
- Where the business wants to win next: {{business_goal}}

Run this prompt on a real model without leaving the page. Every run is saved to your history for this prompt.

How to use

1. 1Fill in the {{product_reality}}, {{market_context}}, {{business_goal}} variables with your real details — specifics in, specifics out.
2. 2Paste the prompt into ChatGPT, Claude, Gemini, or any capable model.
3. 3Answer the clarifying questions it asks; that step is what makes the output fit your situation.
4. 4Iterate on the deliverable: ask for alternatives, tighter versions, or a different angle on any section.

Pro tips

• If the output feels generic, add more concrete detail to the inputs — names, numbers, and constraints sharpen everything.
• Works well in a thread: keep the conversation going to refine a messaging hierarchy.