Track competitor pricing changes on a pricing page and know what to do with them

When people think of pricing changes, they think of the headline number. In practice, the number is only one of several things that move, and often not the most important one.

• Price per plan, monthly and annual.
• The annual discount, which can shrink or disappear without the monthly price changing.
• Plan limits such as seats, projects, usage caps or storage.
• Feature placement, when a feature moves from a lower plan to a higher one.
• New plans, renamed plans or removed plans.
• The enterprise tier, which may switch from a listed price to a starting price or the other way round.
• Fine print under the table, such as overage fees or minimum commitments.

A competitor that keeps the price of its middle plan at 79 USD per month but cuts the included seats from ten to five has effectively raised prices for most teams. A page that removes the "two months free" label on annual billing has changed its pricing without touching a single number in the table. These are exactly the changes that a casual glance misses.

Manual checks are the default and they are unreliable. Pricing pages change rarely, so a weekly look feels pointless and gets skipped, and the one time it matters nobody was looking. Screenshots saved in a shared folder help with history but nobody compares them line by line.

A better setup has four parts.

• Select the pricing table as the watched element, rather than the whole page, so testimonials carousels and banners cannot trigger alerts.
• Add the plan comparison page as a second monitor if limits live there.
• Use a high sensitivity on the table, because a single changed number or word matters.
• Check hourly or daily. Pricing pages rarely need anything faster.

In WebsiteChange you add the URL, click the pricing table on the snapshot or enter a CSS selector, and pick the schedule and sensitivity. Every check renders the public page and stores the text, the HTML structure and a full-page screenshot. The diff engine filters dates, counters, rotating banners, cookie bars and tracking parameters before comparing, and you can add ignore rules for anything specific to that page.

If the page shows annual prices by default, that is the view the monitor records. That works in your favor, because annual discount changes are some of the most telling moves. Our website change detection page describes element and visual comparison in more depth.

A useful pricing alert answers three questions at a glance: what changed, how big is it, and where is the proof.

When a real change survives filtering, WebsiteChange writes a short AI summary and scores importance as low, medium or high. A typical summary reads: "Pro plan price raised from 79 to 99 USD per month; annual discount removed." Below it sit the text diff and the visual diff with highlighting, plus the screenshot of the old and the new version.

That proof matters later. When a sales rep tells a prospect that a competitor raised prices, they should be able to show the before and after, with a date. Every version is kept and searchable, and you can export it as CSV, or as a PDF change report on Growth and higher plans.

Route the alert by importance. A high score on a competitor pricing page should go instantly to the people who act on it, through email, Slack, Microsoft Teams or a webhook. Everything else can wait for a weekly digest. The website change alert page lists the channels per plan.

The worst outcome of good monitoring is an alert that lands in one person's inbox and stays there. Decide in advance who hears about which kind of change.

One owner per competitor keeps this from becoming a group chat. The owner confirms the change from the diff, writes two lines of interpretation, and posts it to the right place.

A battlecard that shows last quarter's prices does more damage than no battlecard, because reps quote it with confidence. Treat every confirmed pricing change as a battlecard update.

• Replace the old prices and limits, and keep a dated line of what they were before.
• Rewrite the pricing comparison for the deal sizes you typically see, for example a ten-seat team on annual billing.
• Note the direction of travel. Two increases in a year tells a different story than one.
• Link the stored before and after screenshots so anyone can verify the claim.

If you watch rivals beyond pricing, such as product pages, careers pages and changelogs, the same habit applies. Our monitor competitors page covers that wider setup.

Telling sales "Competitor X raised prices" is not enough. Reps need two or three sentences they can actually use in a call, and they need to know what not to say.

For a price increase, a good talk track is calm and factual. Something like: "Their Pro plan moved from 79 to 99 USD per month and the annual discount is gone, so a ten-seat team pays noticeably more than last quarter. Here is what the same team gets with us." The point is to let the prospect do the math, not to mock the competitor.

For a price decrease, the talk track shifts to value and fit. Reps should know which limits came with the lower price, because a cheaper plan often has fewer seats or a lower usage cap.

For a packaging change, the most useful line is usually a question: "Which plan are you looking at with them, and does it still include the feature you mentioned?" Prospects often have not noticed the change themselves.

• Stick to facts you can show from the page.
• Never disparage the competitor.
• Do not guess at the reason for the change.

Not every pricing change deserves a response, and reacting to all of them is a strategy in itself, usually a bad one.

• Do not cut your own price because a competitor did. Check first whether they target the same segment and what they removed to get there.
• Do not chase a promotion. A weekend discount or a seasonal offer is noise for strategy, even if it is signal for a sales conversation that week.
• Do not rewrite your pricing page in reaction to one competitor. Look at the pattern across the market over a few months.
• Do not broadcast cosmetic changes. A redesigned table with the same numbers belongs in the digest, not in the sales channel.
• Do not act on a change you cannot verify. If the price is only visible after login or in a quote, it is outside what public monitoring can see, and rumors are not data.

Recording a change and choosing not to act on it is still useful. Over a year, the history becomes a clear picture of how each competitor moves.

A simple test helps when the team is unsure. Ask whether the change affects a deal that is open this month, a segment you sell to, or a message on your own pricing page. If the answer to all three is no, log it, let it flow into the digest and move on. If one answer is yes, the owner writes the two-line interpretation and posts it. That small habit stops pricing changes from turning into a weekly debate and keeps attention on the moves that shape revenue.

Watching a competitor's public pricing page is ordinary market research. Doing it responsibly means staying within public pages. WebsiteChange only reads publicly reachable pages, respects robots.txt, never logs in on your behalf, never solves CAPTCHAs or gets around paywalls and access controls, and fetches politely per host.

For most teams, a handful of competitor pricing pages fits comfortably in Starter, with hourly checks and email alerts. Teams that want Slack or Teams alerts, structured price extraction and PDF change reports usually choose Growth. Plan details are on the pricing page, and the wider method for prices across many pages is in our competitor price monitoring guide.