Software monetization: models, strategy and lessons from companies that changed theirs

Serge Herkül
Founder of Potio, a pricing consultancy for SaaS and AI companies. Former CEO of Toggl.
Published 17 November 2026

Software monetization is how a software company turns the value its product creates into revenue: what it charges for, how it packages that, and how it bills for it.

In every pricing project I run at Potio, the team arrives thinking pricing means (mostly) price points. It doesn’t. The structure underneath (what you charge for, how you package it, which model you bill on) is about 80% of the game. Get the structure right and the price points are easy to set. Try to set price points without it and you can’t.

This guide covers the six layers of a monetization strategy, the main models and how to pick one, what happened when Adobe, Unity, Salesforce, BMW and others changed how they charge, what AI changed in 2025 and 2026, how open source companies make money and how to switch models without losing customers.

What is software monetization?

Software monetization is the system a software company uses to get paid for its product. It has two halves:

  • Pricing architecture: what you charge for (the value metric), how you package features and limits, which pricing model you bill on and what the price points are.
  • Billing infrastructure: licensing, entitlements, metering and billing. The systems that make sure customers get what they paid for and pay for what they use.

The term itself came from the infrastructure side. In the early 2010s, licensing vendors SafeNet (now Thales) and Flexera (now Revenera) used “software monetization” as the umbrella label for copy protection, licence keys and compliance. More recently, billing companies like Paddle, Orb and Schematic have pulled the term toward subscription billing and usage metering, which is still infrastructure.

Why pricing architecture deserves more attention: in a Price Intelligently study of 512 SaaS companies, a 1% improvement in monetization lifted revenue by 12.7%. The same 1% improvement in retention lifted it by 6.7%, and in acquisition by 3.3%.

Six layers of a software monetization strategy

A software monetization strategy is a stack of decisions, and each layer limits the one above it. I build every pricing architecture from the bottom up:

  1. Capability: what the product can do. You can’t monetize value the product doesn’t deliver.
  2. Fencing: what separates one customer segment’s offer from another’s, such as company size, usage limits or support level. Fences stop a large customer from happily buying the plan you built for a five-person team.
  3. Packaging: which features go into which plan. I sort features into four groups: core features (table stakes, in every plan), value drivers (they create the tiers), add-ons (sold separately) and forgettables (never on the pricing page). The test for each feature is one question: would a customer pay more for this, or just expect it?
  4. Pricing model: what you charge for and how the bill moves as the customer grows. This is the most important layer, and the value metric is the most important part of it. Pick the wrong model and nothing above it matters. Pick the right one and nobody notices, because successful customers pay more and nobody feels punished.
  5. Monetization mechanics: trials, freemium, discounts and billing terms. These tune conversion and cash flow.
  6. Price points: the numbers on the page. The tip of the iceberg.

Layers one to four are the pricing structure. That’s the 80%. Most teams start at layer six because it’s the only layer they can see on a competitor’s pricing page.

Software monetization models compared

There are about a dozen software monetization models, and most software companies in 2026 combine two or three of them.

ModelYou charge forFits whenBreaks whenExample
Perpetual licenceThe right to use a version, often plus yearly maintenanceBuyers want to own the software, run it offline or on-premYou need recurring revenue to fund continuous updatesAdobe Creative Suite until CS6
Flat subscriptionAccess for a period, one priceOne product, customers of similar size and useCustomers vary a lot in size or usageSetapp’s Mac app bundle
Per seatEach userEach user gets their own value from the productAI does the work and customers need fewer peopleSlack
TieredPlans with different features and limitsYou serve light and heavy usersTiers are split by features nobody pays more forHubSpot Starter, Professional, Enterprise
Usage-basedUnits consumed, such as API calls, messages or computeUsage tracks value closely and buyers accept a variable billCustomers need a predictable budgetTwilio, Snowflake
HybridA platform fee or seats, plus usageCost to serve varies a lot between customersThe fee and the usage part don’t relate to each otherSalesforce Core with bundled Flex Credits
CreditsPrepaid units drawn down across featuresMany features with different costs to serve, common in AICustomers can’t tell what a credit buysHubSpot Credits
Output-basedA completed result, such as a resolved ticketThe result is countable and attributableVendor and customer disagree on what countsIntercom Fin, $0.99 per resolution
Outcome-basedA business result, such as revenue gainedAlmost never in practiceThe outcome is too far down the value chain to measure and attributeRare
Ad-supportedUsers’ attention, paid for by advertisersConsumer apps with very large audiencesB2B, or small audiencesFree consumer apps
OEM and embeddedA licence for another vendor to ship your software inside theirsComponents, SDKs, enginesThe partner owns the customer relationship and the priceEmbedded SDKs
Open core and managed cloudEnterprise features or hosting on top of free open sourceOpen source projects with real adoptionCloud providers can host the free version themselvesMongoDB Atlas

What companies use depends on who you ask and what they count:

  • Signed contracts split into thirds. Vertice’s procurement data for Q2 2026, cited by billing vendor Orb, shows 36.5% of SaaS contracts priced mainly on usage, 32.4% per user and 31.1% hybrid.
  • AI companies are moving toward consumption. ICONIQ’s 2026 State of AI report (a Q2 2026 survey of about 305 executives building AI products) found 57% charge a subscription or platform fee for AI, 42% charge on consumption, up from 35% about six months earlier, and 23% use some outcome-based pricing.
  • Vendor surveys run high. Metronome’s January 2025 survey of 100 companies found 85% had adopted usage-based pricing, but that counts anyone with a single metered feature. Orb’s 2026 survey of 80 AI agent companies found only 3.8% price strictly on outcomes, against ICONIQ’s 23%, because ICONIQ counts any outcome component inside a broader contract.

Per-seat pricing is shrinking but nowhere near dead: a third of signed contracts are still priced per user.

I go through each of these models with current examples in my guide to SaaS pricing models.

How to choose a software monetization model

Find the value metric first. It shows you the model, not the other way round.

The value metric is the unit you bill on: a seat, an API call, a credit, a resolved ticket. A good one passes three filters:

  • Operational fit: can you measure it, attribute it and bill for it?
  • Customer perception: do customers understand it and feel it’s fair to pay this way?
  • Economic logic: does it grow as the customer gets more value, and does it track your cost to serve?

I go deeper on running those filters in how to find your SaaS value metric. Once you have a metric, these questions narrow the model down.

Can your customers live with a variable bill?

Usage-based pricing generally works better in B2B than B2C. A business can come out ahead when a bigger bill means more value, and a seasonal business likes paying less in quiet months. Consumers mostly want predictability. The exception is the laundromat: you happily pay per wash because you expect to, and because you can see the running cost of water, electricity and machine time.

How vertical is your product?

The more vertical the product, the closer to value you can price. A product built for one industry can charge on a metric that industry cares about. A horizontal product has to pick a metric that satisfies a very wide set of customers, which pushes it back toward infrastructure pricing: tokens, compute, API calls. Eventually that’s electricity.

Is usage bursty or sustained?

Bursty usage (a solo user, a one-off project) suits top-ups, so you monetize flexibility. Steady usage (a team that works in the product every day) should push customers to a higher tier, so you monetize predictability. Selling top-ups to steady users trades good recurring revenue for one-off cash.

Are you picking a model because it’s trending?

Most clients come to me already wanting credits or usage-based pricing because that’s what everyone is talking about. For some of them, seats are still the right model. At Toggl we priced by seat because every user got their own value from tracking their own time, and that logic still holds for plenty of products. A model someone else uses was chosen for their customers, not yours.

Can usage and tiers work together?

Yes. One client, a North American automotive software company, sold API access on usage. We added a higher tier where the same API call returns enhanced data that is hard to get elsewhere, priced 50% higher per call. Over 30% of new customers chose it. The model stayed usage-based, but packaging gave customers a reason to pay more per unit.

And expect to change your model. Between zero and $1M in annual revenue, most companies go through at least three pricing architectures: the launch version, a better one around $100k based on what they learned, and another at around $1M.

What happened when companies changed how they monetize

The pattern across public cases is fairly consistent. Changes that move the price closer to the value customers get, and that respect what customers already paid for, tend to work after a rough patch. Changes that alter the deal retroactively, or charge customers for something they believe they already own, tend to get reversed.

Perpetual to subscription: Adobe, Autodesk and Atlassian

Adobe is the textbook case. In 2013 it stopped shipping new versions of Creative Suite and moved everyone to Creative Cloud subscriptions. Adobe warned investors that revenue and profit would drop while upfront licence sales turned into monthly payments, and they did. But in that first year paid subscriptions grew from 300,000 to 1.4 million, and recurring revenue from its creative products went from $155 million to $768 million. Two years later total revenue was above where it started. Seven years later it had roughly tripled, to $12.9 billion.

The later chapter is less flattering. In 2024 the US Federal Trade Commission sued Adobe over hidden early termination fees and how hard it was to cancel. Subscription revenue held in place by a painful cancellation flow doesn’t last.

Autodesk stopped selling new perpetual licences for most of its products in 2016 and moved to subscription only. Atlassian ended support for its self-hosted Server products in 2024, pushing self-hosted customers to Cloud or Data Center subscriptions, to plenty of grumbling from sysadmins who liked owning their install.

The lesson from all three: expect a dip in reported revenue while upfront licence sales turn into monthly subscription revenue, and have the cash to survive it.

Retroactive changes: Unity’s Runtime Fee

In 2023 Unity announced a Runtime Fee that charged studios per game install above certain revenue and install thresholds. It applied to games already built on Unity, which changed the economics of projects that had been in development for years. Developers had alternatives in Godot and Unreal, and plenty of them said so loudly.

Unity revised the terms within weeks, and CEO John Riccitiello retired a month later. A year after the announcement, the new CEO, Matt Bromberg, cancelled the Runtime Fee entirely and went back to seat subscriptions with a price increase.

Per-install pricing wasn’t absurd as a value metric. Applying it retroactively to work customers had already committed to was the mistake.

Charging for what customers think they already own: BMW and Tesla

In 2022 BMW started selling heated seats as a monthly subscription in some markets, on cars that already had the heating hardware installed. Customers saw it as paying twice for something sitting in their car. BMW dropped the idea the following year.

Tesla went the other way with a feature people already understood as software. It had offered Full Self-Driving both as a one-time purchase and as a $99 monthly subscription, then stopped selling the one-time option in the US in early 2026. Mercedes sells a yearly subscription that unlocks extra acceleration on some electric models.

The difference is perception. Paying monthly for software that keeps improving feels reasonable. Paying monthly for a heater bolted into your seat doesn’t.

AI pushes seats toward credits: Salesforce, HubSpot and Cursor

Salesforce went through three Agentforce pricing models in under two years:

  • 2024: $2 per conversation. Buyers pushed back, because a routine question and a complex case cost the same.
  • 2025: Flex Credits at $500 per 100,000 credits, with a standard agent action at 20 credits ($0.10). Customers could also swap unused user licences for credits.
  • 2026: new Core ($195 per user per month), Advanced ($395) and Max ($550) editions replaced Enterprise, Unlimited and Agentforce 1. Each bundles a yearly pool of Flex Credits per org: 500,000, 1 million and 2.75 million. Core’s list price is $20 above the $175 Enterprise edition it replaces.

So Salesforce kept seats and put a usage pool on top of them: a hybrid model.

HubSpot moved its Customer Agent from $1.00 per conversation, charged whether or not the agent solved anything, to $0.50 per resolved conversation in 2026, paid in HubSpot Credits. It also added credit spend caps so customers don’t get surprised by the bill.

Cursor changed its $20 per month Pro plan in 2025 from a fixed number of requests to usage-based limits, to cover variable model costs. Users were caught out by unclear limits and unexpected charges, and the company publicly apologized. The change itself was defensible. The communication wasn’t.

Summary of the cases

CompanyChangeWhenWhat happenedWalked back?
AdobePerpetual licences to Creative Cloud subscription2012 to 2013Revenue dip, then far higher recurring revenue. FTC lawsuit over cancellation in 2024No
AutodeskPerpetual to subscription only2016Completed the switchNo
AtlassianServer end of life, push to Cloud and Data CenterFebruary 2024Migration with sysadmin resentmentNo
UnityAdded a retroactive per-install Runtime FeeSeptember 2023Developer revolt, CEO retiredYes, cancelled September 2024
BMWHeated seats as a subscription2022Backlash over paying twice for hardwareYes, dropped 2023
TeslaFull Self-Driving to subscription only in the USFebruary 2026One-time purchase endedNo
Salesforce$2 per conversation, then Flex Credits, then credit-bundled editions2024 to 2026Seats kept, AI usage pooled per orgPartly, per-conversation pricing replaced
HubSpotCustomer Agent from per conversation to per resolutionApril 2026Price halved, charged only on resolutionPartly
CursorPro plan from request quotas to usage-based limitsMid-2025User backlash, public apologyClarified

How AI changed software monetization in 2025 and 2026

AI brought back marginal cost. Classic SaaS was built on the assumption that the next customer costs almost nothing to serve. Every AI request costs real money in inference, and that changed which monetization models are safe.

  • Margins dropped. ICONIQ puts average gross margin on AI products at 45% in 2025, projected to reach 53% in 2026 and 59% in 2027. That’s a long way below the 75 to 80% that SaaS valuations were built on.
  • A few customers eat the margin. When I break gross margin down per customer, 1% to 5% of customers usually account for most of the damage. A flat price lets them burn tokens at your expense.
  • Flat AI plans got withdrawn. Cursor’s Pro change and GitHub Copilot’s move to token-based AI Credits in 2026 are the public examples of unlimited or quota-based plans turning metered.
  • Credits became the default unit. Salesforce Flex Credits, HubSpot Credits and Copilot’s AI Credits all put a prepaid pool on top of a seat or plan, so the company keeps predictable revenue and AI usage has a price.
  • Buyers got spend controls. Variable AI bills scare finance teams, so vendors added caps, alerts and the option to trade unused seats for credits.

Public markets reacted too. In early 2026, investors sold off seat-based software stocks over fears that AI agents would mean fewer seats per customer. That risk applies to any company whose revenue scales with headcount while its product cuts the headcount needed.

For AI products specifically, I cover model choice, credit design and margin protection in my guide to AI pricing models.

Can you monetize open source software?

Yes. Open source companies make most of their money from managed cloud hosting and open-core enterprise features. Support contracts alone rarely build a big business.

MongoDB is the clearest public example. It reported $2.46 billion in revenue for fiscal 2026, up 23%, and its managed cloud product Atlas made up 73% of that. Red Hat is the exception that built a large business on subscriptions and support for enterprise Linux, and IBM paid $34 billion for it in 2019.

The main open source monetization models:

  • Managed cloud: you host the open source product as a service. MongoDB Atlas, Elastic Cloud, Confluent Cloud.
  • Open core: the core is free, and enterprise features like security, compliance and admin controls are paid. GitLab is the best-known example.
  • Support subscriptions: paid support, certification and updates for the free product. Red Hat.
  • Dual licensing: a free copyleft licence, plus a commercial licence for companies that can’t meet its terms.
  • Source-available licences: licences that block competitors, mainly cloud providers, from hosting your product commercially.

That last model is where the drama has been. Several infrastructure companies changed their licences to stop cloud providers selling hosted versions of their software, and the community forked the projects:

ProjectLicence changeResponseWhere it stands
MongoDBAGPL to SSPL, October 2018AWS built its own compatible DocumentDBStill SSPL
ElasticsearchApache 2.0 to SSPL and Elastic License, 2021AWS forked it as OpenSearchAdded AGPL as an option in August 2024
Terraform (HashiCorp)MPL to Business Source License, August 2023Community fork OpenTofu under the Linux FoundationStill BSL. IBM completed its HashiCorp acquisition in February 2025
RedisBSD to RSAL and SSPL, March 2024Valkey fork under the Linux Foundation, backed by AWS and GoogleAdded AGPL with Redis 8 in May 2025

Elastic and Redis both went back to an open source licence option, and neither won back the forks. The lesson is the same as Unity’s: changing the terms on something people built on costs trust, and you don’t get it back by changing the terms again.

Monetization mechanics: free trials, freemium and billing terms

Trials, freemium, discounts and billing terms sit on top of the pricing model. They tune conversion and cash flow. They don’t fix a wrong model.

  • Freemium is a mechanic, not a model. It works when free users bring in paying ones, usually through invites or sharing. A free tier that’s too generous gives away exactly the value people would have paid for.
  • Free trials work when the product shows its value quickly. Long setups and short trials don’t mix.
  • Annual billing improves cash flow and gives you a full year to prove value before the renewal decision. The discount for paying annually is a price you pay for that cash and commitment, so set it on purpose.

There are plenty of benchmark numbers for trial and freemium conversion online. Most of them come from secondary compilations with no stated method, so I don’t trust them enough to repeat. Your own funnel data beats an industry average.

How to change your software monetization without losing customers

New customers have no anchor. They see your new model and judge it on its own merits. Existing customers compare it to what they paid last year, however fair the new model is. That’s why changing your monetization model is mostly an existing-customer problem.

What works:

  • Model your existing customers first. Run every current account through the new pricing before you launch. You’ll find customers whose bill drops, which costs you revenue, and customers whose bill doubles, which costs you customers.
  • Cap the increase. When a new model would raise an existing customer’s bill sharply, I cap the increase, by default at 2x, then ramp up over later renewals. Even 2x is high and doesn’t always work. It depends on the customer, their alternatives, the value you’ve added and whether you have a story you believe yourself.
  • Run old and new side by side. One North American sales-led SaaS company I worked with was moving from pure seats to credits as it rebuilt the product around AI. Seats had been allocated inefficiently, so some customers with lots of seats and little usage would have paid less under credits. We ran a transition period with a double ladder: credits paired with seats. It was fair to both sides while customers moved over.
  • Never change the deal retroactively. Unity’s Runtime Fee is the warning.
  • Give buyers control over variable bills. Spend caps, usage alerts and a clear dashboard make the move to usage or credits much easier to accept.
  • Tell the story. Explain why the old model has to go, what customers get in the new one and what special terms existing customers get to make the switch.

Software monetization tools: licensing, entitlements and billing

Pick the tools after the pricing model, not before. The tools enforce your pricing decisions. They shouldn’t make them for you.

The stack has four layers:

  • Licensing and IP protection: licence keys, activation and anti-piracy for software that runs on the customer’s machine. Thales Sentinel, Revenera, Keygen, LicenseSpring. You need this for desktop, on-prem and embedded software. Pure SaaS rarely does.
  • Entitlements: which customer gets which features and limits. Often part of the billing tool, sometimes separate (Schematic, Stigg).
  • Billing and metering: subscriptions, usage tracking, invoices and credit balances. Stripe Billing, Chargebee, Maxio, Zuora, Metronome, Orb, Lago.
  • Merchant of record: a provider that sells on your behalf and handles global sales tax. Paddle, Lemon Squeezy.

The market is consolidating fast. Between 2025 and 2026, Stripe bought Metronome, Adyen bought Orb for $335 million and Zuora was taken private.

Two rules from experience:

  • Never build billing in house. It will bite you. Your pricing will change in ways you can’t predict today, and every change becomes an engineering project. Pick a strong, highly customizable provider so you have room for those changes. The big names are good at that. Avoid unknown vendors and home-grown systems.
  • Check who you’re buying from. At Toggl we went with a fairly popular billing provider and had to roll back six months into the project, because a lot of what the sales rep had promised turned out not to be true. Talk to existing customers with a setup like yours, and test your hardest pricing scenario before you sign.

Software monetization is a pricing decision first

Software monetization is mostly a pricing decision. Licensing and billing tools matter, but they enforce a decision made earlier.

Start with the value metric, let it point you to the model, and build the packaging around it. When you change the model, protect existing customers from the shock and never rewrite a deal they already signed. Then pick the tools, and pick them carefully.

Frequently asked questions

What is software monetization?

Software monetization is how a software company turns the value its product creates into revenue. It covers pricing architecture (what to charge for, how to package it, which pricing model and price points) and the billing infrastructure that enforces it: licensing, entitlements, metering and billing.

How do you monetize software?

Start from the value your customer gets and find a value metric that grows with it, such as users, API calls, credits or resolved tickets. Choose a pricing model that fits that metric and your customers’ tolerance for variable bills, package features into tiers and add-ons, then set price points. Pick licensing and billing tools last.

What is the most common software monetization model in 2026?

Hybrid models that combine a subscription or seats with usage or credits are the most common direction. Vertice’s Q2 2026 contract data shows SaaS contracts split roughly into thirds: 36.5% mainly usage, 32.4% per user and 31.1% hybrid. Among AI products, ICONIQ found 57% charge a subscription or platform fee and 42% charge on consumption.

Is per-seat pricing dead?

No. About a third of signed SaaS contracts are still priced per user, according to Vertice’s Q2 2026 data. Seats still work when each user gets their own value from the product. They break when AI does the work and customers need fewer people, which is why companies like Salesforce now pair seats with a pool of usage credits.

Can you monetize open source software?

Yes, mainly through managed cloud hosting and open-core enterprise features. MongoDB made $2.46 billion in fiscal 2026, with its Atlas cloud service at 73% of revenue. Support subscriptions work too, as Red Hat shows, but few companies have built a large business on support alone.

Do I need a software licensing platform?

Only if your software runs on the customer’s machine, as with desktop, on-prem or embedded products, where you need licence keys and activation. A SaaS product controls access through accounts, so it needs a billing and entitlements system rather than a licensing platform.

Let's fix your pricing

Potio is a pricing consultancy for SaaS and AI companies.
Get a complete pricing redesign and a clear rollout plan in one structured sprint.

Work with me
Potio Founder Serge