, Nils-Erik Jansson
CLM requirements for a Swedish legal team: before the demo
Write the requirements list before the demo, from what your team needs. Written after the demo, it describes what the vendor showed, and then the project has gone wrong before the contract is signed. Here is the list for a legal team in Sweden with one to ten lawyers, in nine areas, with the requirements that separate the vendors and those that every vendor says yes to.
Three numbers first
- Contracts a yearSplit across your five most common types
- Contracts the business could create itselfFrom a template, if one existed
- Active contracts to trackWith a renewal or notice period
Nine areas
Data protection and exit are threshold requirements. Everything else depends on your numbers.
Your progress: 0 of 18
Contract workflow
Templates and playbook
Signing
Archive and search
AI functions
Integrations
Data protection and security
ThresholdExit
ThresholdPrice
Background
Before the list: three numbers
The requirements list is only useful if it starts from your team. You need three numbers first: how many contracts a year, split across your five most common types; how many of them the business could create itself from a template if one existed; and how many active contracts with a renewal or notice period need tracking. With those numbers, much of the list falls away because it does not apply to you, and the rest becomes concrete.
1. Contract workflow
Requests from the business with the fields you need for triage. Creation from templates without a lawyer for the contract types you designate. Review and approval in the order your approval matrix requires, with delegation during absence. Negotiation with the counterparty in the tool or in Word with version tracking.
At my contract management platform, customers often asked for free-text editing of contracts. When I asked what users actually changed, the answer every time was a date, an amount or a choice of clause: five fields at most. The request for free text reflected a habit, and the need fitted in those fields.
2. Templates and playbook
A template library with version control and an owner for each template. Conditional clauses, so that one template covers several cases. A playbook linked to the template, with a standard position, a fallback and a limit for each clause; see the guide on the contract review playbook.
3. Signing
E-signing with the identification you need: BankID, the Swedish e-ID, for Swedish counterparties, and email or another method for foreign ones. Signing order. Evidence that holds: a signing log, a time stamp, and locking of the document.
4. Archive and search
All contracts, including those signed outside the system, with metadata: party, type, value, start, end, notice period, owner. Search in text and metadata. Tracking of renewals and notice periods with reminders to the contract owner as well as the lawyer. Permissions per contract or category.
5. AI functions
What the AI does: extracts metadata on import, summarises, reviews against the playbook, suggests text, answers questions about the contract portfolio. Which model is used, who owns it, where it runs, and whether your contracts are used to train it. Whether you can opt out of the AI functions and what that does to the price.
6. Integrations
With what you already have: document management, email and calendar, e-signing, the ERP or CRM system where contract data should go, and identity management for sign-in. An open API with documentation you may read before signing.
7. Data protection and security
Data processing agreement, list of sub-processors, where data is stored and processed, third-country transfers and the assessment of them, retention periods and deletion, permissions and logging, certifications with reports (ISO 27001 or equivalent, which the Swedish Bar Association's guidance on external IT services asks for [2]), and notification of incidents and requests from authorities. The five questions in the data protection checklist should be answerable before signing.
8. Exit
Export of all contracts and all metadata in an open format, at any time, at no extra cost. What happens to the signature evidence. Deletion by the vendor after termination, with confirmation. A notice period that does not bind you for more than a year.
9. Price
Pricing model: per user, per contract, per module, or fixed. What is included and what costs extra: AI, signing, storage, integrations, support, implementation. Cost in year one including implementation and migration, and cost in year three. Price adjustment during the contract term.
Requirements that separate the vendors
| Area | Requirement | Why it separates them |
|---|---|---|
| 1. Contract workflow | The approval matrix can be built without the vendor's consultants, and the business can use the workflow without training | Shows whether the team can own the workflow itself |
| 2. Templates and playbook | The tool applies the playbook when reviewing the counterparty's paper, as well as when creating your own | The playbook adds value once it drives the review |
| 3. Signing | Signing is built in or integrates with a service you already pay for, and the evidence comes with you if you leave the system | Decides what happens to the evidence when you switch |
| 4. Archive and search | It is clear how existing contracts get in, in what format, and who creates the metadata | Shows whether the migration is planned |
| 5. AI functions | The AI functions are evaluated on your own contracts under the same protocol for every vendor; see technology selection | A demo on the vendor's examples tells you nothing |
| 6. Integrations | The integrations exist as standard and the cost of maintaining them through updates is known | Standard and custom-built integrations need different maintenance |
| 8. Exit | The export is shown in the demo | A vendor who cannot show it does not have it |
| 9. Price | A price per year for three years, in writing, before the pilot starts | Makes the cost comparable over the whole term |
How to use the list
I do not give weights per requirement. You set them yourselves by going through each requirement and choosing threshold, important or nice to have, based on the three numbers at the start. Threshold requirements screen vendors before the demo; the rest are scored during the demo and the pilot. Data protection and exit are threshold requirements. Everything else depends on your numbers. The demo and pilot protocol builds on the LegalBenchmarks evaluation framework [1], with additions for Swedish conditions described under technology selection.
How HOVR Legal works with this
The requirements list is the first step in legal technology selection, before the questions to the vendors, the demo on your own contracts and the pilot against fixed criteria. If you want to know what a single system actually does behind the demo, there is the technical vendor review.
See also e-signatures in Sweden.
Frequently asked questions
- Does a team of three lawyers need a CLM system?
- Not always. With a low contract volume, templates, e-signing and an orderly archive in the document system the company already has are enough, together with an AI tool set up with the team's playbook. CLM pays off when the business is to create contracts from templates itself, when renewals and notice periods must be tracked in volume, or when contract data needs to go into other systems. The requirements list is also useful for reaching the conclusion that the answer is no.
- Should we require a Swedish vendor or EU hosting?
- Require that you know where data is processed and by whom, and that the five data protection questions can be answered. A Swedish vendor does not settle the question by itself, because it may use US cloud services and AI models. The chain still has to be assessed. Requiring EU hosting is reasonable for the contract archive. For the AI functions, the question is which model provider sits behind them and under which agreement.
- How long does a technology selection with this list take?
- It depends on how quickly the vendors can do a demo on your contracts. The pilot should take four to eight weeks and be finished before a contract is signed.
Sources
- [1]LegalBenchmarks.ai, The Evaluation Framework
- [2]Uppdaterad vägledning om användningen av externa IT-tjänster i advokatverksamhet, Sveriges advokatsamfund, 15 april 2026, in Swedish; the Swedish Bar Association's updated guidance on external IT services; the requirements on the agreement with the vendor are a useful yardstick also outside law firms
Insights on the topic
Back to Technology selection
More under Technology selection
- Technical review of legal tech vendors
An independent review of what a legal tech or AI tool does behind the demo. You get a report on technology, data and vendor, with a recommendation.
- Legal technology selection: from need to decision
HOVR Legal leads the selection of legal tech, CLM or AI tools: requirements, long and short list, pre-demo questions, demo on your contracts, pilot, decision.
- Legal tech implementation: from selection to daily use
HOVR Legal brings the tool you chose into your organisation: owners, templates and rules, migration, data protection, a pilot group, training and handover.
- Demo on your own contracts: a protocol for legal tech
How a legal team runs a demo of legal tech and AI tools on its own contracts in place of the vendor's examples.
- Pilot criteria for legal tech: what to agree before signing
How a legal team runs a pilot of a legal tech or AI tool against fixed criteria set in advance.
- Legal AI in Sweden 2026: tools and framework deals
An overview for lawyers working with Sweden: the AI tools sold to Swedish law firms and legal teams, and what vendors say about sources and data.
- E-signatures under eIDAS, with Sweden as an example
The three eIDAS signature levels and their legal effect across the EU, what evidence rests on, and Sweden as an example: BankID and form requirements.