Competitor Pricing History: How to See Old SaaS Pricing

To see a SaaS competitor's pricing history, open archived copies of its pricing page in the Wayback Machine, read each one for tier names, prices and limits, and compare them in date order. Then keep watching the live page so you never reconstruct history by hand again. BigIdeasDB Desktop runs that workflow for you. In a November 2, 2026 BigIdeasDB Desktop run on 5 well-known SaaS pricing pages over roughly 5 years, the entry paid tier went up on 4 of 4 products where prices were readable, and the plan structure changed on all 5.

Almost every guide on this topic is written for e-commerce: product price trackers that chart a sneaker or a TV. A SaaS pricing page is a different object. The headline number matters less than the seat limits, usage caps, add-ons and which feature moved up a tier. This guide is about reading that object over time, with real output instead of advice.

How can I see a competitor's pricing history?

How do I check historical pricing by hand, and where does it break?

The manual method takes about 30 minutes per competitor and works well for one or two pages. You do not need any software to start.

1. Go to the Wayback Machine and paste the pricing URL, for example example.com/pricing.
2. Pick one capture per half year from the calendar. A capture is a saved copy of the page on a given day.
3. Open each capture and write down, per plan: name, price, billing period (monthly or annual), seat or usage limits, and any feature that is marked as new or moved.
4. Put the rows in a sheet with the date as the first column.
5. Diff the rows. Mark every price move, every renamed plan, every added or removed tier.
6. Write one sentence per change on what you think it means.

Founders already do exactly this. One r/SaaS commenter described pulling monthly snapshots of a competitor homepage from the archive's capture index and running a diff on the headline, subheadline and button text. Another keeps a sheet with date, plan, price and limits.

The manual route breaks in four places:

• Scale. Ten competitors at 10 captures each is 100 pages to read.
• Pages that draw prices with JavaScript. The archive saves the HTML, not always the script output, so some captures show plan names and no prices. In our run this hit Zapier (3 of 12 sampled captures) and Slack (9 of 12).
• Billing toggles and currency. A capture can show the annual price, the monthly price, or a euro price served to the archive's crawler. Compare like with like.
• It is a one-off. The moment you finish the sheet, it starts going stale. That is the problem behind the r/SaaS thread on how to keep track of pricing changes.

What we ran: the pricing history of 5 SaaS products

We queued 8 pricing pages in BigIdeasDB Desktop (Notion, Calendly, Zapier, Slack, Mailchimp, Webflow, Canva, Linear) and sampled 12 captures per page, 2 a year across 5 years. The archive's own rate limits slowed the run: Desktop paces requests at about 2.5 seconds each, and when the archive asked it to slow down, it stopped asking rather than retrying through a block. By the time of writing, five pages had finished. Mailchimp returned an archive list that stopped in May 2021 and no readable captures, and Webflow and Canva were still throttled in the queue, so this article reports only the five that finished. We chose products founders commonly benchmark against and whose pricing URL has stayed in one place.

Every number below is what Desktop read from the archived page text, dated by the capture that first shows it. A change is dated by the first capture that shows it, so the real change happened somewhere between that capture and the one before. Where a page returned no prices, the table says so instead of guessing.

How much did SaaS entry prices change? Then versus now

Slack is the honest failure of the run. Nine of its twelve sampled captures archived with no prices, so we can describe where it is now and what it added, but we cannot tell you how much its entry price moved. That is the real shape of this method: strong on pages that serve prices in plain HTML, weak on pages that do not.

What did the pricing histories show? Five findings

1. Every readable entry tier went up, and three of four went up exactly 25%

Entry paid prices rose on 4 of 4 products where the page gave a price, with a median change of +25%. Notion, Calendly and Linear each moved their cheapest paid plan from $8 to $10. Zapier moved from $19 to $19.99, a 5% change that looks like a rounding choice rather than a repricing. Seat-based SaaS prices ratchet up in small, round steps, and the steps are rarely announced on the pricing page itself.

2. The mid and top tiers moved more than the entry tier

Business-level tiers rose 33% at both products that show a clean series. Notion Business went from $15 to $20. Linear Business went from $12 to $16 in under two years, in two steps of $2. If you only watch the cheapest plan, you miss where the money moves.

3. Tier structure changed on 5 of 5, more often than price

Plans were renamed, merged, added or removed on every product. Calendly collapsed a $8 tier and a $12 tier into one $10 tier. Notion deleted a $4 tier. Zapier rewrote its plan lineup more times than it changed a headline price. A price history that only tracks numbers misses this, because a renamed or merged tier changes what a buyer compares.

4. AI arrived on the pricing page as a feature line, not as a priced add-on

4 of 5 products now list AI features on the pricing page, but only one ever showed AI as its own priced tile. Notion displayed a "Now with AI connectors" plan at about $10 in its Jan and Jul 2025 captures and had removed it by Jan 2026, folding AI trials into the Free plan and Agent into Business. Linear put AI agents on the Free plan in Jan 2026 and added Triage and agent features to Business. Slack's mid tier is now named around AI. The pattern is AI as a reason to upgrade, not as a separate line item.

5. Free plans survived, but what they contain kept changing

All 5 still have a free plan. Contents moved on several: Notion's free plan lost and regained collaboration lines, Zapier renamed Free to Free forever, and Linear had no Free plan in three consecutive sampled captures before bringing one back. For a founder deciding whether to offer a free tier, the lesson is that incumbents treat it as a dial, not a fixed promise.

Product by product: what each history shows

Notion is the cleanest example of tier surgery. In November 2021 the page showed Personal Pro at $4 and Team at $8. By December 2022 Personal Pro was gone and a Business plan at $15 had been added. The cheapest plan with collaboration read $8 in the Dec 2023 capture and $10 in July 2024, and Business reached $20 in July 2025. One note on method: the Jan 2025 capture was served in euros, so we compared dollar captures only.

Calendly shows the fewest price moves and the most packaging moves. Teams stayed at $16 for the entire window. What changed was the self-serve ladder: Premium and Pro became Essentials and Professional in Jan 2022, then Standard replaced both in Jan 2024. Features such as automations, reminders and payments shifted between tiers in the captures from 2025 and 2026.

Linear gives the best price series. Its Business tier appears in the June 2024 capture at $12 and reads $14 six months later and $16 a year after that. The same capture that raised the entry plan from $8 to $10 also moved Issue SLAs from the Enterprise tier to Business. A feature moving down a tier while the price goes up is the kind of change a headline-price tracker never shows.

Zapier is hard to read because the first three sampled captures (Nov 2021, Jan 2022, Jul 2022) archived with no prices. From Jan 2023 on, it reads Starter at $19 and Professional at $49. By Jul 2026 the page shows a single entry plan from $19.99 plus a Free forever plan. Plan names changed more than any number.

Slack is a gap. Only the June 2023, July 2026 and November 2026 captures returned prices. The latest shows Pro at $8.75, a mid tier at $18 named around AI, and Enterprise+ at $45. Without a readable 2023 entry price we do not state a change.

How do I automate competitor pricing history with BigIdeasDB Desktop?

BigIdeasDB Desktop runs the Wayback workflow on your own computer and saves every capture with its source. It is a local-first research app for Mac and Windows that connects to the AI agent you already use (Claude, Claude Code, ChatGPT desktop, Codex or Cursor) through a local MCP server. There is no AI bill from us, because it uses the plan you already pay for. Pricing History is one of its research modules.

There are two ways in. For a quick look at one page, use the ad hoc tools:

1. wayback_snapshots lists the captures of a URL, one per distinct page body by default, so you skip near-identical copies.
2. wayback_page reads chosen captures, or an evenly spread set, and pulls out prices and plan names.
3. wayback_timeline shows what each capture displayed and what moved since the one before.
4. wayback_diff compares any two captures: which price-like figures and plan names moved, and which lines were added or removed.

For competitors you want to keep, use the Pricing History library, which is what produced the table above:

1. pricing_target_add saves a competitor's pricing URL with a label.
2. pricing_run fetches the archive list, then samples captures by year (we used 5 years, 2 a year) and reads the plans from each. It reports the request count and a time estimate up front.
3. pricing_timeline_get returns a step line per plan with raised, cut, renamed, added and removed flags, the capture dates, and gaps of six months or more with no archived copy.
4. pricing_compare_get compares two snapshots plan by plan, with feature lines added or removed per plan. pricing_snapshot_get returns the stored page text so you can read an unclear capture yourself.

When a capture is unreadable, Desktop saves it as "could not read" and counts it, which is how we know Slack had 9 of 12. A missing capture is a gap, not a price change. You can also correct a misread plan with pricing_plans_set, and several of our rows needed a human check for exactly that reason: the reader sometimes takes a heading as a plan name.

Then ask your agent to summarize. A prompt that works: "For the pricing target Notion, get the timeline, list every raised, cut, added and removed plan with its date, and tell me which change most affects a tool priced under $15 a seat." The agent calls the tools, reads the timeline, and writes the summary. Our MCP setup guide covers connecting Claude, and the founder MCP roundup compares the options.

See the live price on the pricing page. Desktop is included with Basic and Pro, or sold as a one-time add-on, and can be activated on up to 3 computers.

How can I track my competitors' pricing from now on?

History tells you what already happened. A watch tells you the day it happens again. The archive lags, so for the live page use the watch tools: pricing_target_watch turns on re-checks for a saved page, pricing_recheck_due runs the checks that are due, and pricing_changes_get lists what changed since the last read. pricing_competitors_get shows all your tracked pages in one place.

Two habits from the r/SaaS threads are worth copying. First, watch the pricing table, not the whole page, so testimonial swaps and cookie banners do not fire alerts. Second, log the limits and caps next to the price, because one commenter put it well: "the limit changes (seats, usage caps, what moved to a higher tier) usually tell you more than the headline price."

How do I read a pricing history without fooling myself?

• Compare the same billing period. A move from an annual price shown to a monthly price shown looks like a hike and is not one. Check the capture text.
• Compare one currency. The archive's crawler can be served euro prices on some dates. We dropped the euro capture from the Notion comparison.
• Read limits before prices. Seat caps, task caps, storage and history limits are where tiers really differ. Notion's free plan went from unlimited blocks to a trial to a different set of limits, with the same $0 price.
• Watch for moved features. A feature that drops a tier while the price rises is a repricing in disguise.
• Count gaps as unknown. If there is no capture for six months, you cannot say when a change happened, only that it happened between two captures.
• Check hidden pricing separately. Some categories do not publish prices at all. As one commenter said about their space, most competitors do not publish prices, so the archive has nothing to read.

What founders say about tracking competitor pricing

The question behind this article is asked again and again in r/SaaS, often after a deal is lost. Four of the threads that rank for it share one pattern: someone found out late.

"We lost a deal last quarter because a competitor had dropped their pricing three weeks before the call."
– r/SaaS

"We got caught out last month because a competitor quietly dropped their entry tier by about 20 bucks and i found out from a prospect on a call."
– r/SaaS

"The piece that no tool solves well is interpreting the change. A competitor drops their price by 40%, is that desperation or a strategic land-and-expand move?"
– r/SaaS

"We do a formal competitor pricing review every quarter, 90 minutes, with the whole product team. Tooling surfaces the signals, the meeting is where we actually decide whether to respond."
– r/SaaS

"I do market intelligence, and pricing pages are one of the slower signals for me. By the time a tier changes, there have usually been hints elsewhere."
– r/SaaS

Two things follow. A history gives you the context for the second quote, because a 20 dollar drop reads very differently if the same plan rose 25% two years earlier. And the third quote is the job for your AI agent: the monitoring is the easy part, the interpretation is the work.

What price increases look like from the customer side

In BigIdeasDB's structured pain points, about 130 of roughly 51,800 rows explicitly mention a price increase, price hike, pricing change or forced upgrade. That is under 0.3%, so price hikes are not a top complaint. They are a specific one. The count is 68 in Capterra pain points, 54 in G2 insights and 7 in Reddit pain points. A wider pricing match (expensive, overpriced, hidden fee, paywall, plus the increase terms) finds about 570 rows, roughly 1.1% of the same base.

Read that as a floor. These are extracted pain points from our 1M+ complaint corpus, a summarized layer rather than every raw review, so the real number of people grumbling about price is larger. It still gives you a useful rule: a rise is rarely what makes a customer leave, but a rise combined with a feature moved up a tier or a forced upgrade is. That is the pattern in the Linear and Notion histories above. For how pricing models differ by product type, see our AI SaaS pricing models breakdown.

Using a pricing history to set your own price

A history turns "what do competitors charge" into "how do they move", which is the question you need answered before you set or change a price. Use it in this order:

1. Find the ladder. Note each competitor's tiers and the step between them. If the step between entry and business tiers is $10 to $20, your own step has to make sense next to that.
2. Find the anchor. In our five, the entry paid anchor settled at $10 per seat per month for three of them. That is a data point about where this buyer expects the first paid step, not a rule.
3. Find the move. If every competitor raised 25% in the last few years and you did not, you are cheaper by drift, not by decision.
4. Find the limits. Copy the caps that drive upgrades, not the price. The free plan and the first paid plan are separated by limits.
5. Decide, then log your reason. Write the price, the date and one sentence on why, so next year's you can read it as a history too.

For the surrounding work, see our guides on SaaS pricing strategies, estimating competitor revenue, running a competitor analysis and what to do when a funded competitor enters your market. If you are still choosing tools for that work, the best competitor research tools for founders list puts BigIdeasDB first.

Methodology and data sources

What this data cannot tell you: why a company changed a price, what customers it lost, or what enterprise buyers pay. Pricing pages show list prices, not negotiated ones. Treat the findings as evidence about public list prices, from five products, not a market-wide rate.

Frequently Asked Questions

Related Reading

BigIdeasDB Research. (2026). Competitor Pricing History: How to See Old SaaS Pricing. BigIdeasDB. Retrieved from https://bigideasdb.com/saas-competitor-pricing-history