Software procurement

SaaS Price Changes in 2026: Verified Watchlist

A pricing tracker is only useful when every row has a primary source, effective date, renewal rule, region and billed unit. This watchlist carries three changes that meet that standard, and says plainly what each one does and does not tell you about your own invoice.

Every vendor claim below carries its own read date at the claim. The Microsoft row was rechecked August 1, 2026; the Webflow and Klaviyo rows were last checked July 24, 2026 and are the older of the three. A tracker is only as current as its most recent check, so open the linked vendor page before acting on any figure here. Vendor dashboards, contracts and invoices remain the source of truth for a specific account.

Hassan Jamal·May 31, 2026·5 min read

The verified watchlist

✓
Microsoft published commercial Microsoft 365 changes effective July 1, 2026, with renewal and market caveats.
✓
Webflow began a phased Site-plan restructure on May 13, 2026, with account-specific transition dates.
✓
Klaviyo's active-profile compliance change began February 18, 2025 and can still affect 2026 billing.
✓
None of these rows establishes the percentage change on your invoice without your SKU, region, term and usage.

Effective date

Announcement, new purchase, renewal and migration dates can differ.

Billing unit

Whatever they meter you on.

Account notice

Dashboard, invoice, message center, renewal quote and contract amendments.

What has already taken effect, and what is still ahead

Two of the three dates on this watchlist have passed, which changes what you should be doing about them. Microsoft's new commercial list prices took effect on July 1, 2026, and Webflow's first transition date for existing sites passed on June 29, 2026. Neither is something to prepare for. They are something to check for on the next invoice or renewal quote that lands.

The November 16, 2026 date is the last of the three. Webflow lists November 16, 2026 for Freelancer, Agency and legacy-pricing accounts, so if you are on one of those the review is still worth doing before the date rather than after it. Everything dated before today is a reconciliation exercise rather than a warning.

Why there is no industry-wide percentage on this page

Search this topic and you will be given a single number: SaaS prices are up some percentage this year, a share of buyers face increases at renewal, a share of price rises blame AI. Those figures are not on this page, and the reason is worth stating.

They are almost all published by companies that sell SaaS spend management or price-tracking software. That does not make them false, and it does mean the organisation reporting the inflation rate is the organisation selling the cure. The methodology behind them is rarely public in enough detail to check: which vendors were sampled, which tiers, which contract sizes, whether a repackaging counts as an increase, and whether the sample was renewals only, which would tilt it upward by construction. A number you cannot audit is not evidence about your bill.

The number that actually matters is yours, and it takes about an hour to produce. Export twelve months of card or bank transactions for software. Group them by vendor. For each one, put last year's monthly figure next to this year's and note whether the seat count changed, because a rise driven by hiring is not a price rise. Then total both columns. That percentage is auditable, it is about your business, and it is the only one you can take into a renewal conversation.

The entries below are the opposite of an aggregate: three specific vendors, with the dates and terms read from each vendor's own announcement, so you can check them yourself rather than take ours.

Microsoft 365: the July 1, 2026 change

Microsoft's licensing and packaging update page, read August 1, 2026, lists U.S. commercial price changes effective July 1, 2026 for selected Enterprise, Business, Frontline and standalone products. It lists Business Basic with Teams moving from $6 to $7 and Business Standard with Teams from $12.50 to $14, while Business Premium remains listed at $22. Existing customers remain on their current price until the applicable renewal, and country, currency, channel and product configuration can change the result.

The renewal condition is the part that matters most once the date has passed. Because existing customers hold their current price until renewal, nothing changed on July 1 for most accounts already under contract. What changed is the number your next renewal quote will be built from. So the useful action is not to check today's invoice, which will probably look normal. It is to find your renewal date, and to read the first quote issued after it against the published table rather than against last year's bill.

Do not apply one percentage to every Microsoft invoice. Export assigned licenses, identify the exact SKU and Teams configuration, remove or reassign unused seats through the supported admin process, and compare the renewal quote with the official table and contract. The full method for that reconciliation is in our software pricing audit walkthrough.

"A pricing tracker only earns trust when every row carries a source, a date and a billed unit.

Webflow: phased plan restructuring

Webflow's May 2026 plan update article, read July 24, 2026, says new Site-plan purchases changed May 13, 2026. It combined CMS and Business into Premium, listed Premium at $25 per month billed yearly or $39 monthly, and included 20,000 CMS items. Existing-site timing differs: June 29, 2026 for some accounts and November 16 for Freelancer, Agency or legacy-pricing accounts, then at renewal or a billable change.

The impact is not uniformly an increase. Webflow's own scenarios show cases where a Business customer pays less, the same or more after bandwidth add-ons. Record the current plan, renewal, bandwidth, workspace, add-ons and billable changes before modeling an alternative. We itemize those lines in our Webflow cost breakdown. If the review turns into a departure, our notes on leaving Webflow, what a Webflow migration involves and Webflow compared with a custom build cover the work that follows.

Klaviyo: a 2025 billing-unit change still relevant in 2026

Klaviyo's billing-change FAQ, read July 24, 2026, says that from February 18, 2025 credit-card customers had to use an email plan that matched or exceeded active-profile count. It also introduced optional flexible sending and auto-downgrade behavior. This is not a 2026 price increase, so it is labeled here as an earlier billing-policy change that can affect a 2026 invoice.

We do not publish a typical percentage for what this change costs, because the effect on any account depends on its own profile counts, plan and sending behavior. Compare active profiles, suppressions, sends, SMS, credits, selected preferences and the current invoice for the specific account. Storefront owners tracking this alongside app subscriptions can use our walkthrough of how Shopify app charges land on a monthly bill.

Why this tracker has no headline percentage

We do not publish an industry-wide software inflation rate, a per-employee software cost or a blanket saving from replacing licensed software with a custom system. Each of those moves with company size, region, contract term, usage and renewal timing, so a single figure quoted without a stated sample and method is not something you can budget against. Licensed software and custom systems both carry ongoing operating costs, so compare them on your own invoices and your own running costs across a full renewal cycle.

How to maintain a defensible internal tracker

A tracker survives scrutiny at renewal only if each row carries its own evidence. Six field groups do that: the contract identity, the money as actually billed, the four dates each with its primary-source URL, the definition of the billed unit, the termination and notice obligations, and the invoice that proves what you paid rather than what you were quoted.

✓
The vendor, the product, the exact SKU, your region, the currency, how you are billed, and who owns the contract.
✓
The unit price today, how many you are billed for, discounts, credits, tax, and the invoice total.
✓
Announcement, effective, renewal and notice dates with the primary-source URL.
✓
Definition of the billed unit and any threshold, overage or auto-upgrade behavior.
✓
Termination, downgrade, export, deletion and renewal-notice requirements.
✓
Evidence captured from the dashboard, renewal quote and paid invoice.

Once the tracker holds those fields, it feeds directly into the review steps in our guide to reducing a software bill.

Match the response to the type of change

Not every billing change calls for the same move. Four patterns come up often enough to decide in advance how each one will be handled.

✓
A published list-price rise: confirm assigned seats and actual use first, then remove or right-size before accepting the new rate at renewal.
✓
A redefined billing unit: read the new definition against your own counts. A tier price can stay still while the invoice moves, so check what is being counted, not only what is being charged per unit.
✓
A forced plan restructure or migration: treat it as a scheduled review point. Configuration work you were deferring is happening anyway, so this is the moment to compare staying, right-sizing and moving on the same set of numbers.
✓
A single workflow carrying a large share of the bill: scope it properly through a build-versus-buy comparison rather than reacting to the renewal notice.

Respond with usage evidence, not a migration reflex

A price rise is not by itself a reason to leave. Strip duplicate and inactive seats through the supported process, right-size only after confirming which features and permissions you actually need, and check what your negotiated terms and notice periods already oblige. Alternatives get compared on migration, integration, security, support, training and exit cost, not on sticker price.

✓
Remove duplicate, inactive or incorrectly assigned seats using the vendor's supported process.
✓
Right-size the plan only after confirming the features, permissions and data needed.
✓
Check negotiated discounts, committed usage, renewal notice and termination obligations.
✓
Compare alternatives on migration, integration, security, support, training and exit costs.
✓
Consider custom software only when requirements and total cost support it; custom code still needs hosting, maintenance and ownership.

Work the last point through properly rather than by instinct. Our build versus buy comparison sets out the inputs, our migration cost assessment covers what moving off a platform involves, and our delivered project write-ups show what the finished work looks like. Where a replacement is worth scoping, our custom engineering service and engagement tiers describe how we work.

Primary sources

Get your migration plan

Bring the current invoices, renewal dates, usage exports and workflow requirements. We will separate seats to remove, plans to right-size, tools to retain and workflows worth scoping as a replacement.

Frequently asked questions

Frequently Asked Questions

Which SaaS changes are verified in this watchlist?

The page covers Microsoft's July 1, 2026 commercial Microsoft 365 changes, Webflow's phased May 2026 Site-plan restructure, and Klaviyo's February 2025 active-profile billing policy because it can still affect 2026 invoices. Each row links to a primary vendor source.

How much did SaaS prices increase in 2026?

There is no universal percentage. The result depends on vendor, SKU, region, channel, contract, renewal, billed units, usage and discounts. Calculate each change from the account's current invoice and dated renewal quote.

What is a billing-unit change?

It changes which users, profiles, contacts, messages, transactions or other units count toward a plan. The published price can stay the same while the billed quantity changes. Verify the vendor definition and your actual invoice rather than applying a generic impact percentage.

How do I protect my business from SaaS price changes?

Maintain an owner, invoice, renewal date, SKU, billed-unit definition and usage export for every tool. Remove unused seats through supported processes, right-size features, review notice and exit terms, and compare alternatives on equivalent total cost.

Is Microsoft 365 going up in price in 2026?

Microsoft's official U.S. commercial table lists selected changes effective July 1, 2026. Business Basic with Teams moves from $6 to $7 and Business Standard with Teams from $12.50 to $14, while Business Premium remains $22. Existing-customer timing, market, currency, channel and configuration can affect the invoice.

Why did my Webflow plan change in 2026?

Webflow began a phased Site-plan restructure for new purchases on May 13, 2026 and published later transition dates for existing accounts. CMS and Business move to Premium under account-specific renewal and billable-change rules. Check the official FAQ and the site's billing screen because bandwidth and add-ons can make the total lower, unchanged or higher.

Pricing8 min