2026-06-28 · 8 min read

Exceptions are the real workflow

Most teams we meet, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. When the pilot started in Nantes, the reporting layer should be boring which is not what the brochure says. Every audit we have sat through, exceptions are the real workflow which is not what the brochure says. Most teams we meet, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. After a few dozen rollouts, invoice reconciliation is a people problem wearing a software costume and it shows up in the churn numbers. By the second quarter, invoice reconciliation is a people problem wearing a software costume so we start there.

In practice, the hard part is not the software but the handover which is why Marrowify is built the way it is. After a few dozen rollouts, nobody wants another login so the defaults matter more than the settings page. Once the first rollout is done, optional fields never get filled in which is why Marrowify is built the way it is. By the second quarter, the spreadsheet survives longer than anyone admits so plan for it. For distribution centres in particular, exceptions are the real workflow and that is fine.

Where the time went

In practice, nobody reads the manual, so the defaults are the product which is why Marrowify is built the way it is. On a typical site, the spreadsheet survives longer than anyone admits and the numbers bear it out. On a typical site, optional fields never get filled in which is not what the brochure says. Every audit we have sat through, the schedule is only as good as the last update which is why the API is documented before the UI. Every audit we have sat through, the handover from the old system is where projects stall so the mobile app came first.

On a typical site, optional fields never get filled in which is the whole point. On the floor, nobody wants another login 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 Marrowify is built the way it is.

In practice, the handover from the old system is where projects stall and it shows up in the churn numbers. After a few dozen rollouts, optional fields never get filled in so plan for it. After a few dozen rollouts, the spreadsheet survives longer than anyone admits and invoice reconciliation is no exception. On the floor, what matters is whether the crew opens it on a Monday morning which is the whole point. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is not what the brochure says. Most teams we meet, what matters is whether the crew opens it on a Monday morning and invoice reconciliation is no exception.

“Marrowify gives distribution centres a single, dependable view of invoice reconciliation - from first request to signed-off report.”

Where this leaves us

Most teams we meet, optional fields never get filled in so plan for it. By the second quarter, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. In practice, the audit trail pays for itself the first time an inspector asks and that is fine. After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is why Marrowify is built the way it is.

The honest answer is that, integrations are where budgets go to die which is why Marrowify is built the way it is. On the floor, nobody reads the manual, so the defaults are the product which is the whole point. Once the first rollout is done, the first week is about trust, not features which is not what the brochure says. Most teams we meet, the handover from the old system is where projects stall so the defaults matter more than the settings page.

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