AI contract review · commercial practice
Brief reads every inbound agreement against your firm's own playbook, marks the clauses that fall outside your positions, and drafts the redline with the fallback language you actually use.
Brief does not give legal advice and does not sign anything. Every output is a draft, attributed to the clause and playbook rule that produced it, for an attorney to accept or reject.
9.3 Limitation of Liability. Except for the indemnity obligations set out in Section 11, neither party's aggregate liability shall exceed the fees paid in the three (3) months preceding the claim, whether in contract, tort or otherwise.
9.4 Exclusions. Neither party shall be liable for indirect, incidental, special or consequential damages, including loss of data, howsoever arising.
9.3, cap is 3 months of fees. Firm position is 12 months. Fallback 2 (9 months, mutual) inserted.
9.4, loss of data carved into the exclusion. Firm position requires data loss to sit outside the exclusion where the vendor hosts. Struck.
Four passes, in the order a senior associate would do them, with a citation back to the source rule at every step.
Identifies agreement type, parties, governing law, term, renewal mechanics and every defined term, including the ones defined in an annex three documents away.
Runs each clause against your firm's positions and fallbacks. Not a generic risk list, your positions, loaded from your own precedent bank.
Produces tracked changes in the original Word file using your house style, with a margin comment explaining the rationale for each edit.
A one-page issues list in plain English, ranked by commercial exposure, ready to attach to the covering email.
The reason generic contract AI produces redlines nobody sends.
Most contract review tools score clauses against an aggregate of public agreements. That produces a redline that is defensible in the abstract and useless in practice, because it does not know that your firm concedes on audit rights and never concedes on assignment.
Brief is loaded from your own material. Point it at a folder of executed agreements and the accompanying negotiation history, and it derives the positions your partners have actually taken, including the ones nobody has written down.
Sometimes it finds an inconsistency: the same clause conceded in one matter and fought in another. It surfaces that conflict for a partner to resolve rather than picking one silently.
Positions are versioned. When a partner changes the firm's stance on liability caps, the change is dated and every subsequent redline reflects it. Reviews run before the change keep the reasoning they were produced under, which matters when a matter is looked at two years later.
Nothing is a black box. Every edit Brief proposes carries the playbook rule number and the precedent clause it came from, so the associate accepting it can see exactly why.
And when Brief has no position on a clause, it says so plainly and escalates, rather than inventing one.
A twenty-two lawyer firm, mid-market technology and services agreements.
“The first draft used to take an associate four hours and it still came back to me with the cap wrong. Now it lands on my desk in ten minutes with the cap already at our position and a note telling me which fallback it used and why.”
Partner, commercial practice, twenty-two lawyer firm, London
Send one executed agreement and the redline your team produced. We'll show you what Brief would have marked, and where it would have disagreed with you.