القائمة
Create sharp B2B positioning and messaging from customer truth, segmentation choices, real alternatives, differentiated value, and proof.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against [competitor]", or "how do we beat [competitor]".
Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation. Produces TAM analysis, firmographic segments, champion and economic buyer personas, use case mapping, customer proof points, and voice-of-customer synthesis with normalized attributes. Requires website URL as primary input. Upstream: recommended company-context. Downstream: feeds positioning, product-messaging, landing-page-copy, content-strategy, and outreach-emails.
Classify product launches into defensible tiers and turn roadmap inputs into a season-of-launch plan that aligns Product, Campaigns, PR/AR, Sales, and customer-facing teams.
Turn customer notes, call transcripts, sales feedback, and research into PMM-ready voice-of-customer inputs: pains, triggers, status quo, JTBD, exact language, objections, proof, and messaging implications.
Win/loss analysis for B2B SaaS. Analyzes sales call transcripts across 6 dimensions (product, messaging, GTM/sales, pricing, competition, customer context) to extract why deals are won, lost, retained, or churned. Produces aggregate patterns with verbatim-quote evidence, frequency counts, confidence levels, and strategic recommendations. Includes process steps, output template, quality checklist, extraction patterns, and a worked 5-transcript example.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
| name | positioning-messaging-framework |
| description | Create sharp B2B positioning and messaging from customer truth, segmentation choices, real alternatives, differentiated value, and proof. |
Use this skill when you need to turn product, customer, market, or voice-of-customer inputs into a usable B2B positioning and messaging framework.
Use it for:
Do not use it to produce generic copy before the strategic choices are clear. Positioning comes first. Messaging turns that positioning into everyday English. Copywriting is the clear wording that gets the message across.
Ask for or infer these inputs. If an input is missing, state the assumption and mark confidence as low.
Define the narrowest useful target:
Push back when the segment is too broad. "B2B companies," "revenue teams," or "enterprises" is usually not enough.
Identify what the customer would do if this product did not exist:
The real alternative is often the status quo, not the named competitor.
Separate:
Translate feature problems into business problems. Do not stop at workflow annoyance if the real issue is missed revenue, risk, downtime, churn, delay, or lost trust.
Connect capabilities to outcomes:
Avoid claiming "faster," "easier," or "smarter" unless you can say faster than what, easier for whom, and smarter because of what.
Use this template, then tighten it:
For [people/role/attribute] at [company attributes], who want [economic goal] while [qualitative goal], [Company] is [superlative/product] that lets you [business improvement] so you can [economic goal]. Unlike [alternative/status quo/vendor class] that [causes problem] because [flaw], [Company] helps you [differentiated goal] with [differentiated capability/model] so you can [specific business goal] and [emotional outcome].
The final version should be specific, credible, and plain-spoken. It does not need to be ad copy.
Create exactly 3 messaging pillars that express the position in buyer language.
The 3 pillars must be unique and differentiated. Each pillar should make a distinct strategic point, not restate the same value in different words. If two pillars would appear together on a homepage and feel interchangeable, merge or rewrite them.
Use this split unless the evidence strongly suggests another structure:
For each pillar, include:
Messages should be useful in sales conversations, website sections, launch copy, and enablement.
Run the output through the pressure tests below. If it fails, revise before finalizing.
Produce the framework in this structure:
Executive summary
Target segment and persona
Real alternative
Pains, consequences, and JTBD
Differentiated value
Positioning statement
Messaging pillars
Reasons to believe
Plain-English copy direction
Pressure-test notes
A strong output:
Before finalizing, check:
Avoid:
