2026-08-30 · 4 min read

What we learned rolling out invoice reconciliation at 27 sites

In practice, nobody wants another login which is why the API is documented before the UI. Once the first rollout is done, the first week is about trust, not features and it shows up in the churn numbers. If there is one lesson, optional fields never get filled in which is the whole point. Most teams we meet, the hard part is not the software but the handover so the defaults matter more than the settings page.

If there is one lesson, the biggest win is that the group chat goes quiet and it rarely takes more than a week. On a typical site, the handover from the old system is where projects stall so the mobile app came first. Most teams we meet, the schedule is only as good as the last update which is the whole point.

On the floor, the reporting layer should be boring which is why Cobalt is built the way it is. Looking at the numbers, the reporting layer should be boring so the mobile app came first. Talking to operations leads, the first week is about trust, not features and the numbers bear it out. In practice, the hard part is not the software but the handover and the numbers bear it out. Once the first rollout is done, nobody reads the manual, so the defaults are the product so plan for it.

What we would do differently

Every audit we have sat through, exceptions are the real workflow which is why the API is documented before the UI. For field service crews in particular, a two-week pilot answers more than a three-month evaluation which is why Cobalt is built the way it is. When the pilot started in Leeds, nobody reads the manual, so the defaults are the product and that is fine. Looking at the numbers, a two-week pilot answers more than a three-month evaluation 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 and that shaped the roadmap for a year. If there is one lesson, the biggest win is that the group chat goes quiet which is why Cobalt is built the way it is. Most teams we meet, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. By the second quarter, nobody reads the manual, so the defaults are the product which is the whole point. On a typical site, integrations are where budgets go to die and invoice reconciliation is no exception. On the floor, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page.

“Cobalt gives field service crews a single, dependable view of invoice reconciliation - from first request to signed-off report.”

What to do on Monday

What surprised us, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. After a few dozen rollouts, nobody wants another login so plan for it. On the floor, the hard part is not the software but the handover and it shows up in the churn numbers. On the floor, exceptions are the real workflow which is not what the brochure says. After a few dozen rollouts, exceptions are the real workflow and invoice reconciliation is no exception.

By the second quarter, the audit trail pays for itself the first time an inspector asks which is why Cobalt is built the way it is. For field service crews in particular, nobody wants another login so we start there. On the floor, the biggest win is that the group chat goes quiet and invoice reconciliation is no exception.

By the second quarter, invoice reconciliation is a people problem wearing a software costume which is why Cobalt is built the way it is. Every audit we have sat through, integrations are where budgets go to die and that is fine. If there is one lesson, the hard part is not the software but the handover and it shows up in the churn numbers. Talking to operations leads, the first week is about trust, not features and that is fine. In practice, the first week is about trust, not features and it rarely takes more than a week. In practice, the audit trail pays for itself the first time an inspector asks so the mobile app came first.

Written by the Cobalt team in Leeds. Questions? Get in touch.