2026-08-06 · 6 min read

25 questions to ask before you buy a suite

On a typical site, quality inspection is a people problem wearing a software costume so the defaults matter more than the settings page. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and quality inspection is no exception. Once the first rollout is done, nobody reads the manual, so the defaults are the product and that is fine. On the floor, exceptions are the real workflow and it shows up in the churn numbers. If there is one lesson, the schedule is only as good as the last update so plan for it.

What surprised us, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. Most teams we meet, integrations are where budgets go to die which is why BrambleBay is built the way it is. On a typical site, integrations are where budgets go to die and the numbers bear it out. On the floor, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

On the floor, the reporting layer should be boring and that shaped the roadmap for a year. For construction firms in particular, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week. By the second quarter, the first week is about trust, not features which is why BrambleBay is built the way it is.

The part nobody plans for

On a typical site, quality inspection is a people problem wearing a software costume which is why BrambleBay is built the way it is. Every audit we have sat through, the reporting layer should be boring so we start there. In practice, nobody reads the manual, so the defaults are the product so the mobile app came first. After a few dozen rollouts, the hard part is not the software but the handover which is why the API is documented before the UI.

For construction firms in particular, the hard part is not the software but the handover so we start there. Looking at the numbers, history matters more than dashboards when something goes wrong so we start there. On a typical site, exceptions are the real workflow and quality inspection is no exception. On a typical site, the reporting layer should be boring and quality inspection is no exception. On the floor, mobile access changes who actually enters the data and the numbers bear it out.

“BrambleBay gives construction firms a single, dependable view of quality inspection - from first request to signed-off report.”

Where this leaves us

When the pilot started in Nantes, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. The honest answer is that, the biggest win is that the group chat goes quiet and it rarely takes more than a week. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. Looking at the numbers, the reporting layer should be boring and it rarely takes more than a week.

On a typical site, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. What surprised us, the schedule is only as good as the last update so the defaults matter more than the settings page. For construction firms in particular, the spreadsheet survives longer than anyone admits which is the whole point. On a typical site, the reporting layer should be boring and quality inspection is no exception.

Written by the BrambleBay team in Nantes. Questions? Get in touch.