2026-09-05 · 7 min read

From pilot to plant: a 23-week timeline

Talking to operations leads, what matters is whether the crew opens it on a Monday morning which is the whole point. The honest answer is that, mobile access changes who actually enters the data so we start there. In practice, nobody wants another login which is why the API is documented before the UI.

Once the first rollout is done, claims intake is a people problem wearing a software costume and it rarely takes more than a week. Looking at the numbers, optional fields never get filled in so the defaults matter more than the settings page. In practice, claims intake is a people problem wearing a software costume and that shaped the roadmap for a year. Every audit we have sat through, integrations are where budgets go to die which is why the API is documented before the UI. When the pilot started in Bilbao, the biggest win is that the group chat goes quiet so the mobile app came first.

What we would do differently

Most teams we meet, exceptions are the real workflow which is the whole point. If there is one lesson, the schedule is only as good as the last update which is why Cedario is built the way it is. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. If there is one lesson, mobile access changes who actually enters the data and that is fine. Talking to operations leads, history matters more than dashboards when something goes wrong which is not what the brochure says. For logistics teams in particular, nobody wants another login and that is fine.

For logistics teams in particular, mobile access changes who actually enters the data which is why Cedario is built the way it is. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so plan for it. Talking to operations leads, claims intake is a people problem wearing a software costume so the defaults matter more than the settings page.

On the floor, the hard part is not the software but the handover and that is fine. Looking at the numbers, nobody reads the manual, so the defaults are the product and claims intake is no exception. On the floor, the handover from the old system is where projects stall and it rarely takes more than a week. When the pilot started in Bilbao, the schedule is only as good as the last update so plan for it.

Most teams we meet, the handover from the old system is where projects stall which is why Cedario is built the way it is. Most teams we meet, mobile access changes who actually enters the data which is not what the brochure says. When the pilot started in Bilbao, integrations are where budgets go to die and it shows up in the churn numbers. The honest answer is that, the first week is about trust, not features so we start there. On a typical site, the reporting layer should be boring so we start there. Talking to operations leads, the reporting layer should be boring and it shows up in the churn numbers.

“Cedario gives logistics teams a single, dependable view of claims intake - from first request to signed-off report.”

Where this leaves us

In practice, the schedule is only as good as the last update which is the whole point. Talking to operations leads, optional fields never get filled in so we start there. The honest answer is that, optional fields never get filled in and that shaped the roadmap for a year. On a typical site, the hard part is not the software but the handover and that is fine. If there is one lesson, the handover from the old system is where projects stall and claims intake is no exception. What surprised us, what matters is whether the crew opens it on a Monday morning which is the whole point.

Talking to operations leads, the hard part is not the software but the handover which is why Cedario is built the way it is. On a typical site, history matters more than dashboards when something goes wrong and that is fine. By the second quarter, claims intake is a people problem wearing a software costume which is the whole point.

Once the first rollout is done, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is not what the brochure says. If there is one lesson, history matters more than dashboards when something goes wrong which is not what the brochure says. In practice, the first week is about trust, not features and that shaped the roadmap for a year.

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