Key takeaways
- Value-based pricing without a structural framework turns into custom pricing for every deal, and custom pricing does not scale past a few dozen customers.
- Maintenance renewals and price increases get exponentially harder to administer when every contract has its own logic instead of a shared rate card.
- Cross-selling a new product, whether built internally or acquired, only works smoothly if it can attach to an existing, predictable pricing structure.
- In a private equity buy-and-build scenario, a clean license model is a due diligence asset. A pile of bespoke contracts is a liability that slows integration.
- Perpetual, SaaS, usage-based, and outcome-based licensing are the four dominant B2B software license models, each suited to a different kind of product and buyer.
Why B2B software license models matter more than any single pricing tactic
Every growing software company eventually has the same conversation. A big renewal is coming up, and nobody can agree on what the customer pays for, or why. The answer usually traces back to a deal that was priced on instinct three years earlier, then copied and adjusted for the next customer, and the one after that. This is how B2B software license models quietly disintegrate into a patchwork of one-off agreements.
Value-based pricing is the philosophy that a customer should pay in proportion to the value they receive. It is a good philosophy. However, on its own it is not a pricing model. It is a negotiating stance. Without a structure behind it, the phrase “value-based pricing” becomes a way to justify whatever number a seller and a buyer land on in the room. Our earlier piece on how structure replaces arbitrary discounting covers this from the negotiation side. This article looks at the same problem from a different angle: the license model itself, and what happens when a company scales without one.
The maintenance and price increase problem
Consider a company with 150 customers, each on a slightly different contract. Some pay for named users, others for concurrent users, others for a flat site license negotiated during a slow quarter. When it is time to calculate maintenance renewals, finance cannot run a single formula across the base. Someone has to look up each contract individually.
Now add an annual price increase to that picture. A company with a standard rate card can announce a 6 percent increase and apply it uniformly, with clear exceptions for multi-year locks. A company with 150 custom contracts has to renegotiate 150 times, because there is no shared baseline to increase from. Every renewal becomes a mini negotiation instead of a routine billing event. This is not a hypothetical. It is the default state of companies that treated every early deal as a one-off, because in the early days, that felt like good selling. It stops feeling like good selling once the finance team has to close the books.
Cross-selling breaks without a shared pricing structure
The second place this shows up is cross-sell and upsell. Say a startup builds or acquires a new module, perhaps an analytics add-on or an integration layer. If the core product has a clean tiered structure, the new module can attach to it immediately: it becomes an add-on at a defined price for Standard tier customers, and bundled by default for Enterprise. If the core product has no consistent structure, every existing customer needs an individual quote, because nobody can say with confidence what “list price” even means for that account.
This becomes existential during a private equity buy-and-build strategy, where a platform company acquires several smaller vendors and tries to cross-sell each one’s product into the others’ customer base. A clean, structured license model lets a PE-backed platform integrate an acquisition’s pricing in weeks. A tangle of bespoke enterprise agreements can take quarters, and every quarter of delay is a quarter of lost cross-sell revenue that was supposed to justify the acquisition multiple in the first place.
Pro tip: Before your next fundraising round or exit conversation, pull every active contract and check how many distinct pricing structures exist across your customer base. If the number of structures approaches the number of customers, that is worth fixing before a buyer’s diligence team finds it for you.
Four B2B software license models and where each one fits
Most B2B software sold today falls into one of four license models. Each one has a different origin, a different metric, and a different customer relationship. The rest of this series covers each one in depth. Here is the short version.
Perpetual licenses
A perpetual license means the customer owns the right to use a specific version of the software indefinitely, after paying a one-time license fee plus an annual maintenance fee, typically 18 to 22 percent of the license price, for updates and support. This model is usually built around a central server or platform component, with additional modules licensed on top. It is still common in industries with long hardware refresh cycles, such as manufacturing engineering software, and in regulated environments where customers prefer to control exactly which software version runs in production.
SaaS licenses
Software as a service replaces the one-time fee with a recurring subscription, usually billed per user per month or per year, with the vendor hosting and operating the software. Salesforce popularized this model in the B2B world starting in 1999. The part companies underestimate is the second S in SaaS: service. A subscription customer expects ongoing support, onboarding, and a system that simply works, and underinvesting in that service layer is one of the most common ways SaaS companies lose renewals.
Usage-based licensing
Usage-based, or consumption-based, licensing charges customers according to how much of the product they use: API calls, messages sent, pages processed, or compute consumed. Twilio, Snowflake, and AWS built this model into the default expectation for infrastructure and API-driven products. It aligns cost directly with value delivered, which customers like, but it also makes revenue harder to forecast for the vendor and harder to budget for the customer.
Outcome-based licensing
Outcome-based licensing goes one step further than usage: instead of charging for an API call or a processed page, it charges for the finished result, a completed invoice, an executed contract, or a resolved support ticket. This model has moved from a niche idea to a real category with the rise of AI agents. Intercom charges roughly a dollar per resolved support ticket through its Fin agent, and Salesforce has experimented with per-conversation and per-action pricing for Agentforce. It is the model with the tightest link between price and value, and also the hardest one to price correctly, which the rest of this series will get into.
Quick facts
- Enterprise perpetual license maintenance fees typically run 18 to 22 percent of the license price per year, meaning maintenance equals the original license cost within four to five years.
- Salesforce launched its “No Software” campaign in 1999 and is widely credited as the company that made SaaS a mainstream B2B category.
- Twilio, Snowflake, and AWS are the three companies most often cited as having established usage-based pricing as a credible default for infrastructure and API products.
- Intercom’s Fin AI agent charges close to one dollar per resolved support ticket, one of the clearest live examples of outcome-based licensing at scale.
- Autodesk’s 2016 shift away from new perpetual licenses caused a regional revenue drop of up to 42 percent in a single quarter in some markets, according to Autodesk’s own investor disclosures, illustrating how disruptive a license model change can be without careful sequencing.
Frequently asked questions
- What are the main B2B software license models?
The four dominant B2B software license models are perpetual licensing, SaaS subscription licensing, usage-based licensing, and outcome-based licensing. Each ties price to a different thing: ownership of a software version, ongoing access, measured consumption, or a completed result. - Why does value-based pricing need a structured license model behind it?
Value-based pricing describes a philosophy, not a mechanism. Without a structured model, such as defined tiers, usage units, or outcome definitions, “value-based pricing” becomes shorthand for a custom number negotiated deal by deal, which cannot be maintained consistently at scale. - How does a license model affect a company’s exit or acquisition value?
Buyers and private equity firms evaluate how easily a target’s revenue can be integrated and grown. A standardized license model can be modeled, forecast, and cross-sold quickly. A base of bespoke contracts adds integration risk and typically depresses the multiple a buyer is willing to pay. - Can a company use more than one license model at the same time?
Yes. Many software companies combine a base SaaS subscription with usage-based add-ons, or layer outcome-based pricing on top of a subscription platform. The key is that each layer needs its own clear, repeatable structure rather than being negotiated ad hoc. - What is the biggest risk of not having a structured license model?
The biggest risk is that maintenance calculations, renewal price increases, and cross-sell all become manual, deal-by-deal work. That does not just slow finance and sales down. It actively caps how fast the company can grow, because every new deal type requires new negotiation instead of a repeatable process.
B2B software license models: the structure decision you cannot outsource to a sales team
None of the four models described here is inherently better than the others. A perpetual license makes sense for a customer who wants full control over a locked software version. A SaaS subscription makes sense for a product that improves continuously. Usage-based pricing makes sense when consumption is easy to measure and tightly linked to value. Outcome-based pricing makes sense when the vendor can define and deliver a clear result. The mistake is not picking the wrong model. The mistake is not picking a model at all, and instead letting each sales negotiation invent its own logic.
That decision gets harder to reverse the longer a company waits. A software business with ten customers can still clean up its pricing in an afternoon. A software business with a thousand customers, three acquired products, and a pending exit conversation cannot. The earlier a company commits to a structured license model, the more of its growth that structure gets to support rather than fight against.
Over the next few weeks, this series will go deep on each of the four models: how they work, where they came from, and what they mean for the company selling them and the customer buying them. Two further articles will cover the operational side that gets least attention: the hidden complexity of moving from perpetual to SaaS, and the specific challenge of pricing an outcome that is harder to define than it first appears.
If your own pricing has grown into a patchwork of one-off deals and you want to rebuild it into a structure that scales, let’s have a conversation.