How to track competitor pricing changes without scraping
A practical way to notice when a competitor changes its prices or plans, using public pages, a weekly routine and a simple change log.
By DanPublished 5 min read
Pricing is the competitor move that hurts most when you miss it. A rival drops its entry plan, adds a free tier or moves a feature you compete on into a cheaper plan, and you hear about it three weeks later from a prospect who has already compared the two.
You don't need a scraper, a data vendor or a fake account to catch these changes. Almost everything that matters is on pages anyone can open in a browser. What you need is a short list of pages, a routine, and a place to write down what changed.
What "without scraping" means here
Scraping, in the sense most teams worry about, means pulling data you aren't meant to take: pages behind a login, review sites that forbid it, thousands of requests a day, or tricks to get around a block. None of that is needed for pricing, and much of it goes against the terms of the sites involved.
This guide sticks to three rules:
- Public pages only. If you can't see it without signing in, leave it.
- Look like a person, not a crawler. One visit per page per day at most is plenty. Pricing rarely changes more often than that.
- Keep the source. Every change you record links to the page and the date you saw it.
Step 1: list the pages where prices live
A pricing page is rarely the only place prices show up. For each competitor, write down:
- The pricing page, including regional versions if they have them (a separate EU or UK page, or a currency switcher).
- The plan comparison table, if it sits on its own page or behind a "Compare plans" link.
- The billing or pricing FAQ, where limits, seat rules and discounts often hide.
- Docs pages about limits: usage caps, API quotas, what counts as a seat.
- The changelog and the blog, where price changes are sometimes announced, or quietly explained after the fact.
Five to eight pages per competitor is normal. Put them in a shared doc or spreadsheet with one row per page, so anyone on the team can pick up the routine.
Step 2: save a dated copy
You can't spot a change without something to compare against. The simplest version:
- Once a week, on the same day, open each page on the list.
- Save it as a PDF or a full-page screenshot, named
competitor-page-YYYY-MM-DD. - Put the files in one folder per competitor.
It takes a few minutes per competitor, and it gives you evidence. When someone asks "since when do they offer annual billing?", you can answer with a date.
For history you didn't save yourself, public web archives often have past copies of popular pricing pages. Coverage is patchy for smaller companies, so treat it as a bonus, not a system.
Step 3: read what they publish
Some price changes are announced before they happen. Follow each competitor's changelog or release notes, subscribe to their newsletter with a work address, and add their blog to a feed reader if it has RSS. Announcements often say more than the pricing page does: why the price changed, who is affected and when.
Existing customers of a competitor sometimes hear first, by email. If your sales team talks to people who are switching, ask them to pass on anything they received.
Step 4: know what counts as a change
Not every edit to a pricing page matters. A new photo or a reworded headline is noise. These are the changes worth recording:
- A price goes up or down, on any plan, in any currency.
- A plan appears, disappears or is renamed. A new "Starter" plan often means they are going after smaller customers.
- A limit moves: seats, projects, usage, contacts, API calls.
- A feature moves between plans, especially one you compete on.
- The billing model changes: per seat to usage-based, monthly-only to annual discounts, a free trial becoming a free plan.
- The call to action changes: "Start free" becoming "Book a demo" usually means a move towards larger deals.
Step 5: write it down the same way every time
A change log only helps if people can scan it. One line per change, with the same fields every time: the date you saw it, the competitor, what changed, before, after, and the source. For example (both companies are made up):
- 14 September, Acme CRM, entry plan price: €29 per seat before, €19 per seat after. Source: pricing page.
- 21 September, Cedar Support, free plan added: none before, 1 seat and 100 tickets a month after. Source: pricing page and launch post.
Keep the log in one place the whole team can read. A spreadsheet is fine. The point is that a change is recorded once, with its source, instead of living in someone's inbox.
Step 6: decide what it means for you
Recording a change is half the job. For each one, answer three questions:
- Who does this affect? Your prospects, your existing customers, or neither?
- Does it change a comparison you rely on? If sales says "we're cheaper for small teams", check that it is still true.
- What is one thing to do this week? Update a battlecard, brief the sales team, adjust a landing page, or decide that nothing needs to happen and say so.
Most weeks, most changes need nothing. That is a useful answer too, as long as someone made the call.
When to automate it
The manual routine works well for two or three competitors. It gets hard when the list grows, when someone is on holiday, or when a change lands on a Tuesday and nobody looks until the following Monday.
A page-change tool automates steps 2 and 4: it checks the pages on your list, compares each version with the last one, and tells you when something changed. Look for one that shows you the before and after, keeps a dated history, and lets you ignore changes that don't matter.
Plainrival does this for your competitors' public pages, pricing included. It checks them once a day, keeps a text diff and a screenshot of every change, and explains in a sentence or two why a change matters to you and what you could do about it. It follows the same rules as this guide: public pages only, robots.txt respected, at most one request per second to any site.
Pricing page
Orbit Analytics · checked daily
| Plan | Sep 21 | Sep 28 |
|---|---|---|
| Starter | €29 / month | €35 / month |
| Team | €79 / month | €79 / month |
| SSO | Business only | All paid plans |
Starter plan up from €29 to €35 a month, SSO in every paid plan
Why it matters: Orbit now includes SSO from €35 a month. If yours costs less, say so on your pricing page.
Pricing page · before and after
Whichever way you do it, the routine is the same: know which pages matter, keep dated copies, record changes the same way every time, and decide what each one means for you.