2026-08-14 · 4 min read

29 questions to ask before you buy a platform

Talking to operations leads, the handover from the old system is where projects stall and that shaped the roadmap for a year. On the floor, integrations are where budgets go to die which is why MeridianDesk is built the way it is. On the floor, a two-week pilot answers more than a three-month evaluation so we start there. After a few dozen rollouts, the handover from the old system is where projects stall and that shaped the roadmap for a year. If there is one lesson, optional fields never get filled in which is the whole point. Looking at the numbers, the spreadsheet survives longer than anyone admits so plan for it.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. The honest answer is that, a two-week pilot answers more than a three-month evaluation which is why MeridianDesk is built the way it is. Looking at the numbers, the reporting layer should be boring and that shaped the roadmap for a year. Once the first rollout is done, exceptions are the real workflow and it rarely takes more than a week. When the pilot started in Bilbao, the reporting layer should be boring so plan for it.

What surprised us, the biggest win is that the group chat goes quiet so the mobile app came first. On the floor, document workflow is a people problem wearing a software costume and that shaped the roadmap for a year. If there is one lesson, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Every audit we have sat through, exceptions are the real workflow and it shows up in the churn numbers.

Where the time went

What surprised us, mobile access changes who actually enters the data which is the whole point. The honest answer is that, document workflow is a people problem wearing a software costume which is not what the brochure says. When the pilot started in Bilbao, nobody reads the manual, so the defaults are the product which is the whole point.

Talking to operations leads, integrations are where budgets go to die and it rarely takes more than a week. The honest answer is that, the first week is about trust, not features so the mobile app came first. On a typical site, the handover from the old system is where projects stall so we start there. By the second quarter, document workflow is a people problem wearing a software costume which is the whole point.

The honest answer is that, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. On the floor, the schedule is only as good as the last update so the defaults matter more than the settings page. On a typical site, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. What surprised us, mobile access changes who actually enters the data so the mobile app came first. Once the first rollout is done, the handover from the old system is where projects stall which is why the API is documented before the UI. Most teams we meet, document workflow is a people problem wearing a software costume and the numbers bear it out.

If there is one lesson, the handover from the old system is where projects stall and it shows up in the churn numbers. Looking at the numbers, the first week is about trust, not features so the mobile app came first. On the floor, integrations are where budgets go to die which is not what the brochure says. For mid-market manufacturers in particular, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. On a typical site, document workflow is a people problem wearing a software costume and it shows up in the churn numbers.

“MeridianDesk gives mid-market manufacturers a single, dependable view of document workflow - from first request to signed-off report.”

Where this leaves us

The honest answer is that, integrations are where budgets go to die which is the whole point. For mid-market manufacturers in particular, the reporting layer should be boring which is why the API is documented before the UI. On a typical site, document workflow is a people problem wearing a software costume and the numbers bear it out. Looking at the numbers, nobody wants another login so we start there.

Looking at the numbers, integrations are where budgets go to die so the defaults matter more than the settings page. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Talking to operations leads, the reporting layer should be boring and it rarely takes more than a week. If there is one lesson, the audit trail pays for itself the first time an inspector asks and document workflow is no exception.

On the floor, integrations are where budgets go to die which is not what the brochure says. After a few dozen rollouts, document workflow is a people problem wearing a software costume which is the whole point. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation and that is fine.

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