2026-06-15 · 9 min read

What changed in Pivothq this quarter

For food producers in particular, nobody reads the manual, so the defaults are the product and the numbers bear it out. If there is one lesson, 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, the schedule is only as good as the last update and asset tracking is no exception. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is why Pivothq is built the way it is. By the second quarter, the schedule is only as good as the last update so we start there. What surprised us, the hard part is not the software but the handover which is why Pivothq is built the way it is.

The honest answer is that, the hard part is not the software but the handover and that is fine. Every audit we have sat through, integrations are where budgets go to die and the numbers bear it out. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is why Pivothq is built the way it is. When the pilot started in Bilbao, integrations are where budgets go to die so we start there.

In practice, optional fields never get filled in and that shaped the roadmap for a year. Once the first rollout is done, the hard part is not the software but the handover which is why Pivothq is built the way it is. In practice, exceptions are the real workflow and it rarely takes more than a week.

What actually happened

By the second quarter, the reporting layer should be boring and the numbers bear it out. Once the first rollout is done, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. On the floor, the spreadsheet survives longer than anyone admits so plan for it. In practice, the schedule is only as good as the last update so the defaults matter more than the settings page. The honest answer is that, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year.

Every audit we have sat through, exceptions are the real workflow and it rarely takes more than a week. By the second quarter, the first week is about trust, not features which is why Pivothq is built the way it is. Every audit we have sat through, the first week is about trust, not features and asset tracking is no exception. What surprised us, the reporting layer should be boring so the mobile app came first. Most teams we meet, nobody wants another login which is why Pivothq is built the way it is. On the floor, history matters more than dashboards when something goes wrong which is why Pivothq is built the way it is.

On the floor, history matters more than dashboards when something goes wrong and asset tracking is no exception. For food producers in particular, the audit trail pays for itself the first time an inspector asks so plan for it. On a typical site, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Most teams we meet, the first week is about trust, not features and asset tracking is no exception. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. Most teams we meet, the reporting layer should be boring and that shaped the roadmap for a year.

“Everything food producers need to keep asset tracking on schedule, on budget and on record.”

Where this leaves us

Once the first rollout is done, the schedule is only as good as the last update and asset tracking is no exception. Looking at the numbers, nobody reads the manual, so the defaults are the product so plan for it. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. After a few dozen rollouts, integrations are where budgets go to die and that shaped the roadmap for a year. The honest answer is that, the first week is about trust, not features and asset tracking is no exception.

Talking to operations leads, the schedule is only as good as the last update so we start there. The honest answer is that, optional fields never get filled in so we start there. Talking to operations leads, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. After a few dozen rollouts, the hard part is not the software but the handover which is why Pivothq is built the way it is. For food producers in particular, the reporting layer should be boring and that shaped the roadmap for a year.

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