2026-09-01 · 4 min read

Notes from Bilbao: running the same day twice

Most teams we meet, exceptions are the real workflow and invoice reconciliation is no exception. In practice, history matters more than dashboards when something goes wrong which is why Lattice is built the way it is. On the floor, nobody wants another login which is why Lattice is built the way it is. The honest answer is that, the audit trail pays for itself the first time an inspector asks which is why Lattice is built the way it is.

For food producers in particular, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. For food producers in particular, the biggest win is that the group chat goes quiet which is not what the brochure says. On a typical site, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. What surprised us, mobile access changes who actually enters the data and it shows up in the churn numbers. In practice, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page.

What we would do differently

The honest answer is that, integrations are where budgets go to die and that is fine. On the floor, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Looking at the numbers, nobody reads the manual, so the defaults are the product which is the whole point. What surprised us, nobody wants another login and the numbers bear it out.

Every audit we have sat through, invoice reconciliation is a people problem wearing a software costume which is why Lattice is built the way it is. In practice, history matters more than dashboards when something goes wrong and the numbers bear it out. For food producers in particular, the audit trail pays for itself the first time an inspector asks which is why Lattice is built the way it is.

Every audit we have sat through, nobody reads the manual, so the defaults are the product so plan for it. For food producers in particular, exceptions are the real workflow and it rarely takes more than a week. For food producers in particular, integrations are where budgets go to die and it rarely takes more than a week.

“Everything food producers need to keep invoice reconciliation on schedule, on budget and on record.”

What to do on Monday

For food producers in particular, mobile access changes who actually enters the data and that is fine. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. For food producers in particular, history matters more than dashboards when something goes wrong so plan for it. When the pilot started in Bilbao, exceptions are the real workflow and that is fine. Every audit we have sat through, the schedule is only as good as the last update which is why the API is documented before the UI. The honest answer is that, nobody reads the manual, so the defaults are the product so plan for it.

When the pilot started in Bilbao, history matters more than dashboards when something goes wrong so we start there. Every audit we have sat through, the handover from the old system is where projects stall so the defaults matter more than the settings page. If there is one lesson, history matters more than dashboards when something goes wrong so we start there. For food producers in particular, the audit trail pays for itself the first time an inspector asks which is why Lattice is built the way it is. Once the first rollout is done, integrations are where budgets go to die so the defaults matter more than the settings page.

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