The platform, inside
One system, from intake to renewal.
Two capabilities on one foundation: matters run the operation, contracts run the lifecycle. They share entities, documents, deadlines and permissions — and speak the same language.
The two capabilities
Matters and contracts, in one system.
What it answers
The pain that nags you in the morning, and where the platform answers it.
Matters and contracts are parts of the same system — used together and speaking the same language.
| If your pain is… | Where it answers | How |
|---|---|---|
| “I don't know where the latest version of this contract is.” | Contracts | A single repository with versions, parties, dates and negotiation status. |
| “We renewed for another year without meaning to.” | Contracts | Alerts for auto-renewal and notice deadlines, each with an owner. |
| “Every lawyer drafts their own way.” | Contracts | Approved templates and a clause library with defined fallback positions. |
| “Requests arrive by phone, with no context at all.” | Matters | A single front door, with a form per request type, priority and a deadline set up front. |
| “I only learn the work has overrun when the firm's invoice arrives.” | Matters | Instruction with a scope and a fee cap, with spend tracked as it goes. |
| “I can't make the case for another person on the team.” | Matters | Volume, turnaround and load per person — the numbers the board asks for. |
| “Deadlines live in people's heads.” | Matters | Deadlines with an owner, a backup and automatic escalation. |
| “I don't know which clients are profitable.” (firms) | Matters | Profitability by client and by matter, with the real cost of the team assigned. |
| “Both, linked.” | All together | A contract can be generated from a matter, and the matter sees the obligations born from it — over the same entities, people and permissions. |
Shared foundation
What the platform shares inside.
Nothing is duplicated between matters and contracts: one entity, one document, one deadline — recorded once, used everywhere.
Entities and people
Group, areas, counterparties and clients recorded once.
Documents and versions
Full history, with side-by-side comparison.
Deadlines and alerts
Owner, backup and automatic escalation.
Permissions
Access by team and by matter, on least privilege.
Reporting
Management dashboards and export to spreadsheet.
Audit trail
Actions recorded in an immutable log.
Implementation
Live in weeks, not quarters.
One team, one contract type, real data. We only widen once the first group is self-sufficient.
Configuration
Teams, permissions, contract types, templates and approval flows.
Migration
Live contracts, open matters and counterparties, with data validation.
Training
Short sessions per profile, with the organisation's real data already inside.
Follow-up
Close presence in the first weeks and an adoption review at 30 days.
Security and data
Where your documents live.
Where is the data hosted?
Dedicated hosting, with a choice of region and the option to install on your own infrastructure. The location is fixed in writing in the contract.
Who can see what?
Access by team and by matter, with restricted matters. No one sees what they were not given, and everything is logged.
Can we export everything if we stop being clients?
Yes. Full export in open formats is a contractual right, not an exit negotiation.
Does it integrate with what we already use?
Email, document storage, e-signature and an API for finance systems.
See the system with your own cases.
On a scenario close to yours, so the conversation is about your work and not about features.