2026-08-12 · 4 min read

From pilot to plant: a 39-week timeline

Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so plan for it. After a few dozen rollouts, the first week is about trust, not features and the numbers bear it out. In practice, the reporting layer should be boring and quality inspection is no exception.

Once the first rollout is done, the spreadsheet survives longer than anyone admits which is not what the brochure says. In practice, quality inspection is a people problem wearing a software costume and that shaped the roadmap for a year. Talking to operations leads, the handover from the old system is where projects stall which is not what the brochure says.

Every audit we have sat through, integrations are where budgets go to die so the defaults matter more than the settings page. Once the first rollout is done, the spreadsheet survives longer than anyone admits so we start there. If there is one lesson, the audit trail pays for itself the first time an inspector asks which is why Cedarify is built the way it is.

The part nobody plans for

The honest answer is that, mobile access changes who actually enters the data so we start there. The honest answer is that, nobody wants another login which is why the API is documented before the UI. Every audit we have sat through, optional fields never get filled in 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. The honest answer is that, quality inspection is a people problem wearing a software costume which is why the API is documented before the UI. If there is one lesson, nobody wants another login and that is fine.

Every audit we have sat through, mobile access changes who actually enters the data which is the whole point. Most teams we meet, nobody reads the manual, so the defaults are the product and that is fine. What surprised us, a two-week pilot answers more than a three-month evaluation and that is fine. Most teams we meet, the biggest win is that the group chat goes quiet which is not what the brochure says.

When the pilot started in Tallinn, the schedule is only as good as the last update which is the whole point. Talking to operations leads, the first week is about trust, not features which is why Cedarify is built the way it is. Most teams we meet, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. For retail chains in particular, mobile access changes who actually enters the data and that is fine.

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

What to do on Monday

For retail chains in particular, the hard part is not the software but the handover so the defaults matter more than the settings page. Talking to operations leads, optional fields never get filled in and it rarely takes more than a week. What surprised us, mobile access changes who actually enters the data and that shaped the roadmap for a year. After a few dozen rollouts, the reporting layer should be boring which is why the API is documented before the UI.

Once the first rollout is done, nobody wants another login so we start there. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so we start there. Every audit we have sat through, nobody wants another login and it rarely takes more than a week.

When the pilot started in Tallinn, integrations are where budgets go to die so plan for it. Talking to operations leads, the biggest win is that the group chat goes quiet and the numbers bear it out. Most teams we meet, quality inspection is a people problem wearing a software costume so we start there. When the pilot started in Tallinn, optional fields never get filled in and it rarely takes more than a week.

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