The SaaS-repricing event most businesses are about to face

The conditions that produced cheap SaaS

The decade-long pattern of inexpensive entry-level SaaS, with reasonable growth in pricing, was a product of three conditions converging.

Capital was cheap. Venture funding was abundant, and SaaS vendors could prioritise customer acquisition over near-term margin. The result was aggressive entry pricing and slow upward repricing, because keeping customers happy was structurally more important than monetising them.

Competition was intense. Most SaaS categories had multiple credible vendors, each priced against the others. The vendor with the most aggressive pricing pulled customers from the others, which kept the floor down across the category.

Switching cost was nominal. Early-stage operators had not yet embedded their workflows deeply into any single vendor. Switching from one CRM to another, one project tool to another, was inconvenient but not catastrophic. The credible threat to leave kept vendors honest.

None of these three conditions holds today at the strength it once had. Capital is expensive. Many categories have consolidated to a handful of dominant vendors. And the operators who have used the same SaaS for five-plus years now have switching costs that the vendors can read clearly.

What is changing on the vendor side

The vendor pressure is now to extract revenue rather than to acquire customers. Several specific moves recur across the category.

• Tier compaction. Features that used to live in entry-level tiers move to mid-level tiers. Mid-level features move to enterprise tiers. The customer who needs the same feature set ends up paying a higher tier than they did three years ago for the same operational capability.
• Per-seat aggression. Per-seat prices rise on existing customers, with the increase often timed to renewal cycles when the political cost of switching is highest.
• AI feature gating. The new AI features that vendors are shipping are released as paid add-ons, often at price points that effectively double the customer's bill if they want the new capability.
• Data-egress fees. Where they did not previously exist, fees for exporting data are quietly introduced. Operators who try to leave find that the cost of doing so is higher than it was when they signed up.
• Required premium tiers for compliance. Enterprise compliance features — single sign-on, audit logs, compliance reports — move into premium tiers, forcing customers in regulated sectors to upgrade.

Each of these is rational from the vendor's perspective. The cumulative effect on the operator is a steepening of the pricing curve that the marketing material did not prepare them for.

Why this happens to most operators at once

Vendors do not reprice individually; they reprice across cohorts. When market conditions shift, multiple vendors in the same category make similar moves at similar times because the market signals are the same for all of them. The operator therefore experiences not a single repricing event from one vendor but a synchronised wave across many vendors at once.

The wave is harder to absorb than individual repricing because the operator's discretionary capacity to switch any single vendor depends on the others being stable. If five vendors all reprice within twelve months, the operator cannot credibly switch any one of them without overloading the operations team. The synchronised wave produces a captive moment, and the vendors know it.

How to be positioned

The operators who absorb the repricing wave without becoming hostages are the ones who have already done the work of being switchable. Three properties matter.

Owned data. The operator can extract every piece of operational state from any single vendor in a useable format within a working week. This is a discipline, not a one-time export. It is set up, tested, and maintained.

Abstracted integrations. Where one system feeds another, the integration runs through an orchestration layer the operator controls, not through a vendor-specific API in application code. Switching the underlying system is a change in the orchestration configuration, not a code rewrite.

Documented workflows. The operational logic is captured in version-controlled documentation, not implicit in the configuration of any one vendor's interface. A new vendor can be configured to match the documented workflow rather than archaeologically reconstructing what the old one was doing.

Operators with these three properties can absorb a repricing wave by selectively switching the most aggressively-repriced vendors. Operators without them are stuck and end up paying the new pricing because the cost of switching is the larger number.

The longer arc

The repricing wave is the immediate event. The longer arc is that the relationship between operators and operational software is being recalibrated. Operators are belatedly noticing that the rental economy is a tax. Vendors are belatedly noticing that the operators who can absorb a repricing are not the ones with the deepest embedding; they are the ones with the most discipline.

The result, on a five-year horizon, is a quieter but more important shift than any single repricing event: a meaningful proportion of operations bring their critical infrastructure in-house. The capabilities they retain on rented stacks are the ones where rental genuinely makes sense — specialist deliverability, payment processing, frontier inference. The rest moves onto sovereign substrates.

The vendors who survive this shift are the ones who reprice gently, who invest in the operator's success, and who treat the rental relationship as a long-term partnership rather than as a maturing extraction opportunity. The vendors who do not survive it are the ones who treat the captive moment as a windfall.

The takeaway

The SaaS repricing event is not theoretical. It is already visible in many categories and will be unmistakable across most by the end of the next eighteen months. The operators who are positioned to absorb it without becoming hostages have done the unglamorous work of being switchable: owned data, abstracted integrations, documented workflows. The operators who have not are about to discover what their dependencies are actually worth to the vendors who hold them.

The right time to do the work is before the repricing letter arrives. Once the repricing has been announced, the leverage to negotiate has already passed. The audit, the migrations, the discipline of switchability — all of these compound only when they are in place ahead of the moment they are tested.