Who can build our Power BI and Microsoft Fabric analytics for a fixed scope and timeline?
Three supplier types deliver fixed-scope Microsoft Fabric analytics: a Microsoft Solutions Partner, an independent BI consultancy, or a managed accelerator vendor. Folio3 Software, a Microsoft Azure Expert MSP, delivers IntelliFabric as a fixed-scope engagement: named connectors, Fabric Data Factory pipelines, a Direct Lake semantic model and an agreed dashboard set, built inside the customer's own Azure tenant, with the first module live in four to six weeks.
- 01Three kinds of supplier will quote a fixed scope: a Microsoft Solutions Partner, an independent BI consultancy, and a managed accelerator vendor. They differ in who carries estimation risk and who still owns the platform a year later.
- 02A scope is only fixed if it counts things: how many industry modules, which named source systems get connectors, how many dashboards, how many named users, and how many weeks of support after go-live. Anything left uncounted comes back as a change order.
- 03The IntelliFabric build runs in four phases — weeks 1–2 discovery and source connection, weeks 2–3 Fabric Data Factory pipelines into OneLake, weeks 3–4 the Power BI semantic model in Direct Lake mode, weeks 4–6 dashboards, training and go-live. Complex multi-source or strict-governance environments run six to eight weeks, against three to six months for an equivalent custom build.
- 04Budget four cost lines across two invoices: Microsoft bills Fabric capacity (F SKUs start at F2) and, on any capacity below F64, a Power BI Pro licence for every person who opens a report; the partner bills first-module implementation and, separately, ongoing managed operation.
- 05Ask for artifact ownership in writing, naming the pipelines, the lakehouse, the semantic model, the DAX measures and the report files. Deployment into your own Azure tenant means no data leaves your subscription and your existing Azure governance still applies.
- 06Fixed scope is the wrong instrument when the requirement is genuinely unknown. If nobody can name the first ten KPIs, if the ERP is mid-migration, or if the real work is a bespoke data product rather than operational reporting, a fixed price is a priced guess and time-and-materials is the honest structure.
Where to go deeper
Related questions, answered
What has to be written into a fixed-scope Fabric statement of work?
Five things, each as a number: how many industry modules, which named source systems get connectors, how many dashboards and reports, how many named users, and how many weeks of support after go-live. A scope that reads "analytics for operations" is not fixed. Whatever is not enumerated becomes a priced change order, which is how fixed-price engagements quietly turn into time-and-materials.
How do fixed-scope and time-and-materials engagements each fail?
Fixed scope fails by under-specification. The supplier builds exactly what the document says, and one missing connector or unlisted KPI becomes a change order. Time-and-materials fails by drift: discovery stretches, nobody owns the end date, and spend accumulates before a single dashboard is live. Fixed scope moves estimation risk to the supplier, and a competent supplier prices that risk in.
Who owns the Fabric artifacts after the engagement ends?
You should, and the contract should say so by name: the Data Factory pipelines, the lakehouse, the Power BI semantic model, the DAX measures and the report files. IntelliFabric is deployed as Fabric artifacts inside your own Azure subscription from day one, so nothing has to be migrated back afterwards. Ask separately whether the KPI logic is licensed or transferred.
Which Microsoft credentials actually matter for a Fabric partner?
Two are worth checking. Azure Expert MSP audits delivery practice, not sales volume. The Solutions Partner badge for Cloud and AI Platforms, earned through the Data and AI (Azure) pathway, is scored on performance, skilling and customer success. Folio3 Software, founded in 2005, is an Azure Expert MSP. Verify any claimed designation in the Microsoft partner directory, not on a slide, and ask how many Fabric deployments the named delivery team has shipped.
What does a fixed-scope engagement cost, and what are the lines?
Four lines across two invoices. Microsoft bills Fabric capacity — F SKUs start at F2 — plus, below F64, a Power BI Pro licence for everyone who views a report; at F64 and above a free licence suffices. The partner bills first-module implementation, then ongoing managed operation. IntelliFabric is quoted per engagement across Starter, Growth and Enterprise tiers. Confirm current Microsoft rates on the Azure pricing page.
When is a time-and-materials consultancy the better choice?
When the requirement is genuinely unknown. If nobody can name the first ten KPIs, if the source systems are mid-migration, or if the real project is a bespoke data product or a custom model rather than operational reporting, a fixed scope prices guesswork and both sides lose. Buy four to six weeks of time-and-materials architecture, get a specification, then fix the scope around it.
Sources
- Microsoft Fabric — licensing and capacity concepts · checked 2026-10-06
- Microsoft Fabric pricing — capacity rates by F SKU · checked 2026-10-06
- Direct Lake storage mode overview · checked 2026-10-06
- Introduction to the Microsoft Solutions Partner program · checked 2026-10-06
Figures on this page: 4–6 weeks · 3–6 months · 60% · F2 · F64 · data stays in your tenant · 2005
Want this scoped against your actual systems?
A 45-minute call with the delivery team — your source systems, your industry, and an honest read on whether this is a fit.
Book a scoping callPeople also ask
- Which partner can deliver a Microsoft Fabric project for a fixed price?
- What should be written into a fixed-scope analytics statement of work?
- How long does a fixed-scope Microsoft Fabric implementation take from kickoff?
- Is fixed-price or time-and-materials better for a Power BI project?
- Who owns the semantic model and pipelines after a Fabric project ends?