CLM pricing models compared: per-seat, per-module and per-contract

A disclosure before the argument

IntelloSync prices per module with unlimited users. That is a commercial position and it shapes what follows. The reasoning below is offered on its merits, and the cases where a per-seat licence is the better buy are set out honestly, because a buying guide that never concedes anything is an advertisement.

The four models

Almost every quote reduces to one of these, or a combination:

• Per seat or named user. A fixed annual price per licensed person. Predictable, easy to compare, and the dominant model in enterprise software.
• Per module. A price for a capability — contracts, compliance, vendors — with access not metered by headcount.
• Per contract or per transaction. Priced on volume: contracts created, envelopes sent, pages processed.
• Platform fee plus usage. A base fee for the tenant, with metered add-ons such as e-signature envelopes, AI processing or storage.

Why per-seat pricing quietly limits adoption

A contract touches far more people than the legal team. A procurement manager raises the request. A business owner supplies the commercial terms. Finance checks the payment schedule. One or two approvers sign off. A director signs. Someone in operations looks up a renewal date eighteen months later.

Under a per-seat licence, every one of those people is a line item. What happens next is predictable, and it is not that the company buys more seats. Legal gets the seats, and everyone else keeps working by email and attachments. The approval that should be an auditable step in the system becomes a forwarded message, and the repository stops reflecting reality.

The cost of that is not on the invoice. It shows up as a contract register nobody trusts, renewals discovered after they auto-renewed, and an audit trail with gaps precisely where decisions were made.

When per-seat is genuinely the better buy

Per-seat is not a trap. It is the right shape in several real cases.

• A small legal team that does its own approvals, where the user count genuinely is the team and will stay that way.
• High-volume, low-participant work — a collections or claims function where five people process thousands of standard documents and nobody else is involved.
• Pilots. A per-seat deal for ten users is usually cheaper and easier to cancel than a module commitment, which makes it a sensible way to test a vendor before committing.
• Procurement policy. Some organisations can only approve per-user software. That is a real constraint, not a mistake.

The costs that are not on the quote

Model aside, the headline figure is rarely the spend. Ask about each of these explicitly, in writing, before comparing two quotes:

• Implementation and template migration, especially converting an existing template library, and who does the work.
• Integrations — ERP, CRM, SSO, storage — and whether each is included, one-off or annual.
• E-signature. Envelopes are often metered separately, and in India the choice between Aadhaar eSign, DSC and a global provider changes the per-signature cost materially.
• Stamp duty and e-stamping, where applicable, which is a real cash cost quite separate from software.
• AI usage, if metered by pages, documents or tokens rather than included.
• Storage and retention, particularly for scanned legacy archives.
• Support tiers, and whether a named contact or a response SLA costs extra.
• Renewal uplift. A capped annual increase in the contract is worth more than a discount in year one.

How to compare two quotes properly

Build a three-year total, not a year-one price, and model it against how you actually expect to work rather than how you work today.

Write down the number of people who should touch a contract if the process were done properly — including approvers, signers and occasional readers — and price both quotes against that number, not against your current licence count. That single step tends to reverse the apparent ranking, because the per-seat quote was cheaper only under an assumption of restricted access that you were not intending to keep.

Then ask each vendor the same question in writing: what does it cost to add fifty occasional users next year? The answer, more than the discount, tells you what the relationship will feel like at renewal.