The Licensing Model: What the Unit Is, and What It Grants

TL;DR A software licensing model is two decisions, not one: the value metric names the unit you sell, and the grant defines what that unit entitles a buyer to do. Most companies debate the metric in a room and inherit the grant from an agreement template. The metric half can be evaluated on six dimensions, and three of them turn out to be answered by the grant rather than by the meter. The grant is where the durable commercial properties live: assignment, deployment, duration, and boundedness.

A software company sells five hundred seats. At renewal the customer’s headcount has not moved, but consumption has tripled, because someone wired the product into a workflow that runs whether or not a person is logged in. The account team opens the agreement to find out what the company is owed. It says the customer bought five hundred user licenses. It does not say what a user is.

A software licensing model names the unit you sell and defines what that unit grants. This company decided only the first half, and the gap that leaves is not a legal oversight. Both halves are real decisions. Most companies make the first deliberately and inherit the second from whatever the last agreement template happened to say.

A Licensing Model Is Two Decisions, Not One

The industry’s shorthand collapses the two. Ask a pricing team what their licensing model is and the answer comes back as a metric: per-seat, per-transaction, per-gigabyte, per-agent. That is half the question. A metric with no defined grant is not a licensing model; it is a number waiting for a contract to give it meaning.

One venture investor put the metric half well, observing that per-seat pricing never priced the seat at all. It priced the best available proxy for value. Correct, and it is exactly why the other half matters. A proxy only works if the paper says what the proxy stands for. Five hundred seats is a defensible proxy when a seat means a named person who logs in. It is an unpriced liability when a seat means an authenticated connection and nobody wrote down which one was intended.

Metric selection is its own discipline. How to choose a value metric covers the buyer-facing half in depth, and the argument over whether the metric or the model is the real lever is settled elsewhere. What follows is the frame we evaluate a metric against, and what that frame exposes about the half neither article covers.

The Six Dimensions a Licensing Metric Is Judged On

A metric is not chosen well by taste or by copying whatever the category leader counts. The framework we have used across decades of engagements evaluates a candidate value metric, the licensing metric in the framework’s own vocabulary, on six dimensions.

Increased use. A metric that meters every interaction teaches customers to use less. Granularity that feels precise to a finance team reads as a toll booth to a user, and people route around toll booths: they batch their work, they share access, they cap their own adoption, and the vendor reads the flat line as a product problem. The test: does the meter count at the moments the customer extracts value for their organization, or somewhere disconnected from them?

Revenue scalability. Each additional unit consumed should track a dollar the customer gained, whether that is revenue added, expense removed, or a mandate met. The tighter that correspondence, the longer the metric survives contact with an account that grows. The test: does your revenue scale with your customer’s ability to extract additional value?

Fit to the customer’s business. The metric should count something the customer’s own organization already recognizes, in the vocabulary their industry already uses. When it does not, sales carries a second job before the first one can start: teaching the buyer to convert your unit into terms that mean something on their side of the table. At the far end of that gap the metric becomes friction the deal has to overcome. The test: does the buyer already think in terms of this count, or will you be teaching it in every deal?

Ambiguity and understandability. The metric is a mutual agreement about how much access is being exchanged for how much money, and it lives inside terms both parties sign. One unambiguous definition holds. A term that needs interpretation will be interpreted later, by whoever has the most at stake when it comes up. The test: can a customer intuitively grasp what you are counting, and would two reasonable people read your agreement and count the same thing?

Estimation ease. Buyers size their purchase before they have any experience of the product, and your sellers have to substantiate the size they propose. Customers rarely resent buying more when they need more. They resent a misestimate that forces an unplanned purchase before the renewal they budgeted for. The test: can a buyer estimate what they need before signing, without a spreadsheet from your sales engineer?

Customer and vendor monitoring. Both sides have to see the count: the customer to budget and plan, you to invoice and verify. A metric is also carried, by sales compensation, contract terms, billing, and provisioning, and changing it means re-gearing all of them. The test: can both you and the customer easily monitor the count and agree on it, and can your own company carry it, from billing to provisioning to sales compensation?

Four properties cut across all six. A metric should never discourage use. It should be hard to game, including by sharing credentials. It should leave headroom for expansion rather than capping the account. And it should treat equal customers equally, where equal means equal in what they consume.

Three of the six are settled in the paper, not the meter

Read the dimensions back and notice where the answers live. Ambiguity is resolved in the terms both parties sign, or it is not resolved at all. Monitoring depends on provisions that make a count verifiable to someone who did not produce it. Estimation depends on what the buyer is committing to and for how long. Those three are grant questions that present as metric questions, which is how a company picks a defensible metric, satisfies itself on the dimensions it can see, and still finds itself negotiating at every renewal.

The dimensions are the visible part. The framework’s power is what you put in it, how you score each metric against the others, and the judgment applied to the result. Six names do not tell you which candidate wins for your product, your Customer Groups, and the contract you sell. The scoring, and the judgment applied to it, is where the framework earns its keep.

What a Software License Grant Actually Covers

Strip the boilerplate and a software license grant resolves into four dimensions: assignment, deployment, duration, and boundedness.

• Assignment. Who may use a unit, and whether that assignment is fixed to a person or floats across a population.
• Deployment. Where the software may run and be accessed: your environment, the customer’s, a named geography, or private infrastructure the customer controls.
• Duration. Whether the grant conveys indefinite rights to a version or a term that ends.
• Boundedness. Whether the quantity being counted has a ceiling. Unlimited-use language enters agreements here, priced as though it had not.

Where each of those lands is architecture work, specific to what a company sells and to whom. They are decisions either way; unmade, they default to the template.

Assignment is the one most companies never make

In modern B2B software the default is a named seat: a specific person holds it, and changing that requires an admin action. The older pattern pools fewer licenses across a larger population, working simultaneously up to the pool size. A device variant follows a workstation rather than a person. An active-user variant is consumed only by someone who logs in during a period.

Those are four structurally different licensing models with different growth behavior, different audit provisions, and different renewal conversations. Most vendors say per-seat and mean one of them without ever having chosen.

The Grant Is Where the Durable Properties Live

A widely repeated position in the pricing commentary holds that seat-based licensing produces predictable revenue, that predictable revenue earns a better valuation multiple, and that seats are therefore the safe architecture. The first clause is doing work the other two cannot support.

Predictability comes from contract structure and retention. A usage metric with a floor, a commitment, and a defined term is as predictable as a seat count. A seat count with monthly true-down rights and no minimum is not predictable at all. What produces predictability is the grant: how long it runs, what the buyer committed to, what happens when consumption moves. Companies reaching for seats to buy predictability are reaching past the mechanism that delivers it. It is also why diligence that sizes the wrong axis keeps mistaking a licensing question for a rate question.

Pricing policy is the other property that lives here, and it is the part of the grant most often left undefined: what happens when a customer goes beyond a grant threshold, how price increases are handled, whether overages bill at a premium per-unit rate, whether a true-up is allowed and on what terms. Each of these is answerable at design time. Left open, each surfaces later as a negotiation: at renewal, at the audit, or on the invoice that follows the overrun. Answered beforehand, they form the choice set that billing and entitlement are configured against later. Billing and entitlement come after the decisions, never before.

The buyer-side pull toward predictability is real. Peer-reviewed research on enterprise software licensing found that enterprise users tend to prefer concurrent licensing over usage-based arrangements out of concern for cost predictability. Separate peer-reviewed work on plans that pair a fixed fee with an included allowance found that buyers facing variable usage select larger allowances than their average consumption would justify. Buyers do not reject usage; they pay for a bill they can forecast.

The market is relitigating exactly this

In July 2026, Microsoft’s chief executive described the company’s commercial model as evolving beyond per seat toward per seat plus consumption to expand its addressable market. In the same period, an investor observing enterprise buying said procurement remains built around seat-based contracts. Both accounts hold. The tension is not resolved by picking a metric. It is resolved in the grant, where a seat and a consumption allowance can be defined as one unit or as two.

If you are working out which of those your own agreements can support, talk to a pricing expert and describe the contract you sell.

When the Grant Is Silent, the Meter Does the Arguing

The failure is rarely a bad grant. It is an undefined one, and something always fills the vacuum. Three moments do the filling: the renewal, the audit, and the first time something that is not a person starts consuming the product.

The sales floor meets the vacuum earlier than any of them. The licensing model and its grant hold the blueprint of the objections sales fields: how part-time employees count under a per-employee metric stops being hypothetical in the first deal where the prospect’s workforce is mostly part-timers. The more defined upfront, the less chaos selling generates.

What fills it is usually the enforcement layer. Whatever the product happens to check becomes the operative definition of what was sold. That is backwards, and it explains why so many companies discover their licensing model by reading their own telemetry. Enforcement and billing execute decisions; they cannot make them, and the decision layer is separate from the runtime layers that carry out its instructions. The systems that track entitled usage and control access are a mature software category, and they enforce a coherent grant and an incoherent one with equal fidelity.

Entitlement carries two definitions

In the tooling vocabulary an entitlement is a runtime construct: a feature flag, a configuration, a usage cap the system enforces. In the licensing model it is the contractual right itself, which exists whether or not any system checks it. The runtime definition has become the public one, and it describes how software enforces rather than what a contract grants. A company whose only answer to “what did we sell” is a list of flags has an enforcement inventory, not a licensing model.

Done deliberately, the two connect. GitHub calculates a cost center’s AI credit pool limit from assigned licenses, adjusting it as licenses are added or removed. That is the grant acting as the input to the meter rather than the meter acting as the record of the grant.

Duration Is a Grant Decision, and the Industry Already Proved It

The largest licensing change the software industry has made in thirty years was not a change of metric. It was a change to how long the grant lasted.

Perpetual licensing grants indefinite rights to a version. Subscription licensing grants rights for a term. In both, the unit counted was frequently the same: a user. What changed was duration, and every downstream mechanic reorganized around it. The fee structure moved from a one-time license charge plus maintenance to a recurring charge. Termination provisions began applying to access rather than support. Compliance provisions stopped being about version eligibility and became about active entitlement. Peer-reviewed research on enterprise software pricing published in the mid-2000s documented the resulting inversion of the revenue mix, as license fees gave way to recurring maintenance and services revenue over roughly fifteen years. Nothing about the metric had to move.

The enterprise license agreement is the same dimension

When a buyer asks for an ELA, they are usually not asking for a discount. They are asking to replace a counted metric with an uncounted grant across a defined population for a defined term. That is a licensing decision with a boundedness consequence, not the pricing concession enterprise deals are usually read as.

The US Department of Veterans Affairs awarded Salesforce a three-year agentic enterprise license agreement worth up to $1.6 billion. The term and the scope of that grant are the deal. The per-unit rate is arithmetic performed afterward.

What Licensing Hands to Packaging and Pricing

Licensing is called the first of the three architecture decisions for a structural reason, not a chronological one. Packaging groups what the licensing model made a unit of. The pricing model computes against that unit. Both take the licensing model’s output as their input, which is why a licensing decision made by default propagates into two more decisions that then look broken for reasons their owners cannot locate.

The boundary between licensing and packaging is where most architecture arguments start. A usage limit, a token allowance, a credit pool, or a seat count is a metric decision governing expansion: more of what the customer already bought. A module, an add-on, or an edition is a packaging decision governing upsell: capabilities the customer did not have before. When a volume commitment gates which capabilities a customer can access, those two motions have collapsed into one axis, and the buyer with modest volume and serious governance needs has nowhere to land.

The full three-decision sequence and the catalogue of models the market runs both operate on units the grant defines.

The Test to Run Against Your Own Agreement

Open the paper you sell and read the section that defines the unit. Then ask three questions.

If the thing consuming your product stopped being a person, would the agreement already have an answer, or would you be negotiating one? The structural response when agent activity starts displacing seat counts depends entirely on what the existing grant says.

If your largest customer doubled its usage without adding a single name, what would you be entitled to invoice? If the answer requires a conversation, the grant is doing less work than the metric assumed.

And if you moved your metric tomorrow, would the grant survive the move? Companies running a transition from seats to consumption usually find the metric change is the easy part and the grant rewrite is what takes the quarters.

Most companies can answer the first question and not the other two. That is not a legal-review failure; it is a decision never framed as one, costing money at every renewal nobody read closely. Talk to a pricing expert, describe what you sell and what your contract says about it, and a pricing architect will read the grant against the metric it is carrying and tell you where the two have come apart.

FAQs