Home/Solutions/Insurance & Professional services
Insurance & Professional services
Keep client work moving. Show what your team delivered.
Firms that sell judgement — adjusters, consultants, accountants, engineers — carry their exposure in two places: the engagement, and the machine the engagement runs on. The second one used to be nobody's problem. Now it is a section on your professional-liability renewal and a clause in your client's contract, and both of them ask for evidence you probably cannot produce today.
The characteristic ticket
14:05, at a loss site, three inspections behind.
A field adjuster is standing in somebody's driveway with a laptop that will not authenticate to the claims application. A certificate renewed overnight, the client rebuilt itself, and now nothing syncs. She has two more inspections today and a contact standard the carrier has to meet on the file she is currently on.
- She is not on your network. The machine is reachable because it runs an enrolled agent with a tunnel back to the gateway — not because she is on a VPN she cannot currently get onto.
- She is not the technician. Nobody is talking her through a certificate store on a phone in the rain.
- The fix is bounded. A certified runbook re-enrols the client, with the check that defines success and the way back written before it runs.
- The record exists by 14:19 — before anybody thinks to ask for it, which is the only time evidence is cheap to make.
This is the shape everywhere in the sector: a person doing chargeable work on a machine, away from the office, on a clock that belongs to somebody else. A consultant on a client site under the client's own security terms. An engineer in a plant. A partner reviewing files the night before a deadline.
The exposure
The artifact is created before the work, or not at all.
Here is the thing nobody says out loud on a renewal call. The two paths below are identical in every respect that feels important on the day — same technician, same client, same fix, same result. They differ at one moment, and it is the moment before anything happened. By the time the question arrives, the difference cannot be manufactured.
The people who ask
Three conversations this shows up in.
The E&O underwriter, at renewal
The automation and privileged-access questions on a professional-liability or cyber application are getting longer every year, and they are no longer satisfied by "we have a policy". They ask what your tooling may do unattended, whether it holds standing rights, and how you would detect it doing something else.
Answer with the operations themselves. Each one names its authorizer, its privilege and expiry, the machine's own confirmation, and the undo that was declared first.
How privilege is leased →Your client's vendor-risk reviewer
Large clients now push their own security terms down into engagement letters and master services agreements: who may access systems holding our material, under what controls, and what you will give us if we ask.
That clause was written expecting evidence. Most firms answer it with prose because prose is all they have. A period export, under your branding, changes the conversation from persuasion to inspection.
Client-ready exports →The partner whose name is on the engagement
When something goes wrong on a file, the first question inside the firm is not technical. It is who did what, when, and on whose say-so — and it gets asked while everyone is trying to remember a Tuesday from four months ago.
One reference number resolves to the whole operation. That is worth more at that moment than any dashboard.
The operation loop →Two more clocks
Busy season, and machines you cannot take away.
The deadline weeks
An accounting or advisory firm has a handful of weeks a year when a laptop out of action for an afternoon is not an inconvenience, it is chargeable time nobody recovers. Those are also the weeks when standing admin rights get handed out "just for now" and quietly never come back.
Leasing removes the trade. Rights exist for one operation on one machine, expire on the clock rather than on the job finishing, and there is no shared account left behind in March.
One technician, several workstreams →On a client's site, under their rules
A consultant working inside a client's building is often subject to that client's security terms, sometimes on that client's hardware. What you can do to a machine there is constrained, and what you must be able to show afterwards is not negotiable.
Where a person genuinely has to be on the machine, the session is launched under authorization and bound to the operation rather than opened as a free-standing tool. We stay narrow about what that record covers today.
Governed sessions →Straight about scope
What we do not claim here.
- No claims-system, PSA or practice-management integration. Seraph works at the machine, service, account and update layer beneath your applications.
- Evidence, not an insurance outcome. Nobody can promise you a premium, a coverage position or an underwriter's opinion — what we supply is the evidence that conversation runs on. Our own SOC 2 position is on the trust center.
- No unmanaged miracles. A machine with no enrolled agent has no tunnel back to the gateway, so we cannot create or rotate credentials on it. Identity there has to be vaulted or held by the client, and the work is brokered from a managed neighbour.
- No complete session recording. Governed launch, authorization and binding to the operation are what we describe — not multi-surface replay we do not ship.
The honest version of the argument on this page: a record does not reduce your exposure by itself. It changes what happens when the exposure is tested. If a client's counsel asks what your firm's tooling did to a machine holding their material in the second week of March, the difference between a good afternoon and a bad quarter is whether that answer already exists. It costs almost nothing to make at the time and it cannot be made later — that is the whole case, and if you think it is overstated, bring it to the demo and press on it.
Fifteen minutes, on a live system
Bring the automation section of your last renewal application.
We will go through it line by line against a live operation and tell you which lines the record answers — and which it does not.