Do we have to use all of it?

No. Each page in this group is a surface you can adopt on its own — teams commonly start with the deal room or with clause negotiation on one agreement type and widen from there.

Where does the document actually live?

In the room, as one versioned record. There is no canonical copy sitting in an attachment, which is what makes the audit history meaningful rather than decorative.

Can a counterparty take part without an account?

Yes. A counterparty is invited into the specific room with scoped access to that agreement, not into your workspace.

What runs the automation — the agent or the rules?

Both, deliberately. Rules decide what must happen (which clauses gate, who approves what); the agent decides how to get there inside those rules.

The workspace the agent runs inside

An agent is only as good as the record it acts on. These pages cover the parts of the platform that hold that record — where the conversation happens, where the clauses get argued, where the signature lands, and where all of it stays provable afterwards.

Every part of the workspace

Each page covers one surface of the platform. Adopt them in any order; most teams start with whichever is currently costing them the most time.

Clause-level negotiation — Negotiate the clause, not the attachment
Contract AI — Comparison, extraction and drafting from your library
Workflow automation — Intake, routing, gates and dated triggers
E-signature — Signing as the last step, not a separate product
Review & audit trail — Where an agent must stop, and what it leaves behind
Security & control — Scoped access, agent limits, and what we don't claim

Four things every agreement needs somewhere to happen

Most teams have four tools for these and no connection between them. The cost of that is not licence fees, it is the reconciliation.

Somewhere to talk — A deal room where the conversation and the document are the same thread, so context never has to be reconstructed from an inbox.
Somewhere to argue — Clause-level positions with accept and counter as first-class actions, instead of a document with tracked changes attached to an email.
Somewhere to sign — Signature in the same place as the negotiation, so the signed version is provably the version that was agreed.
Somewhere to prove it — A timestamped, tamper-evident history of who moved which clause, when, and under what authority.

How a deal moves through the platform

Each step is a page in this group. Read them in order for the whole path, or jump to the one that is currently costing you time.

Open a room — Both sides land in one place with the request, the attachments and the people who need to approve it.
Draft from a position — Contract AI drafts from your approved paper rather than from whatever the last deal happened to settle on.
Negotiate clause by clause — Positions are accepted, countered or escalated individually, so the thing being argued about is always legible.
Route the exceptions — Workflow automation sends the clauses that need a human to the person who owns them, with the argument attached.
Sign and seal — E-signature closes it out and the audit history records what was signed and what deviated from standard.

Questions about the platform

Do we have to use all of it? No. Each page in this group is a surface you can adopt on its own — teams commonly start with the deal room or with clause negotiation on one agreement type and widen from there.
Where does the document actually live? In the room, as one versioned record. There is no canonical copy sitting in an attachment, which is what makes the audit history meaningful rather than decorative.
Can a counterparty take part without an account? Yes. A counterparty is invited into the specific room with scoped access to that agreement, not into your workspace.
What runs the automation — the agent or the rules? Both, deliberately. Rules decide what must happen (which clauses gate, who approves what); the agent decides how to get there inside those rules.