A competitor analysis should help someone make a decision. If the final output is a spreadsheet with 40 feature rows and no clear conclusion, you have collected data without producing much intelligence.
For B2B SaaS teams, the useful question is rarely “Who has more features?” It is usually closer to: Has a competitor moved upmarket? Is their pricing model changing? Are they closing a product gap that matters in live deals? Has their positioning shifted toward our ideal customer?
This guide shows how to build a competitor analysis around those questions using public evidence, while keeping observation separate from interpretation.
What is a competitor analysis?
A competitor analysis is a structured, point-in-time assessment of the rivals that matter to a specific business decision. It brings together evidence about pricing, product, capabilities, hiring and positioning, then turns that evidence into a view you can act on.
That is different from competitor research, which is mostly collection, and from competitive intelligence, which is the broader ongoing process of collecting, analysing and distributing market signals over time.
A useful shorthand is:
Competitor research gathers the clues. Competitor analysis explains the current picture. Competitive intelligence keeps that picture current as the market moves.
The distinction matters because a one-time analysis and ongoing competitor monitoring solve different problems. If you need to understand where rivals stand today, start with the analysis. If your problem is finding out when that picture stops being true, you need monitoring as well.
Start with the decision, not the competitor list
The fastest way to make a competitor analysis too broad is to begin with “analyse our competitors.”
Instead, write down the decision that the analysis is meant to support.
Examples:
- Should we change the packaging of our Pro plan?
- Are we still differentiated on a capability that matters in enterprise deals?
- Is a competitor moving toward larger customers?
- Which rival is putting the most pressure on our positioning?
- Do recent product changes justify moving something up our roadmap?
This gives the research a boundary. A pricing decision needs deeper evidence on tiers, allowances and packaging. A positioning decision needs more attention to home pages, navigation, category language and who the competitor says the product is for.
The decision should determine what evidence deserves weight. Otherwise every visible difference looks equally important.
Choose the competitors that can actually change the decision
You do not need a giant market map for every analysis.
Start with the competitors that create real pressure:
- the alternatives that appear in live deals;
- the companies prospects compare you with;
- the category leader that sets buyer expectations;
- a fast-moving challenger that could change the market frame;
- an indirect alternative that solves the same problem in a different way.
A few relevant competitors studied carefully are usually more useful than a long list copied into a comparison grid.
A competitor belongs in the analysis because their move could change yours, not because they happen to share a category label.
Build the evidence base from public signals
For B2B SaaS, some of the most useful competitive evidence is already public. The challenge is collecting it consistently and reading different surfaces together.
Pricing and packaging
A pricing page can reveal much more than a number. Look for:
- plan names and tier structure;
- published prices and billing units;
- usage allowances;
- free plans and trials;
- feature gates;
- annual discounts;
- “contact sales” boundaries;
- changes in the primary call to action.
A competitor can leave the headline price unchanged while materially changing what the buyer gets for that price.
Product pages and changelogs
Track what has shipped, what is newly emphasised and which capabilities have moved from roadmap language into published product language.
Do not treat every release as strategic. A small integration and a new enterprise governance layer are both “product updates,” but they do not carry the same decision weight.
Documentation
Documentation is valuable because it often answers a harder question than a marketing page: what can the product actually do?
Reference pages, implementation guides and configuration docs can confirm whether a capability is real, limited, gated or still ambiguous.
Hiring
Hiring is not proof of strategy, but it can be useful supporting evidence.
A group of enterprise account executive roles, a new security leadership position or repeated hiring in a new market may strengthen a reading already suggested by pricing or product changes. On its own, a job posting should rarely carry the conclusion.
Positioning
Watch the home page, navigation, category language and audience claims.
A messaging change can show that a competitor wants to be understood differently, but it does not prove the underlying product or commercial strategy changed. Treat positioning as a signal to investigate, not as a shortcut to intent.
See how MoveClue structures public evidence in a Competitive X-Ray.
Separate observation from inference
This is the most important discipline in a credible competitor analysis.
An observation is what the public evidence directly shows.
A competitor removed a Starter tier. A documentation page now describes SSO. The home page changed its headline. Three new enterprise sales roles appeared.
An inference is what you think those observations may mean.
The company may be moving upmarket. It may be packaging governance features more aggressively. It may be testing a new category position.
Those are useful readings, but they are not facts about the competitor’s intent.
Evidence tells you what changed. Analysis tells you what that change may mean. Good competitive intelligence never pretends those are the same thing.
When you write the conclusion, label the difference. It makes the analysis easier to trust and easier to challenge.
Use a competitor analysis framework that can survive disagreement
A decision-ready competitor analysis should make it possible for a sceptical colleague to ask “why?” and get an answer without rebuilding the research.
For each important conclusion, capture four things.
1. The claim
Write the conclusion in one sentence.
Example: “The available evidence makes an upmarket packaging move more plausible.”
Avoid pretending to know private intent.
2. The evidence
Attach the specific public observations that support the claim. Prefer independent evidence from different surfaces over five versions of the same marketing statement.
3. The counter-case
Ask what else could explain the same evidence.
A new Enterprise plan may be a packaging test. Hiring may replace attrition rather than signal expansion. A rewritten headline may be an A/B test.
If the conclusion survives plausible alternatives, it deserves more confidence. If it does not, say that.
4. What would change your mind
Define the next observable event that would strengthen, weaken or update the reading.
This turns a static analysis into something you can revisit later instead of treating the document as permanent truth.
What most competitor analyses get wrong
They compare features instead of decisions
Feature matrices are useful for narrow product questions, but they become misleading when every row is given equal weight.
A capability that never appears in a deal should not automatically matter as much as a pricing change that affects every renewal.
They mix facts and interpretations
Once a guess is written in the same tone as an observation, it becomes hard to see which part of the analysis is solid and which part is judgement.
Keep the layers separate.
They use one source to support a broad conclusion
A home-page rewrite can be interesting. It is not enough on its own to prove a market move.
Confidence should rise when independent signals agree.
They ignore what could not be observed
Public competitor research always has coverage limits. Pages can be unavailable, historical versions can be missing and some companies simply publish less.
A credible analysis states those gaps instead of quietly turning missing evidence into certainty.
They never expire the conclusion
A competitor analysis is a snapshot. It should have a date, sources and a clear point after which the market needs to be checked again.
When a one-time analysis is enough
A point-in-time competitor analysis is often enough when you have a bounded decision:
- a pricing or packaging review;
- a board question;
- a market-entry decision;
- a positioning exercise;
- a roadmap prioritisation discussion.
That is the job of MoveClue’s Competitive X-Ray: a one-time, evidence-linked brief on the competitors you name and the decision you are trying to make.
It captures the public surfaces it can discover, states the coverage it achieved, separates observations from interpretations, and keeps the evidence attached to the conclusion.
When competitor monitoring becomes the better next step
A static report becomes less useful when the cost of being late is high.
If competitors reprice often, ship quickly, change packaging or repeatedly appear in active deals, you need a way to notice when the earlier analysis stops holding.
MoveClue Monitor works standalone against its own observation history. It re-reads tracked public surfaces on a schedule, filters cosmetic changes and can produce a brief when a material change deserves attention.
For the process around choosing signals and filtering noise, read Competitor Monitoring: What to Track and What to Ignore.
If a monitored competitor also appeared in a recent published X-Ray, that X-Ray can add strategic context to the later brief. It is useful context, not a requirement for monitoring.
Compare the one-time X-Ray and ongoing Monitor if you are deciding which problem you actually have.
If you want to inspect the deliverable before doing anything else, read the full sample X-Ray.
A simple competitor analysis checklist
Before you call the work finished, ask:
- Did we define the business decision first?
- Did we choose competitors because they matter to that decision?
- Can every important observation be traced to a public source and date?
- Did we separate observation from inference?
- Did we look for independent corroborating evidence?
- Did we write down plausible alternative explanations?
- Did we state the important coverage gaps?
- Did we define what would make us change the conclusion?
- Is there a clear next action for the team?
If the answer is yes, you have something more useful than a comparison spreadsheet: you have a defensible current view of the competitive landscape.
Frequently asked questions
How often should you update a competitor analysis?
Update it when the decision demands a current view. A pricing review made six months after the original analysis should not assume the old evidence still holds. For fast-moving competitors, ongoing monitoring can be more efficient than repeatedly rebuilding the same analysis from scratch.
What information should a competitor analysis include?
For B2B SaaS, useful public inputs include pricing and packaging, product and changelog updates, documentation, hiring and positioning. The exact mix should depend on the decision you are trying to make.
What is the difference between competitor analysis and competitive intelligence?
Competitor analysis is usually a point-in-time assessment. Competitive intelligence is the broader ongoing discipline of collecting, analysing and distributing signals that can change business decisions. Competitor monitoring is one part of that ongoing system.
Can you do competitor analysis with public information only?
Yes, for many strategic questions. Public pages can reveal pricing, packaging, capabilities, product releases, hiring and positioning. The important constraint is to state what the public evidence supports—and what it does not.