Recurring set maintenance
A competitor-set review begins with the decisions and market boundary the list must serve. It removes stale or low-value coverage, retests watch-list companies, uses a confirmed Business Profile for bounded discovery, validates every candidate, and assigns source onboarding only after a company is accepted.
Input
A confirmed Business Profile, the current competitor tiers, active rejections, watch-list dates, and the decisions the set should inform.
Decision
Retain, retier, remove, reject, restore, accept, or watch each company with a reason and next review trigger.
Output
A bounded current set, a dated decision record, and source-onboarding tasks for accepted competitors.
Why sets go stale
The companies that helped frame a launch, market, or content plan may not remain the companies that deserve attention.
A competitor set becomes stale when companies change audience or market focus, disappear, merge, stop affecting current decisions, or remain on the list only because nobody has reviewed them. New entrants can also emerge through a product launch, category shift, geographic move, customer mention, sales objection, or repeated public publishing pattern.
This workflow is for recurring maintenance after the first competitor set exists. Use the discovery guide to learn how direct, indirect, search, and substitute competitors differ when building the initial set. Return here when the question is whether the working list is still current.
Keep the output bounded. A useful review does not produce the longest list of companies in the market. It produces a deliberate core set, a smaller adjacent tier, time-limited watch items, recorded rejections, and enough source coverage to support the decisions the team actually makes.
Cadence and triggers
The right cadence depends on market movement and decision pressure. Use a predictable baseline, then reopen the set when a meaningful trigger changes the question.
| Decision | Use it when | Review focus | Completion condition |
|---|---|---|---|
| Quarterly starting point | The market and current set are reasonably stable, but the list supports recurring planning or monitoring. | Reconfirm scope, remove stale entries, retier the rest, review watch expiry, and run discovery only for a defined coverage gap. | Every retained company still informs a named decision and every open watch item has a next review date. |
| Planning or launch trigger | A new market, segment, product, campaign, or positioning decision changes who could affect the work. | Update the Business Profile and decision boundary before reviewing direct, indirect, or both relationship scopes. | The competitor set matches the new planning question rather than the previous one. |
| Market-movement trigger | A new entrant, acquisition, shutdown, repositioning, sales objection, customer mention, or repeated public signal changes the landscape. | Validate the event, test the affected companies, and review only the tiers and sources the event could change. | The set records the evidence, decision, uncertainty, owner, and next trigger. |
| Monitoring-quality trigger | The queue is noisy, important sources stay quiet or fail, or accepted findings no longer affect decisions. | Separate source-health problems from competitor relevance, then narrow or repair coverage before expanding it. | The team can distinguish a stale company, a weak source, and a genuinely quiet competitor. |
Quarterly is a starting point, not a universal rule. Review sooner when a decision or credible event changes the market boundary; review less often when the set remains stable and no new question is being asked.
Scope reset
Discovery quality depends on the business context and scope supplied to it. Repair those inputs before judging candidates.
Decision
State the current market, audience, product or service, geography, and decision horizon. A list for sales objections may differ from one used for content planning or market-entry work.
Business Profile
Check the business description, audience, market, and positioning used for discovery. Update and confirm it when the business or the review question has materially changed; do not run recurring discovery against stale context.
Relationship
Use direct when the question concerns close alternatives, indirect when adjacent approaches or substitutes matter, and both only when the team can review the broader result set without collapsing the distinction.
Market scope
Use the scope that matches the decision. Local and global results require supporting market evidence; an unknown market should remain unknown instead of being forced into a narrowed result.
Capacity
Define the maximum core, adjacent, and watch-list sizes the team can support. Check remaining workspace discovery capacity before running a search because delivered candidate domains count against a monthly workspace quota.
Current-set review
Evaluate existing companies with the same discipline that will be applied to new candidates.
Retain
Retain a company when current public evidence and team experience show that it still affects a named audience, market, evaluation, positioning, content, or product decision.
Promote
Promote only when the defined trigger occurred and the company now affects recurring decisions. Add the evidence and the attention level it deserves.
Demote
Move a company to an adjacent tier or watch list when relevance weakens but a specific future trigger could restore it. Give that watch item an expiry or review date.
Remove
Remove companies that no longer fit the market, duplicate another record, have ceased operating, or repeatedly fail the decision test. Record the reason so removal is not mistaken for missing research.
Expire
At the review date, promote, renew with new evidence, or close the watch item. Do not let temporary curiosity become permanent monitoring scope.
Bounded discovery
Content Radar competitor discovery is a user-started, bounded search based on a confirmed Business Profile and the selected relationship and market scope.
Name the missing relationship, geography, segment, or decision coverage. If no gap remains after the current-set review, do not run discovery merely to produce new names.
Choose direct, indirect, or both and all, local, or global for the current question. Discovery uses bounded provider requests, website validation, deterministic scoring, and evidence-based market classification; it is not an always-on market scanner.
Treat each delivered company as a candidate, not a verified competitor. Previously delivered domains, live competitors, active rejections, the user's own domain, and domains already counted in the current quota period are excluded from later delivery under the supported rules.
A run may return fewer useful companies because of scope, evidence, provider availability, validation, rejections, prior delivery, or the workspace monthly quota. Record the outcome rather than widening scope automatically.
Candidate validation
A candidate belongs in the set only when a reviewer can connect public evidence to the current decision boundary.
| Decision | Accept when | Reject when | Record |
|---|---|---|---|
| Company identity | The domain represents an active company and the public site supports the identity shown. | The result is a directory, publication, duplicate, parked domain, unrelated company, or otherwise not the company being evaluated. | Canonical company name, domain, evidence URL, and any identity uncertainty. |
| Relationship | The company clearly serves the same need, audience, buying decision, or a defined adjacent approach under the selected relationship scope. | The relationship depends on topic overlap, vague category language, or an unstated assumption. | Direct or indirect rationale in one evidence-based sentence. |
| Market | The selected all, local, or global scope is supported by public evidence where a narrowed market was requested. | The candidate is outside the market or its market is unknown under a local or global run. | Observed market evidence and unknowns without forced classification. |
| Decision value | Adding the company changes a current comparison, monitoring need, planning question, or watch decision. | The company is merely interesting or the team cannot name a decision it could affect. | Tier, owner, review cadence, and the decision the company can inform. |
| Capacity | The team can support the competitor's sources and review burden without weakening stronger coverage. | The set is already at its useful capacity and no lower-value company should leave. | The remove-before-add choice and any deferred watch trigger. |
Reject with a concrete reason. Active rejections prevent the domain from returning in later discovery until the candidate is restored, reducing repeated review work.
Acceptance and sources
Company discovery and publishing-source discovery are separate decisions with different evidence and limits.
Accept
Accepting a candidate creates or reuses the Competitor and adds a starter Website source through the supported transaction. The Website source is a discovery starting point, not a fetchable monitoring feed.
Discover
Run bounded source discovery against the public site to look for usable RSS or Atom feeds and sitemaps. It checks fixed common paths and accessible robots.txt declarations; it does not crawl arbitrary links, render JavaScript, bypass access controls, or guarantee full coverage.
Promote
Explicitly promote useful structured-source candidates and record source type, expected publishing behavior, owner, known limits, and first healthy outcome. Do not add every discovered source by default.
Recover
Use a user-provided Google Alerts RSS feed, manual candidate or Article capture, or manual sitemap and URL-list recovery where appropriate. Keep partial or blocked coverage visible.
Handoff
Once the company and sources are accepted, the competitor content monitoring workflow owns source health, intake, qualification, and routing. This set review returns only when the company list or its market boundary needs reconsideration.
Worked review
This generic example shows the sequence and does not claim a real market outcome.
Scenario
A SaaS team enters quarterly planning with eight core competitors, three adjacent companies, and four watch items. One core company has left the target segment, two watch items have reached their review dates, and sales repeatedly mentions a newer company in active evaluations.
The team confirms that the decision concerns direct alternatives for the same operations audience and global market. It updates and confirms the Business Profile before discovery.
The company that left the segment is removed with evidence and a dated reason. One expired watch item is closed; the other is renewed because a defined launch trigger appeared.
The team runs a bounded direct, global discovery to test the remaining gap. Delivered candidates are reviewed against identity, relationship, market evidence, decision value, and capacity.
The company already appearing in sales evaluations is accepted into the open core slot. Unrelated tools and a company with unknown global relevance are rejected with reasons; one plausible adjacent company receives a time-limited watch date.
The accepted company receives its starter Website source. The owner discovers and promotes a useful public feed and sitemap, records their coverage limits, and hands source health to content monitoring.
Resulting decision
The review ends with the same bounded core-set size, one renewed watch item, explicit rejections, supported-source onboarding, and owners for follow-up. It does not claim that discovery will continue finding companies between user-started runs.
Ownership and history
The product can preserve scoped evidence and lifecycle actions; the team remains responsible for competitive judgment and the final set design.
Content Radar stores the confirmed Business Profile, Discovery Runs, Competitor Candidates, persistent rejections, accepted Competitors, starter sources, and supported lifecycle changes. Workspace History records supported candidate, profile, competitor, source, and Article actions with actor and time, and eligible entity versions can be restored within the documented seven-day window.
Workspace History is not a full workspace rollback and does not replace a set-review record. Keep the review date, decision question, tier choices, rejection reasons, watch expiries, source-onboarding owners, and known uncertainty in the team's working output.
Humans decide whether a company is strategically relevant, which tier it deserves, whether another should leave, and which public sources justify ongoing attention. The product supports bounded discovery, review states, source onboarding, health evidence, and traceability; it does not continuously discover the market or make the final strategic judgment.
Choose this approach when
Choose another approach when
Quarterly is a practical starting point for many teams, but the set should also be reviewed after a material market, product, audience, geography, sales, or planning change. Stable sets may need less frequent full reviews.
No. Competitor discovery is a bounded, user-started run based on a confirmed Business Profile and the selected direct, indirect, or both relationship plus all, local, or global market scope.
Initial research teaches the competitor types and builds the first set. This workflow begins with an existing set, removes stale coverage, retests tiers and watch items, runs discovery only for defined gaps, and hands accepted companies into source onboarding.
Results are bounded by the selected scope, available public evidence, provider responses, validation, previously delivered domains, live competitors, active rejections, and the workspace monthly delivered-candidate quota. A smaller reviewed set is preferable to padding the list with weak matches.
The supported acceptance path creates or reuses the Competitor and a starter Website source. The team then runs bounded source discovery, promotes useful supported structured sources, records limitations, and hands ongoing source health to competitor content monitoring.
Continue exploring
Move from this resource into the source, workflow, comparison, or team context that matches the next decision.
Related sources
Related use cases
Related industries
Monitor approved sources, review new findings, and connect useful signals to clear actions.