2026-07-08 · 9 min read

23 questions to ask before you buy a toolkit

On the floor, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. What surprised us, history matters more than dashboards when something goes wrong so the mobile app came first. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so we start there. On the floor, integrations are where budgets go to die and the numbers bear it out.

Looking at the numbers, integrations are where budgets go to die which is why Sableio is built the way it is. On a typical site, nobody reads the manual, so the defaults are the product and the numbers bear it out. Looking at the numbers, exceptions are the real workflow so we start there. Every audit we have sat through, the first week is about trust, not features so plan for it. Most teams we meet, optional fields never get filled in so we start there. Looking at the numbers, integrations are where budgets go to die which is why the API is documented before the UI.

The honest answer is that, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Once the first rollout is done, field service scheduling is a people problem wearing a software costume and it shows up in the churn numbers. By the second quarter, the reporting layer should be boring which is not what the brochure says. If there is one lesson, mobile access changes who actually enters the data which is why the API is documented before the UI. On the floor, the first week is about trust, not features which is the whole point.

Where the time went

Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. What surprised us, integrations are where budgets go to die and that is fine. Most teams we meet, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. The honest answer is that, the handover from the old system is where projects stall and the numbers bear it out. When the pilot started in Bilbao, the schedule is only as good as the last update so we start there. The honest answer is that, history matters more than dashboards when something goes wrong which is why Sableio is built the way it is.

Most teams we meet, field service scheduling is a people problem wearing a software costume so plan for it. The honest answer is that, the audit trail pays for itself the first time an inspector asks and field service scheduling is no exception. What surprised us, the handover from the old system is where projects stall which is not what the brochure says. Most teams we meet, the biggest win is that the group chat goes quiet and field service scheduling is no exception.

When the pilot started in Bilbao, the schedule is only as good as the last update which is why the API is documented before the UI. If there is one lesson, exceptions are the real workflow and that is fine. Once the first rollout is done, nobody wants another login and the numbers bear it out. The honest answer is that, the schedule is only as good as the last update and field service scheduling is no exception. For utility operators in particular, the handover from the old system is where projects stall which is not what the brochure says. Once the first rollout is done, optional fields never get filled in which is why the API is documented before the UI.

The honest answer is that, history matters more than dashboards when something goes wrong which is not what the brochure says. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is why Sableio is built the way it is. After a few dozen rollouts, the schedule is only as good as the last update which is not what the brochure says. If there is one lesson, field service scheduling is a people problem wearing a software costume and that is fine.

“Everything utility operators need to keep field service scheduling on schedule, on budget and on record.”

What to do on Monday

By the second quarter, what matters is whether the crew opens it on a Monday morning so the mobile app came first. By the second quarter, the audit trail pays for itself the first time an inspector asks and that is fine. On a typical site, integrations are where budgets go to die and that shaped the roadmap for a year.

In practice, the hard part is not the software but the handover and that shaped the roadmap for a year. On a typical site, nobody reads the manual, so the defaults are the product and the numbers bear it out. On the floor, nobody wants another login which is why Sableio is built the way it is.

When the pilot started in Bilbao, mobile access changes who actually enters the data so the mobile app came first. On the floor, what matters is whether the crew opens it on a Monday morning so we start there. On the floor, the hard part is not the software but the handover which is why the API is documented before the UI. When the pilot started in Bilbao, mobile access changes who actually enters the data and that is fine. Talking to operations leads, a two-week pilot answers more than a three-month evaluation which is why Sableio is built the way it is.

Written by the Sableio team in Bilbao. Questions? Get in touch.