What is coming
The rest of what we can tell you.
Every other page in this report shows a real result. This page shows what we are building next. For each area: what we look at, the kind of answer you get, and why it is worth knowing.
How to read this page
Why this page is here
So you can see everything we can do, not just the parts that run at the push of a button today.
Two kinds of number
Real number, from real work means we measured it on a real client system. Example only means we made it up to show you the shape of the answer.
What is automatic today
Two checks run start to finish on their own: configuration and work type lifecycle. Everything else in this report we ran by hand.
What you can ask for now
Any area below. We can do the work today. Making it automatic is what we are building next.
What we are building next
Who actually uses it
What it measures. We count real work, not logins. Every account is sorted into never used, logged in only, light, regular or heavy. We also show what each role does with the system, and which paid licences nobody touches.
The headline it returns. Nearly every enabled account had logged in at least once, which looked healthy. The work split by role told the real story: fee earners spent most of their time generating documents, while partners only appeared to approve things.
Why it matters. You can decide about training and licences from facts instead of opinions.
We measured this on a real client system. We do not name the client. We can do this work for you today, but it is not yet a one-click step.
Automation that has quietly stopped
What it measures. We check every trigger and workflow for silent failure: ones sitting in an error state, ones that fail most times they run, old stuck jobs, and integrations pointing at the wrong system.
The headline it returns. 33 of 152 triggers were sitting in an error state. One of them was the automatic conflict check. Nobody knew, because the system tells nobody.
Why it matters. When automation breaks, nothing warns you. Work just stops happening. This is usually the quickest problem to find and fix.
We measured this on a real client system. We do not name the client. We can do this work for you today, but it is not yet a one-click step.
What breaks if you change a field
What it measures. Pick any field. We show every place that depends on it: forms, workflows, triggers, list views, and the document templates it prints into.
The headline it returns. One field was about to be renamed. It turned out to be used in 31 places, including 11 document templates that would have printed a blank space where the value used to be.
Why it matters. You see what a change will break before you make it, not after.
This is an example of what the answer will look like. We have not measured it.
Who can see and do what
What it measures. We pull the full picture of which roles can do what on which work types, read only. Then we show the odd ones: roles missing permissions they need, named people hard-wired into settings, accounts skipping single sign-on, and powerful accounts nobody has used in months.
The headline it returns. A permission map of several thousand rows, read straight out of the system. It showed partner roles with no permissions on matters, and individual people hard-wired into dozens of work types.
Why it matters. You have a clear answer ready before an auditor or an incident asks the question.
We measured this on a real client system. We do not name the client. We can do this work for you today, but it is not yet a one-click step.
Can you prove your client checks
What it measures. We check whether the system can actually evidence your client due-diligence process: identity fields, company ownership, politically exposed person flags, a risk rating, a gate that stops work until checks are done, and whether all of it can be pulled back out as a record.
The headline it returns. Of the client-check controls expected on the intake work type, only one was set up. Nothing stopped a matter moving forward before the checks were done.
Why it matters. You find out what the system can prove now, not in the middle of a regulator request.
This is an example of what the answer will look like. We have not measured it.
Are your environments in step
What it measures. We capture the setup of your live, test and next-version environments and compare them item by item. Each difference is labelled: same, waiting to go live, changed only in test, drifted in live, or in conflict. We also show who changed what and when.
The headline it returns. Around three thousand settings compared across three environments. The result was a short decision list and one clear conclusion: none of the three environments was safe to release as it stood.
Why it matters. A release becomes a list of decisions your team works through, instead of a hopeful deployment.
We measured this on a real client system. We do not name the client. We can do this work for you today, but it is not yet a one-click step.
Which documents are actually used
What it measures. We band every template, email template and content block by real usage, and show which ones share content with each other.
The headline it returns. Around 1,900 templates were being maintained. Fewer than 50 were in regular use. Nobody had measured the gap before.
Why it matters. Template owners get a short, ordered list of what to keep, convert or retire.
We measured this on a real client system. We do not name the client. We can do this work for you today, but it is not yet a one-click step.
Ask questions about your own matters
What it measures. You ask a question in plain English about your own matters, parties and notes. You get an answer with a link to every record it came from. We can also read file notes to pull out reserves, offers and dates.
The headline it returns. Ask which matters name a given insurer and are past their limitation date, and get the answer in one sentence, with the matter list and the source behind every part of it.
Why it matters. Partners get answers about their own work without waiting for someone to build a report.
This is an example of what the answer will look like. We have not measured it.