Competitor monitoring: what to watch, how to prove a change, and a weekly digest your team acts on

What to monitor, and how often

Most of what a competitor publishes never changes a deal. Monitor the sources that carry claims your buyers repeat to your reps, and ignore the rest until the first ones run on schedule. If you have not settled who your competitors are, identify them first; this guide assumes a closed list.

Monitoring vendors set far shorter intervals. PageCrawl's guide to tracking competitor websites recommends checking pricing pages every two to four hours. That suits a tool that only alerts. A person reading every alert needs fewer of them, so read pricing alerts the day they arrive and batch everything else into one weekly review.

Watch a section, not a whole page. A full-page watcher fires on a rotated testimonial, a new blog card or a cookie banner, and after a week of false alarms nobody opens the alerts. Point the watcher at the plan table or the integration grid and it fires only when those change.

Free tools that do the watching

You need three kinds of tool: one that watches pages, one that watches news, and one that holds an earlier copy of a page you forgot to save. Each has a free option.

• Visualping watches a page, or one element on it, and emails you when it changes. The free plan covers 5 pages and 150 checks a month, and the shortest interval is 60 minutes. Checked daily, 150 checks cover four pages in a 31-day month: the pricing pages of four competitors, or pricing plus integrations for two.
• changedetection.io is open source (Apache-2.0) and self-hosted with Docker, so page count is limited only by your server. It targets an element with a CSS or XPath selector and posts to Slack, email, Discord or a webhook. It suits a team with someone who can run a container.
• Google Alerts emails you when new Google results match a query. One alert per competitor name, set to arrive at most once a day, covers press releases and news coverage.
• The Wayback Machine holds dated captures of many public pages. When a rep says "Acme used to list that feature", it is often the only proof of what the page said last quarter.

Competitive intelligence platforms such as Klue, Crayon, Kompyte and Contify do the watching and the delivery to sales in one product. The Klue alternatives guide compares them row by row. Start with the free tools; the routine below shows when they stop being enough.

Prove a change with two dated copies

An alert says a page changed. It does not prove what the page said before, and the first time you tell sales "Acme raised its price" a seller will ask how you know. The proof is two dated copies of the same section and a one-line note on what differs.

1. Save the section as plain text. Open the page in a private window so you see what a prospect sees. Copy the plan table or the integration list into a file named for the competitor, page and date: acme-pricing-2026-10-06.txt. Record the URL exactly as shown, including any region or plan parameter. Check the prices in the file against the screen; copying from a heavily scripted page sometimes drops table cells.
2. Take a screenshot with the address bar in it, saved under the same name. The text copy is what you compare; the screenshot ties it to the URL.
3. Save the second copy the same way when the watcher fires or at your next weekly review.
4. Compare the two. For a short section, read them side by side. For a long one, paste both into Claude, labelled with their dates, with the prompt below. Give it the saved copies, never a URL to fetch: a fetched page carries no date you chose and may differ from what a logged-out visitor sees.
5. Confirm each change on the live page before you tell anyone. Claude read two text files; it did not see the page.

Below are two copies of the same section of [competitor]'s [page], saved on [date A] and [date B].
List every content change in plain sentences: prices, plan limits, features added or removed,
integrations, named customers and claims. Quote the before and after text for each change.
Ignore whitespace, layout, navigation and order. If you cannot tell whether a line changed or only moved, say so.

A good answer quotes both versions for every change and names nothing that is not in the two files. Reject an answer that explains why the competitor made the change; that is a guess, and it belongs in the digest as your reading, labelled as one.

If you never saved a first copy, look the URL up on the Wayback Machine and use the closest capture as your before, citing its date. Then save today's copy, because it is the before for next month. Keep one folder per competitor with the text files, the screenshots and the note, and delete nothing.

The note needs one row per change: the before wording with its date, the after wording with its date, the date you confirmed it live, whether it matters to sales and why, and anything you could not confirm, such as a price shown only in one region. A change you could not find on the live page stays out of the note.

Sort the alerts before you read them

A week of watcher emails, news alerts and new reviews for two competitors can run to dozens of items, and most need nothing. Ask four questions of each, in this order, and only the items that pass all four reach the digest.

1. Is it new? A press release about a feature launched two months ago, a re-announced integration, a swapped homepage logo: seen before, closed. Keep a list of what you have already logged so a repeat is obvious.
2. Would a buyer decide differently? A price, a plan limit, a security certification, an integration your buyers use, or a claim your reps hear in objections all count. A post on the competitor's culture does not.
3. Am I sure what it means? A pricing page that drops "starting at $49" could mean a price rise, a move to sales-led pricing or a redesign in progress. If you are not sure, open the page and check before anyone hears about it.
4. Who has to act, and by when? Today, if a rep has an open deal the change touches. This week, in the digest. Otherwise, log it and move on.

Only the "today" case interrupts anyone. A pricing change that touches an open deal goes straight to that rep with the dated copies attached; everything else waits for the digest. Pricing changes have their own playbook in the competitor pricing analysis guide.

A sample competitor digest

The digest is the output of monitoring. One message, sent on the same day each week, where the people who act on it already read: a sales channel in Slack or Teams, or a short email. Every line gives the fact with its source and date, what it means for your deals, what you have not confirmed, and who acts by when. Below is a full digest for a week in which Acme and Emca, the two sample competitors, each changed something.

Competitor digest, week of 5 October 2026. Acme and Emca.

Standing questions. Is anyone winning the deals we lose on price? Yes: see Acme Lite above. Has any approved claim on our cards gone stale? Yes: the Emca HubSpot line. Has either competitor announced a partnership, acquisition or funding? No change.

Also seen, no action. Acme published two blog posts on customer success (acme.example/blog, 6 and 8 Oct). Emca posted four engineering roles (emca.example/careers, 7 Oct).

Five rules hold the format together. The unknown sits in its own column, because a doubt folded into the implication reads as confirmed once the digest is forwarded. Every line names one owner, and "no action this week" counts as a decision. A standing question with nothing new says "no change", so the reader knows you looked. Unknowns from last week stay on the digest until someone resolves them; one that quietly disappears reads as answered. The "also seen" footer stays shorter than the table; when it outgrows the table, tighten the sort.

Claude can draft the "what it means" column if you give it only the verified changes and tell it to add no fact that is not in the list. Write the facts and the owners yourself. Keep the sent digests in one place, such as a Claude Project, so next week's review has a dated record to compare against. When a line changes a battlecard claim, the AI battlecards guide covers how to update the card without losing the source.

One person, two competitors: the weekly routine

A product marketer who owns competitive intelligence alongside launches and messaging can monitor two competitors in one hour a week. It works when five decisions are made once and written down.

1. A closed list. Two competitors, named, chosen because they show up in your deals. One named in lost deals belongs on it even if it publishes little; a loud one your buyers never mention does not. A new name someone raises goes into a holding note with the reason, and the quarterly review decides whether it replaces one of the two.
2. Three standing questions, each tied to a decision someone makes: "Is anyone winning the deals we lose, and on what?", "Has any approved claim on our cards gone stale?", "Has either competitor changed pricing or packaging?". A question with no decision behind it is answered in chat when someone asks, not every week.
3. The watchers. A page watcher on each pricing page and each integrations page, checking daily, and one Google Alert per competitor name. That is four of Visualping's five free pages and up to 124 of its 150 monthly checks. Read changelogs and homepage headlines by hand in the weekly hour.
4. A fixed hour on a fixed day. Thursday works if sales meets on Friday.
5. A named reader. One person whose next action changes when the digest changes, usually the sales lead. Agree on the day they read it.

The hour itself:

Once a quarter, reread the standing questions and the list. Retire a question nobody acted on, swap a competitor that has not appeared in a deal for one from the holding note, and count the weeks you skipped. If the reader used nothing for a month, change the questions before you change the reader. The competitive research plan covers the deeper research a quarterly review sometimes triggers.

This routine outgrows itself in predictable ways. A third and fourth competitor turn one hour into three. A page watcher fires twenty times a week and the sorting eats the hour. The weekly review slips twice in a row, and a rep hears about a price change from a prospect before you do. Any one of those means collection and the first pass need to run without you.

Where Steve fits

Steve does the collection half of this routine. Add a competitor's website and Steve checks it daily, flags pricing, product and messaging changes, and reads competitor news, reviews and supported social sources every day, with up to 25 custom news sources per project. Each morning it posts a news summary to the Slack or Microsoft Teams channel you choose, and it pulls competitor mentions from connected call recorders and a Slack channel, so what reps hear sits beside what the competitor published. When a news item, a review or an uploaded document affects a battlecard claim, Steve drafts the update and a person approves it before reps see it.

The tradeoff is that Steve watches and summarises, but the judgement in the digest stays yours: what a change means for an open deal, and who acts by when. If two competitors fit in your hour, the free tools above are enough. If the hour no longer holds, see the Competitive Intel product page.