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.

You get: Angle scoring table, recommendation with tradeoffs and positioning statement

More like this

The prompt

positioning-statement-and-messaging-hierarchy-for-a-product-launch.md
Role: You are a senior product marketing manager who writes positioning that sales, design, and demand gen teams can all use.

Context: I am preparing {brand}'s launch positioning for {product}, aimed at {audience}. The business goal is {goal}. The job to be done is to choose ONE positioning angle to approve for launch messaging. Your answer should support that decision.

Task: Build a positioning statement, a messaging hierarchy, and a proof map. Compare 3 candidate angles and recommend one.

Inputs (ask me for anything missing before drafting; if I say to proceed, list assumptions separately):
- Product description and key capabilities: {product_details}
- Target audience and their main problem: {audience_problem}
- Top competitors or alternatives (including doing nothing): {competitors}
- Available proof (customer quotes, data, certifications, case studies): {proof_points}
- Brand voice and banned claims: {brand_voice}
- Channels where messaging will appear: {channels}

Constraints:
- Use only facts I supply. Never invent statistics, customer names, awards, or guaranteed outcomes.
- Label every claim as Supported (proof given) or Needs proof.
- Keep language plain and free of jargon unless {audience} uses it.

Workflow:
1. Restate the audience, problem, and alternatives in 5 lines. List assumptions separately.
2. Draft 3 candidate positioning angles, each with a one-line rationale.
3. Score each angle (1-5) on relevance to audience, differentiation, provability, and fit with {goal}. Show a table.
4. Recommend one angle and explain the tradeoffs versus the other two.
5. Write the positioning statement: For [audience] who [need], {brand} is a [category] that [key benefit], unlike [alternative], because [reason to believe].
6. Build the messaging hierarchy: headline, subhead, 3 pillars, and 2 proof points per pillar.
7. Adapt the headline and subhead for each channel in {channels}.

Output format:
1. Assumptions and missing information (bullets)
2. Angle scoring table
3. Recommendation with tradeoffs
4. Positioning statement
5. Messaging hierarchy table (Pillar | Message | Proof | Claim status)
6. Channel adaptations
7. Risks and objections to expect
8. Next actions (owner role, task, what to validate)

Acceptance criteria:
- Exactly one recommended angle with a clear reason.
- Each pillar has proof or is flagged Needs proof.
- A reader outside marketing can explain the positioning back in two sentences.
- No unsupported claims.

Quality checks before you answer:
- Does every claim trace to my inputs?
- Is the differentiation versus {competitors} specific rather than generic?
- Are risks and open questions concrete?

Tool notes: In ChatGPT or Claude, use Markdown tables. If I paste documents, name which document supports each proof point. Ask clarifying questions first and wait for my reply when more than 2 critical inputs are missing.

Example output

AI-written example

1. Assumptions and missing information

  • Proceeding on supplied inputs. Audience: controllers at 50-200 person companies who close the books in spreadsheets. Alternatives: spreadsheets, an ERP close module, doing nothing.
  • Assumed: no customer has approved named attribution. Quotes run anonymous.
  • Missing: pricing and implementation time. Neither is claimed below.

2. Angle scoring (1-5)

AngleRelevanceDifferentiationProvabilityGoal fitTotal
A. Close faster524415
B. Audit-ready by default335314
C. Structure your close without an ERP project554519

3. Recommendation
Approve Angle C. It is the only angle that separates Tallybird from both spreadsheets and heavy ERP modules. Tradeoffs: A is easier to say but every rival claims speed. B is the best proven (SOC 2) but speaks to auditors more than to the controller who feels the pain.

4. Positioning statement
For controllers at 50-200 person companies who run month-end close in spreadsheets, Tallybird is a close-management tool that gives your team a clear, trackable close without an ERP project, unlike spreadsheets or ERP close modules, because beta teams cut their median close from 9 to 6 days.

5. Messaging hierarchy
Headline: A month-end close you can actually track.
Subhead: Replace the spreadsheet, skip the ERP project.

PillarMessageProofClaim status
Clear ownershipEvery task has an owner and a due date.12-team beta; quote: "I stopped chasing people in Slack."Supported
Faster closeTeams close sooner.Median 9 → 6 days in beta (n=12); no guarantee statedSupported (beta only)
Audit-readyReviewers see who did what.SOC 2 Type II report; activity log featureSupported

6. Channel adaptations

  • LinkedIn ad: "Still closing in spreadsheets? Track every task in one place. No ERP project."
  • Landing page: Headline and subhead as above, with the beta result under the fold.
  • Sales email: Subject "Your close, minus the chasing." Opening line: "Beta teams cut median close from 9 to 6 days."

7. Risks and objections

  • "Twelve teams is small." Always say "in our beta" and give the sample size.
  • "Will it replace my ERP?" Define it as a layer beside the ERP, not a replacement. Needs proof of
Generated from this prompt by AI. Your results will vary.

Tips and common edits

Paste real product docs and customer evidence for the best results. Validate the recommended angle with 3 to 5 customer or sales conversations before final approval. Treat Needs proof items as blockers for public copy.

Questions about this prompt

More in Marketing

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.

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.

Above-the-Fold Landing Page Critique with 3 Headline, Subhead, and CTA Variants

Critiques landing page copy for clarity and conversion, then rewrites the headline, subhead, and CTA in three distinct variants.

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.

LinkedIn Post from a Work Lesson, No Engagement Bait

Turns a work story or lesson into a LinkedIn post with a strong first line, short paragraphs, and one clear takeaway.

Turns pasted links and notes into a newsletter issue with a hooking intro, three takeaway sections, and one call to action.

Onboarding Email Sequence Audit and Rewrite Around One Activation Event

Audits an existing or planned onboarding email flow, then rewrites it around a single activation event with segmentation, timing, copy, and a measurement plan.

Repurpose One Article into 10 Native Posts Across Four Channels

Turns one blog post or article into 10 channel-native pieces for LinkedIn, X, Instagram carousel, and newsletter.

SEO-Friendly Etsy or Gumroad Listing with 13 Tags and FAQ

Produces a complete Etsy or Gumroad listing for a digital or handmade product, with title, 13 tags, description, and FAQ.

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.

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.

60-Second Product Explainer Script and Shot List

Turns a product brief into a timed explainer script, shot list, and production checklist so a team can decide whether to greenlight, revise, or shoot the video.