Positioning and Messaging Hierarchy Builder from Competitor and Customer Evidence

Turns your product facts, customer evidence, and competitor notes into a tested positioning statement, messaging hierarchy, and proof-gap list so a marketing team can decide what to say and what to validate first.

You get: A strategy you can act on

More like this

The prompt

positioning-and-messaging-hierarchy-builder-from-competitor-and-customer-evidence.md
ROLE: You are a senior product marketing strategist who builds positioning for {brand} using only the evidence supplied and clearly labeled assumptions. CONTEXT: The team must decide which positioning angle to commit to for {launch_or_campaign} aimed at {audience}. The job-to-be-done is to choose one primary positioning angle and a messaging hierarchy that sales, content, and paid teams can use consistently. TASK: Analyze the inputs, compare candidate positioning angles, recommend one, and show what evidence supports or weakens it. CONSTRAINTS: Do not invent customer quotes, statistics, competitor claims, or results. Do not claim you browsed the web or checked live competitor pages. If evidence is missing, mark it as an assumption or a gap. Avoid generic claims such as best-in-class or all-in-one unless the inputs prove them. TOOL INSTRUCTIONS FOR CHATGPT: First ask up to 8 clarifying questions in a numbered list if any required input is missing, then wait. If the user pastes long documents, summarize each in 5 bullets before analysis. Use markdown tables for comparisons. Keep a running Assumptions list separate from Facts. If the user wants a revision, change only the affected sections and say what changed. Inputs: 1) Product or service description: {product_description}. 2) Target audience and buying context: {audience}. 3) Primary competitors or alternatives, including doing nothing: {competitors}. 4) Customer evidence such as interview notes, reviews, win-loss notes, or support themes: {customer_evidence}. 5) Proof assets available such as case studies, data, certifications, or demos: {proof_assets}. 6) Business goal and success metric: {goal}. 7) Brand voice constraints and legal or compliance limits: {constraints}. Workflow: Step 1, Input check: list what was provided, what is missing, and which missing items block a confident recommendation. Step 2, Facts versus assumptions: build two lists. Step 3, Customer problem map: extract the top 3 problems, the trigger events, and the current workaround for each. Step 4, Competitive frame: build a table of each alternative with its likely promise, its weakness as supported by the inputs, and the opening for {brand}. Step 5, Candidate angles: propose 3 distinct positioning angles, each with a one-sentence statement, the target segment, the differentiator, and the proof required. Step 6, Scoring: score each angle 1 to 5 on customer pain relevance, differentiation, proof strength, sales usability, and risk, showing a one-line rationale per score. Step 7, Recommendation: choose one angle and explain the decision and tradeoffs. Step 8, Messaging hierarchy: write the positioning statement, a one-line value proposition, 3 supporting message pillars with proof points, objection responses, and a list of words and claims to avoid. Step 9, Validation plan: define 3 low-cost tests such as landing page headline test, sales call script test, or customer interview check, each with a metric, a sample size note, and a decision rule. Output format: Use these headings in order: Input Check, Facts and Assumptions, Customer Problem Map, Competitive Frame Table, Candidate Angles, Scoring Table, Recommendation, Messaging Hierarchy, Proof Gaps and Risks, Validation Plan, Next 5 Actions with owner role and timeframe. Acceptance criteria: The recommendation names one angle and one primary audience segment. Every message pillar maps to a proof point or is flagged as unproven. The scoring table is consistent with the recommendation. Assumptions are never presented as facts. The validation plan has a measurable metric and a decision rule for each test. Quality checks: Before finalizing, verify that no statistic or quote appears that was not in the inputs, that competitor statements are labeled as supplied by the user, that the messaging is specific enough that a competitor could not say the same sentence, and that missing information is listed with who can supply it. End with a confidence rating of low, medium, or high and one sentence explaining it.

Example output

AI-written example

Input Check

Provided: product description, audience (finance leads at 20–100 person creative agencies), 3 alternatives, 6 interview summaries, 1 published case study, goal (40 demo requests in 60 days). Missing: win-loss notes, pricing (Sales). Neither blocks a recommendation.

Facts and Assumptions

Facts (user-supplied): Ledgerlane matches bank transactions to invoices and flags exceptions. 5 of 6 interviewees described month-end reconciliation as manual spreadsheet work. The case study covers a 35-person agency.
Assumptions: Finance leads, not owners, hold the budget. Exception flagging is the feature buyers value most.

Customer Problem Map

ProblemTriggerWorkaround
Close drags past the first weekMonth-endSpreadsheets
Unmatched payments get lostClient pays late or partiallyEmail chasing
Owner questions can't be answered fastBoard or lender reviewManual reports

Competitive Frame Table

AlternativePromise (per user)Weakness (per inputs)Opening
SpreadsheetsFree, flexibleManual, error-proneException-first matching
Suite vendor AFull accounting suiteReconciliation described as an add-onSpecialist depth
Do nothingNo change costClose delays persistCost of delay

Candidate Angles

  • A. Close faster: Reconcile in hours, not days. Proof needed: timing data.
  • B. Exceptions-first: Only review what doesn't match. Proof: demo and case study.
  • C. Audit-ready trail: Every match is traceable. Proof: compliance review.

Scoring Table

AnglePainDiff.ProofSales useRisk (5 = low)Total
A5224215
B4444420
C2313211

Rationales: A is crowded and rests on an unproven speed claim. B is demoable and backed by interviews.

Recommendation

Angle B, for finance leads at 20–100 person agencies. Tradeoff: it gives up the stronger "speed" headline until timing data exists.

Messaging Hierarchy

Positioning: For agency finance leads who lose days to spreadsheet reconciliation, Ledgerlane shows only the transactions that don't match, so month-end review starts with exceptions.
Value proposition: Stop checking what already matches.
Pillars:

  1. Matching runs automatically. Proof: live demo.
  2. Exceptions
Generated from this prompt by AI. Your results will vary.

Tips and common edits

Paste real interview notes, win-loss summaries, and competitor positioning text for best results. Treat competitor information as only as current as what you supply. Run the validation plan before rolling the positioning out across all channels.

Questions about this prompt

More in AI Marketing

Positioning Statement and Messaging Hierarchy for a Product Launch

Turns product facts, audience insight, and competitor context into a positioning statement, messaging hierarchy, and proof map so a team can approve one launch angle.

90-Day Lifecycle Marketing Diagnostic and Experiment Roadmap for Onboarding and Retention

Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.

Customer Review Mining: Personas, Jobs-to-Be-Done, Objections and Verbatim Copy Phrases

Turns pasted customer reviews into evidence-based personas, jobs-to-be-done, objections and a bank of exact customer phrases ready to reuse in copy.

Five-Angle Meta and Google Ad Copy Generator with Character Counts and A/B Test Plan

Produces Meta and Google ad copy across five distinct angles within platform character limits, plus a simple test plan with decision rules.

One-Page Brand Voice Brief Builder from Copy Samples for ChatGPT, Claude and Gemini

Analyzes your brand copy samples and builds a reusable one-page voice brief with tone rules, banned words, example rewrites and a paste-ready instruction block.

Competitor Homepage vs Your Positioning: Overlap, White Space, and a Sharper Line

Compares competitor homepage copy with your positioning to map overlap, find unclaimed angles, and propose one sharper differentiating line.

Competitor Landscape Scan with Source-Backed Citation Table

Runs a structured competitor scan that starts with search queries, ranks sources by reliability, and ends with a cited comparison table and a positioning recommendation.

4-Week Small Business Launch Plan: $0 and Small-Budget Versions

Builds a 4-week launch plan for a product or service in a specific market, with channels and weekly tasks in a $0 version and a small-budget version.

Business Idea Validation Sprint with a $100 Two-Week Test

Turn a business idea and target customer into a ranked list of risky assumptions, five interview questions and a $100 test to run in two weeks.

Competitor and Audience Evidence Review with Citation Table and Go/No-Go Brief

A research workflow that plans online source discovery, scores evidence, builds a citation table, and ends with a decision brief, without pretending live browsing happened.

Competitor Landscape Research Plan with Source Discovery and Citation Table

Builds a source discovery plan, evidence review, citation table, and decision-ready synthesis for a competitor or market question, without pretending live browsing occurred.

Competitor UX Pattern Research Plan with Evidence Table and Design Recommendation

Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.