Lorenzo Reale

Power BI consultant · UK and EU

Services

Review, build, or join your team.

Three ways in, depending on where your reporting stands today and how your team is set up.

  1. 01 Review An independent look at your existing reporting
  2. 02 Build and rebuild New reporting, or existing reporting rebuilt
  3. 03 Join your team A contract Power BI developer inside your team
01

Review

Covers
Semantic models DAX SQL and loads Refresh and access Manual steps

An independent look at the Power BI reporting you already have, before anyone commits to fixing or rebuilding it. I go through it layer by layer: the semantic model and its DAX, the queries and loads underneath, and the manual steps that feed it. You come away knowing what's sound, what's fragile and what to fix first, in an order you can act on, with me or with anyone else.

What you get

  • A written review of the model, the data layer and the process around them
  • Each finding backed by evidence, with its risk and the effort to fix it
  • A plan for what to fix, and in what order
  • What is already sound and should be left alone
  • A walkthrough of the findings with the people who own the numbers
When this fits

You know the reporting isn't right but can't see where the problem starts. Or you want an independent view before funding a rebuild.

02

Build and rebuild

Covers
Power BI DAX Power Query T-SQL Report design Power BI Service

New Power BI reporting built from the data up, or existing reporting rebuilt so people trust it again. The work runs from the sources and the SQL layer, through the semantic model and DAX, to the report pages, then on to deployment, refresh and access on the Power BI Service. The aim is figures that are defensible, not just presentable. Where manual steps feed the reporting, Power Automate and SharePoint can take them over.

What's included

  • Semantic modelling, star-schema design and DAX, documented measure by measure
  • T-SQL and Power Query work under the model, so logic sits in the right layer
  • Report pages designed around the questions each audience needs answered
  • Deployment, workspaces, refresh and row-level security
  • Source files in your own repository, with notes your team can follow
When this fits

You're setting up reporting for the first time and want it built to last. Or the reporting you have is slow, inconsistent or simply not trusted.

03

Join your team

Covers
Power BI DAX T-SQL Power Query Power Automate

A contract Power BI developer inside your existing team, for a delivery peak or a gap in skills. I pick up work from your backlog, follow the conventions the team already has, and work remotely, with on-site days when they're needed.

What I bring

  • Semantic models, DAX and report pages, from new builds to fixes
  • T-SQL and Power Query work under the model when the job needs it
  • Power Automate and SharePoint work around the reporting, where it helps
  • Notes on what I built, so nothing depends on me once I leave
When this fits

Your team has more Power BI work than people, or needs someone who can cover the SQL and the model as well as the report.

How I work

How the work runs.

The steps stay the same; how deep each one goes depends on the job. When I join an existing team, I work its way and bring the checks with me.

  1. Understand what it's for

    Who reads the report, what they decide with it, and which numbers have to be right. If no decision follows from a number, it doesn't earn a place on the page.

  2. Check the data first

    Before modelling anything, I profile the sources: what one row means, where the gaps are, what doesn't join. Problems found at this stage are the cheapest to fix.

  3. Build, and show it early

    The model comes first, then the report. You see it while it takes shape, so feedback arrives while it's still easy to act on.

  4. Reconcile and hand over

    Every figure is checked against its source before go-live. The files, and the notes on how it all works, stay with you, so your team can run it without me.

What I cover

The whole reporting chain.

Whichever way we work, I can reach every layer the numbers pass through.

Power BI

Semantic models, DAX and Power Query, report and dashboard design, then deployment, workspaces, refresh and row-level security on the Power BI Service.

Power BI DAX Power Query M RLS

The SQL data layer

T-SQL queries, views and stored procedures, query tuning, warehouse and reporting-layer modelling, repeatable loads and reconciliation checks, on SQL Server and Azure SQL.

T-SQL SQL Server Azure SQL Data warehousing

Power Platform automation

Power Automate flows, SharePoint lists and libraries, and Office Scripts that replace the emailed spreadsheets and re-keying that often sit in front of a report.

Power Automate SharePoint Office Scripts

Get in touch

Not sure which one fits?

Tell me what the reporting has to do, and I'll tell you where the work actually is.

Discuss a project