Customer communications management license models

Before a buyer can defend a customer communications finding, the buyer has to know which license model the finding rests on. Customer communications management software is not licensed the way most enterprise applications are. It is rarely a simple count of named users. Instead it is priced against output, capacity, or a subscription envelope, and the model that applies decides which evidence matters and where the finding can overreach. Understanding the available customer communications management license models is the foundation of any Exstream defense, because each model is measured differently and each fails in its own way.

This article describes the common license models for customer communications software, explains how each is measured, and shows where a finding inflates within each one. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

Why CCM is licensed by output

Customer communications software earns its value by producing communications at scale. A single design team can configure templates that generate millions of statements, notices, and letters, so a seat based model would bear no relation to the value delivered. Vendors therefore price the software against what it produces. That is why a customer communications finding is usually a volume figure rather than a headcount, and why the most important questions are what the chargeable unit is and how it is counted. The underlying concept is set out in what is an Exstream volume based license metric.

The volume model

The most common model prices a quantity of output: documents, pages, communications, or output transactions over a defined period. The entitlement is a volume of that unit, and a finding asserts usage above it. Everything turns on the unit definition and the counting window, both of which a finding tends to read for maximum value. The distinction between counting pages and counting documents is set out in Exstream page and document counting explained, and the channel dimension is examined in Exstream output channel counting traps. Under a volume model, production logs are the buyer's strongest evidence, because they show what was actually produced rather than what the system was configured to handle.

The capacity model

Some agreements license capacity rather than throughput: the provisioned ability to produce up to a defined volume, or the infrastructure on which the software is deployed. The danger here is that a finding measures provisioned capacity and treats it as consumed output, charging for headroom that was never used. The difference between counting what was produced and counting what could have been produced is the subject of Exstream transactional versus capacity metrics. Under a capacity model the buyer's task is to separate the provisioned envelope from actual production, and to confirm that the contract charges for one rather than the other.

The subscription model

Cloud and term arrangements increasingly license customer communications as a subscription, with a defined volume or tier included and overage terms beyond it. The model looks simpler but introduces its own traps: how overage is measured, whether non production environments are inside the subscription, and how the tier is interpreted at renewal or in an audit. These questions are covered in Exstream cloud subscription audit considerations and the deployment split in Exstream on premise versus cloud licensing. Under a subscription model the buyer reads the included envelope precisely and tests every claimed overage against the production record.

Where each model inflates

Each model has a characteristic failure point a finding tends to exploit:

• Volume model. The unit is read broadly and the counting window catches a peak rather than a representative period.
• Capacity model. Provisioned headroom is counted as consumed output.
• Subscription model. Non production environments and misread tiers are folded into the included envelope or counted as overage.

Across all three, the buyer's defense begins by identifying which model actually governs the contract, then reading the metric strictly against that model. The cost consequences of misreading the model are set out in how much does an Exstream volume finding usually cost.

How the four Rs apply across the models

The method works the same way whichever model governs. In the respond stage the firm takes over the single controlled channel inside the seven day notice window so the vendor does not fix the model reading before the position is built. In the reconstruct stage it identifies the governing model and rebuilds the genuine position against it, from production logs for a volume model, from deployment records for a capacity model, and from the subscription terms for a cloud arrangement. In the rebut stage every assumption that does not match the governing model is challenged. In the resolve stage the settlement reflects the model as written, and the forward agreement fixes the model and its measurement so the next audit cannot reinterpret it. The earlier the governing model is confirmed, the more precisely the rest of the defense can be aimed.

A representative outcome

In a recent engagement, an Exstream finding had been built as though a capacity arrangement licensed throughput, so the provisioned ability to produce a large volume was treated as volume actually produced. The buyer established from the contract that the governing model charged for produced output, reconstructed the genuine production volume from output logs, and showed that actual production sat far below the provisioned headroom the finding had charged. The matter settled well below its opening number, consistent with the reductions the firm sees across customer communications matters, with no figure introduced beyond what the production records contained.

The license models in one line

Customer communications software is licensed by volume, by capacity, or by subscription, and a finding can only be read once the governing model is fixed and the metric is read strictly against it. Identify the model first, then everything else follows. To prepare the underlying evidence, read reconciling Exstream entitlements before an audit, and to have your governing model identified and defended you can open a case with our team.

For the first week after a notice arrives, read the OpenText seven day notice response white paper.