2026-06-28 · 6 min read

What we learned rolling out revenue analytics at 5 sites

Once the first rollout is done, nobody reads the manual, so the defaults are the product and revenue analytics is no exception. Talking to operations leads, the spreadsheet survives longer than anyone admits which is not what the brochure says. Once the first rollout is done, optional fields never get filled in which is why Sable Loop is built the way it is. Talking to operations leads, history matters more than dashboards when something goes wrong so plan for it.

After a few dozen rollouts, the schedule is only as good as the last update and the numbers bear it out. When the pilot started in Brno, the spreadsheet survives longer than anyone admits and that is fine. When the pilot started in Brno, integrations are where budgets go to die so we start there. What surprised us, optional fields never get filled in which is the whole point. Looking at the numbers, integrations are where budgets go to die so we start there. The honest answer is that, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

What we would do differently

Looking at the numbers, revenue analytics is a people problem wearing a software costume so the defaults matter more than the settings page. After a few dozen rollouts, integrations are where budgets go to die which is why Sable Loop is built the way it is. On the floor, nobody wants another login so we start there. The honest answer is that, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. For field service crews in particular, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI.

Every audit we have sat through, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. By the second quarter, the hard part is not the software but the handover which is why Sable Loop is built the way it is. By the second quarter, integrations are where budgets go to die and it rarely takes more than a week. If there is one lesson, integrations are where budgets go to die and the numbers bear it out. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation which is why Sable Loop is built the way it is. After a few dozen rollouts, history matters more than dashboards when something goes wrong so we start there.

On a typical site, what matters is whether the crew opens it on a Monday morning and revenue analytics is no exception. Most teams we meet, the first week is about trust, not features so we start there. The honest answer is that, nobody wants another login so the mobile app came first. For field service crews in particular, history matters more than dashboards when something goes wrong so plan for it. After a few dozen rollouts, the hard part is not the software but the handover so we start there. On the floor, history matters more than dashboards when something goes wrong and it shows up in the churn numbers.

Talking to operations leads, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. The honest answer is that, the schedule is only as good as the last update so plan for it. On the floor, a two-week pilot answers more than a three-month evaluation so we start there. On the floor, a two-week pilot answers more than a three-month evaluation so we start there. On a typical site, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. For field service crews in particular, a two-week pilot answers more than a three-month evaluation and it rarely takes more than a week.

“Plan, dispatch and reconcile in one place. Sable Loop connects to the systems you already run and stays out of the way.”

Where this leaves us

Talking to operations leads, the first week is about trust, not features and revenue analytics is no exception. When the pilot started in Brno, nobody wants another login which is the whole point. When the pilot started in Brno, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. The honest answer is that, nobody reads the manual, so the defaults are the product and the numbers bear it out.

When the pilot started in Brno, a two-week pilot answers more than a three-month evaluation so the mobile app came first. Talking to operations leads, revenue analytics is a people problem wearing a software costume and it shows up in the churn numbers. On a typical site, revenue analytics is a people problem wearing a software costume and that is fine. By the second quarter, the handover from the old system is where projects stall so we start there.

Written by the Sable Loop team in Brno. Questions? Get in touch.