Pricing change tracker

Figures reflect the nightly snapshot of October 11, 2026. The table grows with each round of checks.

Coverage so far

Nightly snapshots archived per vendor, and what the automated check flagged in that period. A flag means the page's content signature moved — it does not mean a price moved. Every flag below was followed by a manual read of the official page before we drew any conclusion.

Zoho CRM's page moved to a new address during the first week of tracking; the count covers the current address from September 23, with the original address also captured from September 21. Pipedrive's page could not be read on ten of the twenty-one nights since tracking began — most of the first week, October 5 and 6, and again October 9 through 11 — when the request returned an anti-bot interstitial instead of the pricing page. Those nights are recorded as failed fetches, not as changes. The page has read normally again after every streak so far, most recently on October 8; the current streak is the longest one yet, and the October 12 capture will show whether it clears on its own again.

What the flags turned out to be

In the same window the nightly check flagged differences on 29 occasions across every page we follow, including the email marketing platforms tracked on the same schedule. Each flag got the same treatment: pull the two raw captures, diff them, and check whether any published number moved.

• Asana (11 flags). Every one traced to a single $5.99 add-on token appearing on and disappearing from the page's markup between captures, including the runs on October 5, 6 and 7 and again on October 9 and 11. The four published tiers — $10.99, $13.49, $24.99 and $30.49 — never moved.
• ClickUp (1 flag). Tripped on the October 9 capture. The diff showed a promotional layer added around the same prices — a "Save up to 33% with yearly" banner, a money-back guarantee line and an added regular-price reference next to a discounted Core figure. Every listed tier price was unchanged; we recorded it as a verified promotion, not a price move.
• Pipedrive (1 flag). Triggered on the night the fetch method was switched to a browser-style render; the diff showed rendering differences, not price differences. Confirmed unchanged by hand the following night.
• Everything else. The remaining flags across the wider set were the same story in different costumes: token render order, computed values that resolve differently between captures, and rotating promo blocks.

How the nightly check works

1. Fetch. Each night, every tracked pricing page is re-fetched the way a browser renders it — several vendors draw their real numbers with scripts, and a plain fetch sees an empty shell. If a page returns something other than the pricing page, that night is logged as a failed fetch and stays visible as a gap rather than being counted as an unchanged night.
2. Compare. The price tokens visible on each capture are reduced to a signature and compared with the previous night's.
3. Flag and verify. A signature change flags the vendor. A person then reads the diff and re-checks the official page. Only confirmed number changes touch the tables on this site; noise is recorded as noise.

The rules behind what we record — both billing cycles, seat minimums, "not listed" when a vendor stops printing a rate — are in the pricing verification methodology, along with the most recent verification log.

Found a price we missed?

A checkout page is the only source that counts. If a number here disagrees with what the vendor is charging you today, tell us at [email protected] — we will re-verify and correct the page, and say so.

More on how the site works: about & methodology · affiliate disclosure