How an HVACR Distributor Replaced Legacy Reporting With Self-Service Analytics

An HVACR distributor runs a large network of independently operated stores across North America. Its reporting ran on a legacy BI stack that still produced reports but could not answer anything new, which left every store owner’s question queued behind someone else’s. OnPoint Insights rebuilt the reporting in Power BI on optimised SQL views, with scheduled refresh from the on-premise databases, so the people running the stores can analyse their own performance.

5 reports replaced the legacy stack

Sales, customer analysis, product analysis, claimbacks and programme insights, rebuilt in Power BI on a modelled and cleansed dataset.

Store owners serve themselves

Independently operated stores analyse their own sales and customer trends rather than requesting a report and waiting for it.

Fast loading, scheduled refresh

Report-specific SQL views and a Power BI Gateway, so on-premise data refreshes on schedule and reports open quickly enough to be used in a conversation.

The problem

The reports still ran. Nobody could ask anything new

Legacy BI fails in a particular way. The existing reports keep working, so nothing looks broken, but every new question becomes a request and every request joins a queue. For a distributor whose stores are independently operated, that queue is the real problem: the person who needs the answer does not work at head office.

Our client’s system lacked the flexibility and visual clarity to keep up with growing data demands, and the performance underneath it was part of the reason. Queries against the on-premise SQL databases were slow, and the data they returned needed work before anyone could rely on it.

What was getting in the way

  • The legacy reports could not support interactive or scalable reporting, so growing data demands had nowhere to go.
  • Queries against the on-premise SQL databases needed optimisation to bring report loading times down.
  • The underlying data needed cleansing, transformation and modelling work before it could deliver reliable insight.
  • Sales, operations and customer analysis teams each needed dashboards built around their own decisions, not one shared report.

Our approach

Fix the data and the queries, then design the dashboards

What we found

Nothing in the old system was slow because of its visuals. The constraint was the queries and the state of the data behind them, so the first work was in SQL rather than in Power BI. A dashboard built on a slow, inconsistent source is just a faster way to arrive at the wrong number.

What we did

Agreed what each group actually needed. Stakeholder workshops aligned report objectives with business goals, so five reports were built against stated decisions rather than a list of requested charts.

Data cleaned and modelled properly. Nulls removed, data types corrected, unnecessary fields dropped and the model rebuilt, so the figures reconcile across reports.

A dedicated SQL view per report. High-performance, report-specific database views rather than shared generic queries, which is what brings loading times down against an on-premise source.

Signed off as a wireframe first. Interactive Figma wireframes were approved before development started, so the design conversation happened before the build rather than after it.

The choice we made

We put the performance work at the source, building a view per report, rather than letting Power BI carry the load. It is more objects to maintain, and it is the difference between a report that opens immediately and one a store owner gives up waiting for. Self-service only works if the service is fast.

BUILT ON
  • Azure SQL Database Azure SQL Database
  • Power BI Power BI

The results

What changed for the business

Reporting stopped being something the business requested and became something it did.

Reports open fast enough to use

Optimised views and a cleaner model cut report generation time and improved accuracy, which together decide whether a dashboard gets opened in a meeting or avoided.

The IT queue got shorter

Users analyse trends themselves, so routine reporting questions no longer go through IT. For independently operated stores, that means the owner answers their own question on the day they ask it.

One place performance gets reviewed

The dashboards became the basis for performance monitoring, planning and trend analysis across sales, customer, product and programme activity, rather than one of several competing versions.

Let's Connect

Facing a similar challenge?

Talk to our data and AI team about where you are today and what good looks like. 30 minutes, no obligation.

Book a consultation
Professional customer service agent on a support call
More Case Studies
Next Case Study
Contact Us

Collaborate with us

We're here to answer your questions and help you find the right solution.

Client-oriented
Results-driven
Problem-solving
Transparent

"*" indicates required fields

This field is for validation purposes and should be left unchanged.