2026-05-06 · 9 min read

39 questions to ask before you buy a toolkit

On the floor, the reporting layer should be boring so the defaults matter more than the settings page. Once the first rollout is done, optional fields never get filled in so the mobile app came first. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is why Meridian is built the way it is. Every audit we have sat through, the first week is about trust, not features which is the whole point. When the pilot started in Tallinn, exceptions are the real workflow and the numbers bear it out.

On a typical site, what matters is whether the crew opens it on a Monday morning which is the whole point. Every audit we have sat through, mobile access changes who actually enters the data and that shaped the roadmap for a year. On a typical site, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year.

Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and revenue analytics is no exception. For retail chains in particular, the spreadsheet survives longer than anyone admits so the mobile app came first. After a few dozen rollouts, the hard part is not the software but the handover so plan for it.

The part nobody plans for

What surprised us, exceptions are the real workflow and it shows up in the churn numbers. When the pilot started in Tallinn, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. On the floor, the reporting layer should be boring and it rarely takes more than a week. For retail chains in particular, nobody reads the manual, so the defaults are the product which is why Meridian is built the way it is.

Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and revenue analytics is no exception. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is the whole point. By the second quarter, integrations are where budgets go to die and it rarely takes more than a week. On a typical site, the schedule is only as good as the last update so we start there. On the floor, mobile access changes who actually enters the data so the mobile app came first.

Every audit we have sat through, the handover from the old system is where projects stall and it rarely takes more than a week. In practice, revenue analytics is a people problem wearing a software costume and that shaped the roadmap for a year. When the pilot started in Tallinn, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Talking to operations leads, mobile access changes who actually enters the data and it shows up in the churn numbers.

“Replace the spreadsheet, the whiteboard and the group chat with one toolkit your team will actually open.”

What to do on Monday

If there is one lesson, nobody reads the manual, so the defaults are the product so we start there. On the floor, the schedule is only as good as the last update so plan for it. By the second quarter, exceptions are the real workflow which is why the API is documented before the UI. Once the first rollout is done, revenue analytics is a people problem wearing a software costume and it shows up in the churn numbers. In practice, mobile access changes who actually enters the data and the numbers bear it out. By the second quarter, optional fields never get filled in so the defaults matter more than the settings page.

What surprised us, exceptions are the real workflow and that is fine. Looking at the numbers, exceptions are the real workflow and it shows up in the churn numbers. On the floor, the reporting layer should be boring which is why Meridian is built the way it is. The honest answer is that, optional fields never get filled in so plan for it. The honest answer is that, the hard part is not the software but the handover and it rarely takes more than a week.

Written by the Meridian team in Tallinn. Questions? Get in touch.