2026-07-06 · 7 min read

From pilot to plant: a 35-week timeline

Looking at the numbers, the hard part is not the software but the handover and that shaped the roadmap for a year. By the second quarter, mobile access changes who actually enters the data and the numbers bear it out. When the pilot started in Nantes, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Most teams we meet, history matters more than dashboards when something goes wrong and the numbers bear it out. For mid-market manufacturers in particular, asset tracking is a people problem wearing a software costume so the mobile app came first.

Once the first rollout is done, history matters more than dashboards when something goes wrong so we start there. If there is one lesson, nobody wants another login and that shaped the roadmap for a year. The honest answer is that, the reporting layer should be boring and the numbers bear it out.

Where the time went

Looking at the numbers, the biggest win is that the group chat goes quiet which is not what the brochure says. By the second quarter, the schedule is only as good as the last update so plan for it. By the second quarter, exceptions are the real workflow which is why the API is documented before the UI. For mid-market manufacturers in particular, nobody wants another login which is not what the brochure says.

By the second quarter, the audit trail pays for itself the first time an inspector asks and that is fine. The honest answer is that, mobile access changes who actually enters the data and it shows up in the churn numbers. By the second quarter, what matters is whether the crew opens it on a Monday morning so the mobile app came first. Most teams we meet, the audit trail pays for itself the first time an inspector asks and that is fine.

In practice, a two-week pilot answers more than a three-month evaluation so we start there. Looking at the numbers, nobody wants another login which is why the API is documented before the UI. By the second quarter, optional fields never get filled in so we start there. When the pilot started in Nantes, optional fields never get filled in which is not what the brochure says. For mid-market manufacturers in particular, the hard part is not the software but the handover 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 is fine. On a typical site, asset tracking is a people problem wearing a software costume so we start there. For mid-market manufacturers in particular, asset tracking is a people problem wearing a software costume and the numbers bear it out. For mid-market manufacturers in particular, the schedule is only as good as the last update 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.

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

Takeaways

What surprised us, nobody wants another login so the mobile app came first. What surprised us, mobile access changes who actually enters the data and the numbers bear it out. On the floor, mobile access changes who actually enters the data and asset tracking is no exception.

When the pilot started in Nantes, integrations are where budgets go to die so plan for it. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation so plan for it. Most teams we meet, the handover from the old system is where projects stall so the mobile app came first. Looking at the numbers, the biggest win is that the group chat goes quiet and that is fine.

What surprised us, a two-week pilot answers more than a three-month evaluation so the mobile app came first. On a typical site, the reporting layer should be boring which is why EmberCore is built the way it is. When the pilot started in Nantes, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. On the floor, optional fields never get filled in and it rarely takes more than a week. By the second quarter, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Looking at the numbers, the reporting layer should be boring and that is fine.

Written by the EmberCore team in Nantes. Questions? Get in touch.