£5,950 fixed · Microsoft Partner
Everyone's being told to move to Fabric. Almost nobody's been told what it costs.
Five days of work that answer three questions properly: what capacity you would actually need, what it would cost you over three years, and which parts of your estate should not move at all. You end up with a decision you can defend to a board, whichever way it goes.
A maturity benchmark across data, platform, operating model and skills, scored so you can re-run it in a year and show what moved.
A target architecture with the decisions and the reasoning written down, not just a diagram.
Capacity sizing plus a three-year total cost model, built from your actual usage rather than a pricing page.
A 90-day plan and an 18-month roadmap, sequenced by risk rather than by what is easiest to demo.
A skills and operating model gap list, naming roles rather than people.
An executive deck you did not have to write, with the cost model in it.
Current state, honestly
What you run today, what it costs, where it hurts, and what your refresh and usage patterns actually look like rather than what anyone assumes they look like.
Model the options
Target architecture, capacity sizing and the three-year cost of each realistic path, including the path where you stay where you are.
The recommendation
A written decision with the numbers behind it, a 90-day plan, an 18-month roadmap and a readout for whoever holds the budget.
- One tenant
- Maturity benchmark you can re-run later to evidence movement
- Capacity sizing modelled on your real refresh patterns and user counts
- Half the fee comes off a migration booked within 90 days
- A free 20-minute call, no pitch
- We work out which engagement fits, or whether none of them do
- If a cheaper piece of work solves it, I'll tell you
"Not yet" is a valid outcome, and sometimes the valuable one.
Plenty of estates are being moved to Fabric on momentum: a roadmap slide, a conference talk, a nervous feeling about being left behind. Momentum is not a business case, and a migration that lands on the wrong capacity tier gets expensive quietly, months after everyone stopped paying attention to it.
This assessment is just as useful as evidence for waiting, or for scoping the move much smaller than proposed. The three-year cost model is usually the part that changes the conversation, because it is the first time anyone has put the real number next to the plan.
50% to book, 50% on delivery, 14 days to pay.
Invoice or card, whichever suits your finance team. All prices exclude VAT where applicable.
The deposit holds your date
Booking blocks out my diary, so the first half is non-refundable inside 14 days of the start date. Move it with more notice than that and nothing is lost.
Work pauses on an overdue invoice
Not a threat, just how it works, and saying it now saves an awkward conversation later.
Scope changes get quoted, not absorbed
Every fixed price names what it covers. Anything outside that gets priced before it starts rather than appearing on a final invoice.
Access delays move the date, not the price
Waiting on permissions is the most common reason a turnaround slips. It shifts the delivery date and never the fee.
Frequently asked questions
What is a Fabric Readiness Assessment?
A fixed-price £5,950 assessment, five days of work delivered over about three weeks, that answers whether you should move to Microsoft Fabric, what it would cost over three years, and which parts of your estate should not move at all. You get a maturity benchmark, a target architecture with the reasoning written down, capacity sizing, a 90-day plan and an 18-month roadmap.
Can this be used to argue against moving to Fabric?
Yes, and sometimes it should be. Plenty of estates are being pushed toward Fabric on momentum rather than a business case. The assessment is equally useful as evidence for slowing a migration down or scoping it much smaller, and the three-year cost model is usually the part that changes the conversation.
Why does capacity sizing matter so much?
Because Fabric capacity is the cost that surprises people. The difference between the smallest workable SKU and what sustained real usage needs is very large, and it is easy to pilot happily on something that will not carry production. Sizing it with your actual refresh patterns and user counts is more useful than any feature comparison.
Do you need to be a Microsoft Partner to deliver this?
It helps, and I am one. It means the assessment lines up with how Microsoft expects these engagements to be scoped, and it removes the procurement objection that comes with hiring an individual. It does not mean I sell you licences: I sell no Microsoft seats or software, so nothing in the recommendation is shaped by resale.
What happens at the end?
You get a decision you can defend to a board, in writing, with the numbers behind it. If you then want the migration delivered, that is scoped separately and half of this fee comes off it if you book within 90 days.
Stop arguing about the numbers. Start using them.
Book a fixed-price Power BI Health Check and find out how trusted, usable and audit-ready your reporting really is, and exactly what to do next.