Talk to an Expert

Staged change

Licensing: the unit and the grant

5 min on the light depth

The frame

The licensing decision has a unit and a grant. The unit, the value metric your price attaches to, was taught in an earlier module. The grant is the set of rights that unit entitles a buyer to: who may use the software, where it may run, for how long, and how much use the terms permit. Who counts as a user, which affiliates are inside, which environments are covered and what a trial permits are all grant questions. Licenses with the same unit and different grants are different products.

The grant is the half you most likely inherited. Teams debate the unit in a room and take the grant from the template the first deal started from. The gap surfaces later as pricing problems that are grant ambiguities. A request to run the product on the customer’s own infrastructure reaches the deal desk as a discount conversation. An AI agent acts against the product and the agreement never says whether that is licensed. An enterprise agreement is a grant written for one buyer, so the counting moves to its boundary. Entitlement management enforces the grant and can never write it.

The licensing model piece argues that the grant holds the durable properties, assignment, deployment, duration and boundedness, and that a silent grant leaves the meter to do the arguing. The per-seat variations piece argues that per-seat is an umbrella over separate decisions, and that each combination is a different grant. The deployment rights piece argues that where the software runs and where the model runs are separate grant questions, answered by template in most agreements.

Changing licensing on a live base is the deepest staged change, because every signed contract holds the old grant. The heavy depth gives the reading order, the shelf, and where the Observatory records licensing moves.

In your own license agreement, which sentence says what a licensed unit entitles the customer to do, and who besides a human user may act against the product?

Three things to say in the room this week

  • Our licensing model is the unit and the grant; we chose the unit and inherited the grant from a template.
  • Before we discount a request to run the product somewhere new, ask what the license now permits.
  • Every user license we sign from now on names a human; an agent is licensed through the person it works for.

Core reading

Go deeper: the heavy depth

Read the core in this order.

  • The licensing model: both halves of the decision, why the grant holds the durable properties, and the test for your own agreement.
  • Per-seat licensing as an umbrella: the axes under the phrase, how each variation behaves at renewal, and what AI agents do to the question.
  • Where your software may run: deployment as a grant dimension; the software’s location and the model’s location are separate grants.

Then the shelf.

  • The enterprise license agreement: a counted metric swapped for an uncounted grant across a defined population; the definitions at the boundary become the deal.
  • The fair usage policy: boundedness patched in at the policy layer when a flat plan rests on an unbounded metric; the repair is in the licensing model.
  • The trial license grant: a trial, a pilot and a proof of concept are different grants, with riders on who holds each and what bounds it.
  • The AI licensing model: the grant addresses the person, the agent and the model; the agent is usually left open.
  • AI agents and seat-count repricing: anchor user descriptions to humans on go-forward contracts, then watch what customer agents do.
  • Open source commercial pricing: what stays free is a Customer Group question; existing users move account by account.
  • License and entitlement management: these systems enforce what was granted; the decision is made elsewhere.

Glossary terms to open: license grant, licensing model and per-seat.

Where this leads. The Observatory’s licensing layer page collects the licensing moves from its verified ledger: metric swaps, credit introductions, entitlement changes. In its own words, the layer decides who may use the software, on what grant, measured by what unit.

Next on the spine: Price changes on the installed base, where a new grant meets contracts signed under the old one.

The shelf

Terms

Where this leads

Which depth did you take?