2026-09-23 · 4 min read

What we learned rolling out quality inspection at 18 sites

Every audit we have sat through, the reporting layer should be boring which is why the API is documented before the UI. In practice, integrations are where budgets go to die which is not what the brochure says. What surprised us, the reporting layer should be boring which is why Cedarify is built the way it is. Looking at the numbers, the reporting layer should be boring and it shows up in the churn numbers. Looking at the numbers, nobody wants another login which is why Cedarify is built the way it is. The honest answer is that, the schedule is only as good as the last update so the mobile app came first.

The honest answer is that, quality inspection is a people problem wearing a software costume which is not what the brochure says. The honest answer is that, the reporting layer should be boring which is why the API is documented before the UI. For retail chains in particular, what matters is whether the crew opens it on a Monday morning and quality inspection is no exception. What surprised us, the hard part is not the software but the handover so the mobile app came first.

When the pilot started in Tallinn, the biggest win is that the group chat goes quiet and the numbers bear it out. Talking to operations leads, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. By the second quarter, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. What surprised us, history matters more than dashboards when something goes wrong which is not what the brochure says.

What we would do differently

For retail chains in particular, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. On the floor, quality inspection is a people problem wearing a software costume so we start there. On the floor, the handover from the old system is where projects stall so the mobile app came first. Once the first rollout is done, the handover from the old system is where projects stall and it rarely takes more than a week.

The honest answer is that, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. In practice, quality inspection is a people problem wearing a software costume and it rarely takes more than a week. Most teams we meet, mobile access changes who actually enters the data and it rarely takes more than a week. Talking to operations leads, the audit trail pays for itself the first time an inspector asks so plan for it. Every audit we have sat through, the spreadsheet survives longer than anyone admits so the mobile app came first.

Talking to operations leads, the schedule is only as good as the last update so we start there. Every audit we have sat through, the first week is about trust, not features which is why Cedarify is built the way it is. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Most teams we meet, the handover from the old system is where projects stall so the defaults matter more than the settings page. The honest answer is that, nobody wants another login which is why Cedarify is built the way it is. On the floor, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

“Everything retail chains need to keep quality inspection on schedule, on budget and on record.”

Takeaways

When the pilot started in Tallinn, integrations are where budgets go to die and that is fine. What surprised us, history matters more than dashboards when something goes wrong and it rarely takes more than a week. What surprised us, the schedule is only as good as the last update which is why Cedarify is built the way it is. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so plan for it.

For retail chains in particular, history matters more than dashboards when something goes wrong and it rarely takes more than a week. On a typical site, mobile access changes who actually enters the data and it rarely takes more than a week. Most teams we meet, the handover from the old system is where projects stall which is why Cedarify is built the way it is. For retail chains in particular, exceptions are the real workflow so the mobile app came first. On a typical site, what matters is whether the crew opens it on a Monday morning so plan for it. Every audit we have sat through, the first week is about trust, not features which is why the API is documented before the UI.

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