# How to Build a SaaS Competitive Analysis

> A one-page competitive analysis template for SaaS teams: what to include, what to leave out, and how to keep the document from going stale.

Canonical: https://www.usetraced.xyz/blog/how-to-build-a-saas-competitive-analysis
Published: October 30, 2026
Updated: October 30, 2026

## Key takeaways

- A competitive analysis is a decision document, not a research archive. Choose the artifact your audience will actually use.
- A one-page structure beats a long deck: scope, competitor set, landscape, comparison, implications, actions, sources.
- Date every claim and link the source. Undated competitive claims become liabilities.
- Assign an owner and a review date before you share it, or the document will be stale within a quarter.

## Analysis is a process. The analysis is an artifact.

“Do a competitive analysis” can mean two different jobs. One is the ongoing process of reading competitor changes and deciding what they mean. The other is a specific deliverable: a landscape map, a battlecard, a pricing comparison, or a win/loss summary.

Teams get stuck because they try to make one document do all four jobs. A sales battlecard needs different detail from a board-level market map. A pricing comparison needs different evidence from a product roadmap review. Pick the artifact first, then collect only what it needs.

**Choose the artifact by audience and decision**
| Artifact | Audience | Decision it supports | Typical length |
| --- | --- | --- | --- |
| Market landscape | Founders, leadership, investors | Where to play, how the category is segmented | One page plus a map |
| Sales battlecard | Sales, solutions, customer success | How to position against a named competitor in a live deal | One to two pages |
| Pricing and packaging comparison | Product, marketing, finance | Whether to change price, packaging, or trial terms | One table plus notes |
| Win/loss summary | Product, sales, leadership | Why deals are won or lost and what to fix | One page per quarter |

If you are unsure, build the one-page landscape first. It forces you to name the market, the buyer, and the competitor set. The other artifacts can be derived from it later.

## The one-page template

The template below fits on a single page if you keep each block to a few bullets. It is deliberately boring. The value is in the discipline of filling it with dated evidence and a clear implication.

1. **Scope.** What decision is this analysis supporting, and by when? Name the market, segment, and geography.
2. **Competitor set.** Three to seven companies, each with a one-line reason it is included. Note the source of the list.
3. **Landscape.** Place competitors on two axes that matter to buyers, such as price versus depth or self-serve versus sales-led. Label the axes and explain why you chose them.
4. **Comparison.** A short table of the dimensions that change deals: target buyer, entry price, packaging, core workflow, proof, and a clear strength or weakness.
5. **Where we win and lose.** Three bullets each, tied to evidence from deals, reviews, or product tests. Avoid generic claims.
6. **Implications.** What should change in pricing, messaging, product, or sales? If nothing should change, say so.
7. **Actions and owners.** One to three actions with an owner and a date. A document with no actions is a report, not an analysis.
8. **Sources and review date.** Link the pages you used, date the capture, and set the next review.

> **Keep the axes honest**
>
> A 2×2 is only useful if the axes reflect a real buyer trade-off. “Innovation” versus “experience” is decoration. Price versus depth of workflow, or self-serve versus sales-led, changes how a buyer shortlists.

## Build the first version in about ninety minutes

The first pass does not need to be perfect. It needs to be dated, sourced, and useful enough to discuss. A time-boxed sprint keeps the document from turning into a research project.

**A 90-minute first pass**
| Time | Work | Output |
| --- | --- | --- |
| 0–10 min | Write the decision, audience, and deadline | A one-sentence scope at the top |
| 10–25 min | Choose three to seven competitors and write the reason for each | A competitor set with inclusion criteria |
| 25–55 min | Capture pricing, positioning, and one proof point per competitor | Dated source links and a rough comparison table |
| 55–75 min | Write where you win, where you lose, and the implication | Three bullets each, no unsourced claims |
| 75–90 min | Add actions, owners, dates, and the review date | A shareable one-pager |

If you already have a weekly change report, the first 55 minutes are mostly assembling evidence you already have. That is the advantage of separating monitoring from analysis: the raw material is current before the document sprint starts.

> **Let Traced watch the pages for you.** Traced checks competitors' pricing, homepage, feature, and changelog pages every week, then sends a report of what changed. Monitoring runs on its own; the analysis stays with you. [Start tracking](https://www.usetraced.xyz/sign-up) · [See pricing](https://www.usetraced.xyz/pricing)

## Make the document survive the quarter

Most competitive analyses do not fail because the research was wrong. They fail because nobody owns them. Six months later, a sales rep is quoting a price that changed in March and a feature that was discontinued in June.

- **Name an owner.** One person is responsible for the document, even if several people contribute.
- **Date every claim.** Put the capture date next to the price or feature. If a claim has no date, it is not ready to share.
- **Link the source.** A URL is faster to verify than a screenshot, and it lets the next reviewer refresh the evidence.
- **Label confidence.** Mark estimates as estimates. “Published price” and “inferred from a sales call” are different levels of evidence.
- **Set a review date.** Monthly for pricing and messaging, quarterly for the full landscape. Put it on the calendar.
- **Archive old versions.** Keep the previous version so you can explain why a recommendation changed.

The review cadence should match the market. A fast-moving category needs a monthly refresh; a stable enterprise category may only need a quarterly one. [How often should you analyze your competitors?](/blog/how-often-should-you-analyze-competitors) has a framework for choosing.

## What to leave out

- **The fifty-row feature grid.** It takes hours to maintain and rarely explains a purchase. Compare the five features that change deals, not every checkbox.
- **Unsourced claims.** “Competitor X is enterprise-ready” is an opinion until you link the pricing page, docs, or customer story that supports it.
- **A history of every change.** The document is a snapshot, not a changelog. Keep the change history in your monitoring tool.
- **Strategy-by-imitation.** A competitor's move is evidence, not an instruction. Copying their pricing page without their cost structure or buyer is a fast way to damage your own model.
- **A deck with no actions.** If the last slide is “questions?”, the document is not finished.

> **The one-question test**
>
> Before you share the document, ask: “What would someone do differently after reading this?” If the answer is vague, cut the document until it is specific.

## Keep the raw material fresh

A competitive analysis is only as good as the evidence behind it. The document can be a one-time sprint, but the inputs need a rhythm: pricing pages, homepage messaging, product pages, changelogs, and proof points.

Traced monitors those public pages every week and sends a report of what changed, with dated diffs and AI-written summaries. When it is time to refresh the one-pager, you are editing a current document instead of rebuilding it from memory.

For the interpretation step, [how to analyze SaaS competitors](/blog/how-to-analyze-saas-competitors) has a six-step loop. For the most common failure modes, see [common mistakes in competitor analysis](/blog/common-mistakes-in-competitor-analysis).

## FAQ

### What should a SaaS competitive analysis include?

At minimum: the decision and scope, the competitor set with reasons, a landscape or comparison, where you win and lose, implications, actions with owners, and dated sources. A one-page document with those blocks is more useful than a long deck without them.

### How long should a competitive analysis be?

A decision-ready landscape or battlecard is usually one to two pages. The length should follow the decision, not the amount of research available. If a section does not change what someone does, cut it.

### How often should I update a competitive analysis?

Refresh pricing and messaging inputs monthly, and review the full landscape quarterly. In a fast-moving category, shorten the cycle. Set a review date when you publish the document so it does not quietly go stale.

### What is the difference between a competitive analysis and a battlecard?

A competitive analysis explains the market and the implications for your strategy. A battlecard is a sales tool for one competitor in one deal: their pitch, strengths, weaknesses, objection handling, and proof points. The analysis can feed several battlecards.

### Can I build a competitive analysis without a research team?

Yes. A founder or product marketer can build a useful one-pager in about ninety minutes if the competitor set is already chosen and the source pages are current. Automation helps most with the recurring capture, not the judgment.

## Related guides

- [How to Analyze SaaS Competitors: A Practical Guide](https://www.usetraced.xyz/blog/how-to-analyze-saas-competitors)
- [7 Common Mistakes in Competitor Analysis](https://www.usetraced.xyz/blog/common-mistakes-in-competitor-analysis)
- [How to Find Competitors for Your SaaS](https://www.usetraced.xyz/blog/how-to-find-competitors-for-your-saas)

## About Traced

Traced is an automated competitor monitoring tool for SaaS teams. It checks competitors' public pricing, homepage, feature, and changelog pages every week and reports exactly what changed. Learn more at https://www.usetraced.xyz/.