2026-05-29 · 6 min read

Pricing per seat, explained honestly

If there is one lesson, the spreadsheet survives longer than anyone admits and revenue analytics is no exception. What surprised us, the first week is about trust, not features which is why Latticehq is built the way it is. Talking to operations leads, the hard part is not the software but the handover so the defaults matter more than the settings page. In practice, integrations are where budgets go to die so plan for it. Talking to operations leads, exceptions are the real workflow which is not what the brochure says.

Once the first rollout is done, exceptions are the real workflow which is why Latticehq is built the way it is. Once the first rollout is done, nobody wants another login which is why Latticehq is built the way it is. What surprised us, mobile access changes who actually enters the data and it rarely takes more than a week.

What we would do differently

When the pilot started in Bergen, revenue analytics is a people problem wearing a software costume which is the whole point. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and revenue analytics is no exception. For logistics teams in particular, optional fields never get filled in which is not what the brochure says. If there is one lesson, the reporting layer should be boring so the mobile app came first. After a few dozen rollouts, nobody reads the manual, so the defaults are the product and that is fine.

What surprised us, the handover from the old system is where projects stall which is the whole point. What surprised us, the spreadsheet survives longer than anyone admits so plan for it. Most teams we meet, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. By the second quarter, the reporting layer should be boring so the mobile app came first. Once the first rollout is done, mobile access changes who actually enters the data and that shaped the roadmap for a year. What surprised us, the handover from the old system is where projects stall and that shaped the roadmap for a year.

“Everything logistics teams need to keep revenue analytics on schedule, on budget and on record.”

Takeaways

On a typical site, a two-week pilot answers more than a three-month evaluation so plan for it. Every audit we have sat through, revenue analytics is a people problem wearing a software costume and that shaped the roadmap for a year. Talking to operations leads, exceptions are the real workflow which is why the API is documented before the UI. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. The honest answer is that, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. Looking at the numbers, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year.

The honest answer is that, the hard part is not the software but the handover so the defaults matter more than the settings page. After a few dozen rollouts, revenue analytics is a people problem wearing a software costume so we start there. What surprised us, mobile access changes who actually enters the data and it shows up in the churn numbers. When the pilot started in Bergen, the handover from the old system is where projects stall and revenue analytics is no exception. On a typical site, the schedule is only as good as the last update so the defaults matter more than the settings page. After a few dozen rollouts, the handover from the old system is where projects stall and revenue analytics is no exception.

Written by the Latticehq team in Bergen. Questions? Get in touch.