Early access
Revenue Contract Agent
Reads customer contracts, flags revenue risk, drafts the accounting.
−65%1 (modeled outcome) contract review time for revenue accounting
Legal and operations agent
GAContract Review Agent
The Contract Review Agent is a governed AI agent that redlines third-party paper against your playbook before signature.
How it works
What the Contract Review Agent does
Compares every clause of an incoming contract to your playbook positions, produces a tracked-changes redline with rationale, and escalates walk-away terms to the right approver.
- 01
Encode the playbook
Legal loads preferred, fallback, and walk-away positions by clause type and agreement type, plus the approval matrix. The playbook is versioned and owned by legal.
- 02
Receive and classify
Counterparty paper arrives from email, the CLM, or procurement. The agent classifies the agreement type and maps each clause to the playbook.
- 03
Redline and explain
The agent produces tracked changes with a comment per edit, flags walk-away terms, and drafts the issues list. Escalations route per the approval matrix.
- 04
Approve, send, record
An attorney or authorized owner approves before anything is sent. At signature, final deviations are recorded. The Registry reports cycle time and which positions hold.
app.meridian.example/agents/contract-review/atlas-msa
MSA · Atlas Manufacturing · redline v3
6 of 41 clauses off playbookCounsel review
9.2 Limitation of liability
− ...shall not exceed the fees paid in the twelve (12) months preceding the claim.
+ ...shall not exceed two times (2×) the fees paid in the twelve (12) months preceding the claim, excluding breaches of confidentiality and indemnity obligations.
Playbook §4.1 requires a 2× cap with carve-outs for confidentiality and indemnity. Counter drafted; counsel approves before it leaves.
The agent contract
Six terms, applied to this agent
Every Meridian agent runs under the same six terms, enforced at the Gateway below the agent. Here is what each one means for the Contract Review Agent.
Scoped to one workflow
Redlines third-party paper against your playbook. It does not negotiate.
Reads only permitted data
Reads the playbook, your templates, and incoming paper. Privilege labels are respected.
Every action logged
Full review history retained per contract. Final deviations recorded at signature.
Consequential actions require human approval
Never sends a redline externally. An attorney or authorized owner approves first.
Measurable outcome
Cycle time and which positions hold reported to legal operations.
Runs on your chosen model
Choose the model per workspace. Your documents never train Meridian's models or any third party's.
Scope
Data, actions, and approvals
What the Contract Review Agent reads, what it does on its own, and where a person signs.
Data it reads
- Clause playbook: preferred, fallback, and walk-away positions by agreement type
- Your templates and prior executed agreements
- Incoming counterparty paper from email, CLM, or procurement intake
- Approval matrix by clause type and deal value
- Entity, signatory, and counterparty records
- Deal context from CRM or procurement
Actions it takes
- Classify the agreement type and map clauses to the playbook
- Produce a tracked-changes redline with a rationale comment per edit
- Flag walk-away terms and clauses outside the playbook
- Route escalations by clause type and deal value per the approval matrix
- Draft the counterparty cover note and the internal issues list
- Record final deviations at signature for playbook analytics
What needs approval
- Never sends a redline externally; an attorney or authorized business owner approves first
- The playbook is versioned and owned by legal; the agent cannot change positions
- Clauses outside the playbook are flagged, not drafted from general knowledge
- Full review history per contract retained; privilege and confidentiality labels are respected
- Your documents are never used to train Meridian's models or any third-party model
Outcomes
Numbers the Contract Review Agent is accountable for
Modeled outcomes from design-partner deployments. The Registry reports your actuals from the first week an agent is live.
65%
faster pre-signature processing1
−70%
clauses requiring attorney edits after the first pass1
< 10 min
to first redline on standard agreement types
100%
of deviations at signature logged against the playbook
- 1.Modeled outcome from design-partner deployments. ↩
“We evaluated three platforms. Meridian was the only one where the approval step could not be turned off by the person building the agent. That is the property our audit committee cared about.”
100%
of consequential actions with a named approver at Atlas Manufacturing
In production at
Integrations
Systems it works with
Connected through prebuilt connectors and zero-copy warehouse access in Data Fabric. The agent acts as the user and inherits each system’s permissions on every read.
- Contract lifecycle management
- Document management
- Microsoft Word
- E-signature
- Procurement
- CRM
Credits
What the Contract Review Agent costs
Included on every plan: Starter with 5,000 credits per month, Growth with 30,000, and Enterprise with custom pools. Credits are consumed per completed action, never per message. Usage beyond the plan is billed at $0.12 per credit.
| Action | Credits |
|---|---|
| Contract redlined against the playbook | 8 |
| Issues list and cover note drafted | 2 |
| Single-clause playbook check | 1 |
Questions
Questions about the Contract Review Agent
Answered the way buyers ask them. Each answer is also published as structured data.
Related terms
It is software that compares an incoming contract to your organization's standard positions and produces tracked changes that move the document toward them, with an explanation for each edit. Meridian's Contract Review Agent works from a playbook your legal team owns and returns a first redline in minutes. An attorney approves it before it goes anywhere.
Legal encodes them in a playbook: for each clause type and agreement type, the preferred language, acceptable fallbacks, and walk-away terms, plus who must approve deviations. The agent applies only these. Clauses the playbook does not cover are flagged for a human.
No. It drafts the redline and the cover note. A person reviews, edits, and sends. The agent can process the counterparty's response and produce the next turn, again for approval.
Those are the highest-volume use. Design partners started with NDAs and standard vendor agreements, then extended to customer order forms and SaaS agreements once the playbook coverage was proven.
Yes. Redlines are delivered as native tracked changes with comments, so attorneys review in Word or in the CLM as they do today.
Related agents
Agents most often deployed alongside the Contract Review Agent, on the same data and the same approval policy.
Get started
Put the Contract Review Agent to work.
Start with one workflow, one approver, and one number to move. Most design partners were live in five weeks.