Solutions · Legal AI

Your Playbook decides. Every clause, checked.

Your Playbook sets what is accepted, what needs approval and what you may give in return. Luis reads every clause and value against it and shows the exact words as the source – and never negotiates outside your mandate.

PlaybooksClause LibraryNegotiation

Rule · Limitation of liability

  • Preferred12 months' fees
  • Their text6 months' fees
  • Fallback 19 months · Legal approves
  • StanceBalanced · Buyer
Product example

Sound familiar?

Sound familiar?

  • “Every counterparty sends their own paper, and we start from scratch.”

  • “Our playbook lives in the head of one senior lawyer.”

  • “We tried an AI tool. Nobody dared to send what it wrote.”

Why now

Most legal teams try AI on contracts. Few trust it with the outcome.

Contract review is where AI helps legal teams the most – and where a wrong answer costs the most. An answer you can't check is worth nothing, and an AI that concedes on its own is a risk no General Counsel will take. So the question is not what the AI can do, but what it is allowed to decide.

Today's alternatives and what good looks like

How it is usually solved

  • A general AI assistantFast, but you can't check it and it doesn't know your mandate.
  • Word and a checklistThe playbook is a document nobody opens under time pressure.
  • A separate review toolReviews the draft, then forgets everything once it is signed.

What good looks like

  • AI finds and reads. Your Playbook decides.
  • Every concession stays inside the mandate.
  • Every negotiation makes the next one better.

Legal and Legal AI, together

Your lawyers make the calls. Luis does the legwork.

Follow one supplier agreement from their paper to a signature. The Playbook flags, the Workflow pings the right person, Luis drafts within your mandate – and Legal makes every decision that matters.

  1. Legal AITheir paper arrives. The Playbook flags it.

    Luis reads every clause the moment the counterparty's draft is uploaded, and checks each one against your Playbook.

    2 deviations · § 11 liability cap · § 6.3 sub-processors
  2. Legal AILuis drafts the counter-proposal.

    For § 6.3 he writes the reply from the Playbook's rationale and your own data, citing GDPR article 28 on sub-processors. He proposes – he never sends.

    Draft reply · § 6.3 · Sources: Playbook, GDPR art. 28
  3. Legal AITheir answer is read in seconds.

    § 11 accepted, § 6.3 changed within your mandate. The negotiation history shows every round – and the next step.

    Version 3 · 2 settled · 0 open
  4. TogetherSigned.

    Both parties sign with BankID. The obligations become tasks with owners, and the renewal date has someone who answers for it.

    Signed with BankID · 3 Obligations · Renewal owner: Procurement
Product example

How it runs in Paragraf

From their paper to a signed contract – within your mandate.

Step 1 of 5

Every clause found, every value read.

Luis identifies each provision with its exact words and reads out the values – cap, days, months, governing law. Every value links to the passage it came from.

Playbook review · Nordlog AB

  • Limitation of liability6 months' fees · Deviating
  • Payment termsNet 45 · Deviating
  • Governing lawSweden · Accepted
  • Confidentiality24 months · Accepted
Product example

What you get

Three things that change.

Answers you can check

Every finding shows its source passage, the values and the reason. If something can't be verified, it is left out.

Inside the mandate

Luis never creates a concession outside the Playbook. Exceptions go to the approver you named.

A memory for your team

Negotiation history per counterparty version, and Improvements that turn experience into a better Playbook.

Your lawyers spend their time where judgement matters.

The reading, flagging and drafting is done. What is left are the decisions only Legal can make.

A man in a petrol blue sweater explains something with open hands, mid-sentence.

Before you decide

The questions that usually hold teams back.

Changing how work is followed up is a real decision. Here is how we make it a safe one.

Where do we start?

With one situation, not the whole organisation. We go through your systems and requirements together, set up the first flow with you, and then your teams build further on their own.

Do we have to change how we work?

No. Start from the contracts, templates and policies you already have. Paragraf takes over the follow-up – who does what, by when, and what proves it.

What happens to our data?

It stays yours. Everything follows your permissions, sensitive data is masked on the server and every change is logged. Ask us where data is stored and how export works – we answer in writing before you decide.

What if it isn't right for us?

Start with a limited first scope and clear acceptance criteria, agreed up front. You evaluate on your own data before you expand.

For the buying group

Everyone in the decision gets an answer.

A decision like this involves many people. This is what each of them can say when they bring it to the others.

  • General Counsel“Our legal risk goes down, and I can show it.”
  • CFO“Fewer overlapping tools and no consultant project for every change.”
  • Procurement“Supplier terms, dates and reviews have owners, not reminders.”
  • CEO“Management can see that we are in control – without asking around.”
  • CISO“It follows our permissions and gives one log for people, systems and AI.”

Next step

Fewer systems.
More control.

Book a walkthrough of your systems and requirements. We show you the thread from requirement to proof – with your own requirements.