Product
Everything a negotiation needs, in one place.
Apua is not a repository you file the outcome into. It is the surface the outcome is decided on — with the review, the people, the approvals and the signature all in the same document.
Workspace
The day-to-day surfaces
Where the negotiation actually happens — and the assistant that stays with you through it.
Assistant
Ask a question about the contract in front of you and get an answer grounded in the document, your playbook, and your firm's material — with the citation attached.
- Reads the actual contract body, not just its metadata
- Every answer carries the source it rests on
- Declines rather than guessing when the sources do not support a position
- Available anywhere in the platform without losing your place
Contracts
The negotiation surface: draft, redline, comment, compare and sign in one living document instead of a chain of attachments.
- Track changes with Word-style markup views
- Comments anchored to the clause they concern
- Every round versioned, any two versions comparable
- Chain of custody behind every change
Workflows
Route agreed text to the people whose sign-off your policy requires, in the order it requires them.
- Sequential approval steps, each locked until the one before clears
- A rejected step sends the contract back for another round
- Skip straight to approval or signature when a contract does not need review
Projects
A private workspace for a deal or a matter — its documents, its people, and nobody else's.
- Membership is the privacy boundary, not a department label
- Files scoped to the project are what the Assistant answers from
- Invite colleagues without opening the rest of your workspace
Library
The material your team already owns
Positions, precedent and paper — turned from folders into something the platform can act on.
Playbooks
Your negotiating positions, written once and applied to every incoming draft — the opening position, the fallbacks in order, and the line you do not cross.
- Structured rules, not a prompt someone has to remember
- Fallback language drafted in advance, ready to insert
- The same position on every desk, however late in the day
Knowledge
Your firm's own material — precedent, guidance, past agreements — searchable and answerable rather than sitting in a folder.
- Answers cite the document they came from
- Scoped to your tenant before the search runs
- Grows as your team works, without a migration project
Clauses
Reusable language you can drop into a negotiation without rewriting it from memory.
- Insert mid-negotiation without leaving the document
- Matched to the contract type you are working on
- Sits beside the playbook rule that governs it
Templates
Start from your own paper. Generate a first draft from a template you control rather than a generic form.
- Your standard, your numbering, your defined terms
- Feeds straight into the negotiation surface
Data Sources
Connect the places your documents already live so the work comes to you.
- Google Drive, OneDrive and SharePoint connectors
- Documents stay scoped to your tenant once ingested
Insights
What your contract portfolio is actually doing
Renewals coming up, obligations open and overdue, where risk concentrates, and which terms depart from your norm — for the people accountable for the function.
Legal departments are asked to justify headcount and tooling with anecdotes. Insights replaces the anecdote with the record the platform already holds.
Available to organisation administrators.
Portfolio
What you hold, by status, party and value
Renewals
What is coming up, before the date passes
Obligations
What is open, what is overdue
Risk and anomalies
Where risk concentrates, and which terms depart from your norm
Trust
The part you cannot bolt on afterwards.
Data Sovereignty
Your contracts stay in the EU, isolated to your tenant at the database, cache, storage, vector-search and model-context layers. By default, no tenant data is used to train any model unless separately agreed.
Security
Five independent layers of encryption, customer-managed keys, and a hash-chained audit log where altering one entry breaks every entry after it. Enterprise tenants can hold their own key.
EU Native
Built in Helsinki and hosted in Finland. EU-only routing is the default on every model call rather than a flag a caller can forget — residency is where the system was built to live, not a setting.
See it on a contract you already know.
Send us one — redacted as far as you like — and we will run it in a 30-minute call, including where your data sits and what it costs.
Request a demo