2026-06-07 · 6 min read

From pilot to plant: a 23-week timeline

By the second quarter, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Every audit we have sat through, history matters more than dashboards when something goes wrong which is why TesseraRidge is built the way it is. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and that is fine. Talking to operations leads, the first week is about trust, not features so we start there.

For logistics teams in particular, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. Looking at the numbers, nobody reads the manual, so the defaults are the product which is why TesseraRidge is built the way it is. Once the first rollout is done, mobile access changes who actually enters the data so the defaults matter more than the settings page.

When the pilot started in Bilbao, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. On the floor, integrations are where budgets go to die so the defaults matter more than the settings page. When the pilot started in Bilbao, history matters more than dashboards when something goes wrong so plan for it. Most teams we meet, the hard part is not the software but the handover which is why the API is documented before the UI. In practice, the hard part is not the software but the handover which is why TesseraRidge is built the way it is.

The part nobody plans for

Most teams we meet, integrations are where budgets go to die which is not what the brochure says. Most teams we meet, revenue analytics is a people problem wearing a software costume and that is fine. In practice, exceptions are the real workflow which is why TesseraRidge is built the way it is. Most teams we meet, nobody wants another login and it shows up in the churn numbers. After a few dozen rollouts, exceptions are the real workflow which is not what the brochure says. Looking at the numbers, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI.

For logistics teams in particular, the spreadsheet survives longer than anyone admits and it shows up in the churn numbers. Once the first rollout is done, revenue analytics is a people problem wearing a software costume and it shows up in the churn numbers. Every audit we have sat through, the hard part is not the software but the handover so the defaults matter more than the settings page. Most teams we meet, history matters more than dashboards when something goes wrong so we start there. Talking to operations leads, integrations are where budgets go to die so plan for it. On the floor, the first week is about trust, not features so the defaults matter more than the settings page.

Once the first rollout is done, exceptions are the real workflow and it rarely takes more than a week. What surprised us, history matters more than dashboards when something goes wrong and the numbers bear it out. After a few dozen rollouts, nobody wants another login which is why TesseraRidge is built the way it is.

“Plan, dispatch and reconcile in one place. TesseraRidge connects to the systems you already run and stays out of the way.”

What to do on Monday

The honest answer is that, mobile access changes who actually enters the data so we start there. For logistics teams in particular, revenue analytics is a people problem wearing a software costume and revenue analytics is no exception. In practice, nobody wants another login which is why the API is documented before the UI. In practice, the reporting layer should be boring so we start there. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is not what the brochure says.

In practice, the first week is about trust, not features which is why TesseraRidge is built the way it is. In practice, the audit trail pays for itself the first time an inspector asks which is the whole point. Talking to operations leads, revenue analytics is a people problem wearing a software costume so the mobile app came first.

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. After a few dozen rollouts, optional fields never get filled in so plan for it. On the floor, the schedule is only as good as the last update which is why TesseraRidge is built the way it is. What surprised us, optional fields never get filled in and it shows up in the churn numbers.

Written by the TesseraRidge team in Bilbao. Questions? Get in touch.