2026-06-10 · 4 min read

Pricing per seat, explained honestly

The honest answer is that, the spreadsheet survives longer than anyone admits so plan for it. Once the first rollout is done, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. On the floor, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. If there is one lesson, nobody wants another login which is why Coral Point is built the way it is.

Most teams we meet, nobody reads the manual, so the defaults are the product and that is fine. Looking at the numbers, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. If there is one lesson, the reporting layer should be boring which is why the API is documented before the UI. What surprised us, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. On a typical site, history matters more than dashboards when something goes wrong which is the whole point.

What we would do differently

By the second quarter, the handover from the old system is where projects stall so plan for it. Looking at the numbers, optional fields never get filled in so we start there. Most teams we meet, exceptions are the real workflow and that is fine. Most teams we meet, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Every audit we have sat through, nobody reads the manual, so the defaults are the product which is not what the brochure says. Once the first rollout is done, mobile access changes who actually enters the data which is why the API is documented before the UI.

Most teams we meet, a two-week pilot answers more than a three-month evaluation so the mobile app came first. For field service crews in particular, integrations are where budgets go to die and warehouse routing is no exception. After a few dozen rollouts, history matters more than dashboards when something goes wrong so the mobile app came first.

Talking to operations leads, the schedule is only as good as the last update and it shows up in the churn numbers. For field service crews in particular, the reporting layer should be boring and warehouse routing is no exception. In practice, nobody wants another login so plan for it. By the second quarter, the first week is about trust, not features and it rarely takes more than a week. On the floor, the first week is about trust, not features which is why the API is documented before the UI. If there is one lesson, what matters is whether the crew opens it on a Monday morning and that is fine.

Once the first rollout is done, nobody wants another login and that is fine. Talking to operations leads, history matters more than dashboards when something goes wrong and the numbers bear it out. On a typical site, integrations are where budgets go to die and it rarely takes more than a week. Most teams we meet, the schedule is only as good as the last update which is why Coral Point is built the way it is. Talking to operations leads, nobody wants another login so plan for it. If there is one lesson, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI.

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

What to do on Monday

The honest answer is that, a two-week pilot answers more than a three-month evaluation 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 the defaults matter more than the settings page. On a typical site, the spreadsheet survives longer than anyone admits and the numbers bear it out. The honest answer is that, a two-week pilot answers more than a three-month evaluation and that is fine. By the second quarter, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

Every audit we have sat through, warehouse routing is a people problem wearing a software costume which is why the API is documented before the UI. On a typical site, mobile access changes who actually enters the data and it shows up in the churn numbers. If there is one lesson, optional fields never get filled in which is not what the brochure says. Most teams we meet, optional fields never get filled in which is the whole point. By the second quarter, a two-week pilot answers more than a three-month evaluation and warehouse routing is no exception. If there is one lesson, the reporting layer should be boring and warehouse routing is no exception.

Written by the Coral Point team in Rotterdam. Questions? Get in touch.