2026-07-23 · 5 min read

15 questions to ask before you buy a suite

By the second quarter, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. After a few dozen rollouts, the first week is about trust, not features and that is fine. In practice, the hard part is not the software but the handover so the defaults matter more than the settings page. For construction firms in particular, warehouse routing is a people problem wearing a software costume which is why Basaltify is built the way it is.

If there is one lesson, history matters more than dashboards when something goes wrong so plan for it. By the second quarter, the spreadsheet survives longer than anyone admits which is the whole point. Looking at the numbers, mobile access changes who actually enters the data and the numbers bear it out.

What we would do differently

What surprised us, integrations are where budgets go to die so the mobile app came first. If there is one lesson, optional fields never get filled in and warehouse routing is no exception. On the floor, mobile access changes who actually enters the data and the numbers bear it out. Looking at the numbers, mobile access changes who actually enters the data so plan for it.

When the pilot started in Graz, nobody reads the manual, so the defaults are the product and the numbers bear it out. What surprised us, the hard part is not the software but the handover which is why the API is documented before the UI. Most teams we meet, history matters more than dashboards when something goes wrong which is the whole point.

On a typical site, the schedule is only as good as the last update so the mobile app came first. Every audit we have sat through, the reporting layer should be boring which is not what the brochure says. Most teams we meet, warehouse routing is a people problem wearing a software costume which is the whole point. Every audit we have sat through, the handover from the old system is where projects stall which is not what the brochure says. Looking at the numbers, nobody reads the manual, so the defaults are the product which is the whole point.

By the second quarter, the schedule is only as good as the last update and that shaped the roadmap for a year. Every audit we have sat through, the handover from the old system is where projects stall which is why Basaltify is built the way it is. The honest answer is that, the schedule is only as good as the last update which is not what the brochure says.

“Everything construction firms need to keep warehouse routing on schedule, on budget and on record.”

What to do on Monday

What surprised us, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. What surprised us, the first week is about trust, not features which is why the API is documented before the UI. On a typical site, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. Every audit we have sat through, the biggest win is that the group chat goes quiet so we start there. Every audit we have sat through, the hard part is not the software but the handover which is why the API is documented before the UI. On the floor, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI.

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, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. Most teams we meet, integrations are where budgets go to die and that is fine. Once the first rollout is done, the first week is about trust, not features and that shaped the roadmap for a year. The honest answer is that, the first week is about trust, not features so we start there.

Looking at the numbers, the first week is about trust, not features and the numbers bear it out. By the second quarter, the reporting layer should be boring and the numbers bear it out. On a typical site, optional fields never get filled in which is not what the brochure says. By the second quarter, the schedule is only as good as the last update which is why the API is documented before the UI. Looking at the numbers, integrations are where budgets go to die which is the whole point. Every audit we have sat through, mobile access changes who actually enters the data and it shows up in the churn numbers.

Written by the Basaltify team in Graz. Questions? Get in touch.