Software procurement

2026 SaaS Pricing Audit: Evidence Before Savings

A real software audit starts with paid invoices, accepted contracts and observed usage. Public prices are context, not your total. The output should show what to retain, right-size, consolidate, replace or investigate without promising a universal savings rate.

Reviewed August 2, 2026 against current primary vendor sources.

Hassan Jamal·May 31, 2026·7 min read

The audit deliverables

✓
One list that reconciles: every vendor, what you buy, who owns it internally, the invoices, the terms, your actual usage, and what data sits there.
✓
A decision for every line: retain, right-size, consolidate, replace or investigate.
✓
A map of what depends on what, and where the risk is: security, privacy, integrations, staying running, and getting out.
✓
Conservative, base and adverse cost scenarios for any material change.
✓
A dated pack of evidence, so finance, operations and engineering are all looking at the same facts.

Commercial

What you signed, what you pay, and when you can leave.

Usage

What you actually use, including at peak.

Risk

What data sits there, who can reach it, and how you get it back.

The pattern this audit exists to catch

The shape of the problem is familiar enough to describe without a statistic. You sign up at a modest monthly price. You do not add users, you do not change how you work, and the product does not noticeably improve. Two years later the same line item is several times larger. Nothing dramatic happened. A tier boundary moved, a definition of the billed unit changed, an introductory discount lapsed, a plan was restructured and you were migrated onto the nearest equivalent, and each of those arrived on a different date in a different email.

That is why an audit built on remembered prices does not work. Nobody remembers four small changes across two years, and the vendor is under no obligation to summarize them for you. The invoice does. Everything below starts there.

What actually changed in 2026

The audit below is worth running in 2026 specifically because several widely-used vendors moved price or packaging inside the same twelve months. Each item is linked to the vendor's own announcement. Verify against the live page before you budget from it, because vendors revise these notices and regional pricing differs. We follow the same vendor announcements in our 2026 vendor price-change tracker, and the practical response once a change is confirmed on your own invoice is set out in our guide to reducing a software bill.

Vendor	Change	Effective
Microsoft 365	Per user/month: Business Basic $6 to $7; Business Standard $12.50 to $14; E3 $36 to $39; E5 $57 to $60; F1 $2.25 to $3; F3 $8 to $10. Business Premium is unchanged at $22, so check your own SKU before assuming a rise. Microsoft states existing customers remain on current pricing until renewal, and that tenants get at least 30 days notice in Message Center before packaging changes become available. Figures from Microsoft's licensing news page, checked August 2, 2026.	July 1, 2026
Webflow	Plans restructured and simplified. Because plan boundaries moved rather than a single price, check which new plan your current site maps to rather than comparing the headline number.	May 2026
Klaviyo	Billing model change affecting how contacts and sends are counted. This is an earlier policy change rather than a 2026 price rise, and it can still be the reason a 2026 invoice looks different. The practical effect varies by list size and sending pattern, so read your own invoice rather than a published percentage.	February 18, 2025

Why no percentages for Webflow and Klaviyo

We publish the Microsoft figures because Microsoft publishes them per plan. For the other two, the change is structural rather than a flat uplift, so any single percentage would be wrong for most readers. The primary sources are linked at the end of this article; your invoice is the only authority on what you specifically now pay.

"A real audit starts with paid invoices and observed usage, not the price on the vendor's website.

1. Reconcile finance, identity and vendor records

The register everything else runs on, and it comes from three places rather than one. Twelve months of card, bank and AP charges tell you what you paid. The contracts tell you renewal dates and notice periods. The identity provider tells you what staff actually log into. Anything in that third list missing from the first is either free, personally expensed, or on a card nobody reconciles.

✓
Export at least twelve months of card, bank, accounts-payable and app-marketplace charges.
✓
Match each charge to a vendor account, product, workspace, business owner and technical owner.
✓
Record contract dates, renewal, notice period, auto-renewal, minimum commitment and termination path. Set the reminder off the notice period the contract itself states, not a generic lead time, and add enough working days to get an approval through before the window shuts.
✓
Identify externally billed subscriptions that will not appear in a platform's native billing page.
✓
Export the application list from your identity provider, such as Okta or Microsoft Entra ID, formerly Azure AD. Anything employees sign into but finance never paid for is either free, expensed personally, or billed to a card you have not reconciled yet.
✓
Flag unknown, duplicate, former-employee and test accounts for investigation before cancellation.

Keep that register in a form you can reuse. The same records of spend, owners and renewal dates are what a website rebuild cost assessment or a migration cost assessment depends on later.

2. Normalize the commercial model

Record currency, tax, billing interval, discount, committed quantity, overage and credit separately. A monthly equivalent can aid comparison but must not erase annual commitments or termination terms. Public list prices can differ from a reseller, enterprise agreement, legacy entitlement or negotiated renewal.

Microsoft's July 2026 changes illustrate why SKU and renewal matter. Webflow's 2026 transition illustrates why account type and billable changes matter. Klaviyo's active-profile policy illustrates why the definition of a billed unit matters. Use the vendor announcement and the account invoice together. Our breakdown of Webflow plan and add-on lines works through the same reading exercise on one vendor.

3. Measure use without inventing a dormant-user benchmark

Define what meaningful use means for each product before measuring anything, because a login does not prove value and silence does not prove idleness. State the observation window explicitly as well: a single quarter misses everything that only runs at month-end, quarter-end or year-end. Every change that follows this needs a rollback plan.

✓
Define meaningful use for the product: login alone may not establish value, and absence of login may not mean unused automation.
✓
Review assigned seats, permission level, last activity, feature use, API calls and owned workflows over a window you state explicitly. A quarter misses anything that only runs at month-end, quarter-end or year-end, so record the window alongside the finding and let the next person re-run it.
✓
Check seasonal and campaign peaks before downgrading a usage-based plan.
✓
Ask the business owner what fails if the tool is removed and how that dependency was tested.
✓
Retain a change and rollback plan for any seat, tier or integration adjustment.

Why there is no benchmark figure here

We do not publish a single figure for unused seats, dormant users or expected savings. Any such number depends on which organizations were sampled, how each of them defined an active user and over what period the activity was counted. A benchmark stated without that sample and definition is not something you can budget against. Calculate the result from your own seat inventory, activity records and invoices.

Two things an average month will not show you

First, anything metered by ticket, contact, conversation, message or send does not have a stable monthly cost. A promotion, a seasonal peak or a paid campaign multiplies the units while the plan stays exactly the same, so an annual budget built from a quiet month will be wrong in the months that matter most. Pull twelve months rather than three, and look at the peaks specifically before you right-size anything usage-based.

Check that the cheaper plan is available to you

Vendors frequently introduce lower entry pricing to attract new customers while existing accounts stay on the plan they signed. So a cheaper tier appearing on the pricing page is not yet a saving. Before you build it into a forecast, confirm in writing that your account can actually move onto it, because the answer is sometimes no and it is rarely stated on the page.

4. Map capability and data dependencies

This is the section that separates unused from quietly load-bearing. Five surfaces need inventorying before a subscription can safely be touched: what it does, what regulated data it holds, what it is wired into, what you could get out of it, and who knows how to run it. A tool nobody logs into can still be carrying a scheduled job the business depends on.

✓
Authentication, roles, workflows, forms, approvals, notifications and scheduled jobs.
✓
Customer, employee, payment, health or other regulated data and applicable processing terms.
✓
CRM, commerce, finance, support, analytics, advertising and warehouse integrations.
✓
Exports, backups, retention, deletion, audit history and legal holds.
✓
Support contacts, incident history, recovery objectives and internal operating knowledge.

5. Avoid cancellation mistakes

Confirm the current vendor procedure before changing access. Shopify currently says uninstalling an app cancels future Shopify-billed recurring charges, while pending charges from the current cycle can still appear and externally billed subscriptions must be canceled with the provider. Other products use different timing. Capture confirmation, exports and effective dates. App charges are easy to overlook at this step, so read our walkthrough of where Shopify app charges appear on a monthly bill before you touch a storefront. If commerce is the workload under review, our ecommerce engineering service page describes what we take on.

6. Decide line by line

Five verdicts are available for any subscription, and each has to be earned with different evidence. Retain needs demonstrated use. Right-size needs proof a lower tier covers your peaks rather than your average. Consolidate needs one product genuinely covering the workflows. Replace needs the target to clear requirements at acceptable risk. Investigate is the honest verdict while an owner, a contract or a data location is still unknown.

Decision	Evidence required	Common risk
Retain	Used capability and acceptable total cost	Ignoring renewal or vendor concentration
Right-size	Lower tier meets measured needs and peaks	Losing a required feature or entitlement
Consolidate	One product covers accepted workflows	Migration, retraining and integration gaps
Replace	Target meets requirements at acceptable risk and cost	Underestimating operation and exit work
Investigate	Owner, use, contract or data remains unresolved	Deleting first and discovering dependency later

7. Compare buy, switch and build on total cost

Compare buy, switch and build on one list of inputs: license or build cost, migration effort, the internal hours each option consumes, what it costs to run for three years, and what it costs to leave. An option often looks cheaper only because something was left off that list. Put every option on the same inputs before you compare them. Our website cost guide sets out how we break a scope into those inputs.

✓
Current and projected vendor fees under normal, peak and adverse usage.
✓
Implementation, data migration, integrations, testing, training and transition.
✓
Hosting, databases, email, monitoring, security, backups and incident response.
✓
Internal administration, support, maintenance, vendor change and engineering availability.
✓
Downtime, data loss, adoption, compliance and exit risk.
✓
Residual value, ownership and licensing under the actual agreement.

Custom software is not a zero-recurring-cost category. Vercel, Sanity, databases, email, observability and other dependencies have current plans and terms. A custom system also needs security updates, maintenance, monitoring and support. Build when the requirements and scenarios justify control, not because a monthly threshold guarantees payback. Our note on what a Next.js hosting bill actually contains lists those lines, and the wider decision is worked through in our build versus buy comparison. Our engagement tiers show how we scope custom engineering work.

8. Set change and acceptance controls

A decision to cancel is not the same as a saving that sticks. Six controls make it stick: a named owner and rollback trigger per change, exit evidence including deletion, acceptance testing where a replacement is involved, post-change monitoring against a dated baseline, contract-specific remedy for anything custom, and a procurement gate for the next purchase. Without that last one, the spend reappears on someone's expense claim within a quarter.

✓
Named owner, approval, change window, test script, rollback trigger and communication path.
✓
Data export, reconciliation, access removal and deletion evidence.
✓
Functional, security, accessibility, performance and integration acceptance where relevant.
✓
Post-change monitoring and a dated comparison with the baseline.
✓
Contract-specific support, cure and remedy for any custom replacement.
✓
An agreed route for buying the next tool: who approves it, which card it goes on, and who adds it to the register. Without that, the spend you just removed reappears on someone's expense claim within a quarter and the audit has to start again.

Where the replacement is a website, storefront or internal tool rather than a single subscription, our project write-ups show how scope, acceptance and handover were recorded, including the Panda Patches build.

Primary sources

Seven pages, all vendor-owned rather than third-party summaries, checked on the dates given above. Vendors revise these without notice, so treat the list as where to verify rather than as a substitute for verifying. Where a figure here disagrees with your own invoice, your invoice is the authority.

Get your migration plan

Share invoices, contracts, usage exports and workflow owners. We will build a decision register and scope only the replacements whose requirements and total-cost model support the change.

Frequently asked questions

Frequently Asked Questions

How much is the average business spending on SaaS in 2026?

A general benchmark does not establish your stack cost. Reconcile at least twelve months of card, bank, accounts-payable and app-marketplace charges, then map each item to the exact account, SKU, owner, usage, contract and renewal.

What is the 2026 SaaS inflation rate?

This audit does not apply one market-wide rate to every contract. Vendor, SKU, region, billing channel, renewal, discount and billed quantity differ. Use the official change notice and the account's renewal quote and invoice.

Which software companies changed pricing in 2026?

The related primary-source watchlist currently covers Microsoft's July 2026 commercial Microsoft 365 changes and Webflow's phased May 2026 plan restructure, plus Klaviyo's February 2025 billing-policy change because it can still affect 2026 invoices. It is not presented as an exhaustive market list.

How do I audit my SaaS bill in 2026?

Reconcile invoices and contracts, normalize SKU and billed units, measure meaningful use, map data and workflow dependencies, verify cancellation rules, and assign retain, right-size, consolidate, replace or investigate. Retain dated evidence and rollback for every change.

When does building custom software beat paying for SaaS?

The answer depends on the current system, requirements, evidence, vendor terms, operating costs, and accepted project scope. Validate mutable facts at their primary source and do not treat an example as a ranking, performance, revenue, delivery, ownership, or refund promise.

What is the cheapest way to replace a CRM?

There is no universal cheapest path. Define the required data, roles, workflows, reporting, integrations, compliance, migration, support and exit first. Compare current vendor quotes with a scoped custom option including hosting, maintenance, security, internal time and adoption.

Pricing9 min