Competitor Analysis Template

A competitor analysis template works best when every row has a source, date, and next action.

Copy this structure into a document or workspace and create one row per competitor. Keep evidence close to the statement it supports. If a field is unknown, write unknown; do not fill it with a guess.

Record the competitor’s category, target segment, geography, business model, and closest alternatives. This prevents a feature comparison from treating very different companies as if they were interchangeable.

Add a short reason for monitoring the company. It might be a shared customer segment, a product overlap, a pricing comparison in active deals, or an emerging category move. Review this reason when your strategy changes.

Capture the homepage headline, supporting promise, named audience, category term, differentiators, proof point, and primary CTA. Note repeated language across product, solution, and comparison pages. Repetition can show what the company wants prospects to remember, but it is not proof that the claim is true.

Write the observation and interpretation separately. “The page now leads with workflow automation” is evidence. “The competitor is abandoning its original segment” is a hypothesis that needs more than one page.

Record plan names, visible price, currency, billing period, value metric, usage limits, feature gates, discount language, free access, minimum commitment, and sales qualification. Preserve the assumptions behind any comparison.

List major capabilities, integrations, use cases, customer stories, review themes, hiring topics, and launch activity. Focus on what a buyer can verify. Avoid turning a logo or a job posting into a conclusion about adoption or roadmap certainty.

Add a dated row whenever a meaningful public change occurs. Include the page type, previous state, current state, source URL, importance, confidence, and owner. A simple change log makes it possible to detect sequences instead of reacting to isolated edits.

Use a monthly review to remove stale assumptions, promote recurring signals, and lower the priority of sources that never change a decision. A template should become more useful with use, not more complicated.

Use the template as the schema for your monitoring workflow. Automate the recurring collection of public pages, then reserve human time for classification and decisions. This keeps the data fresh without asking analysts to retype the same company description every week.

Ryvalise provides the evidence layer by crawling competitor websites, classifying pages, preserving source snapshots, and summarizing meaningful changes. Use it to keep the change-log fields current while your team owns the strategic interpretation.

The most useful improvement to a basic template is provenance. Add the exact page, observation date, and confidence beside any claim that might influence product, pricing, or sales. If a statement is derived from several pages, list each page rather than hiding the chain of reasoning.

Add a freshness rule as well. A current pricing row may need weekly review, while a company-history row may need only quarterly review. The template should tell you when a field must be checked again, not just where to store the last answer.

Analysts may need detailed evidence, but executives and sellers need a compact decision view. Use a summary row, a few high-consequence findings, and links to the research record. Do not copy every observation into the headline section. The template works when different readers can use the same source without receiving the same amount of detail.