2026-09-07 · 5 min read

What changed in Bramble this quarter

Talking to operations leads, nobody reads the manual, so the defaults are the product so we start there. Once the first rollout is done, the schedule is only as good as the last update which is not what the brochure says. What surprised us, exceptions are the real workflow which is why the API is documented before the UI. If there is one lesson, the hard part is not the software but the handover which is not what the brochure says. Looking at the numbers, integrations are where budgets go to die which is why Bramble is built the way it is.

In practice, history matters more than dashboards when something goes wrong which is not what the brochure says. After a few dozen rollouts, the hard part is not the software but the handover which is why Bramble is built the way it is. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so plan for it. Once the first rollout is done, nobody wants another login which is why the API is documented before the UI. After a few dozen rollouts, the handover from the old system is where projects stall which is why Bramble is built the way it is.

What we would do differently

If there is one lesson, the audit trail pays for itself the first time an inspector asks and that is fine. Looking at the numbers, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. Most teams we meet, a two-week pilot answers more than a three-month evaluation so we start there. Once the first rollout is done, the first week is about trust, not features so plan for it. In practice, nobody reads the manual, so the defaults are the product and customer onboarding is no exception.

Looking at the numbers, nobody reads the manual, so the defaults are the product which is not what the brochure says. What surprised us, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. The honest answer is that, exceptions are the real workflow and it shows up in the churn numbers. For field service crews in particular, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why Bramble is built the way it is.

In practice, the spreadsheet survives longer than anyone admits so we start there. The honest answer is that, the first week is about trust, not features which is why Bramble is built the way it is. On a typical site, what matters is whether the crew opens it on a Monday morning so plan for it. What surprised us, optional fields never get filled in so we start there. On a typical site, nobody reads the manual, so the defaults are the product and that is fine.

“Everything field service crews need to keep customer onboarding on schedule, on budget and on record.”

What to do on Monday

Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Most teams we meet, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. Looking at the numbers, optional fields never get filled in and the numbers bear it out. For field service crews in particular, a two-week pilot answers more than a three-month evaluation so plan for it. In practice, customer onboarding is a people problem wearing a software costume and it shows up in the churn numbers.

On the floor, the audit trail pays for itself the first time an inspector asks so we start there. What surprised us, nobody wants another login so plan for it. After a few dozen rollouts, history matters more than dashboards when something goes wrong and that is fine. On the floor, the handover from the old system is where projects stall so plan for it.

Most teams we meet, the handover from the old system is where projects stall which is not what the brochure says. By the second quarter, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. When the pilot started in Bergen, optional fields never get filled in and it shows up in the churn numbers. Once the first rollout is done, the spreadsheet survives longer than anyone admits so plan for it.

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