power bi and fabric, done with you.
I've spent five years alongside teams adopting Power BI, and the story rarely changes. A team gets the licences, builds the first reports, and then the difficult part starts:
- the one person who really knows the model becomes the bottleneck;
- things break when anyone else touches them;
- the training course made sense until you tried it on your own data.
And there's always more: Fabric to move onto, Copilot writing DAX, agents building whole reports. The more the tools take on, the sharper one question gets: who's making the calls - you, or the tools?
what i do
no one person has to understand the full stack to every level of detail.
Whatever the shape of the work, the aim is the same: your team ends up more capable of owning it - with or without me.
embedded advisory
I join your team for a stretch - office hours, workshops, one-on-ones - working on your real models and real problems, in your own workspace, across Power BI and Fabric. It runs as a working relationship rather than a scheduled course, so the team gets more capable on the problems you actually have: able to change the model without fear of breaking it, and to catch a wrong number before it goes out, without checking with me first.
Ongoing and month-to-month, sized to your team. Usually £3,000 to £6,000 a month.
reporting strategy
Before anything gets built: what are you actually measuring, and why? We work out the questions the team needs to be able to answer, and what a good answer looks like for each - so everyone means the same thing by the same number. You walk away with a clear picture of what's worth reporting and what to leave out.
architecture review
Then the plumbing: does your model actually serve that strategy, or quietly get in the way? I'll tell you what's carrying its weight and what isn't - including when the honest answer is that a new model won't fix the real problem. And if you're weighing up Fabric, I'll tell you straight whether it earns its keep for you.
A fixed, shorter piece. Scoped and priced up front.
build work, case by case
And if you have a specific, well-thought-through Power BI build in mind, ask - I take those on case by case.
a team that owned it
to be responsible for it, they had to understand why it's built the way it is.
a data team · international law firm
One data team I work with - inside an international law firm - started from “fear of breaking”: production models nobody dared touch, external help needed for the smallest change, the whole thing resting on one or two people. A few months of working together, and they were running their own diagnostic sessions, tracing data lineage end to end, and walking into handover conversations with the likely cause already in hand. The reliance moved from a single expert to the team.
Even a first call should leave you with something useful - a clearer read on where it's stuck. 30 minutes, nothing to prepare.
Book a 30-minute callprefer to write? email mewhat ai's already touching
A team that can own and verify its own reporting is also the team that's ready for what AI adds to the job.
ai fit for teams
Copilot can already write DAX and draft a whole report - and agents that build the model outright aren't far behind. It's the same ownership question, one move on: can your team still change what it ships, and vouch for it? Working out what to hand over, what to keep, and who checks it is the other thing I do.
see ai fit for teams