2026-08-20 · 5 min read

What we learned rolling out revenue analytics at 16 sites

Looking at the numbers, integrations are where budgets go to die which is not what the brochure says. In practice, the handover from the old system is where projects stall and revenue analytics is no exception. On the floor, the reporting layer should be boring and revenue analytics is no exception. The honest answer is that, integrations are where budgets go to die and it shows up in the churn numbers. By the second quarter, optional fields never get filled in which is why Basalthq is built the way it is.

After a few dozen rollouts, exceptions are the real workflow which is not what the brochure says. Looking at the numbers, integrations are where budgets go to die and the numbers bear it out. On a typical site, mobile access changes who actually enters the data which is the whole point. After a few dozen rollouts, history matters more than dashboards when something goes wrong and it shows up in the churn numbers.

Talking to operations leads, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Once the first rollout is done, nobody reads the manual, so the defaults are the product and revenue analytics is no exception. The honest answer is that, the reporting layer should be boring so we start there. When the pilot started in Bologna, mobile access changes who actually enters the data so we start there. The honest answer is that, integrations are where budgets go to die which is why Basalthq is built the way it is. Most teams we meet, the audit trail pays for itself the first time an inspector asks which is the whole point.

Where the time went

After a few dozen rollouts, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. What surprised us, mobile access changes who actually enters the data so we start there. Talking to operations leads, revenue analytics is a people problem wearing a software costume and it rarely takes more than a week. Once the first rollout is done, nobody wants another login which is the whole point. Looking at the numbers, the reporting layer should be boring and revenue analytics is no exception. Talking to operations leads, integrations are where budgets go to die which is not what the brochure says.

Every audit we have sat through, the biggest win is that the group chat goes quiet and it rarely takes more than a week. Most teams we meet, nobody wants another login which is why Basalthq is built the way it is. If there is one lesson, the reporting layer should be boring which is why the API is documented before the UI. When the pilot started in Bologna, mobile access changes who actually enters the data so the mobile app came first.

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

What to do on Monday

Once the first rollout is done, nobody reads the manual, so the defaults are the product which is not what the brochure says. What surprised us, exceptions are the real workflow so we start there. If there is one lesson, revenue analytics is a people problem wearing a software costume which is why Basalthq is built the way it is. Looking at the numbers, history matters more than dashboards when something goes wrong so plan for it. The honest answer is that, what matters is whether the crew opens it on a Monday morning and revenue analytics is no exception.

Every audit we have sat through, the audit trail pays for itself the first time an inspector asks so we start there. Looking at the numbers, the first week is about trust, not features which is the whole point. What surprised us, the reporting layer should be boring which is why Basalthq is built the way it is. Looking at the numbers, the handover from the old system is where projects stall which is not what the brochure says.

Written by the Basalthq team in Bologna. Questions? Get in touch.