Skip to main content
Business Intelligence & Insights · Case Study

Power BI reporting built to last and to support management decisions

Power BI reporting case study PlanetHome

PlanetHome needed a reporting landscape that its team could maintain in-house and the management could use to steer the business. We built a shared Power BI foundation and gave the team the standards, documentation and knowledge to continue developing it themselves.

What changed with the new Power BI reporting


In-house✓

Reporting maintained and developed by the internal team

6

reports: Power BI reports supporting business decisions

3

models: shared KPI logic for Brokerage, Financing and HR

4

business areas: management, partner management, brokers and HR

01

Steering across the sales network

One KPI logic from the management summary down to the individual broker.
02

Better business visibility

Revenue distribution across partners is now visible, including areas of high concentration.
03

Same number per KPI

Business logic sits in shared semantic models, so a definition change is one edit, not one per report.
04

Internal ownership

An internal team was enabled to maintain and further develop the reporting landscape.

The starting point

The starting point for the new Power BI reporting: PlanetHome’s reporting landscape had grown over time across departments and use cases. We reviewed the setup and gathered stakeholder requirements around two goals:

Maintainability

Shared KPI logic, clear standards and an internal team able to maintain and develop the reports after handover.

A management tool

Consistent view of brokerage and financing, helping management and brokers follow performance and identify where action was needed.

What we did

From requirements to handover

A structured reporting journey from analysis to internal ownership.

01
Analyse

Setup, data, stakeholders

02
Concept

Standards, design, DWH requirements

03
Build

Reports & semantic models

04
Test & enable

Validation, training, documentation

05
Handover

Internal ownership and continuation

1.

Started with a concept, not a dashboard

Before building anything, we looked at the existing reports, available data and what people across departments actually needed. We translated stakeholder requirements into a common reporting concept and explicit requirements for the data warehouse.

The concept covered modelling, testing, deployment, documentation and access. A reusable Power BI template added predefined layouts, filters and interactions, making new reports easier to build and consistent for users.

2.

Built a shared semantic layer with PlanetHome

We supported PlanetHome’s team to build the Brokerage, Financing and HR semantic models, using the same modelling guidelines. KPI logic sits in these shared models rather than in individual reports.

When a definition changes, the internal team updates it once in the relevant model in the backend, then tests and validates it with the department before release. The modelling guidelines and documentation support ongoing maintenance.

Within Hopmann’s AI Foundation, the project puts the first layer in place and lays the groundwork for two more: measurement, data quality and governance, and a shared semantic layer. Together, they provide the basis for reliable reporting and future AI-enabled analytics.

Where this sits in the Hopmann AI Foundation

PlanetHome now has the measurement layer in place and a foundation for quality and semantics.

Layer 1

Measurement Framework

Agreed KPI definitions, naming conventions and documentation standards

In place

Layer 2

Data Quality & Governance

Data validated with departments, access and row-level security

Started

Layer 3

Semantic Layer

Shared calculation logic for Brokerage, Financing and HR models

Started

Layer 4

Context Layer

Not part of this project

Not in scope

Layer 5

Agentic Intelligence

Not part of this project

Not in scope
3.

Turned the reports into a management tool

The reports follow PlanetHome’s broker network: growth, getting new brokers started, performance and retention.

For management, we brought brokerage and financing together in an executive summary. We implemented PlanetHome’s growth-based performance score and kept its history, allowing comparisons over time.

For areas and regions, the broker analysis shows performance by tenure, time to first transaction and churn, making onboarding and retention measurable.

For brokers, a goal view translates targets into concrete next steps. All three levels use the same shared KPI logic.

4.

Made quality and handover part of the process

Reports are developed in a dedicated workspace, validated in the production workspace and published through Power BI Apps after approval. Access follows defined audiences, with row-level security where needed.

We tested data, functionality, visual consistency and performance with the relevant departments and supported sign-off. Versions are stored in SharePoint, so changes can be traced and earlier versions restored.

Training, usage guides and support for the internal development team made handover part of the delivery. The team could build on the existing models, template and documented process.

5.

Used AI to accelerate the reporting process

AI helped us understand dependencies and draft changes and documentation across semantic models and SQL logic. We validated the output against the data and business rules.

We also turned stakeholder meeting notes into an interactive HTML prototype in minutes, helping agree the dashboard direction before Power BI development started.

AI-assisted prototyping

Turning an early stakeholder idea into something tangible before Power BI development starts.

Step 1

Stakeholder

conversation
Initial dashboard idea

Step 2

Meeting notes

prompted into AI
No formal requirements yet

Step 3

AI prototype

Interactive HTML
in minutes

Step 4

Validate first

then build
in Power BI

Faster alignment before development

AI accelerates the first solution. Technical and business validation stay with the team.

The results

Maintainability and internal ownership. PlanetHome can maintain and develop its reporting in-house, using shared models, a reusable template and a documented process. KPI changes are made in one place rather than repeated across reports.

A management tool across the network. Management, regions and brokers have a consistent view of growth, performance and retention. Visibility of partner revenue and concentration supports decisions about which partnerships to strengthen and where to look for growth.

Why this matters for partner-driven sales organisations

Management needs to see where revenue comes from and where growth or retention needs attention. A shared reporting foundation makes those questions easier to answer, while clear standards and an enabled internal team keep reporting useful as the business changes.

Stefan Berge, Chief Data Officer at PlanetHome Group, on the Power BI reporting case study

“Hopmann didn’t just deliver reports – they built the foundation with our team and made sure we could own it. Today we change a KPI definition once, and it is consistent from the management summary down to the individual broker.”

Stefan Berge, Chief Data Officer, PlanetHome Group

PlanetHome logo
Dr Ioanna Kakoulidou, Hopmann

Dr Ioanna Kakoulidou
Senior Data Analyst

+49 89 219 099 021

Book your free 30-minute initial consultation now.