How to Do a Competitive Analysis: A 4-Week Roadmap, Step by Step
8 min read · 2026-10-11
To learn how to do a competitive analysis, follow six steps. First, write down the decision the analysis must support. Second, pick 3 to 5 competitors your customers actually consider. Third, collect evidence from public sources and hands-on trials. Fourth, compare everyone on the same criteria. Fifth, turn the gaps you find into roadmap decisions. Sixth, share the results and set a date to look again. For one product, a small team can do all of this in about four weeks, part time.
Many analyses end as a long feature list that nobody uses. The roadmap below avoids that. Every phase ends with a milestone you can check, and the fifth phase makes you keep, change or drop items on your own roadmap. Use it for a new product, a new market or a yearly strategy review.
The roadmap at a glance
Goal: Understand how your product compares to the alternatives your customers consider, and decide what to build, change or ignore as a result. Duration: 4 weeks, part time
Frame the Question (Days 1-3)
Make sure the analysis answers one real decision. Don't collect facts just for the sake of it.
- Write the decision in one sentence, for example "Should we add a free plan this quarter?" or "Which segment should we target first?"
- List the 3 to 5 questions you need answered to make that decision.
- Agree on who will use the results and when they need them.
- Set a time box and name one owner.
Milestone: A one-page brief with the decision, the key questions, the owner and the deadline, approved by the decision maker.
Pick the Right Competitors (Days 4-7)
Choose the alternatives your customers really compare you with, not just the best-known names.
- Ask your sales and support teams which names come up in calls and lost deals.
- Search the main keywords your customers type and note who appears.
- Include at least one indirect alternative, such as a spreadsheet, an agency or doing nothing.
- Cut the list to 3 to 5 competitors, sorted into direct and indirect.
Milestone: A final list of 3 to 5 competitors, each with one line explaining why it is on the list.
Collect the Evidence (Week 2)
Gather facts you can trace back to a source, so nobody has to rely on memory.
- Read each competitor's homepage, pricing page, docs and changelog, and save the date you read them.
- Sign up for free trials or free plans and complete the main task your users care about.
- Read public reviews and pull out repeated praise and complaints.
- Note positioning: who the product says it is for and what it promises.
- Store every fact with its source link and date in one shared document.
Milestone: One evidence file per competitor, with every fact dated and sourced.
Compare and Find the Gaps (Days 15-19)
Put every competitor on the same grid so you can see the differences side by side.
- Choose 6 to 10 criteria linked to your key questions, such as onboarding, core features, pricing model, target customer and support.
- Rate each competitor and your own product on each criterion with a simple scale: weaker, equal, stronger.
- Highlight where everyone is strong (table stakes) and where nobody is (open space).
- Write 3 to 5 insights, each in one sentence starting with "Customers who…".
Milestone: A completed comparison grid and a short list of insights the team agrees on.
Turn Findings Into Roadmap Decisions (Days 20-24)
Connect each insight to a concrete choice on your own roadmap.
- For each gap, decide: match it, beat it or ignore it on purpose.
- Add, move or remove roadmap items and write the reason next to each change.
- Check every change against your strategy and the decision from week one.
- Note the risks you chose to accept.
Milestone: An updated roadmap where every change links back to a specific insight.
Share and Keep It Fresh (Days 25-28)
Make the findings easy to reuse and plan when you will look again.
- Write a one-page summary: decision, top insights, roadmap changes.
- Present it in a 30-minute session and collect questions.
- Give sales and support a short brief on how to answer "How are you different from X?"
- Set a review date, for example each quarter, and name who watches each competitor.
Milestone: Summary shared, review date in the calendar and one owner per competitor.
What a Competitive Analysis Is, and What It Is Not
A competitive analysis is a structured comparison of your product with the alternatives your customers consider. You use it to make a specific decision. The key word is decision. If the work does not change what you build, how you price or how you position, it was research, not analysis.
It is not a copy list. Finding a feature your rival has does not mean you should build it. It also does not replace talking to customers. Competitors show you what is on offer. Customers tell you what they actually need and why they choose. Strong analyses use both: competitor evidence to map the options, and customer interviews to explain the choices.
Where to Find Reliable Evidence
Good evidence is public, dated and traceable. These sources give you the most useful facts for the least effort.
Collect honestly. Use only public or openly available information, the kind any customer can access. Posing as someone else to get private information damages trust and can cause problems for your company. It also makes your own team doubt the results.
- Pricing pages show the business model, what each plan includes and which customer each plan targets.
- Changelogs and release notes show where a competitor is investing right now.
- Help docs and onboarding emails show how the product really works, beyond the marketing.
- Free trials let you time the main task yourself and see where you get stuck.
- Public reviews show the words customers use for what they love and what frustrates them.
- Job postings hint at future plans, such as a new market, a mobile app or an enterprise push.
- Your own sales and support notes show which competitors you meet most and why deals are won or lost.
How to Build a Comparison Grid People Will Read
A grid works when it is short and linked to the decision. Pick criteria that answer your key questions, not every feature you can find. For a pricing decision, compare plan structure, free options, limits and what triggers an upgrade. For a positioning decision, compare target customer, main promise and proof shown on the homepage.
Keep the rating simple. A three-level scale (weaker, equal, stronger) is easier to defend than a score out of 10. Nobody can explain why a rival gets 7 rather than 6. Next to each rating, add the source fact behind it. When someone disagrees in the review meeting, you can point to the evidence instead of arguing about opinions.
Read the grid in two directions. Read across a row to see where the whole market stands on one criterion. Read down a column to see the profile of one competitor. Rows where everyone is strong are table stakes: you need them to be considered at all. Rows where nobody is strong are worth a closer look. They may hide an unmet need, or simply a need nobody has.
From Insights to Roadmap Items
Teams often skip this step, yet it is the one that makes the work pay off. Take each insight and give it one of three answers.
Write the reason next to each roadmap change, for example "Add CSV import: three competitors offer it and it came up in lost deals." That one line lets anyone understand the change months later. If you already score features with a method such as RICE or ICE, feed the insights into that scoring. Don't give them a separate fast track. To see how these choices look on a finished roadmap, browse these product roadmap examples.
- Match it when a gap is table stakes and you lose deals because of it.
- Beat it when the gap matches your strategy and you can do clearly better.
- Ignore it on purpose when the gap serves a customer you do not target.
How Often to Repeat the Analysis
A full analysis does not need to run every month. A common rhythm is a full pass once a year or before a big decision, plus a short check every quarter. The quarterly check can take one or two hours: reread changelogs and pricing pages, update the grid, and flag anything that changes a decision. For a wider view on timing, read how often you should update your roadmap.
Name one owner per competitor so the watch does not depend on one busy person. Keep everything in the same shared file, with dates, so you can see how each rival has moved over time.
Common mistakes to avoid
- Starting without a decision in mind turns the work into a pile of facts. Write the decision on day one and cut anything that does not serve it.
- Only looking at famous brands misses the alternatives your buyers really use. Ask sales and include at least one indirect option.
- Copying features because a rival has them fills your roadmap with other people's strategy. Decide to match, beat or ignore each gap, with a written reason.
- Rating on gut feeling makes the grid easy to dismiss. Attach a dated source to every rating.
- Treating the analysis as a one-off lets it go stale fast. Book a quarterly review and give each competitor an owner.
- Keeping findings inside the product team leaves sales without answers. Share a short brief on how to handle each competitor.
Frequently asked questions
How many competitors should I include?
Three to five is usually enough. Fewer than three gives you a narrow view, and more than five makes the grid too large to read. Include at least one indirect alternative, such as a spreadsheet or doing nothing.
How long does a competitive analysis take?
For one product and a clear decision, about four weeks part time is realistic, as in the roadmap above. A quick update of an existing analysis can take a few hours. A large market study across several segments takes longer.
What is the difference between direct and indirect competitors?
Direct competitors sell a similar product to the same customers. Indirect competitors solve the same problem in a different way, like a consultant, a template or a manual process. Both matter, because customers compare you with whatever they would use otherwise.
Can I do a competitive analysis in a spreadsheet?
Yes. A spreadsheet in Excel or Google Sheets works well for the evidence file and the comparison grid. Keep one tab per competitor for sources and one summary tab for the grid. Then move the decisions onto your roadmap so they lead to work, not just a file. If you need a starting layout, pick one of these roadmap templates.