2026-05-04 · 7 min read

Exceptions are the real workflow

The honest answer is that, the handover from the old system is where projects stall which is why the API is documented before the UI. Looking at the numbers, nobody reads the manual, so the defaults are the product which is why Basalt Point is built the way it is. Once the first rollout is done, exceptions are the real workflow which is why the API is documented before the UI. If there is one lesson, the first week is about trust, not features and it shows up in the churn numbers. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is not what the brochure says.

For utility operators in particular, the first week is about trust, not features and that shaped the roadmap for a year. Talking to operations leads, the first week is about trust, not features which is the whole point. Every audit we have sat through, optional fields never get filled in and that shaped the roadmap for a year. What surprised us, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. By the second quarter, integrations are where budgets go to die so the defaults matter more than the settings page. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week.

Where the time went

The honest answer is that, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Talking to operations leads, optional fields never get filled in so plan for it. In practice, a two-week pilot answers more than a three-month evaluation so we start there. After a few dozen rollouts, integrations are where budgets go to die which is the whole point.

Once the first rollout is done, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. On the floor, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. If there is one lesson, the hard part is not the software but the handover so the defaults matter more than the settings page. On a typical site, the first week is about trust, not features and that shaped the roadmap for a year.

“Basalt Point gives utility operators a single, dependable view of fleet telemetry - from first request to signed-off report.”

What to do on Monday

What surprised us, what matters is whether the crew opens it on a Monday morning so we start there. On the floor, the spreadsheet survives longer than anyone admits which is not what the brochure says. Talking to operations leads, exceptions are the real workflow which is not what the brochure says.

In practice, the first week is about trust, not features and that is fine. After a few dozen rollouts, integrations are where budgets go to die so plan for it. On a typical site, the reporting layer should be boring which is the whole point. Once the first rollout is done, nobody wants another login and it rarely takes more than a week.

Written by the Basalt Point team in Ghent. Questions? Get in touch.