How to monitor a competitor pricing page for changes

A B2B SaaS competitor quietly changes pricing every quarter. Sales finds out two weeks later through a lost-deal review. For the entire window, your quotes assume the old anchor and your battle cards lie. A 15-minute snapshot diff would have closed that gap to the same business day. This article is the exact setup that does it.

What this monitoring catches

• Headline price changes ($79 → $89).
• Plan rename or tier collapse (three tiers → two).
• Annual-discount changes (20% → 15%).
• Feature movement between tiers (a feature dropping from "Pro" to "Enterprise" is also a price change in disguise).
• New tier inserted between existing ones (the most strategic move and the easiest to miss).

2-UA setup, end to end

1. Open Site → Competitors → Add Competitor.
2. Enter the competitor domain. Add the pricing URL as the first tracked page; product comparison and case-study pages can follow.
3. Confirm Snapshot interval: 15 min (the default). This is short enough to catch deploys, long enough to avoid bot-rate triggers.
4. Enable Content diff on the page — 2-UA stores text and structured content, not just HTML, so price tokens stay greppable across redesigns.
5. Route alerts to a dedicated Slack channel shared by sales, marketing, and product (e.g. #competitor-watch). Do not use your generic monitoring channel — pricing alerts have a different audience.

The alert you wait for

On every change, 2-UA posts a side-by-side diff with the old and new snapshot. For a pricing page, you typically see one of three patterns:

• Pure number change — the easiest case; old price strikes through, new price highlighted.
• Structural change with prices unchanged — a copy rewrite, often the start of repositioning before a price move.
• Same prices, new currency split or per-seat model — the most strategic change; same dollar number masks a different unit-economics story.

Ten-minute response playbook

1. Open the diff in 2-UA, copy the before/after to a shared doc.
2. Update the battle card with the new anchor and at least one talking point on why your packaging answers it.
3. Ping the AE on every active deal where this competitor was a finalist.
4. If the change moves a feature between tiers, check whether your feature gating now looks weaker; queue a packaging review.
5. Archive the snapshot. The history view becomes your evidence trail for "they changed pricing three times in 8 months" pitches.

Three patterns that hide a pricing change from manual reviews

• A/B test rendering different prices per user — without snapshots over time, you see "their pricing" the day you happen to look.
• JavaScript-injected prices — pricing pulled from a config endpoint and rendered client-side; a one-shot crawler that ignores JS misses every change.
• Geo-redirected price pages — your office IP sees one price, the buyer's geo sees another; the competitor snapshot from a neutral location surfaces the gap.

Try a one-shot run with the free competitor watch on the competitor's pricing URL, then add the page to a project for continuous 15-minute snapshots.