Positioning
Find the strongest credible contrast between a product and its alternatives. The output should help social content, landing pages, sales notes, and launch campaigns without sounding petty or inflated.
Inputs
- product being positioned
- target customer
- competitors or alternatives
- category frame
- current positioning
- proof points
- known weaknesses or constraints
- claims that must be avoided
If competitor data may be current or factual, verify it with primary sources or ask for source material. Do not invent pricing, feature support, customer counts, integrations, security claims, or roadmap details.
Positioning Lenses
- workflow: what users must do manually
- speed: time-to-value and operational overhead
- control: review, approval, governance, safety
- channel fit: native posting vs generic publishing
- audience: who each product is really built for
- integration: where the tool sits in the user's stack
- taste: quality of output, not just quantity
- risk: compliance, brand safety, missed context
Workflow
Build the landscape:
direct competitors, adjacent tools, status quo alternatives, and "do nothing".
Create a comparison matrix:
audience, primary job-to-be-done, strengths, tradeoffs, credible contrast, and proof needed.
Identify the wedge:
underserved audience, workflow gap, market change, new behavior, or category assumption worth challenging.
Write positioning angles:
one category sentence, three contrast statements, three campaign angles, three "not for you if..." boundaries, and three proof assets to collect.
Convert into social campaign material:
X thread angle, LinkedIn founder post angle, short-form video angle, alternative-page headline, and objection-handling post.
Taste Rules
- Critique workflows, not people.
- Prefer "built for X, unlike tools optimized for Y" over "we are better than Y."
- Name competitors only when the comparison is factual, useful, and defensible.
- Strong positioning includes tradeoffs. Say who the product is not for.
- Never fabricate competitor limitations. Mark uncertain claims as "needs verification."
Output Format
## Landscape
| Alternative | Best for | Strength | Tradeoff | Verification Needed |
| --- | --- | --- | --- | --- |
## Positioning Wedge
[one paragraph]
## Messaging
- Category sentence:
- Contrast statement 1:
- Contrast statement 2:
- Contrast statement 3:
- Not for you if:
## Social Campaign Angles
1. [angle]
Platform fit:
Proof needed:
## Claims To Verify
- [claim]
AgentReacher Notes
Optimized for AI startups, SaaS founders, agentic tooling, and social automation products like AgentReacher. It works best when used before campaign generation so the content calendar is built around a clear wedge instead of generic feature announcements.
Example usage in AgentReacher: "Position AgentReacher against Buffer, Hootsuite, and Postiz for AI founders who want agents to schedule posts directly from their workflow."
1---2name: positioning3description: Analyze competing products and turn the market gap into credible positioning, messaging angles, and social campaign claims. Use when comparing competitors, writing alternative pages, sharpening product positioning, or planning campaigns against a category narrative.4---56# Positioning78Find the strongest credible contrast between a product and its alternatives. The output should help social content, landing pages, sales notes, and launch campaigns without sounding petty or inflated.910## Inputs1112- product being positioned13- target customer14- competitors or alternatives15- category frame16- current positioning17- proof points18- known weaknesses or constraints19- claims that must be avoided2021If competitor data may be current or factual, verify it with primary sources or ask for source material. Do not invent pricing, feature support, customer counts, integrations, security claims, or roadmap details.2223## Positioning Lenses2425- workflow: what users must do manually26- speed: time-to-value and operational overhead27- control: review, approval, governance, safety28- channel fit: native posting vs generic publishing29- audience: who each product is really built for30- integration: where the tool sits in the user's stack31- taste: quality of output, not just quantity32- risk: compliance, brand safety, missed context3334## Workflow35361. Build the landscape:37 direct competitors, adjacent tools, status quo alternatives, and "do nothing".38392. Create a comparison matrix:40 audience, primary job-to-be-done, strengths, tradeoffs, credible contrast, and proof needed.41423. Identify the wedge:43 underserved audience, workflow gap, market change, new behavior, or category assumption worth challenging.44454. Write positioning angles:46 one category sentence, three contrast statements, three campaign angles, three "not for you if..." boundaries, and three proof assets to collect.47485. Convert into social campaign material:49 X thread angle, LinkedIn founder post angle, short-form video angle, alternative-page headline, and objection-handling post.5051## Taste Rules5253- Critique workflows, not people.54- Prefer "built for X, unlike tools optimized for Y" over "we are better than Y."55- Name competitors only when the comparison is factual, useful, and defensible.56- Strong positioning includes tradeoffs. Say who the product is not for.57- Never fabricate competitor limitations. Mark uncertain claims as "needs verification."5859## Output Format6061```md62## Landscape63| Alternative | Best for | Strength | Tradeoff | Verification Needed |64| --- | --- | --- | --- | --- |65## Positioning Wedge66[one paragraph]67## Messaging68- Category sentence:69- Contrast statement 1:70- Contrast statement 2:71- Contrast statement 3:72- Not for you if:73## Social Campaign Angles741. [angle]75 Platform fit:76 Proof needed:77## Claims To Verify78- [claim]79```8081## AgentReacher Notes8283Optimized for AI startups, SaaS founders, agentic tooling, and social automation products like AgentReacher. It works best when used before campaign generation so the content calendar is built around a clear wedge instead of generic feature announcements.8485Example usage in AgentReacher: "Position AgentReacher against Buffer, Hootsuite, and Postiz for AI founders who want agents to schedule posts directly from their workflow."
agentreacher