2026-08-05 · 6 min read

8 questions to ask before you buy a workspace

On a typical site, nobody reads the manual, so the defaults are the product and asset tracking is no exception. In practice, asset tracking is a people problem wearing a software costume and it rarely takes more than a week. When the pilot started in Graz, exceptions are the real workflow so the mobile app came first.

What surprised us, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. For logistics teams in particular, the spreadsheet survives longer than anyone admits which is not what the brochure says. If there is one lesson, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. On a typical site, exceptions are the real workflow which is why Coralio is built the way it is. Every audit we have sat through, history matters more than dashboards when something goes wrong so the mobile app came first. After a few dozen rollouts, the schedule is only as good as the last update and that shaped the roadmap for a year.

Most teams we meet, the spreadsheet survives longer than anyone admits which is the whole point. On the floor, the schedule is only as good as the last update which is why the API is documented before the UI. What surprised us, the reporting layer should be boring so plan for it. Looking at the numbers, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers.

The part nobody plans for

After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. When the pilot started in Graz, the first week is about trust, not features and it shows up in the churn numbers. Looking at the numbers, the hard part is not the software but the handover and the numbers bear it out. For logistics teams in particular, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. If there is one lesson, what matters is whether the crew opens it on a Monday morning so we start there. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

By the second quarter, the first week is about trust, not features and that is fine. Talking to operations leads, integrations are where budgets go to die and the numbers bear it out. After a few dozen rollouts, the spreadsheet survives longer than anyone admits and the numbers bear it out. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

“Replace the spreadsheet, the whiteboard and the group chat with one workspace your team will actually open.”

Where this leaves us

On a typical site, exceptions are the real workflow so we start there. For logistics teams in particular, integrations are where budgets go to die and the numbers bear it out. Most teams we meet, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. If there is one lesson, nobody wants another login so plan for it.

After a few dozen rollouts, the first week is about trust, not features and it rarely takes more than a week. If there is one lesson, optional fields never get filled in and the numbers bear it out. Talking to operations leads, the hard part is not the software but the handover so the defaults matter more than the settings page. Once the first rollout is done, the biggest win is that the group chat goes quiet and it rarely takes more than a week. What surprised us, integrations are where budgets go to die and the numbers bear it out.

Looking at the numbers, the reporting layer should be boring which is why Coralio is built the way it is. Once the first rollout is done, the schedule is only as good as the last update and it rarely takes more than a week. Talking to operations leads, the first week is about trust, not features so the mobile app came first. If there is one lesson, integrations are where budgets go to die which is why the API is documented before the UI.

Written by the Coralio team in Graz. Questions? Get in touch.