What This Template Is For
Most product teams can name their top three competitors but struggle to articulate exactly why a customer should choose them instead. Competitive positioning is not about feature comparison tables. It is about defining the specific context in which your product wins, and making sure every team (sales, marketing, product) tells the same story.
This template helps you build a structured competitive positioning document. You will map the competitive field, identify the axes of differentiation that matter to your buyers, craft positioning statements, and plan responses to competitive threats. The output is a living document your sales and marketing teams can reference daily.
The Product Strategy Handbook covers how positioning fits into broader product strategy, including market segmentation and value creation. If you need to quantify your addressable market at different positioning angles, the TAM Calculator helps size each segment. For teams evaluating whether to compete on price or value, the pricing strategy glossary entry covers the fundamentals. The RICE framework is useful for prioritizing which competitive gaps to close first.
When to Use This Template
- Before a product launch. Define your positioning before the market defines it for you.
- When entering a crowded market. Identify the specific wedge where you can win against established players.
- After losing deals to competitors. Document why you are losing and build a plan to address it.
- When competitors launch features that overlap with yours. Decide whether to respond, differentiate, or ignore.
- During annual strategy planning. Refresh your competitive map and validate that your positioning still holds.
- When sales asks for battlecards. This template feeds directly into sales enablement materials.
How to Use This Template
Step 1: Map the Competitive Field
List every competitor your buyers mention during the sales process. Include direct competitors (same category) and indirect competitors (different category, same job-to-be-done). Do not include companies you wish were competitors. Only include products your actual buyers evaluate.
Step 2: Identify Differentiation Axes
Determine the 2-3 dimensions that matter most to your target buyer. These are not feature lists. They are the decision criteria buyers use to choose between options. Common axes: speed of implementation, price, depth of analytics, ease of use, enterprise readiness, vertical specialization.
Step 3: Plot Competitive Positions
Place each competitor on a 2x2 matrix using your top two differentiation axes. This visual map shows where the market is crowded and where whitespace exists.
Step 4: Craft Your Positioning Statement
Write a one-sentence positioning statement following the format: For [target customer] who [need], [product] is the [category] that [key differentiator] unlike [primary alternative] which [limitation].
Step 5: Build Competitive Response Plans
For each top competitor, document your win strategy (when you win against them and why), your lose scenario (when they win and why), and your response plan for their likely next moves.
The Template
Competitive Landscape Map
| Competitor | Category | Primary Buyer | Price Range | Key Strength | Key Weakness |
|---|---|---|---|---|---|
| [Competitor 1] | [Direct / Indirect] | [Persona] | $[Range]/mo | [Strength] | [Weakness] |
| [Competitor 2] | [Direct / Indirect] | [Persona] | $[Range]/mo | [Strength] | [Weakness] |
| [Competitor 3] | [Direct / Indirect] | [Persona] | $[Range]/mo | [Strength] | [Weakness] |
| [Competitor 4] | [Direct / Indirect] | [Persona] | $[Range]/mo | [Strength] | [Weakness] |
| [Competitor 5] | [Direct / Indirect] | [Persona] | $[Range]/mo | [Strength] | [Weakness] |
| Your Product | [Category] | [Persona] | $[Range]/mo | [Strength] | [Weakness] |
Differentiation Axes
| Axis | Definition | Why Buyers Care | Your Position (1-10) |
|---|---|---|---|
| [Axis 1: e.g., Ease of Use] | [How you measure it] | [Buyer pain it addresses] | [Score] |
| [Axis 2: e.g., Enterprise Readiness] | [How you measure it] | [Buyer pain it addresses] | [Score] |
| [Axis 3: e.g., Time to Value] | [How you measure it] | [Buyer pain it addresses] | [Score] |
2x2 Positioning Matrix.
| High [Axis 1] | Low [Axis 1] | |
|---|---|---|
| High [Axis 2] | [Competitors in this quadrant] | [Competitors in this quadrant] |
| Low [Axis 2] | [Competitors in this quadrant] | [Competitors in this quadrant] |
Your target quadrant. [Which quadrant you occupy and why it is the right one for your buyer]
Positioning Statement
For [target customer with specific context]
who [primary need or job-to-be-done]
our product is the [category frame]
that [primary differentiator with proof point]
unlike [primary competitor or alternative]
which [their key limitation relative to your strength]
Supporting proof points.
- [Proof point 1: metric, case study, or customer quote]
- [Proof point 2]
- [Proof point 3]
Competitive Response Plans
Competitor 1: [Name]
| Dimension | Details |
|---|---|
| When we win | [Scenario: buyer profile, deal size, evaluation criteria where you excel] |
| When we lose | [Scenario: buyer profile, deal size, criteria where they excel] |
| Their likely next move | [Product roadmap signal, hiring patterns, funding, partnerships] |
| Our response | [What we will do: build, partner, position around, or ignore] |
| Key talking points for sales | [2-3 sentences sales should say when this competitor comes up] |
Competitor 2: [Name]
| Dimension | Details |
|---|---|
| When we win | [Scenario] |
| When we lose | [Scenario] |
| Their likely next move | [Signal] |
| Our response | [Action] |
| Key talking points for sales | [Talking points] |
Competitor 3: [Name]
| Dimension | Details |
|---|---|
| When we win | [Scenario] |
| When we lose | [Scenario] |
| Their likely next move | [Signal] |
| Our response | [Action] |
| Key talking points for sales | [Talking points] |
Win/Loss Summary
| Metric | Current | Target (90 days) |
|---|---|---|
| Overall win rate | [X]% | [X]% |
| Win rate vs [Competitor 1] | [X]% | [X]% |
| Win rate vs [Competitor 2] | [X]% | [X]% |
| Top reason we win | [Reason] | - |
| Top reason we lose | [Reason] | [Plan to address] |
| Average deal cycle vs competitor deals | [X] days | [X] days |
Filled Example: B2B Project Management Tool
Competitive Landscape Map
| Competitor | Category | Primary Buyer | Price Range | Key Strength | Key Weakness |
|---|---|---|---|---|---|
| Asana | Direct | VP Ops / PM Lead | $11-31/user/mo | Workflow automation | Complex setup for small teams |
| Monday.com | Direct | Ops Manager | $9-24/user/mo | Visual flexibility | Weak dev integrations |
| Linear | Direct | Engineering Lead | $8-14/user/mo | Developer experience | Limited non-eng use cases |
| Notion | Indirect | Head of Product | $10-18/user/mo | All-in-one workspace | Weak project tracking |
| Spreadsheets | Indirect | Everyone | Free-$12/user/mo | Familiar, flexible | No workflow automation |
| TaskFlow | Direct | Product Manager | $12-22/user/mo | PM-specific workflows | Newer, smaller ecosystem |
Differentiation Axes
| Axis | Definition | Why Buyers Care | TaskFlow Position (1-10) |
|---|---|---|---|
| PM Workflow Depth | Native support for roadmaps, prioritization, stakeholder updates | PMs waste hours adapting generic tools | 9 |
| Time to Value | Days from signup to team adoption | Buyers abandon tools that take months to configure | 8 |
| Cross-Functional Fit | Works for eng, design, and business teams | PMs need one tool the whole team uses | 6 |
Positioning Statement
For product managers at Series A-C SaaS companies
who spend more time managing tools than managing products
TaskFlow is the project management platform
that ships with PM workflows built in (roadmaps, RICE scoring, stakeholder reports) so teams are productive in days, not months
unlike Asana and Monday.com
which require extensive configuration and custom fields to support PM-specific workflows.
Competitive Response Plan: Asana
| Dimension | Details |
|---|---|
| When we win | Mid-market SaaS (50-300 employees), PM-led evaluation, teams frustrated with Asana customization overhead |
| When we lose | Enterprise (500+), IT-led evaluation prioritizing SSO/compliance, teams already invested in Asana workflows |
| Their likely next move | AI workflow builder, PM-specific templates, tighter Jira integration |
| Our response | Double down on out-of-box PM workflows. AI features ship faster at our size. Publish migration guide for Asana-to-TaskFlow. |
| Key talking points for sales | "Asana is a great general-purpose tool. If your PM team needs something that works like a PM thinks, without months of configuration, that is where we focus." |
Key Takeaways
- Positioning is not a tagline. It is a strategic choice about which battles you fight and which you avoid.
- Map differentiation axes based on what buyers care about, not what you are proud of building.
- A 2x2 matrix forces clarity. If you cannot place competitors cleanly, your axes are wrong.
- Win/loss data is the most honest input to positioning. Talk to the deals you lost, not just the ones you won.
- Refresh this document quarterly. Competitors ship fast, and positioning that was true six months ago may not hold today.
- Share the final document with sales, marketing, and product. Positioning only works if the whole company tells the same story.