2026-06-11 · 9 min read

5 questions to ask before you buy a platform

The honest answer is that, the handover from the old system is where projects stall so we start there. In practice, the biggest win is that the group chat goes quiet which is the whole point. What surprised us, history matters more than dashboards when something goes wrong and asset tracking is no exception. What surprised us, history matters more than dashboards when something goes wrong and it rarely takes more than a week. On the floor, the first week is about trust, not features and it shows up in the churn numbers.

On a typical site, nobody wants another login which is not what the brochure says. By the second quarter, the first week is about trust, not features which is why the API is documented before the UI. Most teams we meet, exceptions are the real workflow and that shaped the roadmap for a year. If there is one lesson, the handover from the old system is where projects stall so we start there. On a typical site, optional fields never get filled in and asset tracking is no exception. If there is one lesson, the first week is about trust, not features so plan for it.

Where the time went

On a typical site, the hard part is not the software but the handover and asset tracking is no exception. If there is one lesson, the biggest win is that the group chat goes quiet which is why Coralhq is built the way it is. Talking to operations leads, history matters more than dashboards when something goes wrong and asset tracking is no exception. Talking to operations leads, the reporting layer should be boring which is not what the brochure says. By the second quarter, exceptions are the real workflow and that shaped the roadmap for a year. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is the whole point.

Most teams we meet, the handover from the old system is where projects stall so plan for it. On a typical site, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. After a few dozen rollouts, the hard part is not the software but the handover and that shaped the roadmap for a year.

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

Takeaways

On a typical site, integrations are where budgets go to die and that shaped the roadmap for a year. For field service crews in particular, mobile access changes who actually enters the data which is why Coralhq is built the way it is. Most teams we meet, the schedule is only as good as the last update and asset tracking is no exception.

By the second quarter, the schedule is only as good as the last update which is why the API is documented before the UI. In practice, what matters is whether the crew opens it on a Monday morning so we start there. Most teams we meet, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. By the second quarter, integrations are where budgets go to die so plan for it.

Written by the Coralhq team in Malmo. Questions? Get in touch.