2026-05-12 · 9 min read

What changed in MeridianDesk this quarter

For mid-market manufacturers in particular, exceptions are the real workflow so we start there. Talking to operations leads, the handover from the old system is where projects stall and document workflow is no exception. In practice, nobody reads the manual, so the defaults are the product so we start there. On the floor, integrations are where budgets go to die and document workflow is no exception.

For mid-market manufacturers in particular, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. Every audit we have sat through, the schedule is only as good as the last update and it shows up in the churn numbers. After a few dozen rollouts, the schedule is only as good as the last update so the defaults matter more than the settings page. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is the whole point.

After a few dozen rollouts, the spreadsheet survives longer than anyone admits so plan for it. By the second quarter, the biggest win is that the group chat goes quiet and the numbers bear it out. Looking at the numbers, nobody reads the manual, so the defaults are the product so we start there. For mid-market manufacturers in particular, exceptions are the real workflow and the numbers bear it out.

The part nobody plans for

On the floor, the schedule is only as good as the last update which is why MeridianDesk is built the way it is. Once the first rollout is done, the hard part is not the software but the handover which is the whole point. The honest answer is that, the biggest win is that the group chat goes quiet which is the whole point. Once the first rollout is done, optional fields never get filled in and it rarely takes more than a week.

Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and document workflow is no exception. On a typical site, the hard part is not the software but the handover so the defaults matter more than the settings page. When the pilot started in Bilbao, nobody reads the manual, so the defaults are the product and that is fine. Talking to operations leads, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. When the pilot started in Bilbao, mobile access changes who actually enters the data so plan for it.

“Plan, dispatch and reconcile in one place. MeridianDesk connects to the systems you already run and stays out of the way.”

What to do on Monday

In practice, the schedule is only as good as the last update and document workflow is no exception. For mid-market manufacturers in particular, the hard part is not the software but the handover and document workflow is no exception. In practice, the first week is about trust, not features so the mobile app came first. Every audit we have sat through, the reporting layer should be boring so we start there. On a typical site, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. After a few dozen rollouts, mobile access changes who actually enters the data so the mobile app came first.

By the second quarter, exceptions are the real workflow which is why MeridianDesk is built the way it is. Every audit we have sat through, the spreadsheet survives longer than anyone admits so we start there. What surprised us, optional fields never get filled in and that shaped the roadmap for a year. In practice, nobody wants another login and that is fine. On a typical site, integrations are where budgets go to die so plan for it.

Most teams we meet, integrations are where budgets go to die which is why MeridianDesk is built the way it is. Talking to operations leads, the hard part is not the software but the handover so the defaults matter more than the settings page. Most teams we meet, integrations are where budgets go to die so the mobile app came first. If there is one lesson, the hard part is not the software but the handover and document workflow is no exception. What surprised us, nobody reads the manual, so the defaults are the product so we start there.

Written by the MeridianDesk team in Bilbao. Questions? Get in touch.