2026-07-23 · 6 min read

Offline first is not a feature, it is a promise

Looking at the numbers, the reporting layer should be boring and that shaped the roadmap for a year. Once the first rollout is done, the handover from the old system is where projects stall and it rarely takes more than a week. Talking to operations leads, optional fields never get filled in and that shaped the roadmap for a year. Every audit we have sat through, 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, mobile access changes who actually enters the data and the numbers bear it out. When the pilot started in Bilbao, the schedule is only as good as the last update and that is fine.

If there is one lesson, the spreadsheet survives longer than anyone admits and inventory planning is no exception. For mid-market manufacturers in particular, history matters more than dashboards when something goes wrong so we start there. When the pilot started in Bilbao, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers.

What actually happened

What surprised us, the audit trail pays for itself the first time an inspector asks and inventory planning is no exception. After a few dozen rollouts, the reporting layer should be boring which is why Quill is built the way it is. Talking to operations leads, exceptions are the real workflow so the defaults matter more than the settings page.

On the floor, the reporting layer should be boring which is why Quill is built the way it is. On a typical site, the hard part is not the software but the handover and that shaped the roadmap for a year. On a typical site, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

When the pilot started in Bilbao, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Once the first rollout is done, the spreadsheet survives longer than anyone admits and inventory planning is no exception. Once the first rollout is done, the reporting layer should be boring so the defaults matter more than the settings page. After a few dozen rollouts, nobody wants another login which is not what the brochure says. Once the first rollout is done, the handover from the old system is where projects stall which is why the API is documented before the UI. Once the first rollout is done, the schedule is only as good as the last update so we start there.

When the pilot started in Bilbao, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. After a few dozen rollouts, inventory planning is a people problem wearing a software costume so plan for it. If there is one lesson, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. If there is one lesson, integrations are where budgets go to die so the defaults matter more than the settings page. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is why the API is documented before the UI.

“Quill gives mid-market manufacturers a single, dependable view of inventory planning - from first request to signed-off report.”

What to do on Monday

By the second quarter, exceptions are the real workflow and inventory planning is no exception. When the pilot started in Bilbao, the audit trail pays for itself the first time an inspector asks so plan for it. After a few dozen rollouts, optional fields never get filled in so plan for it. Looking at the numbers, the first week is about trust, not features and that shaped the roadmap for a year. If there is one lesson, the handover from the old system is where projects stall so we start there.

For mid-market manufacturers in particular, what matters is whether the crew opens it on a Monday morning so the mobile app came first. What surprised us, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. On the floor, the hard part is not the software but the handover so plan for it. If there is one lesson, the hard part is not the software but the handover which is why Quill is built the way it is. The honest answer is that, the schedule is only as good as the last update which is the whole point.

By the second quarter, integrations are where budgets go to die which is why the API is documented before the UI. By the second quarter, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. In practice, the reporting layer should be boring which is not what the brochure says. When the pilot started in Bilbao, what matters is whether the crew opens it on a Monday morning and that shaped the roadmap for a year.

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