EN DE

Lawyers

The firm’s own positions, applied to every draft that arrives.

A two-partner commercial firm. An in-house department of five. Three solo Rechtsanwälte. A general counsel who is the entire legal function of a 300-person company. They are not behind on law. They are behind on contracts as objects — files that arrive, move, change and get lost.

Read more

A contract arrives as an attachment called Vertrag_final_final_v3(2).docx. Somebody replies with tracked changes from a version that was already superseded. Three weeks later a deadline that lived only in that document passes unnoticed. Nobody can say which version was signed. The lawyer spends the evening doing archival work with a law degree.

What moves, and what does not.

What the system takes over

  • Holding every contract the firm has touched as one current object — every version, every counterparty, every predecessor, permanently
  • Extracting the facts that carry risk: parties, dates, term, notice periods, governing law, liability caps, auto-renewal — each one pinned to the page it came from
  • The deadline diary — every date buried inside every contract, in front of you before it matters
  • Measuring each incoming draft against the positions the firm actually holds, and marking every departure with its reason
  • Keeping the negotiation moving: who owes a draft, who owes a signature, and how long it has been sitting there
  • Answering "where is this contract, which version is current, and what did we agree" instantly, for anyone in the firm
we build up to here

What stays with you

  • Whether a clause is acceptable
  • What to concede
  • Advice
  • Signature

What we build

The contract record

One place where every contract the firm has touched exists as a current object rather than as a file somebody has a copy of: identified, versioned, linked to its matter and its predecessor, wherever it arrived from. The final_final_v3(2) problem disappears in week one, and it is the change people notice first.

The contract summary sheet

One structured record per contract. Every field carries a pin back to the exact page and paragraph it came from. Nothing is stated without a location, because a fact you cannot check is worse than no fact — it looks like knowledge.

The playbook comparison

The firm’s positions, written down once, properly. This is the hardest and most valuable week of the project, because most firms have never written theirs down. Then each incoming draft is marked against it.

The first-pass markup

The centre of the system. A Word document with tracked changes where every single suggestion carries its reason as a comment: which playbook position it comes from, or which risk it addresses. You open it in Word — your own tool, not ours — and accept or reject each one by hand.

The deadline diary

Every date pulled into your calendar with reminders that escalate as it approaches. This is the piece with the highest raw value, because a missed notice period is a claim.

Where it stops

No legal judgement, ever, and no output leaves the building unread.

Read more

No advice, to anyone, at any point, internal or external. No automatic sending to a counterparty. No clause redrafted without a stated reason you can evaluate. Every extracted fact pinned to its source so checking it takes four seconds. There is no "accept all" — we were asked to build one and refused.

Alongside that, the conditions that make it usable at all in Germany: an AV-Vertrag under Art. 28 DSGVO, a separate confidentiality undertaking in Textform under §43e BRAO with express instruction on §203 StGB, data kept in the EU, no training on client content, privilege preserved, a full audit trail, and a documented answer to the Kammer question "who did this and can you show me?" A legal AI system without an audit trail is not deployable, whatever else it can do.

How you see it working

Missed notice periods since the deadline diary went live: none so far. "What did we agree, and which version is current" answered in seconds rather than in an afternoon. The share of incoming drafts that reach a partner already measured against the firm’s positions. And the one the partners cite — evenings no longer spent on version archaeology.

What it asks of you, and when we say no.

What it asks of you

Two weeks of your time writing the playbook down with us — the positions your firm actually holds, not the ones it assumes it holds. After that, about eleven minutes per contract instead of forty, spent reading suggestions rather than hunting for versions.

When we say no

Bespoke, high-value, one-off negotiation work. There is no playbook there because there is no repetition, and a first-pass markup on a genuinely novel deal is noise dressed up as help.

What clients say

The version problem alone was costing us evenings — Vertrag_final_final_v3 and nobody able to say which one was signed. He shipped only the intake and the filing in the first month and then stopped, which I found strange until I understood it was deliberate. The markup came later and every single suggestion arrives in Word with a reason attached, and I accept or reject each one myself. He was asked for an accept-all button and refused, and I would not have kept working with him if he had built it.

Partner, commercial practice

We are five people doing the legal work of a three-hundred-person company. What changed my week is the diary — every notice period in every contract is now a date I will be told about, and before this we had missed one and it was expensive. The extraction pins every field back to the page it came from, so checking it takes four seconds rather than trusting it. The audit trail was non-negotiable for us and it was the first thing he asked about, not the last.

General counsel, manufacturing, ~300 staff

Tell us what you are dealing with.

Thirty minutes, free, no preparation. We tell you honestly where AI could change something for you, and where it would not.

Book a 30-minute call All examples For law firms