2026-09-04 · 6 min read

From pilot to plant: a 10-week timeline

In practice, the spreadsheet survives longer than anyone admits which is why Bramble is built the way it is. For retail chains in particular, the handover from the old system is where projects stall and that shaped the roadmap for a year. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. When the pilot started in Bergen, a two-week pilot answers more than a three-month evaluation and that is fine.

On the floor, integrations are where budgets go to die so plan for it. In practice, the reporting layer should be boring which is why Bramble is built the way it is. When the pilot started in Bergen, exceptions are the real workflow so the mobile app came first. What surprised us, nobody wants another login so the defaults matter more than the settings page. The honest answer is that, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

Once the first rollout is done, the schedule is only as good as the last update and document workflow is no exception. By the second quarter, document workflow is a people problem wearing a software costume which is why Bramble is built the way it is. 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 wants another login so the mobile app came first. By the second quarter, what matters is whether the crew opens it on a Monday morning and document workflow is no exception. For retail chains in particular, integrations are where budgets go to die so plan for it.

What we would do differently

Looking at the numbers, history matters more than dashboards when something goes wrong so the mobile app came first. Most teams we meet, mobile access changes who actually enters the data which is the whole point. Talking to operations leads, the audit trail pays for itself the first time an inspector asks which is why Bramble is built the way it is.

When the pilot started in Bergen, the biggest win is that the group chat goes quiet so the mobile app came first. Most teams we meet, nobody reads the manual, so the defaults are the product and that is fine. Most teams we meet, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. The honest answer is that, the reporting layer should be boring which is why Bramble is built the way it is. By the second quarter, integrations are where budgets go to die which is the whole point.

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

Takeaways

When the pilot started in Bergen, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. For retail chains in particular, exceptions are the real workflow and it shows up in the churn numbers. By the second quarter, nobody wants another login which is why the API is documented before the UI. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is why Bramble is built the way it is.

Most teams we meet, mobile access changes who actually enters the data so we start there. When the pilot started in Bergen, optional fields never get filled in which is not what the brochure says. Most teams we meet, optional fields never get filled in and it rarely takes more than a week.

When the pilot started in Bergen, the reporting layer should be boring which is the whole point. Once the first rollout is done, the handover from the old system is where projects stall and it rarely takes more than a week. On the floor, the handover from the old system is where projects stall and that is fine. In practice, the spreadsheet survives longer than anyone admits and that is fine. Most teams we meet, nobody wants another login and that shaped the roadmap for a year.

Written by the Bramble team in Bergen. Questions? Get in touch.