[Agentic CLM]

One platform. Every contract.
Proof at every step.

Associates, automations and tested AI carry every contract from first draft to renewal, on your playbook. Your lawyers keep the decisions.

Associates. They work from your playbook. An example. Skills. Your firm's own method, written once. Sandbox. Dynamic code execution, sealed off from everything else. Connectors. The systems you already use, within the limits you set. Draft. On the firm's template, from the brief. Analyse. A risky phrase, found and rated. Redline. Clause 3.2, renewal notice, on their paper. Compare. Two documents, and what moved between them. Search. The whole repository, by keyword and by meaning. Run rules. Tried on your own contracts, read-only, before it goes live. Key facts. Read with the words they rest on. Collaborate. Two lawyers on one line, live. Switched on from Share. Share. To the other side, once a second person in the firm approves. Approve. Bound to this exact version. Sign. Sealed on the document.

An associate plans the steps and does the work.

Describe how your firm does it, and it becomes a skill.

Associates write and run code in a sealed sandbox

When a deal closes in Salesforce, the draft starts itself.

Between Helios Retail and Northwind Systems, for 12 months.

The Customer's liability is unlimited

Renews unless a party gives 30 days' 60 days' written notice.

Against your last deal, the cap moved from 12 months' fees to 6.

Search who can end on short notice? across every contract.

Above $2 million, A. Reyes approves first.would fire·would not·could not be decided

A party gives 60 days' written notice to stop renewal.Notice period: 60 days, in writing.read from clause 3.2

The cap is 12 months' fees, excluding fraud.

Northwind's counsel can view and comment.approved by a second person

Version 4, approved by A. Reyes. Locked to this text.

Signed by both parties.

The AI at work
The legal work
The contract's path

Associates. Give an associate instructions, tools and limits. It plans the steps, does the work and stops at the approvals you set. What it may touch is a ceiling you set.

Skills. A lawyer describes a job, and Clausel writes it as a firm skill, grounded in your own precedents. A library of built-in skills comes with it.

Sandbox. When the work needs real computation, an Associate writes the code and runs it in a sealed container: no network, read-only, a 30-second stop, then deleted. An admin switches it on.

Connectors. Connect Salesforce, Google Workspace and your own systems through MCP and open APIs. On your own APIs, every call except a read waits for a person.

Draft. On the firm's own template, from the brief, under the governing law you chose. Blanks fill from what you said, and the rest wait for a lawyer.

Analyse. Explain and assess, with no edits to the document. Figures in the answer are checked against the document before you see them.

Redline. Every change is placed only where the contract's own words are found. A change that cannot find them is flagged, not guessed.

Compare. Ask what changed between two documents. Quotes and figures in the answer are checked against the documents before you see them.

Search. Search the firm's repository by keyword and by meaning, with embeddings computed on Clausel's own servers.

Run rules. Written in your words and read back, with gaps shown, never guessed. Tried on your own contracts first, read-only: would fire, would not, could not be decided.

Key facts. Each key fact is read from the contract's own words and shows the clause it rests on. Anything else is flagged, not guessed.

Collaborate. Edit together, live, from the Share menu: colleagues see each other's cursors, and every change syncs as it is typed. Viewers watch. One editor writes the record.

Share. A guest outside the firm gets a one-time link to the named items, and nothing else. An owner proposes, a second person approves. Every view and comment is logged.

Approved version. Approval is bound to this exact version. A later edit revokes it, and a signer on an older version is refused.

Sealed. Signed, then sealed: a SHA-256 fingerprint over the document, computed before the certificate is added, with the audit trail.

Book a demo Watch a contract's whole life

One contract, start to finish

Watch a contract live its whole life.

Asked before it drafts

Clausel first asks which side you act for, then the details it needs, in one form. It writes nothing until you answer.

Drafted on your template

The MSA writes itself from the brief: parties, term and your positions, under the governing law you chose.

Reviewed against your playbook

The clasp finds clause 14.2. Unlimited liability is off book, and the rule says what to do.

Redlined, not rewritten

The old words are struck through and the firm's wording types in as a tracked change you can still reject.

Edited together

Colleagues work on the same clause, live, and leave comments on it. Viewers watch, and one editor writes the record.

Shared with the other side

J. Park proposes a link for Northwind's counsel, and A. Reyes approves it. They can view and comment, and every view is logged.

Approved for signing

Above $2 million, A. Reyes signs off first. Approval binds to this version, and a later edit revokes it.

Signed and sealed

Both signatures, then the certificate: a SHA-256 seal over the document and the audit trail, with ECTA section 13 wording, which is South African content.

Filed and watched

The contract lands on the record, and the last day to give notice lights up on the calendar your firm already uses.

EditingARJPLive
Shared withNorthwind's counsel
ApprovalA. Reyes, version 4

Master services agreement

Helios Retail Inc. and Northwind Systems Ltd · 12 months from 1 March 2026 · $4,200,000

3.1

This Agreement starts on the Commencement Date and runs for the Initial Term.

3.2
Term and renewal

This Agreement renews for successive terms of 12 months unless either party gives 60 days' written notice before the end of the current term.

7.1

The Customer shall pay Fees of $4,200,000 for the Initial Term, excluding VAT.

11.3

The Customer shall pay each undisputed invoice within 30 days of receipt.

14.1

Neither party is liable for indirect or consequential loss.

ARJPJ. Park: fraud stays out14.2
Limitation of liability

The Customer's liability shall be unlimited. Each party's liability is capped at the Fees paid in the twelve months before the claim, save for fraud.

15.1

The Supplier shall hold professional indemnity cover of not less than $5,000,000.

Approved for signingA. Reyes · above $2 million
L. Dube, for Helios RetailDirector, 16 Feb 2026
M. Adams, for Northwind SystemsDirector, 16 Feb 2026
SealedECTA s13
SHA-256
Contracts

Everything the firm has drafted or reviewed, kept after its conversation is gone.

MSAMaster services agreementNorthwind Systems · $4,200,000In reviewSigned
NDAMutual non-disclosure agreementKaroo Cloud · no fees payableAwaiting sign-off
SAASaaS subscription agreementHelios Retail · $18,500 a monthSigned
December 2026Deadlines · calendar feed
Last day to give notice on the Northwind MSA · 30 Dec 2026

One contract, start to finish.

The lifecycle

Six stages. One record.

A contract is drafted, reviewed, approved, signed, kept and renewed. Each stage usually lives in a different tool and a different inbox. Clausel holds all six on one record, with your playbook behind every stage and a person approving every step that writes or sends.

Draft on your own templates. Side-aware, under the governing law you choose, with the fields filled from the brief.

Analyse the other side's paper with no edits: what it says, what it risks, and the bottom line.

Redline it against your playbook: every change as a tracked change, with the rule it rests on. Nothing lands until you accept it.

Approvers decide in order, each with a reason on the record. Signing waits for the chain.

An electronic signature with a SHA-256 seal over the document and the audit trail on the certificate. Stale copies cannot be signed.

Key facts, obligations and deadlines on the record, each with the words it was read from. A person confirms each one.

The renewal radar finds renewal, expiry and notice dates due in the next 45 days, and sends nothing without you.

01 Draft

Start on your own paper.

Choose a template, say whose side you act for and which law governs, and Clausel drafts from the brief. The side is declared on the draft, not left as a quiet lean, so a later review of their mark-up carries it.

Drafting and templates

Your templates, with the real roles

Open one in the canvas and draft with Clausel from a brief, or describe a new template and have Clausel author it.

Side-aware intake

The same side question the review asks, so the draft and the redline agree on whose paper it is.

Governing law on the form

The matter's law or the firm default, shown on the draft form, changed in one click, and carried into the brief.

Draft with Clausel, or Draft with AI

Start a contract from a template, or have Clausel author a new one. Nothing saves until you say so.

Filed where it belongs

A template picker and a matter picker in the composer.

02 Review

Analyse it, or redline it.

Light Analyse, and Clausel explains and assesses the other side's paper with no edits. Light Redline, and it marks the paper up against your playbook: an issue table with the clause, the risk, what it says and the suggested fix, then every change as a tracked change with the rule it rests on. Nothing lands in the document until you accept it.

Clause 14.2, Limitation of liability, on their paper
The Customer's liability shall be unlimited. Each party's liability is capped at the Fees paid in the twelve months before the claim, save for fraud or wilful misconduct.
High. Rests on playbook §4.1. A tracked change you accept or reject, never written over.

Detectors read the page first

Then every rule in the playbook is checked, and the bar says how many it already meets.

The consistency engine needs no playbook

Value contradictions, missing schedules and undefined terms, found by code and explained by the model.

Honest about placement

A change it cannot place is listed as to place by hand, with Place in document.

Redline this

Select a passage on their paper and mark up just that clause against the playbook.

Three lenses, then Word

Original, Redline and Clean, margin marks with the clause number, a .docx with native tracked changes, or a Word memo.

Every quote checked

Figures and quotes the document does not contain are caught before you see them.

Review and redline

03 Approve, 04 Sign

Sign-off inside the firm. Signatures outside it.

Approvers decide in order, each with a reason on the record, and signing waits for them. The certificate carries a SHA-256 seal over the document and the audit trail. A routine can send for signature once a person has approved.

A rule in the playbook

Any supplier contract above $2 million needs A. Reyes's approval before signature.

1

J. ParkReviewed the redline. Liability cap holds.

10 Feb
2

Pieter van WykDeal desk. Value and term confirmed.

11 Feb
3

A. ReyesApproved for signature. Reason on the record.

12 Feb

Held until the last approver decides. Then the approved version is locked: a later edit revokes the approvals, and a signer on an older version is refused.

The certificate, with its South African wording

Electronic signatures are recognised under section 13 of ECTA 25 of 2002. Document integrity: SHA-256, computed over the document above this certificate.

Signers

In order, each by name, with consent recorded.

Conditions precedent

Your firm's items before sending, each signer's before signing.

Sealed at completion

The SHA-256 seal, the audit trail and the signer's consent on one certificate.

SHA-256 sealAudit trailSigner's consent

Approvals and signing

05 Keep, 06 Renew

After signature, the record keeps the deal.

Every contract has a page: value, dates, notice and obligations above the document. Key facts are read with the words they rest on, and a person confirms each one. Obligations land in the deadlines calendar your firm already uses. The renewal radar watches the notice date, and books nothing without you.

Key facts with their quote

A key fact Clausel read stays marked as its reading until a person confirms it. A reading that differs from the record is offered with its quote, never written over.

Obligations in your calendar

Each obligation names the clause it rests on. Google, Outlook or Apple subscribe to the deadlines feed.

The renewal radar

A weekly digest of renewal, expiry and notice dates due in the next 45 days. Anything that writes or sends waits for a person, and is never sent twice.

The Contracts ledger

Everything the firm has drafted or reviewed, with saved views from In review to Renewing in 90 days and Missing key facts. Filter, choose columns, edit in bulk, export to CSV.

Counterparties and clients

Every party on one page: its contracts, next renewal, recurring issues and the positions previously accepted. A client holds its matters, and the fields and rules scoped to it.

Your own fields and types

Seven kinds of field, from text and money to a person, scoped by contract type and by client. Every edit is validated on the server and kept in that field's history.

Contracts and lifecycle

Across every stage

Your playbook and your associates run across all six.

Neither is a step in the process. Positions are written once as sentences, compiled, tested on your own contracts and set to watch or enforce. An associate is hired with a brief: its instructions, the rules it never crosses, what it can see and what it can do. Anything it writes or sends waits for a person.

A rule in the playbook

Liability on contracts where we act for the customer must be capped at twelve months' fees.

Standard position

A monetary liability cap is mandatory, default six months of fees.

Fallback

Twelve months of fees, for direct loss only.

Walk-away

Unlimited, uncapped or one-way liability. Never acceptable.

Off, watching or enforcing

Tested on your own contracts first: would fire, would not, could not be decided. Watching records what it would do. Enforcing changes the document.

An associate's brief

You review every NDA the firm receives against our Mutual NDA playbook. List the issues by risk, suggest redlines, and flag anything a partner must see.

Rules it never crosses

Never send anything outside the firm without a person approving it. Never edit a signed document.

What it can see

The whole firm, only its matters, or only where it is bound.

What it can do

List and search the repository, get a contract, get the playbook, contracts due.

Where its work goes

Findings go to the contract record and the matter inbox. Nothing leaves the firm without a person approving it.

Routines. Describe what should happen and read it back, or build it from steps. Off, dry-run or live. A step that is done never runs again, and an outbound write is never sent twice.

The office. Each associate has a page: routines, runs, the issues it found, what is waiting for you, and its guardrails. Give it a task from the app, or from your own systems through an OpenAI-compatible API.

The rules engine Workflows and associates

What stays, and what improves

It remembers your firm. It proves it got better.

Contracts and documents sit on a matter, drafts start from your templates, know-how sits in an approved knowledge base, and what your firm decides becomes memory. A change to how an Associate works has to beat the old way on your own contracts.

Matters

Group contracts, documents, chats and people against one deal. A matter narrows everything Clausel reads while you work on it.

Vault documents

Each document keeps its section offsets, so a search result is a place: section 4.2, page 11. Search by meaning and by keyword together.

Templates

Your firm's own paper, every blank a field. Clausel fills a template and does not rewrite it. Describe a new one and Clausel authors it for a lawyer to keep.

Knowledge base

Precedents, practice notes and a clause bank. Nothing is used until an approver signs it off, and every approval carries a review date.

Contract record

Editable metadata on each contract, with fields your firm sets for each type. A value read from the contract keeps its source until a lawyer confirms it.

Team

Admin, lawyer and viewer roles, members for each matter and ethical walls between matters. A guest sees only the items named for them.

Memory

Remembered by thread, by matter and by firm, the most specific first. Clausel states what it used, and counts how often each memory applied.

How it improves

Your decisions become the firm's history.

Each edit, rejection and precedent is captured by clause type. The next review reads it beside your playbook, as history and not as instruction, so a lawyer still decides.

An Associate's work gets a score.

It reviews up to three of your own contracts in a dry run that writes nothing. The score asks three things: did it cite the playbook, was it grounded, and did it agree with what your lawyers decided?

One change, not a rewrite.

Clausel suggests one change to the Associate's instructions, guardrails or read tools. It can never add a tool that writes.

The same contracts, read again.

The changed Associate reviews the same contracts, also dry. The change only counts with a clear gain and no part of the score going down.

A person decides.

A lawyer adopts or dismisses it, and only an admin can change a live Associate. Adopting makes a new version that records why. Dismissing keeps the lesson, so the same idea does not come back.

Observable. Every run keeps its steps and results. The activity trail shows each view, share, run, approval and signature across the firm, and on each matter and contract.

On your say. A trial starts only when someone asks for it, because it runs real reviews. Where enabled, it never changes anything by itself.

The workspace

Everything above lives behind one sidebar.

New work is where a lawyer starts the day. Automate is where the firm's repeat work runs without one. Every place reads the same record, so the approval chain knows what the review found, and the renewal radar knows what was signed.

New work

Ask anything: redline, analyse, draft, compare, or question your contracts. Five lamps choose the lane. A playbook and a scope, the whole firm or one matter.

Matters

A room per matter: vault, contracts, chats, people with roles, routines, a knowledge base and activity. Ethical walls, guests, and review tables that quote every cell.

Contracts

The ledger, counterparties, deadlines, benchmarks and the risk radar. Built-in views from In review to Renewing in 90 days. A page per contract, and a calendar feed for the deadlines.

Playbook

Positions with a fallback, who must approve, the walk-away and suggested language. Rules set to off, watching or enforcing. A knowledge base with owners and review dates.

Templates

Side-aware templates with the real roles for each type. Open one in the canvas, draft with Clausel from a brief, or author a new template with AI.

Insights

The pipeline, the risk mix, what needs attention and who is carrying what. A board pack for any period, exported to Word.

Associates

Hired with a brief, each with an office. Routines built from blocks: input, AI, logic, human, output, connector and code. Runs and an inbox of what waits for a person.

Skills

The firm's repeatable pieces of work, written once. Open one to read it, run it on a sample, call it from the composer with a slash, or give it to an associate.

Connectors

Your accounts, the firm's calendar, channels, MCP servers and developers: the ingest API, signed webhooks and actions from an OpenAPI document.

The bell. One panel of notifications, with what needs you first: an approval, a signature, a workflow waiting, a request past its turnaround.

The activity trail. Every view, share, run, approval, signature and download across the firm, newest first, and the same trail on each matter and each contract.

How a 100-page contract is handled.

From upload to redline, in six steps.
1

Read. Text comes out of Word or PDF. A page with no text layer goes through vision OCR first.

2

Number. One heading detector numbers every clause. The canvas, the numbered original and the redline all use it, so a clause number never disagrees.

3

Scout. A first pass reads sections of up to 28,000 characters, about nine pages, four at a time against your playbook. At most 40 candidates go forward.

4

Review. The main run checks the candidates, adds what it finds and writes the cards, with the contract's own clause numbers.

5

Window, if needed. When the token budget cannot hold it, the review splits into up to six passes, cut at clause boundaries. The final pass writes the verdict over all of the findings.

6

Place. The numbered original opens in the canvas and changes arrive as patches to single clauses, not a retyped document. A change that cannot find its words is not placed, and Clausel says so.

Ask about clause 48, and it reads clause 48.
1

Budget. Each document gets up to about 60,000 characters in a turn. The question decides how they are spent.

2

Pick. The windows that match the question and the conversation so far are chosen by plain word matching, with no network call.

3

Frame. The title, parties, recitals and the start of the definitions stay in, so the answer knows what the document is.

4

Follow up. A short follow-up still finds its clause, because the earlier conversation counts in the search.

Large redlines stay fast.
1

Open. 2,268 tracked changes on our own 100-page test contract rendered in the canvas in 727 ms.

2

Accept. Accept all is one canvas action with no model call. On the same contract it took 108 ms.

3

Export. The redline downloads as a Word file with native tracked changes.

The ceiling. A review takes up to 600,000 characters, about 190 pages. Beyond that, Clausel says so and points you to Analyse, Ask or a split. The Ask test ran on a 113-page test lease.

Every jurisdiction

Work under whichever law the contract names.

Clausel reads the governing law from each contract, and a review judges the contract under its own stated law. Your playbook holds your firm's positions, for whichever law you work under.

73

countries to choose a firm default governing law from, across Africa, Europe, the Middle East, Asia, the Americas and Oceania.

Drafted to the named law

When a draft names a different law, Clausel drops the home template and drafts from the brief to the named law.

Cross-border deals flagged

Flagged on the record, and a ready workflow routes them to counsel. Optional fields cover forum, seat, dispute mechanism, currency, counterparty jurisdiction and place of performance.

Checked against the words

Answers are checked against the contract's own words, and a person makes the hard legal call.

South African depth, as one example

21 South African templates, ECTA section 13 wording on the signing certificate and POPIA wording. These are South African content.

Your data

Your contracts stay yours.

  • Every read is scoped to your firm, and to the matter you name
  • Figures and quotes the document does not contain are caught before you see them
  • Nothing is written to a contract until a lawyer accepts it
  • Signed documents carry a SHA-256 seal and an audit trail
  • Every webhook is signed with a timestamped HMAC, retried and logged

Works with

The tools the firm already uses.

Built in, needs setup
GmailDriveCalendarOutlook mailBeta
Ready template
Salesforceevent only
One-way feed
SlackMicrosoft TeamsGoogle CalendarOutlookApple Calendar
Open API, your keys
WorkdayServiceNowIngestion APISigned webhooks
Planned
SharePointOneDriveOutlook intakeWord add-in
Not connected
DocuSignClausel signs natively
Runs on
OpenAIAnthropicGoogle Geminione vendor setting per deployment

Levels say what is built today. A mark means Clausel connects to that system, or runs on it, nothing more. Every system, and which way the data moves

Frequently asked questions

Law firms and in-house legal teams. Drafting, review, approvals, signing and the record after signature, on one page per contract.

No. Redlines export as a Word .docx with native tracked changes, the findings export as a Word memo, and signed copies download as PDF. Drafting, review and the record live in Clausel.

Every rule in the playbook is checked against the contract, and the bar says how many rules it already meets. Each finding and each change names the rule it rests on. A review uses the playbook you pick or the firm default, and asks when none is in force.

It says so. A change it cannot place in the document is listed as one to place by hand, with a Place in document control, and a finding with no wording to offer is marked for your judgement, no edit.

No. Anything an associate or a routine would send outside the firm waits for a person, and an outbound write is never sent twice. Routines run off, dry-run or live, and dry-run saves and sends nothing.

A SHA-256 seal computed over the document at completion, the audit trail and each signer's consent. The certificate's wording is South African content: it states that electronic signatures are recognised under section 13 of the Electronic Communications and Transactions Act 25 of 2002.

Bring us a contract you know well.

Book a demo and watch Clausel work against your positions. You will soon know whether it reviews the way your firm does.

Book a demoStart with review
  • FirstA review against your positions, with the rule behind each change
  • ThenA redline that opens in Word with native tracked changes
  • LastApproval and signing on the same contract