How to track competitor pricing changes (and catch them the moment they happen)

When a competitor changes their pricing, it moves your win rate, your churn, and your positioning, usually before you find out about it.

Most teams learn about a price change from a lost deal, a Slack message from a confused rep, or a customer asking why the other option is suddenly cheaper. By then the damage is already done: a prospect anchored on the wrong number, a renewal conversation that starts on the back foot, a sales team improvising an answer they should have had ready.

The gap is not that pricing changes are hard to find. Pricing pages are public. The gap is that nobody is watching them continuously, and even when a change is spotted, raw data (say their Pro tier moves from $49 to $59) does not tell you what to do about it.

So the goal of tracking competitor pricing changes is bigger than noticing a page moved. It is to catch the change the moment it happens and know three things at once: what shipped, why it matters to your specific business, and what to do next. A diff alone is noise. A diff plus context is signal.

What counts as a pricing change worth catching

The headline number on a plan is the obvious signal, and also the one people over-index on. A competitor can reprice without touching a single dollar figure. Watch for all of it:

• Per-plan prices going up or down, monthly and annual.
• Plan structure changing, where a tier is added, removed, renamed, or split.
• Packaging shifts, where a feature moves from a higher tier down to a cheaper one, or the reverse.
• Usage limits and metering, including seats bundled in, API call caps, storage, and overage rates.
• Free tier changes, including a free plan appearing or quietly disappearing.
• Promotions and time-boxed discounts that will revert next month.
• Enterprise gating, where a public price becomes "contact us" or the reverse.

Each of these can change what a buyer measures you against, and most of them never show up as a number in a headline. This is also where the line between change detection and interpretation starts to matter, which is the whole question of whether a generic website change monitor is enough.

The sources to watch, and how often

Point your tracking at the pages that carry pricing signal, not just the homepage:

• The public pricing page, your primary source.
• The plan comparison or feature matrix page, where packaging changes surface first.
• The checkout or billing flow, since the price charged sometimes differs from the price advertised.
• Docs pages that spell out limits, quotas, and overage rates.
• Any pricing FAQ, where promo terms and the fine print live.

Cadence should match how fast a change hurts you. For a competitor you rarely meet in deals, a daily check is plenty. For one you are actively selling against this quarter, check hourly, because the cost of finding out a day late is a lost deal, not a stale spreadsheet. Capture a baseline snapshot on day one so every later check has something honest to compare against.

How to set up competitor pricing tracking, step by step

1. Pick your real competitors, the three to seven you actually lose deals to, not every name in the category.
2. For each one, list the exact URLs that carry pricing signal (pricing page, comparison page, checkout, limits docs). That list is the thing you monitor, not the bare domain.
3. Take a baseline snapshot of each page today, so you know what "unchanged" looks like.
4. Set a check interval per competitor using the cadence rule above, tighter for the ones in live deals.
5. Narrow what triggers an alert to the pricing region of the page, so a testimonial swap or a new footer link does not fire a false alarm.
6. Decide in advance what a useful alert has to contain, so the alert does the thinking instead of you.
7. Route alerts to where you already work and will act the same day, the channel your founders and sales lead actually read.

On step 6, a pricing alert worth reading answers four things without you opening a tab: what changed, stated as old value versus new value on a named plan; which tier or segment it touches; whether it looks structural or like a short-lived promotion; and the recommended next move. Anything less and you are back to doing the interpretation by hand, which is the part that does not scale.

A worked example: from raw diff to a decision

Suppose a competitor drops their Starter plan from $29 to $19 a month and, in the same update, folds a feature that used to be Pro-only into that cheaper Starter tier.

A pixel-diff monitor tells you the pricing page changed. True, and close to useless on its own. The interpretation you actually need reads differently: they cut entry-level price by roughly a third and moved a feature down a tier, which reaches your price-sensitive deals directly, and because it is a structural repricing rather than a banner promo, it is unlikely to revert next month. That framing points straight at a response, and the response is its own decision, covered in what to do when a competitor cuts their price. The alert's job is to hand you a decision you can act on, not a screenshot of a diff.

The practical fix: alerts that arrive already interpreted

Two common tools try to solve this and both miss for a small team. A generic page-change detector fires on any DOM diff, including a typo fix, and buries the one alert that matters under a pile that does not. An enterprise competitive-intelligence suite is built for an analyst reviewing a weekly digest, not for a founder who needs to know within the hour.

The layer that fits sits between the two. Presagon narrows the surface to what moves outcomes (pricing, packaging, and plan structure), watches it on a tight interval, and delivers every change already interpreted: what shipped, why it matters to you, and what to do next. That is the whole difference between knowing a pricing page changed and knowing what the change means for your deals.