Superintelligence.
Under your control.
Where legal, compliance, processes and people work as one. Every answer within your permissions, every step with its source.
Trusted by legal, finance and operations teams across Europe
- Bauer Media
- ISS
- Caparol
- BEWI
- Wellvita
- WaterAid
- Save the Children
Start where the pressure is
One situation first. The rest builds on it.
Most teams start with the requirement that has a deadline. Everything you set up there – suppliers, clauses, owners, evidence – is reused when the next team joins.
- Supplier contracts under NIS2 and DORASee which contracts lack the required terms – and close the gaps. For Legal and Procurement.→
- Prepare for NIS2Duties mapped, owners assigned, evidence ready. For the CISO and Compliance.→
- Meet DORAICT contracts, register and exit plans in one place. For Risk and Finance.→
Why we exist
Large organisations have learned that change is expensive.
Every new requirement becomes a new system. Every new system becomes an integration project. Consultants, years and millions – and still nothing connects. We don't believe it has to be that way.
More systems have never meant more control. Habit is not law.
The platform today
One contract. Every team sees its part.
A supplier agreement is not only Legal's. In Paragraf the clause, the requirement, the review, the price date and the access live on the same record – and every step lands in one log.
Supplier agreementNordlog AB · SEK 1.2 m · 2027–2028
Log
PermissionsLogRules
- LegalClause § 14.2Approved
- ComplianceNIS2 art. 21.2 dLinked
- ProcurementSupplier review3 of 5
- FinancePrice review1 Dec
- ITPortal accessLogged
From requirement to proof
New requirements.
Same foundation.
A requirement becomes a clause, an owner, a routine and evidence – in the same place, under the same permissions. When someone asks if you comply, you show the thread.
- RegulationNIS2 art. 21.2 d
- ClauseSupplier agreement § 14.2
- OwnerCISO
- RoutineSupplier review, step 3 of 5
- EvidenceSigned electronically
14 Oct 09:42 · chain unbroken
Compliance
Requirements become ways of working, from regulation to evidence. See which controls have an owner, which evidence is current and what is missing.
- NIS2
- DORA
- GDPR
- ISO 27001
Contracts
Create, review, sign and follow up in one flow. Every obligation in a contract gets an owner and a date – and ends in evidence.
- Contract Studio
- E-signing
- Repository
- Obligations
Security
Control is in the foundation, not added on top.
People, the systems you connect and AI work under the same permissions and the same log. One data model, so what you build never ends up as a shadow system.
- Permissions everywhereRBAC, SSO and Entra. Everything you build inherits the same rules.
- Full logEvery change and every decision can be traced.
- Frameworks built inNIS2, GDPR and ISO standards article by article, mapped to each other – and a register for the laws you follow.
- In the EU – or on your own serversHosted in the EU, or delivered on your local servers with a local AI model.
- Nothing changes without a personProposals – from Luis or anyone else – wait for review. Every approval is logged with who and when.
- Fewer systemsNo integration projects between your requirements, contracts and processes.
Luis at work
He finds it, explains it
and prepares the next step.
Everything above works without Luis. He just makes it faster: he knows your contracts, requirements and processes, answers in text or voice, always shows where it comes from – and nothing changes until you have reviewed it.
Which supplier agreements renew in the next 90 days – and who owns them?
Luis
Four supplier agreements renew before 31 January. Two of them have no owner yet, and one has a 60-day notice period that starts on 2 December.
Sources
- Repository · 4 contracts
- Logistics agreement § 8.2 Auto-renewal
- Obligations · owner missing
Proposal · waiting for your review
Create an Obligation Task for each agreement without an owner, due at the start of its notice period.
What does NIS2 require of how we review our suppliers?
Luis
NIS2 article 21.2 d requires supply chain security, including the security aspects of your relationships with direct suppliers. You have twelve supplier agreements in scope. Three have no current supplier review as evidence.
Sources
- NIS2 art. 21.2 d
- Control · Supplier security review
- Evidence · 3 missing
Proposal · waiting for your review
Link the requirement to your Control and start the supplier review Process for the three agreements without evidence.
Review this data processing agreement against our playbook.
Luis
Two clauses deviate from your playbook: the liability cap in § 11 is lower than your minimum, and § 6.3 gives you no notice before a new sub-processor is added.
Sources
- Playbook · Data processing
- Clause Library · Approved sub-processor clause
- GDPR art. 28.2
Proposal · waiting for your review
Replace § 6.3 with your approved clause and send § 11 to Legal for a decision in the Workflow.
How is revenue tracking this year – and what is still unpaid?
Luis
Revenue so far this year is SEK 17.3 million, up 14 % on the same months last year. Three customer agreements have overdue payments, together SEK 410 000.
Highest in Oct 26: SEK 2.1 m
20262025
Sources
- Revenue lines · 212 rows
- Customer invoices · 3 overdue
- Counted with your access
Proposal · waiting for your review
Save it as a report with both charts. It stays your draft until you choose to share it.
- Within your permissionsLuis sees only what you are allowed to see. Same roles, same Workspaces, same log as people.
- Always the sourceEvery answer points to a requirement, a clause or a record – so you can check it in one click.
- He proposes, you decideLuis prepares tasks, clauses and links. Nothing is saved until someone reviews and applies it.
- Everywhere in ParagrafOpen Luis over any page and keep working where you are – in text or with your voice.
How to start
Start where it hurts most.
Book a walkthrough of your systems and requirements.
We go through what you have today and where a new requirement or a new system is on its way.
Start where it hurts most – get going yourselves in weeks.
A new requirement, your contracts, a process or something of your own. No consultant project.
Build on the same foundation, without losing control.
The next need lands in the same foundation and inherits everything that is already there.
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.
