Example scenario
A technical sales or product team watches the same competitors every month. New products appear, partner pages change, pricing moves and new market entrants show up. Today the evidence is scattered across browser tabs, spreadsheets and copied snippets, so the next review starts almost from zero.
What matters
A useful monitoring workflow needs repeatability and provenance. The team should know which source produced a finding, when it was collected, whether it has been reviewed and how it differs from the previous state. An AI-generated sentence without that chain is difficult to trust or defend in a commercial decision.
How CompetitorRadar fits
CompetitorRadar is a local-first competitive-intelligence tool for approved-source monitoring, structured crawls, product and partner discovery, evidence review and traceable change history. Findings keep source URLs and timestamps attached, while review gates separate collected evidence from approved intelligence.
Evidence basis
The current public CompetitorRadar functional alpha implements approved-source monitoring, product/partner/channel/price/newcomer views, evidence URLs, crawl timestamps, review-gated activation, SQLite history and structured export. Its public product boundary also states that inaccessible, stale or ambiguous sources remain visible as gaps rather than being promoted into automatic truth.
What this does not prove
This does not claim complete coverage of every competitor or automatic factual correctness. Public sources can be stale, blocked or ambiguous, and some vendors still need better PDF or document acquisition. The current alpha keeps those limitations visible and still requires review before a finding becomes accepted intelligence.
Learn the monitoring method
How Can AI Monitor Competitors Without Inventing Sources? explains how to separate source collection, extraction, review and historical comparison so the evidence remains usable.
Relevant product
CompetitorRadar is aimed at repeated public-source market monitoring. Customer and opportunity context belongs in the separate ClientRadar product path.