A contract lifecycle platform that reads every clause, and stands behind it.

Traditional CLMs are forms-and-workflows tools. They store contracts, route signatures, and surface dates — but they still need a human to read each clause and remember each renewal. CLMSpace produces the same surface area (obligation register, clause library, renewal workflow) but every clause has been read by Claude, anchored to the source PDF, resolved against a scoped playbook, and surfaced as a verifiable obligation row before anyone opens the agreement. The differentiator is the scoped User → AI → Market Practice playbook and the verification gate that sits between AI output and downstream connectors — neither of which exists in the incumbent stack.

No — and this matters. CLMSpace is a contract-lifecycle platform: extraction, playbook, drafting, deviation, renewal. It does not run controls libraries, regulatory horizon scans, evidence catalogues, internal audit workflows, or risk registers. If you need GRC, pair us with a GRC tool — they operate on different objects (controls vs. obligations) and answer different questions (am I compliant with X regulation vs. what does my MSA with Acme actually say). We will gladly help your security team write a clear scoping note for procurement.

Three tiers, resolved in order. Tier 1 (User) is anything your admin entered, imported, or verified — the highest authority, quoted verbatim in drafts. Tier 2 (AI) is what we derived from the templates you bound and from your verified obligation history (statistical, minimum sample size of 3) — surfaces with a 'Verify' button to promote into Tier 1. Tier 3 (Market Practice) is a curated 200+ entry corpus of common UK / EU / US positions we ship with the platform — used as fallback when User and AI are silent for that scope. Every position is scoped by agreement_type × party_role × jurisdiction, so the resolver returns different defaults for vendor-side MSA, buyer-side OrderForm, US-NY MSA, EU DPA, etc.

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-extracted obligation before it can affect a downstream system or a draft.

It cannot reach a downstream connector or a published draft. Every AI-extracted obligation lands in the Review queue with state AI_Extracted; the ERP payment schedule, CRM counterparty snapshot, and Procurement spend-cap exports all gate on Human_Verified (or Human_Overridden) state by default. For drafting and counter-positions, the Negotiator agent is constrained to reuse approved clause-library text verbatim — it does not invent contractual language. Extraction itself uses Claude tool_use with a strict JSON schema, so the model cannot return prose that wasn't in the source PDF.

No. We use zero-retention inference endpoints where our model providers support them, and we do not fine-tune or train on any client data. Your contracts live in your Microsoft 365 tenant; CLMSpace reads them via Microsoft Graph with app-scoped permissions, extracts structured obligations into your per-tenant Dataverse environment, and never copies content into a CLMSpace-owned store.

That is the design point. Bind the SharePoint folders you already keep contracts in; the Watcher polls Microsoft Graph delta queries every 5 minutes. No Power Automate flows to maintain. No parallel document store. Single sign-on through Entra. The Teams app surfaces alerts and approval cards in the channel your team already lives in.

MSAs, NDAs, SOWs, OrderForms, online terms, variations, amendments, DPAs, reseller and licence agreements, and bespoke counterparty paper. File formats: .pdf (with PyMuPDF word-level bbox), .docx (paragraph + table parsing), .md, .txt. PDF citations are click-through with bounding boxes; non-PDF formats use char-offset citations.

Yes. Solo (Extractor + Verifier + Lifecycle) is the entry point for cleaning up the contract register. Adding Drafter, Renewals, Deviations, Watcher, and Ask CLM (Foundation) is a billing-day upgrade with no migration. Negotiator, Risk, Standards Learner, and Curator move you to Commercial Office. Cancel any agent for the next billing period; you stop paying for it.

One day for Solo — bind a SharePoint folder; ingestion runs in the background within 5 minutes. One week for Foundation — template uploads feed Tier-1 positions, Renewals starts assembling packs, Ask CLM answers portfolio questions. Two weeks for Commercial Office — clause library curation, deviation thresholds, counter-position policy review. The first renewal pack typically lands within a week of binding the Agreements folder.