All solutions
Support function · Legal

First-pass review against the clause playbook, with counsel confirming every flag.

Routine contract review queues behind the lawyers who could be on harder work.

For legal teams, general counsel who approves their releases, and the IT team that governs them.

How the example fits together: tools and an agent built on Unflood, with a person approving before anything is written.

Made from a conversation in Claude, released to the AI platforms your team already uses, running in your own environment.

Claude
Turn this conversation into an agent that reviews incoming contracts against our clause playbook.
Unflood created the agent from this conversation, ran its tests on past reviewed contracts and asked general counsel to approve the release.
  • Unflood: Contract-review agent created from this conversation 3m ago
  • Unflood: Tests run on past reviewed contracts 2m ago
  • Unflood: Released after general counsel approved 1m ago
  • Unflood: Shared with the legal team Just now

See it happen in a chat

A person on the team asks for an agent. Unflood does the building in the background and comes back for the decisions that are yours.

  • Unflood tests them.
  • A person approves each release.
  • They are shared with the right people.
  • They are kept up to date, so you step in only when a decision is yours.

Examples for Legal, to learn from

Example 1

Check incoming contracts against the clause playbook

On Unflood: Knowledge: the clause playbook.

Example 2

Flag missing or non-standard clauses, with the clause reference

Example 3

Answer the business's routine contract questions from approved positions

How a first-pass review fits together

Knowledge
Clause playbookThe playbook the lawyers already use.
Agent
Contract checkerCompares a contract with the playbook and cites the clause.
Test suite
Past contractsCases from reviewed contracts, run against every version.
Person
Counsel confirms each flagA lawyer decides; the agent only flags.

Six moments that make the difference

Each one is shown on sample data, with this team's own example where there is one.

Build it from a conversation

Describe the agent in a Claude chat. Unflood records it, its tools and its tests.

In Legal: Check incoming contracts against the clause playbook

  • KnowledgeThe playbook and the approved positions, bound by reference.
  • ToolsThe contract store, read only.
  • Builds itA senior contracts lawyer, from the playbook they already use.
Recorded from the conversation Contract checker
PlaybookPast contractsCounsel
Drawn on sample data.

Test it

Suites and a judge run it; each failed case becomes an item to fix.

In Legal: Past reviewed contracts, with counsel's findings as the answer key.

  • TestsPast reviewed contracts, with counsel's findings as the answer key.
Test lab
  • A case failsJudged against the version tested.
  • It becomes an item to fixNothing is lost between runs.
  • Retest, then release
Drawn on sample data.

Release it with approval

Package a version. Nothing reaches people without a person's approval; the builder cannot approve their own.

In Legal: General counsel.

  • Release with approvalGeneral counsel approves each version.
  • Approves itGeneral counsel.
Release waiting for approval
  • Packaged byA senior contracts lawyer, from the playbook they already use.
  • Needs approval fromGeneral counsel.
The builder cannot approve their own release.
Drawn on sample data.

Share it

Choose who can use it, person by person or team by team, where the team already works.

In Legal: Sales and procurement, for routine questions.

  • Uses itSales and procurement, for routine questions.
Who can use it
  • The Legal teamSales and procurement, for routine questions.
  • A named personChoose person by person or team by team.
Drawn on sample data.

Keep it up to date

Change it, retest it, release the next version. Every version can be rolled back.

Versions
  • Current versionLive.
  • Next versionChanged, retested, waiting for approval.
  • Roll backEvery version can be rolled back.
Drawn on sample data.

The organisation stays in control

Members, roles and a record of every change belong to the organisation.

  • A workspace for the organisation, on its proven domains
  • Members and roles: who uses an agent and who changes it
  • Release approval by a second person
Record of every change
  • The builderCreated the agent.
  • UnfloodRan the tests.
  • The approverApproved the release.
Drawn on sample data.

How the team gets there faster

Your people describe the work and approve it. Unflood does the building, testing and publishing.

Today

Routine contract review queues behind the lawyers who could be on harder work.

With Unflood

First-pass review against the clause playbook, with counsel confirming every flag.

Your people do
  • Builds itA senior contracts lawyer, from the playbook they already use.
  • Approves itGeneral counsel.
  • Uses itSales and procurement, for routine questions.
Unflood does
  • Connects your tools and data
  • Writes and runs the tests
  • Packages each version
  • Publishes it where your team works
  • Retests every change before the next release
  • Keeps the record of who changed what

Talk to us about your team

Tell us the work your team wants an agent for. We set up a workspace with you and build the first one with the people who know the work.

Get in touch