How to track competitor pricing changes without losing history
To track competitor pricing without losing history, store a dated snapshot of the pricing page on every check and compare snapshots, instead of overwriting a cell in a spreadsheet. The history is what lets you say when a price moved and what else changed with it.
Why a latest-price spreadsheet loses information
A spreadsheet with one row per competitor shows today's number. When Meridian's Team plan moves from $49 to $59, the old number is overwritten. Three months later nobody can say when it changed, whether it moved with a packaging change, or whether the minimum seat count changed alongside it.
What to record on each check
- The date and time of the check, and the page address.
- The full page text, or at least the plan names, prices, billing period, limits and minimums.
- Whether the page was readable. A page that failed to load is a gap, not a no-change result.
- Any promotional wording, such as “limited time”, since it explains short-lived changes.
How to read a pricing change
| Snapshot | Team plan | Free plan | Minimum |
|---|---|---|---|
| 2026-08-04 | $49 per seat per month | Listed | None stated |
| 2026-09-08 | $49 per seat per month | Listed | None stated |
| 2026-10-06 | $59 per seat per month | Not listed | 10 seats |
Three things moved in the same window: the price, the free plan and the minimum. A tracker that only stores the price would report a 20 percent rise and miss that Meridian is moving away from small accounts, which is what matters to Fieldnote.
Check what the change is evidence for
- Confirm it on a second source: the changelog, an announcement, a customer email shared publicly.
- Check whether it applies to new customers only. Pages rarely say.
- Note what you do not know, such as whether annual pricing moved.
What a pricing tracker cannot see
- Negotiated discounts and private quotes.
- Pricing behind a login or a “contact sales” form.
- Prices rendered only after a script runs, in some cases.
State these limits whenever you report a competitor's price, so a number from a public page is not read as the number buyers pay.
A cadence that matches how pricing moves
Weekly is enough for most B2B SaaS pricing pages. Daily checks mostly record that nothing happened. Check on demand before a proposal or a renewal conversation that depends on the number.
Who needs to see a pricing change
Pricing changes matter to different people for different reasons. Sales needs to know before the next proposal. Product marketing needs to update comparison pages. Finance may want to revisit assumptions about win rate at a given price. Decide in advance who reads each change, so it is not discovered by chance in a call.
Pricing history in Sigblaze
You add the pricing page to a watchlist. Sigblaze stores a baseline on the first check, keeps every later snapshot, and raises a Signal with the before and after when a price or plan changes. Signals appear in the app. Email and chat alerts are a later capability.
This piece contains no external statistics. Fieldnote and Meridian are fictional companies, and the figures in the examples are synthetic.