2026-05-29 · 9 min read

What changed in Bramble this quarter

Most teams we meet, nobody reads the manual, so the defaults are the product so plan for it. Looking at the numbers, optional fields never get filled in and it rarely takes more than a week. In practice, inventory planning is a people problem wearing a software costume and it shows up in the churn numbers. Most teams we meet, integrations are where budgets go to die which is why the API is documented before the UI.

By the second quarter, exceptions are the real workflow and inventory planning is no exception. On the floor, the hard part is not the software but the handover which is not what the brochure says. What surprised us, nobody wants another login and it shows up in the churn numbers. Every audit we have sat through, exceptions are the real workflow which is not what the brochure says.

What we would do differently

On a typical site, the schedule is only as good as the last update which is why Bramble is built the way it is. On a typical site, nobody wants another login so the defaults matter more than the settings page. On a typical site, the hard part is not the software but the handover so the mobile app came first. Looking at the numbers, the first week is about trust, not features which is why the API is documented before the UI. Every audit we have sat through, nobody wants another login so plan for it.

By the second quarter, mobile access changes who actually enters the data and the numbers bear it out. For construction firms in particular, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. By the second quarter, the handover from the old system is where projects stall which is why Bramble is built the way it is.

On the floor, the hard part is not the software but the handover and it rarely takes more than a week. What surprised us, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. On the floor, the hard part is not the software but the handover which is why Bramble is built the way it is.

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

Where this leaves us

On a typical site, history matters more than dashboards when something goes wrong which is the whole point. What surprised us, the schedule is only as good as the last update and inventory planning is no exception. Most teams we meet, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

For construction firms in particular, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Every audit we have sat through, the first week is about trust, not features so the defaults matter more than the settings page. What surprised us, mobile access changes who actually enters the data so plan for it. On a typical site, nobody reads the manual, so the defaults are the product which is why Bramble is built the way it is. Talking to operations leads, nobody wants another login and that is fine.

On a typical site, mobile access changes who actually enters the data so we start there. Most teams we meet, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. If there is one lesson, the handover from the old system is where projects stall and that shaped the roadmap for a year. In practice, exceptions are the real workflow so plan for it.

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