What connects — and who pays for what.
OpenLPM is deliberately not the centre of a sprawling ecosystem. It connects to the services a firm already uses — signature, payments, messaging, your website — and each one is switched on per firm, with the provider’s own fees paid by the firm, not marked up by us.
Firm-controlled, credential-safe, and reversible
Enabled per firm
A firm turns a connection on for itself. Nothing is switched on by default, and nothing is shared between firms.
Credentials encrypted
Keys are stored encrypted and can never be read back out of the system. An administrator can replace or revoke one at any time.
Signed in both directions
Everything we send to a connected service is signed so the receiver can prove it came from us, and everything we accept is checked the same way. authenticated before anything is written.
Swappable
Use one signature provider now and another next year. Your documents and records stay in OpenLPM either way.
Everything that connects today — and everything that does not, yet
Statuses are honest: “supported” means it works on the live product, not that it is on the roadmap.
| Category | What it enables | Status | Who pays the provider |
|---|---|---|---|
| E-signature | Send engagement letters, agreements and authorities from the matter; track viewing and signature; file the executed copy | Supported | The firm, direct to its chosen provider |
| Online payments | Payment links on invoices and retainers; card and wallet payments; receipts issued on confirmation | Supported | The firm (gateway fees, per transaction) |
| Mobile money & regional rails | Collecting fees through the payment providers a firm’s clients actually use | Supported where the provider operates | The firm, per the provider’s tariff |
| Bank statement import | Importing OFX/CSV statements for trust and office reconciliation, matched against ledger entries | Supported | No cost — no third party involved |
| Inbound email | Enquiries by email landing in the intake inbox with the sender recorded | Supported | The firm’s mail provider |
| SMS & WhatsApp | Client and enquiry messaging through the channels clients actually use | Supported | The firm, per message, to the provider |
| Website forms & embeds | Enquiry and case-evaluation forms embedded on the firm’s own site, feeding the intake pipeline | Supported | No cost |
| WordPress | Connecting an existing firm website to intake without a rebuild | Supported | No cost |
| Document storage | Documents held in storage the firm controls, with versions and locks | Supported | Included in the firm’s infrastructure |
| AI model access | Drafting, summarising and date extraction, configured per firm with usage visible | Supported, firm-configured | The firm, per usage, unless we meter it for you |
| Accounting export | CSV and PDF exports of invoices, payments and ledgers for the firm’s accountant | Supported | No cost |
| Calendar | Deadlines and hearings in the firm’s existing calendar client | Supported (ICS feed) | No cost |
| CRM & automation | Enquiries in and matter events out, to Zapier, Slack, a CRM or your own endpoint | Supported via plugins | The firm’s own automation costs |
| Single sign-on | Enterprise identity providers for staff sign-in | Planned | — |
A plugin registry, not a walled garden
Plugins are first-class: they register with a versioned manifest, declare the permissions they need, and are enabled per firm. Routes are permission-gated, and every outbound call is signed.
- Manifest + permissions. A plugin that asks for more than the firm grants does not start.
- Domain events. Handlers subscribe to events such as matter created or step completed, in isolation.
- Keys encrypted. A plugin’s configuration is stored encrypted, and its credentials can never be read back out.
- Open source. The plugin register, a starter plugin and the signature check are all readable before you write anything.
The absences are the feature
No advertising networks
No ad pixels, no remarketing, no social trackers. There is nothing on a firm’s site or portal that reports to an advertising platform.
No data brokers
Client data is never sold, exchanged, enriched or shared for anyone else’s commercial purpose — not anonymised, not aggregated, not “in aggregate form”.
No training on your files
We do not use a firm’s client material to train third-party models. AI features are enabled per firm and produce drafts for a human to approve.