2026-07-14 · 5 min read

What we learned rolling out revenue analytics at 35 sites

By the second quarter, the handover from the old system is where projects stall and the numbers bear it out. Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. After a few dozen rollouts, integrations are where budgets go to die which is the whole point. For insurance brokers in particular, the biggest win is that the group chat goes quiet and that is fine. If there is one lesson, integrations are where budgets go to die which is the whole point.

What surprised us, history matters more than dashboards when something goes wrong which is the whole point. On a typical site, the handover from the old system is where projects stall so plan for it. What surprised us, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. When the pilot started in Leeds, nobody reads the manual, so the defaults are the product and the numbers bear it out. For insurance brokers in particular, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page.

What we would do differently

If there is one lesson, the first week is about trust, not features which is why the API is documented before the UI. After a few dozen rollouts, the schedule is only as good as the last update so the defaults matter more than the settings page. For insurance brokers in particular, nobody wants another login and it rarely takes more than a week. On the floor, mobile access changes who actually enters the data and the numbers bear it out. For insurance brokers in particular, the first week is about trust, not features and it rarely takes more than a week.

On a typical site, history matters more than dashboards when something goes wrong which is not what the brochure says. In practice, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Talking to operations leads, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so we start there. Talking to operations leads, integrations are where budgets go to die so the defaults matter more than the settings page.

Looking at the numbers, integrations are where budgets go to die and revenue analytics is no exception. In practice, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and revenue analytics is no exception. Every audit we have sat through, the reporting layer should be boring so plan for it.

On the floor, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. By the second quarter, what matters is whether the crew opens it on a Monday morning which is why Meridianify is built the way it is. For insurance brokers in particular, nobody reads the manual, so the defaults are the product and the numbers bear it out. On a typical site, the audit trail pays for itself the first time an inspector asks so plan for it.

“Meridianify gives insurance brokers a single, dependable view of revenue analytics - from first request to signed-off report.”

Takeaways

Looking at the numbers, integrations are where budgets go to die which is not what the brochure says. Most teams we meet, revenue analytics is a people problem wearing a software costume so we start there. Looking at the numbers, the hard part is not the software but the handover so the mobile app came first. On the floor, history matters more than dashboards when something goes wrong and the numbers bear it out.

Looking at the numbers, the first week is about trust, not features so the mobile app came first. Every audit we have sat through, exceptions are the real workflow so the defaults matter more than the settings page. On a typical site, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI.

By the second quarter, exceptions are the real workflow which is not what the brochure says. By the second quarter, the first week is about trust, not features and that is fine. Looking at the numbers, the spreadsheet survives longer than anyone admits so we start there.

Written by the Meridianify team in Leeds. Questions? Get in touch.