SaaS Pricing Page Monitor & Change Tracker

A SaaS pricing tracker that watches competitor pricing pages on a schedule and tells you the day a price moves. Each run extracts every price point on the page (amount, currency, monthly or yearly period, and the plan text around it) and reports only what was added or removed since the last run.

The classic story: a competitor raises prices (or launches a cheaper tier) and you find out weeks later, from a customer. Whoever notices a pricing move first gets to react first — reposition, match, or take the margin.

Who uses this SaaS pricing monitor

• Competitive watch: weekly schedule on 5-10 competitor pricing pages → you only hear about it when something moved.
• Renewal talks: watch your own vendors' pricing pages — a silent price increase before your renewal is negotiation material.
• Your own site: point it at your own pricing page as a regression check after deploys.

How the pricing page change monitor works

1. Fetches each pricing page you list (plain HTTP, respects robots.txt by default).
2. Extracts every visible price point: amount, currency ($, €, £), billing period (monthly / yearly, English and French), plus the text around it (usually the plan name).
3. Compares against the previous run's baseline and outputs only pages where a price was added or removed — a price change shows up as one removed + one added.

Input example

{
  "pricingUrls": [
    "https://competitor-a.com/pricing",
    "https://competitor-b.com/tarifs"
  ]
}

The defaults work as-is.

Output example

{
  "url": "https://competitor-a.com/pricing",
  "changed": true,
  "pricesAdded": [
    { "key": "$24/month", "currency": "$", "amount": 24, "period": "month", "context": "Starter $24 per month For individuals" }
  ],
  "pricesRemoved": [
    { "key": "$19/month", "currency": "$", "amount": 19, "period": "month", "context": "Starter $19 per month For individuals" }
  ],
  "pricesFound": [
    { "key": "$24/month", "currency": "$", "amount": 24, "period": "month", "context": "Starter $24 per month For individuals" },
    { "key": "$79/month", "currency": "$", "amount": 79, "period": "month", "context": "Pro $79 per month For teams" }
  ],
  "checkedAt": "2026-07-06T16:00:00.000Z"
}

A SUMMARY record in the run's key-value store gives the run picture: pages monitored, pages changed, pages skipped (with reasons).

Data you get per change

Per page: url, changed, pricesAdded and pricesRemoved (each with key, currency, amount, period, context), the full pricesFound list, and checkedAt. A price increase shows up as one removed point plus one added point, so you always see the before and the after.

Fair use & data

• Fetches only the public pricing pages you explicitly list; robots.txt is respected by default.
• No personal data of any kind is collected.
• Inputs are hard-capped (20 pages per run) so runs stay bounded and predictable.

FAQ

JavaScript-only pricing pages? Pages that render prices exclusively client-side may yield few or no price points — check pricesFound after the first run; if it's empty, that page needs a browser-based tool instead.

Currency support? $, € and £ with English and French period wording (per month, /mo, billed annually, par mois, par an...). Other currencies show up as unspecified-period points as long as they use those symbols.

How do I reset the memory? Set a new monitorId — each ID keeps its own baseline.