How to monitor a competitor's pricing page without drowning in noise

Pricing pages don't announce themselves. A competitor drops a plan, folds a feature into a lower tier, or quietly shortens the free trial from 14 days to 7 — and the first person on your team to notice is usually a rep who lost a deal to it. By then it's old news internally, and you're reacting instead of deciding.

The obvious fix — a generic page-change monitor — usually makes things worse. Pricing pages are among the noisiest pages on the web: A/B tests, rotating logos, currency toggles, "most popular" badges that move with the season. A tool that alerts on any change will bury the one change you cared about under thirty you didn't.

Here's the setup that works.

1. Write the prompt for the change, not the page

The single biggest lever is describing what counts instead of what to watch. Compare:

Watch acme.com/pricing.

versus:

Watch acme.com/pricing. Tell me if a price, a plan limit, or the trial length changes, or if a plan is added or removed. Ignore design changes, testimonials, and copy edits.

The second prompt gives the semantic tier something to judge against. When the page re-renders with a new testimonial, the check runs, concludes nothing you asked about changed, and stays silent. When the per-seat price moves from $12 to $15, you get a sentence saying exactly that.

A good pricing prompt names three things:

• The numbers: prices, seat minimums, usage limits, overage rates.
• The structure: plans added, removed, renamed, or merged.
• The terms: trial length, "contact us" thresholds, annual-only restrictions.

2. One competitor, one monitor

It's tempting to write one prompt covering five competitors. Don't. Each pricing page has its own rhythm and its own noise profile, and each deserves its own alert history — when your pricing lead asks "when did they drop the starter plan?", the answer should be one monitor's timeline, not an archaeology project.

Five competitors means five monitors. On the Pro plan that leaves room for twenty more.

3. Match the check interval to the page's rhythm

Pricing changes ship during business hours, usually alongside a launch. Overnight checks mostly confirm nothing happened. A practical cadence:

• Steady state: daily is plenty. Pricing moves a few times a year.
• Launch season: when a competitor is teasing something — conference coming up, changelog suddenly busy — drop to hourly for the week.

The check interval is per-monitor, so you can run your closest competitor hot and the rest daily.

4. Pick the tier by how the page is built

• Static pricing tables render fine without JavaScript: use the semantic tier and let the prompt filter noise.
• Pricing calculators and pages that hydrate their numbers client-side are empty shells to a plain fetch: use the browser agent tier, which renders the page in a real browser before checking it.
• If you genuinely want every text change on the page — some teams do, for the archive — run a second monitor on exact diff alongside the semantic one.

5. Let the alert be the artifact

A modsignal alert is one sentence with the before, the after, and a confidence score attached:

Acme raised the Team plan from $12 to $15 per seat and removed the monthly billing option. New since July 19.

That's forwardable as-is. The goal of the whole setup is that when this email arrives, nobody on your team has to open the pricing page to verify it — the evidence came with the claim.

The competitor pricing watch pack ships with prompts like these ready to edit. Free plan covers three monitors — enough for your top three competitors — at app.modsignal.io.