The Competitive Analysis Framework: A 5-Step System
Most competitive analyses answer the wrong question. They map who exists. This framework maps who matters, why they're winning, and where the opening is that they can't close.
📋 Read time: 14 minutes. Use time: every time you enter a market.
Why This Exists
Most founders do competitive analysis once, at the beginning, to fill slide 4 of a pitch deck. They list five companies in a 2×2, put themselves in the top-right corner, and move on. The problem is that this exercise optimizes for investor optics, not product clarity. It tells you who else exists. It doesn't tell you why customers choose them, what keeps customers stuck with them, or where the actual opening is.
Teams that win treat competitive analysis as a recurring practice, not a one-time deliverable. They update it when customers churn to a competitor, when a competitor raises a round, when a new category term starts appearing in sales calls. They use it to shape positioning, pricing, sequencing, and feature bets. It's not a slide. It's a lens.
This framework gives you a structured process for building that lens. Five steps, each one producing a specific artifact you can use. You can do it in a weekend for a new market or run it as a quarterly review for a product already in motion.
How to Use This
- Run it in order. Each step builds on the one before. Don't jump to the positioning map without finishing the job landscape first.
- Anchor every insight in evidence. Customer quotes, public reviews, sales call notes. If you can't point to a source, mark it as a hypothesis and test it.
- Assign a section owner. In a team, one person per step prevents the analysis from becoming a committee document that no one trusts.
- Schedule a review date before you finish. Competitive landscapes shift. If you don't plan the next run before you finish the current one, it won't happen.
Step 1: Define the Arena Before You Enter It 🗺️
The first mistake in competitive analysis is starting with competitors. Start with the job your customer is trying to get done.
Pick one customer segment. Write down the specific job they're hiring your product to do. Not "manage their product roadmap." Something like: "A solo founder, three months from launch, trying to decide which features to cut so they don't run out of runway before they find product-market fit." That level of specificity changes everything about who your competitors actually are.
Once you have the job, list every way a customer currently solves it. Some solutions are products. Some are workflows. Some are people. A consultant, a spreadsheet, a Slack thread with an advisor, doing nothing and hoping, Notion plus a lot of copy-paste. All of these are competitors. All of them have switching costs.
The Arena Definition Template
Copy-paste: Arena Definition
ARENA DEFINITION
Segment: [Describe the specific customer in one sentence. Role, context, constraint.]
Job to be done: [What are they trying to accomplish? What does "done" look like? What does failure look like?]
Current solutions (list all, not just software):
1. [Solution A]
2. [Solution B]
3. [Solution C]
4. [...]
For each current solution, note:
- What it does well
- What it fails to do
- What the customer says when asked why they still use it
Primary arena: [Based on the above, what is the actual competitive space you're entering? Name it precisely.]
Step 2: Map the Competitive Landscape (Without the 2×2 Trap)
Now bring in the named competitors. But map them against the job, not against each other.
For each competitor, answer four questions: What do they do well? What do they make hard? Who do they serve best? Who do they systematically underserve? The last question is where you're looking for your opening. Every product optimizes for someone. The people it doesn't optimize for are the gap.
The classic 2×2 fails because it picks two axes that flatter the maker. Instead, use the table below. The axes come from the job you defined in Step 1, not from your wishlist.
Competitive Landscape Table
| Competitor | Core strength | Core weakness | Best-fit customer | Underserved customer |
|---|---|---|---|---|
| [Name] | [What they genuinely do well] | [Where they consistently fall short] | [Who loves them] | [Who struggles with them] |
| [Name] | ||||
| [Name] | ||||
| [Name] | ||||
| You |
Fill in your own row last. Filling it in first is how you end up rationalizing instead of analyzing.
A note on sources. Public G2, Capterra, and App Store reviews are underused. The negative reviews on a competitor's page are a direct line to what their customers wish existed. Read 20 of them and cluster the themes. That's primary research that costs nothing.
Step 3: Understand Why Customers Stay (The Moat Audit)
Winning customers once is a distribution problem. Keeping them is a moat problem. These are different muscles.
For each major competitor, identify their actual retention mechanism. Not their marketing claim. The real reason customers don't leave. There are four categories:
Moat Type Reference
| Moat Type | What it looks like | How hard to break |
|---|---|---|
| Data moat | Their product gets better the more you use it. Switching means leaving your history behind. | Very hard |
| Workflow moat | Their product is embedded in a daily habit or an existing tool chain. Switching disrupts the whole flow. | Hard |
| Network moat | The product is more valuable when your team or partners also use it. Switching is a coordination problem. | Hard |
| Switching cost moat | Migration is painful. Data export is limited, training is required, or contracts are long. | Medium |
| Brand/trust moat | Customers believe this is the default tool for this job. Alternatives feel risky. | Medium |
| Feature moat | They have something specific that matters to a segment and nobody else has built it. | Low (copyable, but takes time) |
Most products have one strong moat and one secondary one. If you can't identify a competitor's moat, look harder. It's there. Understanding it tells you whether you need to displace them directly (almost always a bad idea) or find the customers who their moat doesn't hold for.
Moat Audit Prompt
Copy-paste: Moat Audit
MOAT AUDIT: [Competitor Name]
Primary moat type: [Choose from: Data / Workflow / Network / Switching cost / Brand / Feature]
Evidence for this moat:
- [Observable signal 1: review quote, behavior pattern, pricing structure, etc.]
- [Observable signal 2]
- [Observable signal 3]
Secondary moat type: [If applicable]
Who is NOT protected by this moat:
- [Segment or scenario where the moat doesn't apply]
Implication for positioning:
- [One sentence on what this means for how we compete]
Step 4: Run the Positioning Gap Analysis
You now know the landscape. You know who customers can choose. You know why they stay. The next step is finding the position that is both credible and uncrowded.
A positioning gap is not just empty space on a chart. It's a real customer need that existing products don't serve well, combined with a reason you can serve it better. Empty space without unmet demand is just a market that doesn't exist. Unmet demand you can't credibly serve is a trap.
Work through this filter for every gap candidate:
Gap Filter: 3 Questions
-
Is there evidence customers want this? Not survey data where you ask leading questions. Evidence: churned customers, help desk tickets, workarounds, complaints in competitor reviews, things customers do manually that could be automated.
-
Is there a structural reason incumbents can't close this gap? They're too enterprise to move fast. Their architecture makes this expensive. Serving this segment conflicts with their core business model. Their sales motion doesn't reach this buyer. If there's no structural reason, assume they'll copy you the moment you prove demand.
-
Can you credibly claim this position in 12 months? Given your team, your current product, and your budget, can you build the proof points that make this claim believable? If no, it's a vision, not a position.
Gaps that pass all three filters are worth building around. Gaps that fail question 2 might still be worth pursuing early, but don't build a company on a position that a well-funded competitor can replicate in a quarter.
Positioning Gap Template
Copy-paste: Positioning Gap Analysis
POSITIONING GAP ANALYSIS
Gap candidate: [Describe the unmet need in one sentence]
Evidence this need is real:
- [Signal 1: source, quote, or observable behavior]
- [Signal 2]
Structural reason incumbents can't close this:
- [Why their product, business model, or go-to-market makes this hard for them]
- If none: [Acknowledge this and note the risk]
Our ability to claim this in 12 months:
- Current proof points: [What we have now]
- Required proof points: [What we need to build]
- Feasibility: [High / Medium / Low] — [One-sentence rationale]
Verdict: [Pursue / Deprioritize / Monitor]
Step 5: Translate Findings into Three Decisions
Analysis without decisions is a document, not a practice. Every competitive analysis should end with three concrete outputs.
Decision 1: Who we are NOT building for right now.
Every gap analysis surfaces tempting adjacencies. Name them. Then explicitly decide to ignore them for now. This is what keeps your roadmap from drifting toward whoever you talked to last week.
Decision 2: One positioning statement update.
Based on what you found, how does your positioning change? This doesn't mean rewriting your homepage. It means sharpening the sentence you say when someone asks what you do. The format: "For [specific customer], who [specific job], [product name] is the only [category] that [specific differentiator], because [reason to believe]."
Decision 3: One competitive watch item.
Pick one competitor or market development to monitor actively in the next quarter. Set a specific trigger: "If [competitor] ships [capability], we revisit our sequencing." This keeps competitive intelligence from becoming reactive.
Decision Log Template
Copy-paste: Decision Log
COMPETITIVE ANALYSIS DECISION LOG
Date: [Date]
Analyst: [Name]
Next review: [Date]
DECISION 1 — Out-of-scope segments (do not pursue for the next [timeframe])
- [Segment/use case A]: [One-sentence reason]
- [Segment/use case B]: [One-sentence reason]
DECISION 2 — Positioning statement update
Previous: [Old positioning statement]
Updated: For [customer], who [job], [product] is the only [category] that [differentiator], because [reason to believe].
DECISION 3 — Watch item
Competitor/trend: [Name]
What to watch: [Specific capability, move, or signal]
Trigger for action: [If X happens, we do Y]
Owner: [Name]
Common Pitfalls
Building the 2×2 for the investor, not the team.
If your competitive slide makes you look better than you actually are, you've optimized for fundraising and not for understanding. The analysis that helps you build is honest, not flattering.
Treating "no direct competitor" as a good thing.
No direct competitor usually means no proven demand, or means you've defined the market so narrowly that you've hidden all the alternatives. Either way, it's a flag, not a trophy.
Stopping at features.
Features are the surface. What matters is the underlying job, the moat, and the positioning. Two products can have identical feature sets and completely different competitive dynamics.
Confusing size for threat.
A large competitor is not automatically your most dangerous one. A small, well-funded startup with a focused thesis and nothing to protect is often more dangerous than an incumbent with a 20% market share and a legacy architecture.
Copying the competitor's roadmap.
If your primary input from competitive analysis is "we need to build what they have," you've already lost. You're always 12 months behind. The output of competitive analysis should be differentiation, not feature parity.
Only interviewing happy customers.
Happy customers will tell you your product is great. Churned customers and customers who evaluated you and didn't buy will tell you where the real gaps are. Both populations belong in this analysis.
Skipping the review cycle.
A competitive analysis done once is a snapshot of a market that will change. If you don't build in a scheduled review, the document becomes stale and the team stops trusting it. Set the next review date before you close the current one.
Why We Built This
Coding is becoming cheaper. Knowing what to build is becoming more valuable. That's the thesis behind ProductOS. But "knowing what to build" isn't just intuition. It's a structured practice: understanding your market, defining your users, making deliberate decisions before anything gets built.
Competitive analysis is one of the highest-leverage inputs to that practice. Done well, it shapes positioning, sequencing, and product bets before a single line of code is written. Done poorly, or not at all, it leaves teams building confidently toward a market they've misread. ProductOS carries that research and decision context all the way through to deployed code, so the insights from a competitive analysis don't evaporate when the sprint starts.
This framework is what we use internally and with product teams we advise. It's not a complete substitute for deep market knowledge, and it won't tell you whether your insight is right. What it will do is structure your thinking so the decisions you make are based on evidence rather than assumption.
If any of this lands and you want to see it in action, we're at productos.dev. No pressure. The toolkit stands on its own.
If you'd rather have humans plus AI run this for you on a real product today, that's what 1Labs AI does.
Built by Heemang Parmar, Founder & CEO of ProductOS. 10+ years in product, 150+ builds. Also runs 1Labs AI, an AI product development agency.