Skip to main content

Solutions

What legal teams actually use Apua for.

Not a list of modules. The six situations European in-house teams bring to us, and what the platform does about each one.

The core

Run the whole negotiation in one place

The draft arrives as an attachment. It goes back marked up. Three rounds later there are nine files called final, and nobody can say what moved between v6 and v7 without reading both.

One living document that every round is written into. The negotiation history is also the audit trail, so there is no reconciliation step at the end — there was never more than one document.

  • Every exchange creates a version rather than a new file
  • Put any two versions side by side and see exactly what moved
  • Comments anchored to the clause, not buried in an email thread

First response

Mark up an incoming draft in minutes

A first-pass review of someone else's paper takes an afternoon, and the quality depends on who picked up the file and how late it is.

Apua checks the draft clause by clause against your playbook and returns what departs from it — ordered by risk, each finding carrying the rule it breaches and a fallback already drafted in your language.

Playbook · Limitation of liabilityRule 4.2
01Preferred

Liability capped at 12 months' Fees, with a 3× super-cap for breach of Section 7.

02Acceptable

Liability capped at the greater of EUR 250,000 or 12 months' Fees.

03Walk away

Any fixed cap below EUR 250,000, or a mutual cap excluding data-breach liability.

  • The specific deviations, not a summary you could write yourself
  • A fallback ladder: preferred, acceptable, walk away
  • Unsupported positions are refused and flagged for a person
  • The same review runs inside Microsoft Word

The other side

Bring the counterparty in without giving anything away

Collaborating with the other side usually means emailing documents, or buying them a licence on a platform they did not choose.

Send a secure link. They work in a browser with no account and no install, at exactly the permission you granted — and you can change or withdraw it at any time.

Who is in the roomLive
JK

In-house counsel

Full edit · full workspace

Owner
ML

Finance

Comment and approve

Reviewer
PS

External counsel

Suggest · tracked changes

Guest link
AR

Counterparty

Edit · no access to your review

Guest link
  • Read, comment or edit — enforced at the connection, not hidden in the interface
  • Their edits arrive as tracked changes, attributed to them
  • They never see your playbook review, risk scoring or approval chain
  • Counterparties never need a licence

Getting to signed

Approvals and signature without a second vendor

Sign-off happens over email, and signature happens on a separate platform with its own invoice and its own copy of your contract.

Route the agreed text through the people your policy requires, in order, then sign on the platform itself with PAdES signatures and trusted timestamps meeting the advanced standard under eIDAS.

  • Sequential steps, each locked until the previous clears
  • Approval resets if the text changes afterwards
  • Identity verification by email or phone before anyone signs
  • Certificate of completion, and later alteration is detectable

After the ink

Know what the agreement committed you to

A signed contract is a set of promises with dates attached — and then, usually, silence until something is missed.

Apua tracks what a signed agreement created — the obligations, who owes them, and when they fall due — so what is open and what is overdue is a view you can open rather than something buried in the document.

  • Obligations captured against the executed contract
  • Renewals surfaced across the portfolio before the date passes
  • Open and overdue obligations in one view

Where it must stay in Europe

Sovereign because you are required to be

For public bodies, regulated industries and anyone with a strict data-protection posture, a platform that quietly moves contracts across an ocean is not procurable at any price.

Apua runs entirely on EU infrastructure in Finland, isolated per tenant at every layer, with EU-only model routing as the default rather than an option.

  • Hosted in Helsinki — residency is architectural, not a setting
  • Five layers of encryption and a hash-chained audit trail
  • Enterprise tenants can bring their own encryption key
  • By default, no tenant data trains any model

Which of these is yours?

Tell us the situation and bring a contract you already know. We will run it in 30 minutes and you will have a price in the same call.

Request a demo