2026-06-04 · 5 min read

The audit that changed our roadmap

Looking at the numbers, the reporting layer should be boring and that is fine. On a typical site, the hard part is not the software but the handover which is the whole point. On a typical site, the biggest win is that the group chat goes quiet which is not what the brochure says. By the second quarter, nobody reads the manual, so the defaults are the product so plan for it. By the second quarter, the spreadsheet survives longer than anyone admits so plan for it.

On a typical site, integrations are where budgets go to die and it rarely takes more than a week. If there is one lesson, the spreadsheet survives longer than anyone admits and the numbers bear it out. On the floor, the spreadsheet survives longer than anyone admits so the mobile app came first. By the second quarter, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Most teams we meet, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. When the pilot started in Porto, optional fields never get filled in so we start there.

Looking at the numbers, the first week is about trust, not features so plan for it. Most teams we meet, field service scheduling is a people problem wearing a software costume and the numbers bear it out. By the second quarter, what matters is whether the crew opens it on a Monday morning so we start there. By the second quarter, the handover from the old system is where projects stall so the mobile app came first.

What we would do differently

On the floor, the handover from the old system is where projects stall and it shows up in the churn numbers. Talking to operations leads, the handover from the old system is where projects stall which is not what the brochure says. Looking at the numbers, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Talking to operations leads, the hard part is not the software but the handover and field service scheduling is no exception. The honest answer is that, the spreadsheet survives longer than anyone admits so plan for it. When the pilot started in Porto, nobody wants another login so the mobile app came first.

When the pilot started in Porto, field service scheduling is a people problem wearing a software costume so the defaults matter more than the settings page. The honest answer is that, mobile access changes who actually enters the data which is the whole point. Looking at the numbers, optional fields never get filled in and it shows up in the churn numbers. If there is one lesson, field service scheduling is a people problem wearing a software costume and field service scheduling is no exception. On the floor, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. In practice, optional fields never get filled in which is not what the brochure says.

On the floor, the handover from the old system is where projects stall and field service scheduling is no exception. On the floor, what matters is whether the crew opens it on a Monday morning and that is fine. In practice, integrations are where budgets go to die which is why Brambleify is built the way it is. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that is fine. Talking to operations leads, optional fields never get filled in which is why the API is documented before the UI.

Once the first rollout is done, the handover from the old system is where projects stall which is why the API is documented before the UI. Every audit we have sat through, field service scheduling is a people problem wearing a software costume which is not what the brochure says. In practice, what matters is whether the crew opens it on a Monday morning and that is fine. The honest answer is that, nobody wants another login and it rarely takes more than a week.

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

Where this leaves us

The honest answer is that, what matters is whether the crew opens it on a Monday morning which is why Brambleify is built the way it is. Most teams we meet, nobody wants another login which is why Brambleify is built the way it is. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. On the floor, integrations are where budgets go to die so plan for it.

After a few dozen rollouts, the reporting layer should be boring which is why Brambleify is built the way it is. If there is one lesson, the hard part is not the software but the handover so plan for it. The honest answer is that, nobody reads the manual, so the defaults are the product and the numbers bear it out. Once the first rollout is done, exceptions are the real workflow which is why the API is documented before the UI.

Written by the Brambleify team in Porto. Questions? Get in touch.