SaaS price increases: what we have actually recorded
Not advice, not an industry average — the price moves this index confirmed, with the dates and the number of readings behind each one.
Window: 2026-10-26 onward ( days). A move counts only when the same tier was read at the old price on at least two different days and at the new price on at least two different days; a single rebuild is excluded. 38 tools have a price history in this index.
The count
- 38 confirmed price moves in the window.
- 15 of them went up; the rest went down.
- Median increase among the raises: +150.8%.
Where the raises landed
Grouped by the price before the change. This is a count of what we read, not a share of the market — tools that never moved are not in the denominator here.
| Price before the change | Went up | Went down |
|---|---|---|
| under $10 | 167 | 43 |
| $10–$24 | 183 | 123 |
| $25–$49 | 86 | 104 |
| $50–$99 | 37 | 59 |
| $100–$199 | 11 | 34 |
| $200 and up | 8 | 27 |
The largest increases on record
| Tool | Before | After | Change | Confirmed |
|---|---|---|---|---|
| buildcheap.app | $9 | $499 | +5444.4% | 2026-11-13 |
| spurnow.com | $15 | $399 | +2560.0% | 2026-11-09 |
| storekit.com | $99 | $995 | +905.1% | 2026-11-10 |
| validatethat.io | $19 | $149 | +684.2% | 2026-11-10 |
| pulserelay.pro | $8.99 | $69 | +667.5% | 2026-11-10 |
| aiwa.codes | $20 | $149 | +645.0% | 2026-11-09 |
| lingrix.com | $15 | $79 | +426.7% | 2026-11-09 |
| apexchatbot.com | $59 | $299 | +406.8% | 2026-11-10 |
What we cannot answer yet
A raise is easy to record; what happened to revenue afterwards is not. This index has 2 price moves where the same tool also published a revenue figure before and after — so any sentence of the form "a 30% increase raised MRR by X" would be invented. We are reading the entry price of every tool with a public revenue figure once a week; the first usable comparison needs a quarter of readings, not a week.
If you are looking for the average SaaS price increase, be careful with that number wherever you find it: an average across companies that publish prices is an average across survivors, and the tools that raised prices quietly are the ones least likely to publish anything at all.
What a price increase analysis has to separate
Most analyses of price increases mix four different things: the list price, the price a customer actually pays (after discounts and annual prepay), the unit the price is charged per (seat, workspace, credit), and the date the price was read. A change in any one of them produces a number that looks like a price increase and is not one. Ours are kept apart on purpose: the ladder on each tool page shows the list price per seat per month, the annual column shows what the page itself says an annual commitment costs, and usage rates are never folded into either.
Tracker, alert, or a page you read once
A price increase tracker is only as good as its reading discipline. Ours reads public pricing pages once per day per domain on a rotation, stores the price and the date, and only counts a move when the old and the new price have each been seen on two different days. That is why this page reports tens of confirmed moves rather than hundreds of "changes" — rebuilding a page without touching the price looks like a move to anything that compares two snapshots, and a tool that quietly fixes its own typo looks like a second one.
If you want a price increase alert rather than a page to check, the honest version is: we know which tools have a price history worth watching, and we read them weekly. There is no free email alert for that yet, and this page does not pretend otherwise. What exists today is the confirmed list on the moves page and the price trail on every tool page.
Track a change, or check one
Every confirmed move is listed with its dates on the moves page, and each tool page keeps the full ladder with the date each price was read. If you have seen a page that changed and we still show the old figure, report it — a correction with a source is worth more than a new row.
Prices are read from public pricing pages, logged out, once per day per domain on a rotation. We store the price, the billing period and the date — not the page.