Competitive Analysis That Drives Decisions

The Problem

After a quarterly review, it is easy to have spreadsheets full of features, pricing tiers, and job postings but no input to the next product decision.

This can happen when competitive analysis documents what competitors do without linking it to a decision.

Competitive analysis is a decision support tool. If a piece of intel does not change a roadmap call, a positioning message, or a deal motion, do not collect it.

The Four Levels of Real Competition

Direct competitors are only one part of the competitive set.

Include "do nothing" in tracking when customers identify it as an alternative. Build the competitor set from win/loss data, customer research, and the buying context.

The ACTION Framework

Six steps from competitor data to product decisions.

A: Assess true competition

List who you actually lose deals to. Include "did nothing" or "kept the spreadsheet" if those are common. The list is usually shorter than the team thinks, and the top entry is usually not who you expected.

C: Choose your battles

You can't win every fight. For each competitor, pick one stance:

• Compete head-to-head when you have a sustainable advantage customers care about.
• Concede the segment when cost to win exceeds value.
• Differentiate by solving the problem on a different axis.
• Change the rules by offering an alternative that makes an incumbent less relevant. This carries higher risk.

Canva and Photoshop illustrate different target users and workflows. Compare how each product serves its audience rather than counting shared features alone.

T: Track what matters

Four sources to review for evidence of competitive moves:

• Win/loss patterns: why deals are won or lost. Track in CRM and review monthly.
• Actual pricing: real discounts, not list prices.
• Customer migration: who switches to or away from you, and why.
• Strategic signals: executive hires, funding, and M&A that may indicate a strategic shift.

What not to track: every feature announcement, social follower counts, press release volume. None of it changes a decision.

I: Identify opportunities

Four places competitors leave openings.

These gaps can point to a different product approach. Airtable and Basecamp illustrate products built around workflows that differed from Excel and Microsoft Project.

O: Operationalize insights

Four deliverables that turn intel into action:

• Battle cards for sales, with one page per top competitor
• Positioning messages for marketing, centered on relevant differentiators
• Roadmap input for product, based on systematic deal losses
• Executive summaries with material changes and a recommended response

If the intel does not inform one of these deliverables, reconsider whether it belongs in the review.

N: Never stop learning

Markets shift. Re-run win/loss interviews quarterly. Monitor how competitors react to your moves. Watch adjacent markets. Schedule a 30-minute monthly competitive review focused on three questions: what changed, what did we learn, what should we do differently.

Real Competitive Plays

These examples show companies choosing a different competitive focus.

Zoom vs WebEx

WebEx had enterprise features and Cisco's distribution. Zoom did not try to match either. They competed on reliability and ease ("it just works") and won the prosumer and small-team market before grinding upmarket. They picked a different battle, one where they dominated.

Notion vs Confluence and Evernote

Notion did not pitch as "better wiki" or "better notes." They pitched as Lego blocks for productivity, a different category. Customers who had Confluence kept Confluence. Customers who wanted something composable came to Notion. Refusing to compete head-on was the strategy.

Slack vs Microsoft Teams

Microsoft bundled Teams with Office 365, which Slack could not match on price. Slack emphasized developer experience and external collaboration, illustrating how segments can require different strategies.

Canva vs Adobe

Adobe owned professional design. Canva targeted non-consumption: the 99% who weren't designers but needed a flyer or social post. Adobe never seriously contested that segment¹. The biggest market is often the one your competitor refuses to serve.

Battle Cards: The One-Pager

A battle card is a one-page reference for sales when a competitor comes up. Not a feature comparison. A decision support tool.

Template:

COMPETITOR: [Name]
UPDATED: [Date - refresh monthly]

POSITIONING:
- How they pitch themselves: [Their main message]
- How we counter-position: [Our differentiated message]

WHERE WE WIN:
- Customer type + use case where we are clearly better

WHERE THEY WIN:
- Honest segments where they are stronger

SWITCHING TRIGGERS:
- From them to us: [Common pain points]
- From us to them: [Why customers might still choose them]

TALK TRACK:
- Opening response when they're mentioned
- Three differentiators that matter
- Two customer proof points
- Topics to avoid (where they're stronger)

DISCOVERY QUESTIONS:
- Three open-ended questions that surface our strengths

Keep it to one page and test whether sales uses it in live conversations.

Building a Battle Card in 30 Minutes

1. Talk to two sales reps. Why do you win this competitor? Why do you lose? What questions do they get stuck on?
2. Read 10 reviews. Use G2 or Capterra. Read 1-star and 2-star reviews for switching triggers and 5-star reviews for where the competitor is strong.
3. Write the one-pager. Start with a version that can be tested.
4. Test with one rep this week. Iterate based on whether they actually use it.

Update monthly. Outdated battle cards are worse than none.

Win/loss interviews

The single best competitive intel comes from talking to recently won and recently lost prospects. Five of each, every quarter, by phone. A third party gets more honest answers than your own sales team².

Three questions that matter:

• "What was the deciding factor?"
• "What almost made you choose differently?"
• "What did you wish [the chosen vendor] did differently?"

Look for repeated themes across interviews instead of treating one request as a pattern.

Win/loss interviews can reveal context that feature comparisons do not capture.

Try It

Use it to score competitors on the dimensions your customers care about. The rows where you and competitors tie or both score low are the white space.

Example: An async-first PM tool could compare its workflow, low-noise notifications, and time-zone-friendly defaults with broader tools such as Asana, Monday, Notion, and ClickUp. The comparison may reveal a segment that values those differences.

Common Pitfalls

1. Feature parity trap. Matching every feature on the competitor's spec sheet. Compete on a different axis instead.

2. Spreadsheet warfare. Detailed tracking that never drives a decision. Remove fields that do not inform a decision.

3. Ignoring indirect competition. Only watching the named rival. Status quo, internal build, and adjacent solutions usually account for more lost deals.

4. Reaction obsession. Reacting to every move within hours. Most moves just need monitoring. Keep an If-Then playbook for the few that need response.

5. Losing customer focus. Keep competitive research connected to customer evidence and product strategy.

Competitive Response: If-Then

Agree on default responses before a move requires an immediate decision.

Update the playbook quarterly. The point is to remove the panic from the moment.

AI Prompts for Competitive Work

Use Claude, ChatGPT, or Gemini. Always include grounding instructions: cite the exact quotes, do not paraphrase or invent.

Win/Loss Synthesis

Analyze these win/loss interview notes:
[paste anonymized notes]

Find:
- Top 3 reasons we win (with verbatim quotes)
- Top 3 reasons we lose (with verbatim quotes)
- Most-mentioned competitors in losses
- Three battle card talking points

Cite the source quote for every claim. If you cannot find evidence, say so.

Competitive Positioning

Position our [product type] against [competitor]:

Our strengths: [list]
Their strengths: [list]
Our target segment: [describe]

Suggest:
- Three positioning axes where we win
- One sales discovery question that surfaces a competitor weakness
- Two segments where we should walk away from the deal

Strategic Response Planning

Competitor [X] just acquired [Y]:

Our position: [describe]
Our customers: [describe]

Recommend:
- 48-hour internal communication
- 90-day strategic options (build, buy, partner)
- Risks of responding vs not responding

Advanced Patterns

These show up in mature markets.

Asymmetric competition. Compete where they can't or won't follow. Open source vs proprietary. PLG vs enterprise sales. Service-heavy vs pure software.

Network effects. Build relationships and integrations around the product, such as Salesforce AppExchange, Stripe partnerships, or the Shopify app store. Their value can grow as participation increases.

Pace of learning and delivery. Consider whether you can test assumptions and respond to customer needs sooner than competitors.

Category creation. A product can define a category around a different customer problem or workflow. HubSpot used "inbound marketing" and Notion used "all-in-one workspace."

Metrics That Track Competitive Health

Skip share-of-market and share-of-search unless you're a public company. Those numbers are too noisy to act on monthly.

A 90-Day Plan

Week 1. List top three competitors (include "do nothing"). For each, write the biggest reason customers choose them.

Weeks 2-3. Run two win and two loss interviews. Listen, don't defend.

Week 4. Build v1 battle cards for top two competitors. Ship to sales.

Months 2-3. Implement systematic win/loss program. Build the If-Then response playbook. Set up the monthly 30-minute review.

End of quarter. Review what changed in the competitive landscape, what you learned, and which roadmap items got prioritized as a result. If none, the program is not working yet.

Sources