Contracts.io

Solutions

Contracts for legal teams.

In-house counsel reads contracts other people made. contracts.io keeps the record straight: which words were sent, which were accepted, which were signed, and by whom, with accepting and signing held as two separate acts and nothing on any page offered as legal advice.

For legal teams

What a legal team can do here.

A version for every send, and for every signature

Each time a contract is sent, and each time it is signed, the words are snapshotted with a hash of the exact text. A signature binds to that hash, never to the contract as a moving object. Move the words and the signature is void, with a re-sign waiting.

The model underneath

Accepting is not signing

Two separate records, not two values of one status field. A signature cannot exist without an acceptance by the same party on the same words. A contract can sit fully accepted and wholly unsigned, and the product draws it as one.

The two acts, kept apart

Words move on unanimity

Nobody writes clause text directly: not a person, not a key, not an agent. A proposal names the block, the words before and after, and a reason. The other side answers it, and only then do the words move.

Redlines and the room

Lex reports what it found

Lex drafts, proposes and explains. It says what it found and where, and makes no claim to have understood. It never sends and never signs, and no setting changes that.

What Lex does

Governing law is a list

A contract names legal units, not countries, and may name several: law and forum can differ, and a schedule can carry its own. The picker names the place. It does not say what the law of that place requires, because that is advice and this product does not give it.

Every governing law

Read the record it keeps by making one.

The other side never pays and never makes an account.

Create contract

Last reviewed by the contracts.io editors. How these pages are written.