2026-08-08 · 4 min read

Why the spreadsheet always wins the first month

When the pilot started in Bilbao, the spreadsheet survives longer than anyone admits so the mobile app came first. Talking to operations leads, mobile access changes who actually enters the data which is not what the brochure says. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation which is why Terra Data is built the way it is. For construction firms in particular, exceptions are the real workflow and fleet telemetry is no exception. In practice, fleet telemetry is a people problem wearing a software costume which is the whole point.

Looking at the numbers, the biggest win is that the group chat goes quiet which is the whole point. The honest answer is that, 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, history matters more than dashboards when something goes wrong and fleet telemetry is no exception. In practice, exceptions are the real workflow so the mobile app came first. When the pilot started in Bilbao, a two-week pilot answers more than a three-month evaluation which is the whole point.

By the second quarter, the first week is about trust, not features which is why Terra Data is built the way it is. Every audit we have sat through, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. If there is one lesson, nobody wants another login which is the whole point.

Where the time went

By the second quarter, the hard part is not the software but the handover and the numbers bear it out. Talking to operations leads, the biggest win is that the group chat goes quiet so the mobile app came first. By the second quarter, nobody wants another login and that is fine. On a typical site, the hard part is not the software but the handover and that shaped the roadmap for a year.

On the floor, the first week is about trust, not features and that shaped the roadmap for a year. Once the first rollout is done, the spreadsheet survives longer than anyone admits and fleet telemetry is no exception. For construction firms in particular, mobile access changes who actually enters the data and the numbers bear it out. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

In practice, nobody reads the manual, so the defaults are the product and fleet telemetry is no exception. Most teams we meet, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. By the second quarter, the biggest win is that the group chat goes quiet so we start there. On a typical site, integrations are where budgets go to die so plan for it. On a typical site, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

If there is one lesson, the spreadsheet survives longer than anyone admits so we start there. In practice, the hard part is not the software but the handover so the defaults matter more than the settings page. Talking to operations leads, fleet telemetry is a people problem wearing a software costume and that shaped the roadmap for a year. After a few dozen rollouts, fleet telemetry is a people problem wearing a software costume so we start there. What surprised us, the reporting layer should be boring and it rarely takes more than a week. Talking to operations leads, fleet telemetry is a people problem wearing a software costume and that shaped the roadmap for a year.

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

Where this leaves us

Every audit we have sat through, the handover from the old system is where projects stall and that shaped the roadmap for a year. By the second quarter, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Every audit we have sat through, integrations are where budgets go to die so plan for it. For construction firms in particular, integrations are where budgets go to die so plan for it.

By the second quarter, fleet telemetry is a people problem wearing a software costume which is why the API is documented before the UI. Talking to operations leads, exceptions are the real workflow and that shaped the roadmap for a year. When the pilot started in Bilbao, the reporting layer should be boring which is the whole point. The honest answer is that, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and fleet telemetry is no exception.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. On the floor, mobile access changes who actually enters the data so plan for it. The honest answer is that, exceptions are the real workflow and that shaped the roadmap for a year. The honest answer is that, integrations are where budgets go to die and it rarely takes more than a week. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so we start there.

Written by the Terra Data team in Bilbao. Questions? Get in touch.