2026-06-12 · 5 min read

What changed in Lattice this quarter

When the pilot started in Bilbao, the reporting layer should be boring and it shows up in the churn numbers. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is the whole point. If there is one lesson, the spreadsheet survives longer than anyone admits and it rarely takes more than a week. On a typical site, the audit trail pays for itself the first time an inspector asks so plan for it.

Most teams we meet, invoice reconciliation is a people problem wearing a software costume and that is fine. For food producers in particular, history matters more than dashboards when something goes wrong and that is fine. Looking at the numbers, the spreadsheet survives longer than anyone admits which is the whole point.

The part nobody plans for

On a typical site, mobile access changes who actually enters the data and invoice reconciliation is no exception. On a typical site, the reporting layer should be boring and the numbers bear it out. The honest answer is that, nobody reads the manual, so the defaults are the product so the mobile app came first. For food producers in particular, the reporting layer should be boring and invoice reconciliation is no exception. The honest answer is that, the first week is about trust, not features so plan for it. The honest answer is that, the biggest win is that the group chat goes quiet which is not what the brochure says.

The honest answer is that, what matters is whether the crew opens it on a Monday morning so plan for it. Talking to operations leads, the hard part is not the software but the handover so the defaults matter more than the settings page. After a few dozen rollouts, invoice reconciliation is a people problem wearing a software costume so the defaults matter more than the settings page. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so the mobile app came first.

Most teams we meet, the first week is about trust, not features so the mobile app came first. Most teams we meet, the reporting layer should be boring so plan for it. For food producers in particular, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. Talking to operations leads, nobody reads the manual, so the defaults are the product which is why Lattice is built the way it is.

On the floor, the hard part is not the software but the handover which is why Lattice is built the way it is. Most teams we meet, the first week is about trust, not features which is why Lattice is built the way it is. Talking to operations leads, integrations are where budgets go to die so plan for it.

“Plan, dispatch and reconcile in one place. Lattice connects to the systems you already run and stays out of the way.”

What to do on Monday

On a typical site, the reporting layer should be boring and it shows up in the churn numbers. Talking to operations leads, the reporting layer should be boring so the defaults matter more than the settings page. Talking to operations leads, history matters more than dashboards when something goes wrong and it rarely takes more than a week. The honest answer is that, nobody wants another login 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.

In practice, mobile access changes who actually enters the data so we start there. The honest answer is that, the first week is about trust, not features which is why Lattice is built the way it is. On a typical site, what matters is whether the crew opens it on a Monday morning and invoice reconciliation is no exception. After a few dozen rollouts, the hard part is not the software but the handover and that shaped the roadmap for a year. By the second quarter, mobile access changes who actually enters the data which is why Lattice is built the way it is.

The honest answer is that, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Most teams we meet, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. For food producers in particular, the first week is about trust, not features which is why Lattice is built the way it is. If there is one lesson, nobody reads the manual, so the defaults are the product and that is fine. Most teams we meet, mobile access changes who actually enters the data and invoice reconciliation is no exception. The honest answer is that, nobody wants another login and that shaped the roadmap for a year.

Written by the Lattice team in Bilbao. Questions? Get in touch.