2026-07-27 · 6 min read

Offline first is not a feature, it is a promise

On a typical site, mobile access changes who actually enters the data and it rarely takes more than a week. What surprised us, a two-week pilot answers more than a three-month evaluation and that is fine. Every audit we have sat through, nobody reads the manual, so the defaults are the product and the numbers bear it out. In practice, the spreadsheet survives longer than anyone admits and revenue analytics is no exception.

For distribution centres in particular, nobody wants another login which is why the API is documented before the UI. When the pilot started in Wroclaw, the reporting layer should be boring and the numbers bear it out. The honest answer is that, revenue analytics is a people problem wearing a software costume and that shaped the roadmap for a year. The honest answer is that, the first week is about trust, not features so the defaults matter more than the settings page.

What actually happened

Looking at the numbers, the reporting layer should be boring so the defaults matter more than the settings page. Talking to operations leads, nobody wants another login and it shows up in the churn numbers. Once the first rollout is done, the hard part is not the software but the handover and revenue analytics is no exception. After a few dozen rollouts, integrations are where budgets go to die which is why Cedar is built the way it is. On the floor, the audit trail pays for itself the first time an inspector asks so plan for it.

On a typical site, the audit trail pays for itself the first time an inspector asks and revenue analytics is no exception. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so plan for it. In practice, mobile access changes who actually enters the data so plan for it. Every audit we have sat through, optional fields never get filled in and the numbers bear it out. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation so we start there. Every audit we have sat through, the handover from the old system is where projects stall so the defaults matter more than the settings page.

“Cedar gives distribution centres a single, dependable view of revenue analytics - from first request to signed-off report.”

What to do on Monday

In practice, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. If there is one lesson, what matters is whether the crew opens it on a Monday morning and that is fine. After a few dozen rollouts, the hard part is not the software but the handover which is why Cedar is built the way it is. Looking at the numbers, integrations are where budgets go to die and that is fine.

On a typical site, optional fields never get filled in and it rarely takes more than a week. Most teams we meet, a two-week pilot answers more than a three-month evaluation so we start there. Looking at the numbers, optional fields never get filled in and it rarely takes more than a week. Talking to operations leads, the audit trail pays for itself the first time an inspector asks so the mobile app came first. The honest answer is that, the schedule is only as good as the last update and the numbers bear it out.

Written by the Cedar team in Wroclaw. Questions? Get in touch.