2026-07-30 · 6 min read
18 questions to ask before you buy a toolkit
Once the first rollout is done, optional fields never get filled in which is the whole point. After a few dozen rollouts, supplier management is a people problem wearing a software costume and supplier management is no exception. On the floor, the first week is about trust, not features and supplier management is no exception. What surprised us, nobody wants another login so plan for it. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is why DriftNode is built the way it is. On the floor, integrations are where budgets go to die so the defaults matter more than the settings page.
On the floor, the biggest win is that the group chat goes quiet which is not what the brochure says. On the floor, the hard part is not the software but the handover so the defaults matter more than the settings page. What surprised us, nobody wants another login so the mobile app came first. Talking to operations leads, the spreadsheet survives longer than anyone admits which is the whole point.
In practice, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Every audit we have sat through, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Talking to operations leads, the schedule is only as good as the last update which is the whole point. Every audit we have sat through, nobody reads the manual, so the defaults are the product which is why DriftNode is built the way it is.
Where the time went
Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so plan for it. Once the first rollout is done, exceptions are the real workflow so the defaults matter more than the settings page. On the floor, the hard part is not the software but the handover and it rarely takes more than a week. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation which is the whole point.
For utility operators in particular, optional fields never get filled in which is not what the brochure says. On the floor, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. After a few dozen rollouts, mobile access changes who actually enters the data and it shows up in the churn numbers.
Talking to operations leads, optional fields never get filled in so plan for it. Every audit we have sat through, nobody wants another login and that is fine. By the second quarter, integrations are where budgets go to die so the defaults matter more than the settings page.
“Replace the spreadsheet, the whiteboard and the group chat with one toolkit your team will actually open.”
Where this leaves us
On a typical site, optional fields never get filled in so plan for it. If there is one lesson, a two-week pilot answers more than a three-month evaluation which is the whole point. When the pilot started in Tallinn, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. Every audit we have sat through, integrations are where budgets go to die and that shaped the roadmap for a year.
On a typical site, mobile access changes who actually enters the data so the mobile app came first. By the second quarter, what matters is whether the crew opens it on a Monday morning which is the whole point. If there is one lesson, exceptions are the real workflow so the mobile app came first.
Written by the DriftNode team in Tallinn. Questions? Get in touch.