2026-09-20 · 6 min read

22 questions to ask before you buy a workspace

Most teams we meet, the schedule is only as good as the last update which is not what the brochure says. When the pilot started in Leeds, nobody wants another login so we start there. Looking at the numbers, the biggest win is that the group chat goes quiet so plan for it. For field service crews in particular, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. The honest answer is that, invoice reconciliation is a people problem wearing a software costume which is why the API is documented before the UI. On the floor, invoice reconciliation is a people problem wearing a software costume so plan for it.

After a few dozen rollouts, nobody reads the manual, so the defaults are the product and that is fine. By the second quarter, nobody wants another login and the numbers bear it out. If there is one lesson, the first week is about trust, not features and it shows up in the churn numbers.

Looking at the numbers, the handover from the old system is where projects stall and that is fine. Most teams we meet, the handover from the old system is where projects stall and that shaped the roadmap for a year. On a typical site, integrations are where budgets go to die which is why Cobalt is built the way it is. After a few dozen rollouts, mobile access changes who actually enters the data which is why the API is documented before the UI.

What actually happened

When the pilot started in Leeds, mobile access changes who actually enters the data so we start there. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. Once the first rollout is done, nobody wants another login so plan for it. Every audit we have sat through, invoice reconciliation is a people problem wearing a software costume which is not what the brochure says.

For field service crews in particular, exceptions are the real workflow and that is fine. When the pilot started in Leeds, integrations are where budgets go to die which is why the API is documented before the UI. Once the first rollout is done, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers.

By the second quarter, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. Talking to operations leads, integrations are where budgets go to die so the mobile app came first. On the floor, nobody wants another login 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 the mobile app came first.

“Everything field service crews need to keep invoice reconciliation on schedule, on budget and on record.”

What to do on Monday

Every audit we have sat through, the hard part is not the software but the handover so plan for it. On a typical site, the first week is about trust, not features and that shaped the roadmap for a year. Talking to operations leads, mobile access changes who actually enters the data which is not what the brochure says. The honest answer is that, the audit trail pays for itself the first time an inspector asks so we start there. On a typical site, nobody wants another login and it shows up in the churn numbers.

In practice, the reporting layer should be boring so plan for it. If there is one lesson, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. After a few dozen rollouts, the biggest win is that the group chat goes quiet and it rarely takes more than a week. What surprised us, the handover from the old system is where projects stall and the numbers bear it out. By the second quarter, the biggest win is that the group chat goes quiet so we start there. What surprised us, the handover from the old system is where projects stall which is why the API is documented before the UI.

Talking to operations leads, integrations are where budgets go to die so we start there. On the floor, nobody reads the manual, so the defaults are the product and invoice reconciliation is no exception. The honest answer is that, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is not what the brochure says.

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