Contract intelligence for legal teams
The platform that reads every clause you sign.
clmSpace reads your contracts, runs them against your playbook, authors the next agreement, and runs diligence on a new supplier before you sign. Built for General Counsel and Heads of Legal who would rather negotiate than chase PDFs.
Connects to SharePoint and Google Drive. Data held in London. Built by a UK company.
Ingest
Contracts come in from SharePoint or Google Drive. No uploads, no renaming, no spreadsheet.
1 / 5
How it works
Four jobs a legal team needs done. One platform that does them.
Your contracts stay where they live. clmSpace reads them, runs them against your house view, authors the next one, and runs diligence on new suppliers. All in one place.
Know what you have signed
Drop a contract in your folder. clmSpace reads it end to end and pulls out the obligations that matter. Payment terms, notice periods, caps, audit rights. Every line clickable back to the source clause. A contract register that knows what is in your contracts.
Run your playbook automatically
Every clause checked against your standard positions. Deviations flagged with the gap, the risk, and a redline in your own approved language. High risk findings ping the General Counsel in Teams the moment they arrive. Your house view, enforced.
Author the next agreement
Mark the variable fields in your template once. From then on, anyone in the team can spin up a fresh draft by answering a short form. It lands in your Drafts folder, picks up redlines as new versions, and runs cleanly to signature.
Vet new suppliers before you sign
Sales wants a new tool. You want to know if it is safe to sign. clmAI Procurement captures the supplier's online terms, version matched to the date they apply, reviews them against your policy, recommends approve, with conditions, or reject, and drafts the rider that closes the gaps. A human verifier signs off.
The work that eats your legal team.
Four jobs that disappear into folders, calendar reminders and Word documents that never talk to each other. Time your team should spend negotiating.
Hundreds of PDFs in SharePoint. “What is the longest confidentiality tail in our active NDAs?” takes three days and a junior associate. A register that lists agreement names is not a register that knows their clauses.
An MSA auto-renews with a CPI uplift no one negotiated out in 2023. The termination notice expired two weeks ago. You needed the standards delta on your desk 60 days early. You got the expiry seven days late.
“Our cap is 12 months.” Until seven counterparty MSAs slip through with uncapped indirects because the redline review was rushed. The standard exists. It is just not enforced anywhere a machine can check.
The same indemnity argument relitigated every quarter. Junior counsel relearning what senior counsel already settled. Your clause library lives in Tom’s head. It belongs in a system your team can reach.
The playbook authority model
Your house view, in three layers. Always the right answer for the deal.
Every redline, deviation flag and renewal draft resolves against the same playbook. Scoped to the type of agreement, your role in the deal, and the governing law. Your position overrides the learned one. The learned one overrides the market view. Nothing overrides what your General Counsel signed off this morning.
What your team has agreed is the house view.
- Entered by counsel
- Imported from your existing register
- Promoted from a learned position you verified
Authority: Highest. Quoted verbatim in every draft.
What your templates and history say you do.
- Extracted from a template you authored
- Mined from the obligations your team has verified
- Always surfaces with a verify button. Never silent authority.
Authority: Used as the default. One click promotes it to your house view.
What the market commonly does, when you are silent.
- Curated UK, EU and US positions
- MSAs, NDAs, SOWs, order forms, DPAs, reseller and licence
- Citable in negotiations. Opt out per tenant if you prefer.
Authority: Lowest. Used only where your team and the learned layer are silent.
One deal, one resolved playbook
Vendor-side MSA, English law. This is what your team gets back.
Every clause type returns one resolved position, with the layer that produced it.
| Clause type | Resolved position | Source |
|---|---|---|
| Liability | 100% of fees in the prior 12 months. Uncapped for confidentiality, IP, mandatory law. | Your position |
| Confidentiality | 3-year tail. Trade secrets indefinite. | Your position |
| Payment | 30 days net of valid invoice. | Learned |
| Indemnification | IPR indemnity with mitigation. Combination and modification carve-outs. | Learned |
| Notice | 30 days written, by either party. | Market view |
| Renewal | Fixed term. No auto-renewal. 60-day non-renewal window. | Market view |
Learned positions arrive with a verify button. One click promotes them into your house view. Market view is your safety net for the gaps in between.
The roster
14 specialists behind the platform.
Each capability is a named clmAI specialist with one job. clmAI Extractor reads the contract. clmAI Verifier holds it until a human signs off. clmAI Deviations compares every clause to your playbook. clmAI Negotiator drafts the redline. clmAI Renewals assembles the pack. clmAI Author drafts the next agreement and runs it to signature. clmAI Procurement vets new suppliers. They work together.
- clmAI ExtractorAgent
- Reads PDFs, Word, Excel, even scanned pages
- Click any obligation to jump to the source clause
- Handles long, layered MSAs without dropping detail
clmAI Extractor
Contract readerEvery clause read. Every obligation logged.
A clean register of who owes what, by when, at what price, across every contract you hold.
All plansDetails - clmAI VerifierAgent
- Review queue ranked by value and age
- Three states: proposed, verified, overridden
- Audit log with names and timestamps
clmAI Verifier
Lawyer-in-the-loopNothing counts until a lawyer signs off.
An audit trail you can show the board. Every AI suggestion accepted, edited or rejected by a named human, with a timestamp.
All plansDetails - clmAI DeviationsAgent
- Findings tiered high, medium and low
- Side-by-side: your standard against the actual clause
- Teams alert on high-risk findings
clmAI Deviations
Standard-vs-actualSee where their paper drifts from yours, the moment it lands.
Every contract scored against your standard positions, with the high-risk findings pinged to your team in Teams as soon as they arrive.
All plansDetails - clmAI NegotiatorAgent
- A negotiation pack for every flagged clause
- Redline written in your own approved language
- Sample paragraph for the reply email
clmAI Negotiator
Counter-position drafterDraft the redline before you draft the email.
For any flagged clause, the counter-position, the redline in your own language, and a paragraph to drop in the reply.
All plansDetails - clmAI DrafterAgent
- Five draft types: renewal, amendment, notice, termination, briefing
- Reads the full counterparty paper trail
- Flags any unknowns rather than guessing
clmAI Drafter
Renewals, amendments, notices, briefingsThe first draft, written from this counterparty's full history.
A first draft of the renewal, the amendment, the termination notice, or the internal briefing. Grounded in everything this counterparty has signed with you.
All plansDetails - clmAI AuthorAgent
- Mark template fields once. Reuse forever.
- Generate clean drafts in seconds
- Track every redline as a new version
clmAI Author
Templates to signatureFrom your template to signature, in one place.
Pick a template, fill the fields, generate a clean draft into your Drafts folder. Negotiate it. Approve it. Send it for signature. Without leaving the platform.
Foundation & upDetails - clmAI RenewalsAgent
- Pack ready 60-120 days out
- Recommended action with the rationale
- Your standards alongside the actual position
clmAI Renewals
Lifecycle orchestratorNever miss a renewal again.
A ready pack 60-120 days before every expiry. Recommended action, key facts, and the draft of whatever you need to send.
All plansDetails - clmAI ProcurementAgent
- Captures online terms incorporated by reference
- Reviews against your policy, grounded in evidence quotes
- Recommends approve, with conditions, or reject
clmAI Procurement
SaaS supplier diligenceVet a new SaaS supplier before legal reads another DPA.
An intake-to-decision file per supplier. Their terms captured, reviewed against your policy, recommended approve, with conditions or reject, and the protections to add.
Commercial & upDetails - clmAI RiskAgent
- Score from 0 to 100 per counterparty
- Reason breakdown you can audit
- Bands: low, medium, high
clmAI Risk
Counterparty risk scorerKnow which counterparties need your attention this week.
A score per counterparty with the reasons spelled out, so you know exactly where to look.
All plansDetails - clmAI StandardsAgent
- House view seeded from your templates
- Second layer learned from your signed contracts
- Market view for the gaps in between
clmAI Standards
Your playbook, kept currentYour playbook, learned from your own contracts.
Three layers of house position. What your templates say, what your verified history says, and a market view for the rest.
All plansDetails - clmAI WatcherAgent
- Bind any SharePoint or Google Drive folder
- Picks up new files every 5 minutes
- Never misses, never duplicates
clmAI Watcher
Document ingestDrop a contract in a folder. Five minutes later it is in your register.
Your SharePoint or Google Drive stays the source of truth, with ingestion running in the background on the folders you already use.
All plansDetails - Ask clmAIAgent
- Natural-language across your whole portfolio
- Citation chips that jump to the source obligation
- Chat history saved per user
Ask clmAI
Conversational portfolioAsk your contracts a question. Get a grounded answer.
"Show me every payment obligation above £50k due in the next 90 days." One sentence in. One answer back. Click any chip to jump to the source.
All plansDetails - clmAI CuratorAgent
- A library for every clause type, in three preference tiers
- Seed from your templates in one click
- Feeds the Negotiator and the Drafter
clmAI Curator
Clause libraryYour clause language, in one place, always at hand.
A library of preferred, fallback and walk-away language for every clause type. Reused verbatim in every redline, so every reply sounds like you.
All plansDetails - clmAI LifecycleAgent
- Explicit lifecycle events, never assumptions
- Reminders at 90, 60, 30 and 14 days
- "Unverified, needs review" is a real state
clmAI Lifecycle
Posture and eventsYour portfolio, always in a state you can trust.
Every contract has a current state you put it in. Active, renewed, terminated, expired, on hold. Nothing assumed. Everything auditable.
All plansDetails
Every plan ships with all core agents. From £9k a year.
Compare the plansProduct tour
Three artefacts your team works from on day two.
A register of obligations grounded in the source contract. A coverage heatmap that shows where your playbook is silent. A deviation pack with a copyable counter-position. The surfaces your team works from on day two.
Every obligation, citation-grounded to the source PDF.
Every obligation arrives with a verbatim quote, a page number, and a click-through to the exact paragraph in the source PDF. AI suggestions are held in the review queue until a human verifies them. Downstream connectors wait for that human sign-off before they fire.
Acme MSA 2024 · Obligations
81 extracted · 64 verified- ConfidentialityVerified
3-year survival of confidentiality post-termination
p.7· - LiabilityVerified
Capped at 12 months' fees; uncapped for confidentiality, IP
p.14· - RenewalUnverified
Auto-renew 12mo unless 60-day non-renewal notice
p.21·
“Each party’s aggregate liability arising under or in connection with this Agreement shall not exceed the fees paid in the twelve (12) months preceding the claim, save for breach of confidentiality, infringement of intellectual property, or liability which cannot be excluded by law.”
See where your playbook is silent, before counterparty paper finds it.
The coverage heatmap shows your playbook by scope and clause type. Green is your house view. Amber is what we have learned from your templates and history, ready for you to verify. Blue is the market view that fills the gaps. Grey is silence: write a position, or accept the market view with one click.
Playbook coverage
42 of 49 cells covered · 7 gaps| Scope | Liability | Confidentiality | Payment | Notice | IP | DP | Termination |
|---|---|---|---|---|---|---|---|
| MSA · vendor · UK | |||||||
| MSA · customer · UK | |||||||
| NDA · mutual | |||||||
| OrderForm · vendor | |||||||
| DPA · processor · EU | |||||||
| MSA · vendor · US-NY |
Flagged clauses come with a redline, not just a warning.
Every flagged clause opens into a negotiation pack. What they drafted, your house position, the suggested redline drawn verbatim from your own clause library, and a sample paragraph for the reply email. Copy the redline. Send the email. Close the gap.
Liability · clause 11.2
High riskAcme Holdings · MSA · vendor · UK · flagged on extraction
“No cap on indirect or consequential losses for breaches of confidentiality, IP, or applicable law.”
Aggregate cap = 100% of fees paid in the prior 12 months; uncapped only for confidentiality, IP indemnity, and mandatory law.
Each party’s aggregate liability shall not exceed 100% of the fees paid in the twelve (12) months preceding the claim, save for breach of confidentiality, infringement of intellectual property, or liability which cannot be excluded by law…
Trust
What your security team will want in writing.
Enterprise-grade reliability is an architecture problem, not a clever prompt. The controls below are built into how the platform runs, and an automated test suite of 160-plus tests covers authentication, authorization, tenant isolation and agreement access control on every change.
Your data, isolated by tenant
Every request is bound to a verified tenant, and identity, configuration and contract data are scoped to that tenant. Caches and the fast read model are tenant-scoped too. Access is checked on every read and write, including single-record lookups, and every check fails closed.
Hosted in the UK, with US AI inference covered
Your contract intelligence is hosted in the United Kingdom: the platform runs on Microsoft Azure in the UK, and your structured contract data lives on managed Postgres in London. Your source documents stay in your own SharePoint or Google Drive, read through connectors you grant and control. Standard documentation is ready on request: DPA, ROPA, DPIA templates.
Restricted transfers, covered
AI inference runs with Anthropic in the United States. That transfer runs under the UK IDTA referencing the EU SCCs, with a documented Transfer Impact Assessment. Under Anthropic's API terms and our commercial agreement, your contract content is not used to train models, and API data is retained only briefly for abuse monitoring.
Every line traces back to the source
Every extracted obligation carries a verbatim quote, the page number, and a click-through to the exact paragraph in the source contract. If the platform cannot cite a clause verbatim, the obligation is held back. Citation grounding is a correctness control, not just a UX nicety.
A human signs off before anything binds
AI suggestions land in a review queue. They are excluded from your authoritative house view, your downstream connectors, and your drafts until a named human verifies them. Every verification and override records the user, the timestamp, the before and after values, and a reason. clmSpace produces draft contract intelligence for your lawyers to act on. It is not legal advice and we say so on every deliverable.
Connects to the stores you already run
Bind the SharePoint or Google Drive folders you already use. Alerts and approvals land in the Teams channel your team already lives in. clmSpace reads only the folders you bind and keeps no separate copy of your source documents.
FAQ
Questions we hear on every first call.
How is this different from the big-name CLMs?
Traditional CLMs store contracts, route signatures and surface dates. Reading every clause and remembering every renewal is still a human job. clmSpace produces the same surface area: register, clause library, renewals workflow. The difference is that every clause has already been read, anchored to the source page, resolved against your house view and a market view, and surfaced as a clean obligation row before anyone opens the agreement. The other difference is the human verification gate between the AI output and any downstream system, so nothing AI-generated reaches your ERP, CRM or counterparty without a named lawyer signing off.
Is this a GRC tool, compliance, audit?
No. clmSpace is contract lifecycle: read, run the playbook, draft, deviate, renew, author, vet new suppliers. We do not run controls libraries, regulatory horizon scans, evidence catalogues or internal audit workflows. If you need GRC alongside, pair us with a GRC tool; they answer different questions on different objects.
How does the three-layer playbook actually work?
Three layers, resolved in order. The top layer is your team's own positions, entered or imported by counsel. The middle layer is learned from you: extracted from the templates you upload, and from the obligations your team has verified on signed contracts. The third layer is a curated market view that sits underneath, in case the top two are silent for that clause. Every position is scoped to the type of agreement, your role in the deal and the governing law, so the answer for a vendor-side MSA under English law is not the same as for a buyer-side order form in New York.
Is this legal advice?
No, and we say so on every deliverable. clmSpace produces draft contract intelligence for your qualified counsel to act on. We do not form a lawyer-client relationship and we do not displace your legal team's judgement. The verification gate exists so a human reviews every AI suggestion before it can affect anything downstream.
What if the AI hallucinates an obligation or a clause?
It cannot reach a downstream connector or a published draft. Every AI-extracted obligation lands in the review queue as proposed. Your ERP, CRM and procurement exports all gate on verified or overridden state by default. Drafting and counter-positions reuse your approved clause library word-for-word; the model is not asked to invent contractual language. Where the library has no entry, it falls back to your resolved standard rather than free-styling.
Do you train on our contracts?
No. AI inference runs with Anthropic, and under Anthropic's API terms and our commercial agreement your contract content is not used to train models; API data is retained only briefly for abuse monitoring. Your contracts stay in your own SharePoint or Google Drive. clmSpace reads them through connectors with scoped permissions, holds the extracted obligations in its UK-hosted service, and keeps no separate copy of your source documents.
Does this work with our existing SharePoint or Google Drive?
That is the design point. Bind the SharePoint or Google Drive folders you already keep contracts in, and new files are picked up every five minutes. Your document store stays your system of record and your source documents stay in place. The Teams app surfaces alerts and approval cards in the channel your team already lives in.
Which contract types and file formats do you cover?
MSAs, NDAs, SOWs, order forms, online terms, variations, amendments, DPAs, reseller and licence agreements, and bespoke counterparty paper. Files: PDF (with OCR for scanned pages), Word, Excel, CSV, Markdown and plain text. PDF obligations come with click-through bounding boxes to the source clause; other formats anchor to the source paragraph.
Can I start small and grow into more later?
Yes. Every plan includes all twelve core clmAI agents and the knowledge base, so Solo is the whole platform for one team, not a stripped-down starter. Foundation adds clmAI Author (template authoring and Drafts to e-signature). Commercial adds clmAI Procurement (specialist SaaS supplier diligence). Enterprise covers higher quotas, Microsoft Entra single sign-on and bespoke integrations. Upgrades take effect immediately and are pro-rated. Your source documents stay in your own SharePoint or Google Drive throughout.
What is the deployment time?
One day to first value. Bind a SharePoint or Google Drive folder and ingestion runs in the background within five minutes. Extraction, the playbook and deviation detection come online as contracts land. Template uploads seed your house positions in the first week, and the first renewal pack typically lands within a week of binding the Agreements folder. Authoring and procurement diligence switch on the same day you move to Foundation or Commercial.
See it run on your own contracts.
Bind a SharePoint or Google Drive folder. Five minutes later your contracts are being read, scored against your playbook and surfaced as a register you can search. A 30-minute call is usually enough to know if it fits.