0
Positioning statement from raw product facts
⁂auto-checked, 4 days oldAauraNovice
The prompt
Help me write a sharp positioning statement for product_name, not generic marketing fluff. I'll give you raw facts, you find the actual angle.
What it does (plainly, no marketing language): plain_description
Who currently buys it: current_customer_profile
What they use instead today (competitors or workarounds): alternatives
The honest tradeoff we ask customers to accept (nothing is perfect, name the real one): honest_tradeoff
Do this:
1. Identify the category we're actually competing in from the customer's mental model, not our internal one (customers don't categorize the way founders do).
2. Find the one dimension where we're genuinely, defensibly different from the alternatives, not a vague 'better/faster/easier' claim, an actual specific difference.
3. Write the positioning statement using the classic 'For [target], who [need], [product] is a [category] that [key benefit]. Unlike [alternative], we [differentiator].' format, but make every blank specific, not templated language.
4. Stress-test it: what's the strongest objection a skeptical prospect would raise against this positioning, and does the statement survive it?
5. Give me 2 alternate versions emphasizing different angles, in case the first isn't right, and tell me which you'd bet on and why.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 4 days ago |
Example output
Category (customer mental model): not 'project management software' as internally framed, but 'the thing ops leads use to stop chasing status updates in Slack,' a narrower, sharper category. Genuine differentiator: not speed or UI, but that it auto-generates the status update from actual work activity rather than requiring manual input, a structural difference competitors can't easily copy without rearchitecting. Positioning statement: 'For ops leads drowning in status-update requests, who need visibility without more meetings, [Product] is a project tracker that writes its own updates from real work signals. Unlike Asana or Monday, we don't ask anyone to fill out a form.' Stress-test objection: 'how accurate can auto-generated updates really be,' statement survives if backed by a concrete accuracy claim in follow-up copy. Two alternates provided emphasizing 'time saved' and 'trust in data' angles; recommend the auto-generation angle as primary, it's the most defensible and least copyable.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.