Competitor price tracking playbook for SaaS and ecommerce teams

SaaS and ecommerce teams both say "price monitoring", but they mean different jobs.

In SaaS, the pricing page is a strategy document. A competitor has three to five plans, a handful of limits per plan, a monthly and an annual price, and maybe an enterprise tier with a starting price. Changes are rare and each one is meaningful. When a rival moves its middle plan from 79 to 99 USD per month, or cuts seats from ten to five, sales and marketing need to know that week.

In ecommerce, price is an operating number. A rival may change the price of a single product several times a month, run a promotion for a weekend, or go out of stock on a size. Changes are frequent and most of them are small. The value lies in seeing the pattern and catching the moves that affect your best sellers.

The rest of the playbook applies to both, with the differences called out where they matter.

Start with the competitors who actually show up in deals or in search results for your products, not the full market map. Five well chosen competitors watched properly beat fifty watched badly.

For SaaS, the watchlist per competitor is usually short.

• The pricing page, with the plan table selected as the element.
• The plan comparison or features page if it lists limits separately.
• The enterprise or "for teams" page if it carries a starting price.
• The terms page section on billing, if renewal and cancellation terms matter in your deals.

For ecommerce, build the list from your own catalog outward. Take your top sellers and the products with the thinnest margin, find the matching product pages at each rival, and add those. A list of thirty product URLs that map to your thirty most important products tells you more than three hundred random ones.

Keep the list in one place with an owner per competitor. When a monitor fires, someone should already know it is theirs.

A small agency example shows the idea. A consultant who runs pricing research for three SaaS clients keeps one workspace per client, with the same structure in each: pricing page, comparison page and enterprise page for every named rival. When a client adds a new competitor to its deal notes, the consultant adds three monitors in a few minutes and the record starts from that day. Because every competitor follows the same pattern, a monthly summary for each client takes minutes to put together instead of an afternoon of clicking through bookmarks.

Prices are rarely just a number. A useful record for each check captures the context that makes the number meaningful.

• The list price and any sale or struck-through price.
• The billing period, monthly or annual, and whether the page defaults to annual.
• The annual discount, stated as a percentage or as two prices.
• Plan limits such as seats, projects, usage or storage.
• For physical products, stock status, variant and shipping cost if shown on the page.

WebsiteChange stores the rendered text, the HTML structure and a full-page screenshot of every check, so the context is there even if you only selected the price block. On Growth and higher plans it also extracts prices and stock status as structured values, which makes it easier to compare numbers over time and export them.

One honest limit to know about: monitoring reads what the public page shows. If a competitor only reveals a price after login, in a quote, or inside a cart that requires an account, a responsible monitor does not get it. 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.

Price pages are noisy in their own way. Countdown timers on promotions, "only 3 left" counters, review counts, personalized recommendations and currency switchers all change between loads.

The fix has three parts. Select the element that holds the price instead of the whole page. Rely on the built-in filters, which strip dates, counters, rotating banners, cookie bars and tracking parameters before comparing. Then add ignore rules for anything specific to that site, such as a "people viewing now" line.

For SaaS pricing pages, watch for the monthly and annual toggle. If the page renders annual prices by default, that is what the monitor sees. That is usually fine, because a change in the annual price or the annual discount is exactly what you want to catch. Just make sure the team knows which view the alert refers to.

Our page on website change detection explains how element, text and visual comparison work together.

A price change nobody acts on is just trivia. Routing is where competitor price tracking becomes useful.

When a real change survives the filters, WebsiteChange writes a short AI summary, for example "Pro plan price raised from 79 to 99 USD per month; annual discount removed", and scores importance as low, medium or high. You then route by importance and by page.

• SaaS pricing changes scored high go instantly to the product marketing channel in Slack or Microsoft Teams.
• Ecommerce price drops on top sellers go by webhook into the pricing team's own tools or spreadsheet.
• Stock-outs at a rival on a product you carry go instantly to the category manager, because that is a window to sell.
• Everything scored low goes into a weekly digest so the record is complete without the interruptions.

The website change alert page covers channels and digests. Email alerts are on every plan; Slack, Teams and webhooks start on Growth.

Most price moves do not need a response. The playbook should say which ones do, before the alert arrives, so the decision is not made in a panic.

For SaaS teams, a useful rule set looks like this.

• A competitor raises prices: update the battlecard, tell sales, and consider whether your value message should lean on the gap. Do not cut your own price in response.
• A competitor lowers prices or adds a cheaper plan: check whether it targets your core segment. If not, note it and move on.
• A competitor changes limits or packaging: this is often more important than the price. Map the new limits to your plans and check which deals are affected.
• A competitor removes the annual discount: expect more prospects asking about annual terms, and make sure sales can explain yours.

For ecommerce teams, the rules tend to be numeric and owned by the pricing function: match within a set band on key items, never follow below a margin floor, and treat a rival stock-out as a chance to hold price rather than discount.

We go deeper on the SaaS side, including the sales talk track and when not to react, in track competitor pricing changes.

The fastest schedule is not always the best. Pick the frequency at which you can actually act.

SaaS pricing pages usually need hourly or daily checks. Ecommerce product pages in competitive categories may need every 15 minutes during promotions and hourly otherwise. Only very time-sensitive pages justify every 5 or every 2 minutes, which are available on Business and Enterprise.

Checks and AI summaries are monthly allowances per plan, counted as usage, and deleting a monitor does not return them. A quick budget: 30 product pages checked hourly is about 21,600 checks a month, which fits Growth. The same pages every 15 minutes is about 86,400 checks, which points to Business. Five SaaS pricing pages checked hourly use about 3,600 checks, well inside Starter. Plan details are on the pricing page.

Alerts handle the moments. History handles the story. Once a month, someone should spend thirty minutes on the record.

• Which competitors changed prices or packaging this month, and in which direction.
• Whether any promotion pattern repeats, such as end-of-quarter discounts.
• Which monitors fired only noise and need a tighter element or a new ignore rule.
• Which pages should be added or removed from the watchlist.

Every version in WebsiteChange is kept with its screenshot, text diff and visual diff, so the review can show exactly what the page looked like on a given day. Growth and higher plans export a PDF change report, and all plans export CSV, which makes the monthly summary easy to share with leadership.