Best PromptsMessaging Hierarchy
Build the message architecture every asset works from: one core promise, three supporting pillars, proof under each, and audience variants.
Build a messaging hierarchy for [PRODUCT/COMPANY]. What we do, plainly: [NO JARGON] Who it is for and who it is not for: [SEGMENTS, AND THE ONES WE SHOULD TURN DOWN] The problem before us: [WHAT THEY DID INSTEAD, AND WHAT IT COST THEM] What is genuinely different about us: [NOT FEATURES, THE THING COMPETITORS CANNOT SAY] Proof we hold: [CUSTOMER RESULTS, NUMBERS, NAMES, CREDENTIALS, DEMOS] How competitors describe themselves: [THEIR CLAIMS] Produce: 1. **Core promise**: one sentence, under 15 words, saying what changes for the customer. It must fail the swap test: if a competitor's name fits in it unchanged, it is not a promise, it is a category description. Show the swap test result. 2. **Three pillars**: the three claims that support the promise. Each with a one-line statement, the customer belief it changes, and the reason to believe it drawn from my proof. 3. **Proof map**: under each pillar, the specific evidence available (result, number, story, demo, credential) and where it is strong or thin. Name the gaps directly; a pillar with no proof is a liability, not a message. 4. **Audience variants**: the promise and pillars rephrased for each segment I listed, in that segment's own vocabulary. Same substance, different words. Note which pillar leads for each segment. 5. **Words we use and words we avoid**: the vocabulary that is ours, the category words we have to use for findability, and the phrases to retire because everyone in the category says them. 6. **Elevator versions**: 10 words, 25 words, and 60 seconds spoken. Rules: every claim must be traceable to my proof. Where a pillar needs proof I did not supply, write [PROOF NEEDED: what would establish this]. Do not write a promise the product cannot keep today, even if it is on the roadmap.
How to use
The swap test in section 1 kills more bad messaging in ten seconds than a workshop does in a day: if your promise still reads correctly with a competitor's name in it, you have written a category definition. The proof map is the deliverable to take to leadership, because a pillar marked [PROOF NEEDED] is a specific request (get this case study, run this benchmark) rather than a vague call for more marketing.
More marketing prompts
Audit my visibility in AI answer engines and give me a fix list. Business: [WHAT YOU SELL, TO WHOM] Category terms people use: [e.g. "invoicing software for freelancers"] Competitors that get named instead of us: [LIST, or "unknown"] Pages to evaluate: """ [PASTE THE FULL TEXT OF 1-5 KEY PAGES: homepage, a product page, your best guide]
AI Search Visibility Audit
Audit whether ChatGPT, Perplexity, and AI Overviews can find, quote, and recommend you, then get a prioritized plan to fix what they cannot.
Audit my existing content and tell me what to refresh, merge, or retire. Page data (title, URL, target keyword, traffic now, traffic at peak, publish date, last update, conversions if known): """ [PASTE AS A TABLE OR LIST] """ Business goal this content serves: [e.g. "trial signups from mid-funnel guides"] For each page, assign one act
Content Refresh Audit
Decide which existing pages to update, merge, or delete based on decay and intent drift, with a specific change list for each keeper.
Write responsive search ad copy for this ad group. Product or service: [WHAT IT IS, WHO IT IS FOR] Ad group theme and keywords: [THE TIGHT KEYWORD SET THIS AD GROUP TARGETS] What the searcher is trying to do: [e.g. "compare options", "buy now", "fix an urgent problem"] Landing page: [WHAT THE PAGE ACTUALLY OFFERS AND WHAT THE PRIMARY ACT
Google Ads Copy
Write responsive search ad headlines and descriptions that match query intent, with pinning guidance and a matching landing page check.