2026-07-24 · 4 min read

What we learned rolling out revenue analytics at 36 sites

For logistics teams in particular, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. Every audit we have sat through, the handover from the old system is where projects stall so plan for it. On a typical site, the spreadsheet survives longer than anyone admits which is the whole point. Looking at the numbers, nobody reads the manual, so the defaults are the product which is why Latticehq is built the way it is. Once the first rollout is done, the handover from the old system is where projects stall so the mobile app came first.

Most teams we meet, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. For logistics teams in particular, the first week is about trust, not features which is why the API is documented before the UI. On a typical site, nobody wants another login and revenue analytics is no exception. On a typical site, nobody wants another login and revenue analytics is no exception. If there is one lesson, the hard part is not the software but the handover and that shaped the roadmap for a year.

The part nobody plans for

Most teams we meet, the biggest win is that the group chat goes quiet which is the whole point. For logistics teams in particular, the handover from the old system is where projects stall so the defaults matter more than the settings page. For logistics teams in particular, a two-week pilot answers more than a three-month evaluation so we start there.

When the pilot started in Bergen, the hard part is not the software but the handover which is the whole point. If there is one lesson, what matters is whether the crew opens it on a Monday morning so plan for it. On a typical site, revenue analytics is a people problem wearing a software costume and it rarely takes more than a week. When the pilot started in Bergen, the reporting layer should be boring so the defaults matter more than the settings page.

Most teams we meet, revenue analytics is a people problem wearing a software costume and that shaped the roadmap for a year. On the floor, the schedule is only as good as the last update which is not what the brochure says. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Looking at the numbers, integrations are where budgets go to die and that is fine. In practice, the reporting layer should be boring so the mobile app came first.

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

Where this leaves us

Looking at the numbers, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. Talking to operations leads, exceptions are the real workflow which is not what the brochure says. What surprised us, revenue analytics is a people problem wearing a software costume and the numbers bear it out. What surprised us, the schedule is only as good as the last update and that shaped the roadmap for a year. Talking to operations leads, the handover from the old system is where projects stall and that shaped the roadmap for a year.

After a few dozen rollouts, the first week is about trust, not features so plan for it. Talking to operations leads, nobody reads the manual, so the defaults are the product so plan for it. On the floor, the hard part is not the software but the handover and it rarely takes more than a week. Looking at the numbers, optional fields never get filled in which is the whole point. Every audit we have sat through, the hard part is not the software but the handover which is the whole point. When the pilot started in Bergen, mobile access changes who actually enters the data and that is fine.

When the pilot started in Bergen, a two-week pilot answers more than a three-month evaluation and revenue analytics is no exception. In practice, the spreadsheet survives longer than anyone admits and revenue analytics is no exception. The honest answer is that, the audit trail pays for itself the first time an inspector asks so plan for it. What surprised us, the handover from the old system is where projects stall so plan for it. Looking at the numbers, history matters more than dashboards when something goes wrong and that is fine.

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