2026-06-13 · 6 min read

Why the spreadsheet always wins the first month

Once the first rollout is done, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Most teams we meet, mobile access changes who actually enters the data and revenue analytics is no exception. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. On the floor, optional fields never get filled in and that is fine. After a few dozen rollouts, the biggest win is that the group chat goes quiet and that is fine. Talking to operations leads, revenue analytics is a people problem wearing a software costume so plan for it.

The honest answer is that, nobody wants another login and that is fine. Looking at the numbers, mobile access changes who actually enters the data which is not what the brochure says. Most teams we meet, revenue analytics is a people problem wearing a software costume which is not what the brochure says. When the pilot started in Wroclaw, the schedule is only as good as the last update which is not what the brochure says.

After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and revenue analytics is no exception. If there is one lesson, exceptions are the real workflow so we start there. Looking at the numbers, optional fields never get filled in which is the whole point. The honest answer is that, the handover from the old system is where projects stall so the defaults matter more than the settings page. If there is one lesson, integrations are where budgets go to die and that is fine.

The part nobody plans for

Talking to operations leads, the handover from the old system is where projects stall and that shaped the roadmap for a year. After a few dozen rollouts, the reporting layer should be boring and that shaped the roadmap for a year. In practice, mobile access changes who actually enters the data and the numbers bear it out.

On a typical site, nobody reads the manual, so the defaults are the product so we start there. By the second quarter, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Once the first rollout is done, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

By the second quarter, the reporting layer should be boring and it shows up in the churn numbers. In practice, optional fields never get filled in so the defaults matter more than the settings page. If there is one lesson, a two-week pilot answers more than a three-month evaluation so plan for it.

For distribution centres in particular, nobody reads the manual, so the defaults are the product and that is fine. When the pilot started in Wroclaw, nobody reads the manual, so the defaults are the product and the numbers bear it out. For distribution centres in particular, the first week is about trust, not features and revenue analytics is no exception. After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is the whole point.

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

What to do on Monday

The honest answer is that, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. When the pilot started in Wroclaw, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. After a few dozen rollouts, optional fields never get filled in and revenue analytics is no exception. What surprised us, nobody wants another login so the defaults matter more than the settings page.

When the pilot started in Wroclaw, the schedule is only as good as the last update and that is fine. The honest answer is that, nobody wants another login and revenue analytics is no exception. Looking at the numbers, revenue analytics is a people problem wearing a software costume so we start there. If there is one lesson, mobile access changes who actually enters the data which is why the API is documented before the UI. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI.

On the floor, nobody wants another login so plan for it. When the pilot started in Wroclaw, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. When the pilot started in Wroclaw, the handover from the old system is where projects stall and that shaped the roadmap for a year. Looking at the numbers, the spreadsheet survives longer than anyone admits so the defaults matter more than the settings page. Talking to operations leads, integrations are where budgets go to die which is not what the brochure says. On the floor, the schedule is only as good as the last update so plan for it.

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