2026-08-22 · 7 min read

From pilot to plant: a 7-week timeline

Talking to operations leads, nobody wants another login which is why QuillFlow is built the way it is. On the floor, optional fields never get filled in and that shaped the roadmap for a year. For retail chains in particular, nobody reads the manual, so the defaults are the product which is why QuillFlow is built the way it is.

After a few dozen rollouts, nobody wants another login and invoice reconciliation is no exception. When the pilot started in Porto, the reporting layer should be boring and that is fine. If there is one lesson, integrations are where budgets go to die which is not what the brochure says. Once the first rollout is done, the reporting layer should be boring and that is fine. Looking at the numbers, optional fields never get filled in and that is fine.

On a typical site, the first week is about trust, not features which is the whole point. Every audit we have sat through, the handover from the old system is where projects stall so we start there. On a typical site, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

Where the time went

For retail chains in particular, mobile access changes who actually enters the data and that shaped the roadmap for a year. Most teams we meet, nobody wants another login which is why QuillFlow is built the way it is. In practice, optional fields never get filled in and that is fine. Looking at the numbers, nobody wants another login and it shows up in the churn numbers. For retail chains in particular, mobile access changes who actually enters the data so we start there.

What surprised us, nobody reads the manual, so the defaults are the product which is why QuillFlow is built the way it is. If there is one lesson, the handover from the old system is where projects stall so the defaults matter more than the settings page. For retail chains in particular, invoice reconciliation is a people problem wearing a software costume and it shows up in the churn numbers. On a typical site, the schedule is only as good as the last update and that shaped the roadmap for a year.

“Everything retail chains need to keep invoice reconciliation on schedule, on budget and on record.”

What to do on Monday

What surprised us, the first week is about trust, not features so the defaults matter more than the settings page. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is why QuillFlow is built the way it is. On the floor, optional fields never get filled in and invoice reconciliation is no exception. Once the first rollout is done, optional fields never get filled in so the mobile app came first.

What surprised us, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation so the mobile app came first. After a few dozen rollouts, the first week is about trust, not features so the mobile app came first. On the floor, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

Written by the QuillFlow team in Porto. Questions? Get in touch.