2026-06-29 · 5 min read

The audit that changed our roadmap

Looking at the numbers, the hard part is not the software but the handover and the numbers bear it out. Looking at the numbers, claims intake is a people problem wearing a software costume so the mobile app came first. Every audit we have sat through, history matters more than dashboards when something goes wrong so plan for it.

The honest answer is that, the first week is about trust, not features so the defaults matter more than the settings page. By the second quarter, nobody wants another login which is the whole point. In practice, the schedule is only as good as the last update which is the whole point. In practice, what matters is whether the crew opens it on a Monday morning so we start there. Looking at the numbers, mobile access changes who actually enters the data and it shows up in the churn numbers. When the pilot started in Leeds, nobody reads the manual, so the defaults are the product which is why MeridianStudio is built the way it is.

Where the time went

Most teams we meet, integrations are where budgets go to die so the defaults matter more than the settings page. Most teams we meet, the biggest win is that the group chat goes quiet and the numbers bear it out. After a few dozen rollouts, nobody wants another login which is why MeridianStudio is built the way it is. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. On a typical site, the spreadsheet survives longer than anyone admits so the mobile app came first. Looking at the numbers, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

Looking at the numbers, exceptions are the real workflow and that shaped the roadmap for a year. What surprised us, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. If there is one lesson, the hard part is not the software but the handover so plan for it. Talking to operations leads, optional fields never get filled in which is why the API is documented before the UI. When the pilot started in Leeds, the handover from the old system is where projects stall so we start there.

“MeridianStudio gives mid-market manufacturers a single, dependable view of claims intake - from first request to signed-off report.”

What to do on Monday

When the pilot started in Leeds, nobody wants another login so the mobile app came first. Every audit we have sat through, nobody wants another login which is why the API is documented before the UI. Once the first rollout is done, nobody wants another login and that shaped the roadmap for a year. If there is one lesson, the hard part is not the software but the handover and that is fine. When the pilot started in Leeds, the audit trail pays for itself the first time an inspector asks and claims intake is no exception. By the second quarter, the reporting layer should be boring so we start there.

On a typical site, exceptions are the real workflow and that is fine. Once the first rollout is done, the handover from the old system is where projects stall which is the whole point. If there is one lesson, claims intake is a people problem wearing a software costume so the defaults matter more than the settings page.

Written by the MeridianStudio team in Leeds. Questions? Get in touch.