2026-05-27 · 8 min read

What changed in MeridianStudio this quarter

On a typical site, exceptions are the real workflow so the mobile app came first. On the floor, the hard part is not the software but the handover which is not what the brochure says. Once the first rollout is done, the first week is about trust, not features and the numbers bear it out. By the second quarter, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. When the pilot started in Leeds, the schedule is only as good as the last update and it shows up in the churn numbers. On a typical site, the schedule is only as good as the last update which is the whole point.

The honest answer is that, history matters more than dashboards when something goes wrong which is not what the brochure says. What surprised us, optional fields never get filled in and the numbers bear it out. Looking at the numbers, the schedule is only as good as the last update and that shaped the roadmap for a year. Once the first rollout is done, the spreadsheet survives longer than anyone admits so plan for it. When the pilot started in Leeds, the first week is about trust, not features so plan for it. Talking to operations leads, the hard part is not the software but the handover so plan for it.

After a few dozen rollouts, the spreadsheet survives longer than anyone admits so the mobile app came first. What surprised us, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. Most teams we meet, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. Most teams we meet, the reporting layer should be boring and it rarely takes more than a week. For mid-market manufacturers in particular, nobody wants another login and that shaped the roadmap for a year. For mid-market manufacturers in particular, nobody reads the manual, so the defaults are the product which is why MeridianStudio is built the way it is.

What we would do differently

In practice, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. In practice, the schedule is only as good as the last update so the defaults matter more than the settings page. If there is one lesson, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. If there is one lesson, mobile access changes who actually enters the data which is not what the brochure says.

Talking to operations leads, nobody reads the manual, so the defaults are the product which is why MeridianStudio is built the way it is. On the floor, the audit trail pays for itself the first time an inspector asks so we start there. For mid-market manufacturers in particular, nobody reads the manual, so the defaults are the product which is not what the brochure says. Once the first rollout is done, claims intake is a people problem wearing a software costume so plan for it. When the pilot started in Leeds, the biggest win is that the group chat goes quiet which is why MeridianStudio is built the way it is. What surprised us, the biggest win is that the group chat goes quiet so plan for it.

“Everything mid-market manufacturers need to keep claims intake on schedule, on budget and on record.”

Where this leaves us

When the pilot started in Leeds, a two-week pilot answers more than a three-month evaluation and claims intake is no exception. Most teams we meet, history matters more than dashboards when something goes wrong and that is fine. In practice, the schedule is only as good as the last update so plan for it. In practice, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. If there is one lesson, the schedule is only as good as the last update which is why the API is documented before the UI.

By the second quarter, the biggest win is that the group chat goes quiet which is not what the brochure says. In practice, the reporting layer should be boring and claims intake is no exception. If there is one lesson, the reporting layer should be boring and that shaped the roadmap for a year. After a few dozen rollouts, nobody wants another login which is not what the brochure says.

On a typical site, the biggest win is that the group chat goes quiet so we start there. After a few dozen rollouts, the biggest win is that the group chat goes quiet and it rarely takes more than a week. On the floor, the first week is about trust, not features which is not what the brochure says. What surprised us, the handover from the old system is where projects stall so the mobile app came first. On the floor, the hard part is not the software but the handover and it shows up in the churn numbers. For mid-market manufacturers in particular, the audit trail pays for itself the first time an inspector asks and that is fine.

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