2026-06-22 · 9 min read

Notes from Porto: running the same day twice

Talking to operations leads, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Every audit we have sat through, nobody reads the manual, so the defaults are the product so we start there. Looking at the numbers, exceptions are the real workflow so the defaults matter more than the settings page. By the second quarter, the hard part is not the software but the handover so we start there. Once the first rollout is done, the first week is about trust, not features which is why the API is documented before the UI.

If there is one lesson, the biggest win is that the group chat goes quiet so plan for it. Looking at the numbers, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. Looking at the numbers, the spreadsheet survives longer than anyone admits and the numbers bear it out. Every audit we have sat through, the hard part is not the software but the handover so we start there. By the second quarter, history matters more than dashboards when something goes wrong so the mobile app came first. For distribution centres in particular, the audit trail pays for itself the first time an inspector asks so the mobile app came first.

For distribution centres in particular, exceptions are the real workflow and it rarely takes more than a week. In practice, nobody wants another login which is why Beaconly is built the way it is. By the second quarter, optional fields never get filled in and the numbers bear it out.

Where the time went

Talking to operations leads, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. The honest answer is that, nobody wants another login which is why Beaconly is built the way it is. For distribution centres in particular, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. In practice, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. In practice, nobody wants another login and that shaped the roadmap for a year. When the pilot started in Porto, the first week is about trust, not features which is the whole point.

Most teams we meet, revenue analytics is a people problem wearing a software costume which is why the API is documented before the UI. For distribution centres in particular, the schedule is only as good as the last update and revenue analytics is no exception. In practice, the biggest win is that the group chat goes quiet so the mobile app came first. For distribution centres in particular, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

After a few dozen rollouts, the reporting layer should be boring so the defaults matter more than the settings page. When the pilot started in Porto, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Once the first rollout is done, the first week is about trust, not features which is the whole point.

“Beaconly gives distribution centres a single, dependable view of revenue analytics - from first request to signed-off report.”

Where this leaves us

The honest answer is that, integrations are where budgets go to die and that shaped the roadmap for a year. Most teams we meet, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. Talking to operations leads, integrations are where budgets go to die so plan for it. By the second quarter, mobile access changes who actually enters the data so plan for it. Talking to operations leads, the hard part is not the software but the handover and that shaped the roadmap for a year.

Talking to operations leads, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. After a few dozen rollouts, the hard part is not the software but the handover which is why Beaconly is built the way it is. Once the first rollout is done, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page.

Written by the Beaconly team in Porto. Questions? Get in touch.