Product · contract and document review

Read it against everything that should govern it.

In build

A contract is checked against four things at once: the law and guidance that bind it, the facts it asserts, the commercial rules you actually run on, and the version of itself you agreed last round. Doing three of those by hand is why review is slow, and why the fourth gets skipped.

contractvetting.com

Why it exists.

One negotiation ran to twenty-six rounds. In each one the counterparty reworded something we had already struck — never the same way twice, never flagged in the summary. A person reading a fresh redline at eleven at night is being asked to remember nineteen previous drafts. Nobody can, and everybody is expected to.

What it does.

Every round, against the lastWhat you asked for and got. What you asked for and did not get. And what appeared that nobody asked for — the clause creep that survives because it arrives reworded rather than restored.

Against case law and guidanceClauses read against the authorities that decide them and the official guidance that applies, with the citation attached rather than a confidence score.

Against the factsThe same reading applied to any document, not only contracts: the claims it makes, checked against sources you can open.

Against your commercial rulesYour rules, written once and applied to every draft: what a payment term delay costs you, what a liability cap does to margin, whether the engagement sits inside IR35.

The round trip, trackedUpload, review, send the amendments, and receive the reply into the same thread — so the record of what was agreed lives with the document rather than in an inbox.

Who it is for.

Anyone negotiating commercial contracts in rounds — procurement, in-house counsel, and the finance people who find out later what the terms actually cost.

Status and access.

In build. Design partners with a live negotiation to point it at are the ones shaping it.