Not one big program with a lock on your rows.
Your firm gets its own copy of the software, its own records and its own documents — set up for you, updated one firm at a time, checked afterwards. Here is what that looks like in practice; press the buttons.
Four things are yours, and only yours
No other firm appears anywhere among them — not filtered out, simply not there.
Your software
Your firm’s own running copy of OpenLPM. Nothing for you to install, nothing for you to patch on a Sunday.
yours alone
Your records
Matters, time, the client ledger and the full history live in your firm’s own store. No shared pool with your name on a row.
your records only
Your documents
Firm documents in folders and versions, with locks on the ones that must not move — and copies of your own taken on a schedule.
your documents only
A separate space for clients
The client portal is its own system, holding only what you have shared. Staff records never enter it.
kept apart
Opening a firm takes eleven steps. Press play.
This is the real sequence, recorded step by step and undone cleanly if anything fails. In a walkthrough it happens with your firm’s name on it.
Changes arrive one firm at a time — on purpose.
The usual software story is “everyone gets Tuesday’s update, hope it’s good.” We treat an update like a filing: tested first, delivered to one firm at a time, checked afterwards, and reversible for your firm alone.
Tested on our own firm first
No client firm is ever the first to run a new version. Our own practice runs it for a period first.
Applied to your firm alone
Your firm’s copy is updated on its own, at a time we can both see, never as part of a crowd.
Checked afterwards
Once it is live we confirm your firm is healthy — sign-in, records, the portal — before moving to the next one.
Kept, or reverted alone
If something is wrong for your firm, your firm returns to the previous version. Nobody else is affected either way.
Three ways to run it, chosen at go-live
Same software, three arrangements — and we say plainly what each one’s privacy claim means, limits included.
| What you are choosing | Your own instance | Shared database option | Split arrangement |
|---|---|---|---|
| Your records | Held for your firm alone | Held in one system, separated by firm | Split between two systems |
| Separation | Structural — separate resources | By configuration, not by structure | Mixed |
| If one firm has a problem | It affects that firm | The shared system is one target | Depends on which part |
| What you pay for | Your own usage, each meter visible | Falls as the group grows; one bill | Between the two |
| Servers to patch | None | None | None |
| Sign-in | A choice of two arrangements: credentials kept inside your firm’s own system (our default), or a specialist identity provider where a firm prefers one. | ||
| Available today | RUNNING FOR DEMO FIRMS | IN BUILD | ROADMAP |
On your firm’s own account
Your firm holds the account, the billing and the exports, with its own app and portal addresses. Nothing of yours depends on our account staying open.
Managed hosting
We run your firm’s instance for you under the same arrangement, on a support calendar. The out-of-hours pager is ours; the account can still be yours.
Separate accounts per firm · in progress
Today the demonstration firms share one account boundary. Giving every firm its own account is in progress and written into the plan. Stated, not hidden.
Every claim here has a section number.
We keep a build record that notes each decision, what we tested, and what went wrong on the way. It is public, so your IT adviser can read it before a meeting instead of taking our word for anything.
Watch a firm get set up, live
In a walkthrough we open a sandbox firm in front of you — every step on screen, and the record it leaves behind.