What Fabric still needs to earn the mid-market’s trust, in the words of the people actually signing the renewal.
Fabric Lab · Issue 08 · By Dave Goyal
I have sat across the table from enough mid-market manufacturing CIOs this year to write this letter on their behalf. None of them asked me to. All of them would sign it.
Dear Microsoft
You built something genuinely useful in Fabric. Unified compute, OneLake, a real answer to years of fragmented BI tooling. That part is not in dispute. Every CIO I talk to agrees the technology direction is right.
What is in dispute is who your enablement materials, your partner incentives, and your default pricing conversations are actually written for.
71% of us have to prove AI value by mid-2026 or lose budget. That is not a Fortune 500 problem with a longer runway. That is a board meeting six months from now, with a five-person IT team and no bench.
68% of us cannot get a pilot past proof of concept. Not because the model is wrong. Because the data underneath it was never fit to run one, and nobody in your enablement funnel says that plainly before we sign.
Only 27% of us have a data warehouse at all. Your Copilot demos assume a semantic layer that most of us do not have yet. When the demo works and the production rollout does not, the gap between the two is rarely explained until we are already three months into a renewal.
Here is what would actually earn our trust in the next twelve months, not another campaign.
Name the F64 threshold in plain language, before the SKU conversation, not after. We should not learn about it from a consultant after the invoice arrives.
Publish a realistic Year 1 TCO range, not just capacity pricing. We know the sticker price is not the real number. Say so, and tell us what the real range looks like.
Stop treating “mid-market” as “small enterprise.” We do not have a platform team. We have five people who also run payroll systems and the email server. Build enablement paths for that reality, not a scaled-down version of the Fortune 500 path.
Hold your partners to naming the hidden costs, not just the license. A partner ecosystem incentivized purely on capacity sold will keep quoting capacity, not honesty.
Why I Am Writing This As A Letter, Not A Complaint
None of this is a rejection of Fabric. Every CIO I know is choosing to build on it anyway, because the alternative fragmentation is worse. This letter is what trust actually requires: naming the gap plainly, in public, instead of pretending the mid-market experience matches the enterprise pitch deck.
What This Means For You
If you recognize your own experience in any of the four asks above, you are not alone, and naming it to your Microsoft account team directly, in these terms, tends to get a more honest conversation than accepting the standard pitch.
If you are choosing a partner right now, ask them directly whether they will name these gaps to you before you sign, not after.
The One Ask
If you want a second opinion on where your own Fabric conversation with Microsoft or a partner is glossing over one of these four gaps, reply here or DM. No pitch, just a real read on your situation.
Which of the four would you add to, or push back on? Tell me in the comments. I read every reply.
Next issue: Five Fabric Mistakes That Quietly Killed Three Q1 Projects. Names removed, lessons kept.
Click here to read Dave’s Demystify Data and AI newsletter on LinkedIn.