CLM buyer's checklist for 2026: what to establish before you shortlist
Contract management is the most expensive purchase on this site and the one most often bought for the wrong problem. The checklist below is ordered deliberately: everything in the first section is free, has to be true before a demo is useful, and is about your organisation rather than any vendor.
1. Before you speak to anyone
- Write down what actually goes wrong now, as incidents rather than themes. "Three renewals slipped last year" is a requirement. "Poor visibility" is not.
- Count your contracts a year, and how many are your paper against the counterparty's. Tools are usually much stronger on your own templates, and a business that mostly receives paper is buying a different product.
- Establish who signs what, and at what value. If nobody can state the approval thresholds, no approval-routing tool can encode them.
- Decide whether your positions are written down. If they are not, that is the project, and it is a legal project rather than a software one.
- Name the internal owner and the hours they have. Every configurable platform assumes one; deployments without one produce a half-built system nobody trusts.
- Ask whether the real problem is pre-signature (getting agreements out and approved) or post-signature (finding them and honouring them). Buying the wrong half is the most common and most expensive error in this category.
2. Scoping the requirement
- Separate must-have from would-like, and be strict. Configuration cost tracks the length of this list almost exactly.
- Decide whether you need obligation tracking or only renewal dates. They are frequently conflated and priced very differently.
- Establish whether reporting has a named consumer. Reports nobody has asked for are the most reliable source of unused configuration.
- Check whether an existing system already does part of this. A finance system holding renewal dates may cover the actual pain at no cost.
- Set the number below which a tool is not worth buying. Under roughly thirty live matters or a few hundred agreements, a maintained spreadsheet genuinely competes.
3. Evaluating vendors
- Test on your worst documents, not the vendor's sample. Extraction quality on a badly scanned or unusually drafted agreement is where tools actually differ.
- Give the trial to the person who will use it daily, not the person choosing it. A trial driven by the buyer tells you nothing about adoption.
- Ask which of their named customers, at your size and in your sector, went live in the quoted time, and ask to speak to them.
- Check whether the tool produces real tracked changes or a comment describing one, if counterparties will receive its output.
- Establish what happens to your data on exit: format, cost, and how long it takes. Ask before signing, because it has no leverage afterwards.
- Ask what the tool does when the model is unsure, and whether an uncertain answer is flagged or presented like any other.
4. The commercial terms
- Get the billing unit before the rate. Seats, contract volume, gigabytes and entities behave very differently as you grow.
- Model three years against that unit using your growth plan, not today's numbers.
- Get the annual escalator in writing at signature. Reported at 5 to 10% in this market, compounding a $100,000 contract to $121,000 by year three.
- Ask what the implementation fee is and whether it is included. Where it is charged separately it is frequently the larger half of year one.
- Ask what is in the base licence and what is a module, particularly AI capability, which is separately priced by several vendors here.
- Put a benchmarkable vendor in the process. Ironclad's reported median near $40,000 rests on 363 recorded purchases and Luminance publishes a list price, so either gives you a reference point in a category where most publish nothing.
5. After signing
- Agree the date of the first real piece of work, not the go-live date.
- Load a genuine sample early. Migration is almost always worse than expected because nobody has audited what is there.
- Set a review at ninety days against the incidents you wrote down in section one. If those have not changed, the deployment has not worked, whatever the dashboard says.
- Diarise the renewal notice window the day the contract starts. Missing your own notice period on a contract management purchase is commoner than it should be.