power bi and fabric, done with you.
Ongoing work with your team - real models, office hours, workshops - and a second opinion on the architecture, the hire, the plan you're being asked to sign off.
Whatever the shape of the work, the aim is the same: a team that can explain its own reporting, change it without fear, and vouch for the numbers that go out - with or without me.
what i do
no one person has to understand the full stack to every level of detail.
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.
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 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.
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.
the things teams tell me
- “When she's not here, we're screwed.”
- “We don't dare touch it in case it breaks.”
- “The course was great - then we tried it on our own data.”
- “The model broke, and we don't know where.”
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.
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 me