How to Track Competitor Pricing Changes (Without Checking Manually)

You have probably done this before: a competitor quietly moves their $49 plan to $59, folds two tiers into one, or slaps a “Contact Sales” label on what used to be a self-serve price — and you find out three weeks later from a customer, or worse, a lost deal. Tracking competitor pricing isn’t hard because the information is hidden. It’s hard because it’s public, changes without warning, and nobody on your team has “check five pricing pages every Monday” as an actual job. This is a practical guide to doing it properly — where prices actually live, why they move, how to catch changes before they go stale, and how to keep records that hold up when someone asks “when did they change this and what else moved with it?”

Where competitor prices actually live

The obvious spot is the pricing page, but that page is rarely the whole story. Pricing information tends to be scattered across several places, and a serious tracking practice checks all of them, not just the URL with “/pricing” in it.

• The pricing page itself— but check every tab. Monthly vs. annual toggles often hide the real story: a vendor can hold the monthly number steady while quietly raising the annual discount required to hit that headline price, which is effectively a price increase with no visible digit change.
• Plan tier boundaries— usage caps, seat minimums, and feature gates that move between tiers. A tier can get more expensive without the price changing at all, simply by moving a popular feature from the mid tier to the top tier.
• The “Contact Us” enterprise tier— you can’t see the number, but you can watch what triggers it. If the self-serve ceiling drops (e.g., the top listed plan now caps at 10 seats instead of 25), that’s a signal the vendor is pushing more of its base into sales-assisted pricing.
• Regional and currency variants— pricing shown to a UK IP, or in EUR, or on a localized subdomain, can differ from the US/USD default. If a competitor sells internationally, check at least one alternate region occasionally.
• Promo banners and discount codes— a site-wide “20% off annual” banner is a pricing signal even though it never touches the pricing page’s base numbers. Banners that appear and disappear on a schedule often correlate with the end of a fiscal quarter.
• Changelog, release notes, and status/blog posts— vendors sometimes announce packaging changes there before (or instead of) updating the pricing page copy.

Why manual tracking fails

The failure mode is rarely dramatic; it’s attrition. A few forces work against anyone trying to do this by hand:

Frequency and forgetting

Pricing pages don’t change on a schedule, so there’s no natural cue to go look. A weekly calendar reminder survives about a month before it gets skipped during a busy sprint, and once it’s skipped once, it’s easy to skip again.

Silent changes

Most pricing changes ship with zero announcement. There’s no press release for moving a plan from $79 to $89 — it just happens between one page load and the next, and unless you happened to look at the right moment, you have no record it ever occurred.

Packaging over price

This is the one manual trackers miss most often: they eyeball the dollar figure, see it’s unchanged, and move on. But the number is only part of the offer. If “unlimited projects” quietly becomes “unlimited projects (up to 50 users)”, the price is identical and the offer is worse. Tracking pricing well means tracking the whole tier — features, limits, and support levels included — not just the digits.

No institutional memory

Even when someone does notice a change, if it isn’t written down anywhere durable, it lives in one person’s head until they forget it or leave. Three months later nobody can say with confidence whether a competitor raised prices once or twice this year.

Concrete methods, from lightweight to rigorous

Bookmark-and-check

The floor: keep a bookmark folder of every competitor’s pricing page (and their top 2–3 alternative-comparison or plan pages) and actually open them on a recurring cadence. This works only if the cadence is real — a recurring calendar block, not a vague intention.

Screenshots over time

A step up: screenshot the full pricing page each time you check, and save it with a date in the filename. This costs almost nothing and gives you something bookmark-and-check doesn’t — a visual diff you can hold up against the current page. It won’t catch changes between checks, but it turns “I think they changed something” into “here’s the before and after.”

Change-detection on the URL

The most reliable manual-adjacent method is a change-detection tool pointed at the exact pricing URL (and each pricing-relevant tab or region variant, since most tools only watch the URL you give them, not every tab behind it). These tools diff the page’s text or HTML on an interval and alert you when something moves. The catch is tuning: pricing pages often have rotating testimonials, dynamic “X customers this month” counters, or A/B-tested layouts that trigger false positives. Scoping the watch to the pricing table element specifically, rather than the full page, cuts down on noise considerably.

Watch packaging, not just the number

Whatever method you use, build the habit of reading the full tier — feature list, usage caps, seat counts, support tier — every time, not just the price row. A packaging restructure (three tiers becoming two, a feature moving up a tier) is often a more meaningful competitive signal than a price move, because it tells you something about where the competitor thinks their margin or their ideal customer profile is shifting.

What to record when you catch a change

A change is only useful if it’s captured in a form someone else (or future you) can act on without re-deriving the context. At minimum, log:

• Date observed (and date first live, if you can narrow it down from a screenshot gap or a cached version)
• Which tierchanged — name it exactly as the competitor names it
• Old value → new value, for both price and any packaging elements that moved alongside it
• What else moved— seat limits, feature inclusions, support level, trial length, annual discount rate
• Source— the URL and, ideally, a screenshot or archived snapshot as proof
• Your read on why— a one-line hypothesis (margin pressure, new competitor response, upmarket push) is more useful six months later than the raw fact alone

Keeping this in a single running log, rather than scattered Slack messages, is what makes it a real competitive record instead of tribal knowledge. If you want a starting structure, the competitor analysis template lays out fields for exactly this kind of change log alongside broader competitive notes.

Ethical and legal boundaries

Everything above works from public information — pages any visitor can load, no login required. That boundary matters and it’s worth stating plainly: don’t use trial or paid accounts to access gated pricing details not meant for public view, don’t misrepresent yourself to a competitor’s sales team to extract a quote under false pretenses, and don’t scrape in a way that violates a site’s terms of service or hammers their infrastructure. Public pricing pages, public blog posts, and public changelogs are fair game. Anything you had to pretend to be someone else to see is not.

How to automate this

Everything described so far is a discipline problem as much as a tooling problem — the methods aren’t complicated, but sustaining them across dozens of competitors, tiers, and regions is where manual tracking quietly falls apart. This is the specific problem Radaris built for: it never stops watching the pricing pages, tabs, and packaging details you’ve pointed it at, and it surfaces what changed and why, rather than just flagging that a page was touched. Because Dozier cites every claim it produces back to a public source, when Radar tells you a competitor moved a tier from $79 to $89, you can trace that claim straight back to the page it came from — the same discipline recommended above, just running continuously instead of on whatever cadence you can personally sustain. If pricing is one signal you’re watching among several, Sweephandles the broader job of learning a market from cited public sources in the first place. And if you’re building out a fuller competitive-tracking practice beyond pricing alone, the competitive intelligence playbook covers how pricing tracking fits alongside product launches and messaging shifts as part of one system, including the sibling practices of tracking competitor product launches and tracking competitor messaging.