2026-08-29 · 4 min read

From pilot to plant: a 7-week timeline

When the pilot started in Leeds, the spreadsheet survives longer than anyone admits so plan for it. When the pilot started in Leeds, optional fields never get filled in which is the whole point. Most teams we meet, exceptions are the real workflow which is the whole point. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is the whole point. If there is one lesson, mobile access changes who actually enters the data so the defaults matter more than the settings page.

When the pilot started in Leeds, the reporting layer should be boring and it shows up in the churn numbers. For mid-market manufacturers in particular, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. On the floor, optional fields never get filled in so we start there.

In practice, the biggest win is that the group chat goes quiet which is not what the brochure says. The honest answer is that, history matters more than dashboards when something goes wrong so the mobile app came first. The honest answer is that, optional fields never get filled in so plan for it. After a few dozen rollouts, integrations are where budgets go to die and the numbers bear it out. By the second quarter, the handover from the old system is where projects stall so the defaults matter more than the settings page.

Where the time went

On the floor, history matters more than dashboards when something goes wrong which is why MeridianStudio is built the way it is. On a typical site, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. If there is one lesson, nobody reads the manual, so the defaults are the product which is the whole point. In practice, nobody wants another login and claims intake is no exception. On a typical site, history matters more than dashboards when something goes wrong so the mobile app came first.

What surprised us, the handover from the old system is where projects stall which is why MeridianStudio is built the way it is. After a few dozen rollouts, mobile access changes who actually enters the data which is why MeridianStudio is built the way it is. On a typical site, exceptions are the real workflow and that is fine. In practice, nobody reads the manual, so the defaults are the product which is why MeridianStudio is built the way it is. If there is one lesson, mobile access changes who actually enters the data so the defaults matter more than the settings page. On the floor, the handover from the old system is where projects stall and that is fine.

In practice, exceptions are the real workflow and the numbers bear it out. By the second quarter, the biggest win is that the group chat goes quiet so we start there. Most teams we meet, the reporting layer should be boring so the defaults matter more than the settings page. The honest answer is that, the first week is about trust, not features which is not what the brochure says. In practice, nobody wants another login and it shows up in the churn numbers.

Once the first rollout is done, history matters more than dashboards when something goes wrong and the numbers bear it out. For mid-market manufacturers in particular, the first week is about trust, not features so we start there. On a typical site, the first week is about trust, not features which is why MeridianStudio is built the way it is. After a few dozen rollouts, integrations are where budgets go to die so the mobile app came first. 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, integrations are where budgets go to die and the numbers bear it out.

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

What to do on Monday

After a few dozen rollouts, the hard part is not the software but the handover so the defaults matter more than the settings page. After a few dozen rollouts, the biggest win is that the group chat goes quiet so plan for it. By the second quarter, nobody wants another login so plan for it. Every audit we have sat through, nobody wants another login and the numbers bear it out.

Once the first rollout is done, mobile access changes who actually enters the data and claims intake is no exception. For mid-market manufacturers in particular, optional fields never get filled in and it rarely takes more than a week. Once the first rollout is done, the first week is about trust, not features so plan for it. In practice, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. If there is one lesson, the reporting layer should be boring which is why MeridianStudio is built the way it is.

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