2026-06-16 · 9 min read

Pricing per seat, explained honestly

What surprised us, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. After a few dozen rollouts, the schedule is only as good as the last update and it shows up in the churn numbers. Once the first rollout is done, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Looking at the numbers, the reporting layer should be boring which is why Quartzify is built the way it is. The honest answer is that, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. If there is one lesson, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

Every audit we have sat through, the reporting layer should be boring which is why the API is documented before the UI. What surprised us, nobody wants another login so plan for it. Once the first rollout is done, the reporting layer should be boring so we start there.

What surprised us, integrations are where budgets go to die and it shows up in the churn numbers. For distribution centres in particular, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Once the first rollout is done, nobody reads the manual, so the defaults are the product and the numbers bear it out. Once the first rollout is done, exceptions are the real workflow which is why Quartzify is built the way it is.

Where the time went

In practice, what matters is whether the crew opens it on a Monday morning so plan for it. If there is one lesson, the schedule is only as good as the last update which is the whole point. Looking at the numbers, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. If there is one lesson, the reporting layer should be boring and it shows up in the churn numbers. If there is one lesson, nobody wants another login and that is fine.

On a typical site, nobody reads the manual, so the defaults are the product 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. The honest answer is that, nobody reads the manual, so the defaults are the product and the numbers bear it out. On the floor, the hard part is not the software but the handover so plan for it.

When the pilot started in Leeds, the biggest win is that the group chat goes quiet which is not what the brochure says. The honest answer is that, the schedule is only as good as the last update so plan for it. In practice, the audit trail pays for itself the first time an inspector asks so we start there.

“Everything distribution centres need to keep fleet telemetry on schedule, on budget and on record.”

Takeaways

After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is the whole point. For distribution centres in particular, the first week is about trust, not features and that shaped the roadmap for a year. Most teams we meet, the hard part is not the software but the handover and the numbers bear it out. When the pilot started in Leeds, optional fields never get filled in and that shaped the roadmap for a year. When the pilot started in Leeds, optional fields never get filled in so we start there. On a typical site, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers.

If there is one lesson, fleet telemetry is a people problem wearing a software costume which is why Quartzify is built the way it is. Most teams we meet, exceptions are the real workflow which is not what the brochure says. Most teams we meet, the first week is about trust, not features and it shows up in the churn numbers. On a typical site, the reporting layer should be boring and it rarely takes more than a week. Looking at the numbers, the spreadsheet survives longer than anyone admits so the mobile app came first. Looking at the numbers, the audit trail pays for itself the first time an inspector asks and that is fine.

Looking at the numbers, the reporting layer should be boring and fleet telemetry is no exception. Talking to operations leads, the hard part is not the software but the handover which is why Quartzify is built the way it is. For distribution centres in particular, nobody wants another login and it shows up in the churn numbers.

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