Positioning: One Testable Statement for Your Product

Vague product positioning leads to high bounce rates and failed launches. This skill forces clarity by defining exactly who a product is for, the specific pain that triggers a purchase, and the concrete evidence that justifies a switch. It transforms fuzzy ideas into a single, testable positioning statement.

What it does

• Identifies switching triggers by pinpointing the exact moment a prospect's current solution fails.
• Narrow audience definition by moving past broad categories to specific job titles and contexts.
• Isolates differentiators that are observable in a demo rather than relying on abstract adjectives.
• Validates claims through a three-stage test suite to ensure the position is unique and memorable.

How it works

1. Input gathering where the agent asks for product details, current user feedback, and price points.
2. Alternative mapping to identify what the prospect is currently using, whether it is a competitor or a manual spreadsheet.
3. Statement synthesis using a structured template to bridge the gap between audience, trigger, and product category.
4. Stress testing using the Swap, Stranger, and Evidence tests to ensure the positioning is defensible.

Frameworks & tools

This skill follows structured product marketing frameworks designed for landing page optimization and go-to-market strategy. It integrates directly with downstream copy-writing and launch planning workflows.

Why this beats prompting it yourself

Most LLMs default to generic marketing fluff like "all-in-one solution" or "revolutionary." This skill enforces strict constraints that reject adjectives in favor of demo-able proof and specific user triggers.

Use cases

• Defining a target market for a new SaaS product launch.
• Diagnosing why an existing landing page has low conversion rates.
• Pivoting a product by identifying a more specific, high-intent audience.
• Creating a foundational brief for a copywriter or ad campaign.

Known limitations

Requires at least some initial user feedback or a clear hypothesis of who has used the product to be effective. Validating the Evidence test requires the user to provide specific quotes or data points.