2026-09-07 · 6 min read

From pilot to plant: a 4-week timeline

After a few dozen rollouts, nobody wants another login and it shows up in the churn numbers. If there is one lesson, the first week is about trust, not features which is the whole point. Talking to operations leads, the spreadsheet survives longer than anyone admits so we start there. By the second quarter, mobile access changes who actually enters the data and that shaped the roadmap for a year. When the pilot started in Leeds, the hard part is not the software but the handover so plan for it. In practice, the first week is about trust, not features which is why the API is documented before the UI.

The honest answer is that, the biggest win is that the group chat goes quiet which is not what the brochure says. By the second quarter, the spreadsheet survives longer than anyone admits which is not what the brochure says. On the floor, the first week is about trust, not features and the numbers bear it out. If there is one lesson, the reporting layer should be boring and that shaped the roadmap for a year.

What actually happened

On a typical site, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. On the floor, the schedule is only as good as the last update so the defaults matter more than the settings page. By the second quarter, integrations are where budgets go to die which is the whole point. Talking to operations leads, the biggest win is that the group chat goes quiet and that is fine.

In practice, exceptions are the real workflow so plan for it. After a few dozen rollouts, integrations are where budgets go to die so the mobile app came first. For construction firms in particular, exceptions are the real workflow which is not what the brochure says. What surprised us, integrations are where budgets go to die which is why Pivot Labs is built the way it is. If there is one lesson, mobile access changes who actually enters the data which is why the API is documented before the UI.

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

Takeaways

The honest answer is that, the first week is about trust, not features and that shaped the roadmap for a year. After a few dozen rollouts, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. Talking to operations leads, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. By the second quarter, the reporting layer should be boring so the mobile app came first.

The honest answer is that, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. For construction firms in particular, the schedule is only as good as the last update so we start there. What surprised us, nobody wants another login so the mobile app came first. Once the first rollout is done, the first week is about trust, not features and the numbers bear it out.

Written by the Pivot Labs team in Leeds. Questions? Get in touch.