A Renewal Hangs on a Word: Defining Active Use in SaaS Contracts

Most SaaS renewal meetings do not begin with a dispute about price. They begin with a slide. The vendor shows a dashboard, a line rises, and someone in procurement asks why the invoice has risen with it. The answer usually turns on a phrase that everyone recognises but nobody has defined: active user. In a UK SME, that phrase may appear in a licence tier, an order form, a renewal notice and a monthly report, each carrying a slightly different meaning. The dashboard is rarely lying. The word is doing too much work.

The number is not the argument

An active user count feels objective because it arrives as an integer. But a count is only as stable as the rule behind it. Is an active user someone who logged in at least once in the month? Someone who clicked a button? Someone who completed a task that the business cares about? Is the window 30 days, 90 days, or the contract year? Is it a named person, a concurrent session, a shared mailbox, a service account, or an integration? Each choice produces a different number, and each number can move a licence tier.

UK SMEs often treat this as a data problem. They ask for a better export, a cleaner dashboard or a meeting with the vendor's reporting team. Those requests have their place, but they can miss the underlying issue. It is cheaper to treat ambiguity in measurement as a vocabulary problem. Data can be queried; a word must be agreed.

Begin with the words that move money

Before renewal, list the terms in the commercial documents that actually change the bill: active user, named user, seat, instance, transaction, device, location, environment, support contact, API call, storage, or whatever your agreement uses. Do not start with every term in the contract. Start with the handful that appear in licence tiers, overage clauses, reporting obligations and renewal notices. A definitions register of six to ten terms is usually enough to expose the risk.

For each term, record four things: where it appears, the operational test that would settle it, the data source that evidences the test, and the owner who can confirm it. The operational test should be written so that two people could apply it to the same month of usage and reach the same answer. Logged in is a test. Using the platform is not.

A short exercise for the renewal file

Take one recent month and ask the vendor to show how the reported figure was produced under the definition in the contract. Then ask your own IT or finance team to reproduce it from single sign-on logs, expense records or the admin console. If the two numbers differ, do not immediately argue about the difference. First ask which definition each side applied. The gap is often not missing data; it is two different words masquerading as one.

Run the same exercise for the tier boundary. If the next tier begins at 250 active users, test the count around that boundary rather than at the total. A definition that is stable at 80 users may become contentious at 248. The purpose is not to win an argument. It is to make the renewal meeting confirm a position rather than discover one.

Edge cases are where the invoice hides

Definitions fail at the edges. Contractors who leave but retain an account. Shared inboxes used by a team. Read-only auditors. Implementation partners. Departed employees whose licences were never reclaimed. Service accounts that log in every night but represent no person. Integrations that write data without a human. Seasonal staff who are active for six weeks a year. A definition that does not address these cases is not wrong; it is incomplete, and incompleteness is where renewal surprises accumulate.

The practical response is to write inclusion and exclusion rules in plain English. For example: a named individual with a unique login who performs at least one saved action in the contract month, excluding service accounts, shared mailboxes and accounts disabled for more than 30 days. That sentence may not be perfect, but it is testable. Testability is the point.

Put the definition where it can be enforced

A slide deck is a poor place for a definition. It is not the contract, it is not the report, and it rarely survives the account manager's departure. The definition belongs in a schedule or annex to the agreement, referenced by the clause that sets the licence metric. It should state the metric, the measurement window, the data source, the reporting cadence, the treatment of edge cases, and the process for resolving a disputed count.

Two clauses are worth particular attention. The first is change control: if the vendor alters the dashboard, the metric methodology or the definition itself, the commercial effect should not arrive silently in the next renewal notice. The second is true-up mechanics: if the count exceeds the tier, how is the overage calculated, over what period, and with what notice? A definition without a consequence is only commentary.

The renewal should start earlier than the negotiation

The cheapest time to fix a definition is before the renewal conversation has a number attached to it. That usually means a short internal review well ahead of the notice period, bringing together the budget owner, the system administrator and whoever holds the contract. The output is not a legal opinion. It is a one-page definitions register, a sample month reconciled against the vendor's report, and a list of edge cases to be agreed.

None of this removes the need to negotiate. It does something more useful: it separates a commercial disagreement from a semantic one. When both sides know what active user means, the renewal can be about price, service and fit. Until then, the dashboard will keep showing a number, and the word will keep deciding what it costs.