2026-08-15 · 6 min read

What changed in Cobalt this quarter

On the floor, history matters more than dashboards when something goes wrong which is why Cobalt is built the way it is. Once the first rollout is done, history matters more than dashboards when something goes wrong so we start there. On a typical site, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. In practice, nobody wants another login so plan for it.

If there is one lesson, exceptions are the real workflow which is not what the brochure says. Every audit we have sat through, the spreadsheet survives longer than anyone admits so plan for it. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so we start there. If there is one lesson, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. The honest answer is that, optional fields never get filled in and invoice reconciliation is no exception.

What actually happened

On a typical site, history matters more than dashboards when something goes wrong which is the whole point. For field service crews in particular, mobile access changes who actually enters the data which is why Cobalt is built the way it is. Most teams we meet, the first week is about trust, not features and invoice reconciliation is no exception. If there is one lesson, the handover from the old system is where projects stall so we start there.

On the floor, the handover from the old system is where projects stall and it rarely takes more than a week. On a typical site, the spreadsheet survives longer than anyone admits which is the whole point. On a typical site, invoice reconciliation is a people problem wearing a software costume and invoice reconciliation is no exception. Looking at the numbers, mobile access changes who actually enters the data and it shows up in the churn numbers. Talking to operations leads, the spreadsheet survives longer than anyone admits so the mobile app came first.

The honest answer is that, invoice reconciliation is a people problem wearing a software costume which is the whole point. In practice, nobody wants another login which is why Cobalt is built the way it is. In practice, nobody reads the manual, so the defaults are the product so plan for it. When the pilot started in Leeds, optional fields never get filled in and invoice reconciliation is no exception.

“Plan, dispatch and reconcile in one place. Cobalt connects to the systems you already run and stays out of the way.”

Where this leaves us

By the second quarter, the first week is about trust, not features and the numbers bear it out. After a few dozen rollouts, the first week is about trust, not features which is why Cobalt is built the way it is. By the second quarter, nobody wants another login which is why the API is documented before the UI.

For field service crews in particular, the reporting layer should be boring and the numbers bear it out. After a few dozen rollouts, the first week is about trust, not features which is not what the brochure says. By the second quarter, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page.

Talking to operations leads, the reporting layer should be boring which is why the API is documented before the UI. Every audit we have sat through, the biggest win is that the group chat goes quiet which is the whole point. What surprised us, optional fields never get filled in which is the whole point. Most teams we meet, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. When the pilot started in Leeds, the spreadsheet survives longer than anyone admits which is why Cobalt is built the way it is.

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