Solutions · Contracts

You set the rules. Every contract follows them.

From the first line to the last obligation, your rules decide who approves, what may be said and when someone must act. The business moves fast. Legal keeps control.

Supplier agreementNordlog AB · draft

§ 4 Price

  • Logistics services · 12 moSEK 360 000
  • Warehousing · 12 moSEK 120 000
  • Cross-dock · 24 moSEK 760 000
  • TotalSEK 480 000

§ 11 Limitation of liability

Liability is limited to 12 months'6 months' fees.

Annex B

Data processing agreement · attached by rule

Approval route

  1. Contract ownerAlways
  2. Sales directorValue over SEK 1 m
  3. Legal§ 11 changed

Ready to send2 signers · in order

BankIDFrejaitsme+ more

rules · 3 active

Product example

Underneath

Powerful where it matters. Simple for everyone else.

Legal sets the rules once. After that, every contract builds, routes and follows itself – and nobody has to remember how.

  • Create

    Contracts that assemble themselves.

    Clause rulesProduct tablesAnnexesTemplates

  • Review

    The right person, only when needed.

    Rule-based approvalsPlaybook reviewTheir paper

  • Send

    One contract or hundreds.

    Bulk send~80 eIDsParallel or in order

  • Manage

    The whole relationship, one truth.

    ObligationsTermsFinance alertsAPI & MCP

Start from what you have – contracts in SharePoint, Google Drive or an inbox are sorted, read and matched with your finance system.

After the signature

Most contract tools stop at the signature. That is where the work starts.

A contract is a set of promises. Paragraf follows them: who owns each obligation, when it is due, and what proves it was done. The same obligation can answer a requirement in Compliance.

  • Renewal and notice dates with an owner, not a reminder in someone's inbox.
  • Recurring obligations that create their own tasks.
  • Evidence attached to the obligation, ready for the auditor.

Signed is where the work starts.

Every obligation in the contract gets an owner, a date and the evidence that it was done.

A man in a camel sweater reads on his phone with a small smile.

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.