2026-09-04 · 8 min read

Notes from Bologna: running the same day twice

Every audit we have sat through, revenue analytics is a people problem wearing a software costume and the numbers bear it out. Most teams we meet, the hard part is not the software but the handover so the mobile app came first. The honest answer is that, what matters is whether the crew opens it on a Monday morning which is the whole point. When the pilot started in Bologna, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year.

Every audit we have sat through, the schedule is only as good as the last update so the mobile app came first. On a typical site, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. In practice, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. In practice, the schedule is only as good as the last update and that shaped the roadmap for a year.

What we would do differently

When the pilot started in Bologna, optional fields never get filled in which is not what the brochure says. By the second quarter, the spreadsheet survives longer than anyone admits which is the whole point. Once the first rollout is done, the reporting layer should be boring so we start there. On the floor, nobody reads the manual, so the defaults are the product which is why Basalthq is built the way it is.

Once the first rollout is done, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. On the floor, the reporting layer should be boring which is why the API is documented before the UI. Every audit we have sat through, the first week is about trust, not features so plan for it. Looking at the numbers, revenue analytics is a people problem wearing a software costume and the numbers bear it out.

“Replace the spreadsheet, the whiteboard and the group chat with one workspace your team will actually open.”

What to do on Monday

After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so we start there. Every audit we have sat through, mobile access changes who actually enters the data so plan for it. Looking at the numbers, revenue analytics is a people problem wearing a software costume and revenue analytics is no exception. In practice, revenue analytics is a people problem wearing a software costume so plan for it. The honest answer is that, optional fields never get filled in so plan for it. The honest answer is that, the audit trail pays for itself the first time an inspector asks which is the whole point.

In practice, what matters is whether the crew opens it on a Monday morning which is why Basalthq is built the way it is. On a typical site, the handover from the old system is where projects stall and it rarely takes more than a week. On the floor, what matters is whether the crew opens it on a Monday morning which is why Basalthq is built the way it is. Looking at the numbers, history matters more than dashboards when something goes wrong which is not what the brochure says. The honest answer is that, history matters more than dashboards when something goes wrong which is the whole point. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

Written by the Basalthq team in Bologna. Questions? Get in touch.