2026-07-14 · 5 min read

Notes from Bologna: running the same day twice

By the second quarter, what matters is whether the crew opens it on a Monday morning which is the whole point. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that is fine. On the floor, the first week is about trust, not features and it rarely takes more than a week.

By the second quarter, integrations are where budgets go to die and that shaped the roadmap for a year. After a few dozen rollouts, the hard part is not the software but the handover so plan for it. On a typical site, nobody wants another login and that is fine. On a typical site, a two-week pilot answers more than a three-month evaluation which is the whole point.

What we would do differently

The honest answer is that, nobody wants another login which is not what the brochure says. When the pilot started in Bologna, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year. For construction firms in particular, the spreadsheet survives longer than anyone admits and sample tracking is no exception. On the floor, exceptions are the real workflow which is not what the brochure says. Once the first rollout is done, the handover from the old system is where projects stall and that is fine.

The honest answer is that, the reporting layer should be boring and it rarely takes more than a week. By the second quarter, the schedule is only as good as the last update and it shows up in the churn numbers. In practice, nobody reads the manual, so the defaults are the product and that is fine. The honest answer is that, mobile access changes who actually enters the data which is why Harbor Point is built the way it is. When the pilot started in Bologna, optional fields never get filled in so the defaults matter more than the settings page.

“Harbor Point gives construction firms a single, dependable view of sample tracking - from first request to signed-off report.”

What to do on Monday

In practice, mobile access changes who actually enters the data which is why Harbor Point is built the way it is. Most teams we meet, sample tracking is a people problem wearing a software costume which is why the API is documented before the UI. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. For construction firms in particular, optional fields never get filled in which is why Harbor Point is built the way it is. What surprised us, integrations are where budgets go to die and the numbers bear it out.

When the pilot started in Bologna, sample tracking is a people problem wearing a software costume and that is fine. For construction firms in particular, the spreadsheet survives longer than anyone admits which is not what the brochure says. Looking at the numbers, history matters more than dashboards when something goes wrong so the mobile app came first.

Written by the Harbor Point team in Bologna. Questions? Get in touch.