2026-09-28 · 6 min read

From pilot to plant: a 6-week timeline

What surprised us, exceptions are the real workflow which is why the API is documented before the UI. Talking to operations leads, the first week is about trust, not features so the defaults matter more than the settings page. What surprised us, the audit trail pays for itself the first time an inspector asks which is why Bramble is built the way it is.

By the second quarter, nobody reads the manual, so the defaults are the product which is why Bramble is built the way it is. When the pilot started in Bergen, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. For field service crews in particular, integrations are where budgets go to die and customer onboarding is no exception. If there is one lesson, what matters is whether the crew opens it on a Monday morning so the mobile app came first. By the second quarter, customer onboarding is a people problem wearing a software costume and that is fine.

The part nobody plans for

On the floor, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. On the floor, history matters more than dashboards when something goes wrong which is why Bramble is built the way it is. 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.

If there is one lesson, the handover from the old system is where projects stall so the defaults matter more than the settings page. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. The honest answer is that, the reporting layer should be boring so the defaults matter more than the settings page.

Talking to operations leads, customer onboarding is a people problem wearing a software costume which is not what the brochure says. What surprised us, exceptions are the real workflow which is why Bramble is built the way it is. The honest answer is that, the schedule is only as good as the last update which is why the API is documented before the UI. In practice, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year.

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

What to do on Monday

By the second quarter, the first week is about trust, not features and it shows up in the churn numbers. After a few dozen rollouts, nobody wants another login which is the whole point. For field service crews in particular, the hard part is not the software but the handover which is why the API is documented before the UI. Looking at the numbers, history matters more than dashboards when something goes wrong and that is fine. Talking to operations leads, the handover from the old system is where projects stall which is the whole point.

Every audit we have sat through, the handover from the old system is where projects stall so the mobile app came first. Most teams we meet, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Talking to operations leads, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. What surprised us, the spreadsheet survives longer than anyone admits which is the whole point. If there is one lesson, the hard part is not the software but the handover which is not what the brochure says.

Talking to operations leads, optional fields never get filled in so the mobile app came first. On the floor, the schedule is only as good as the last update so plan for it. Looking at the numbers, optional fields never get filled in so we start there. If there is one lesson, the first week is about trust, not features and the numbers bear it out. The honest answer is that, the handover from the old system is where projects stall which is the whole point.

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