How much does implementation cost on top of the licence?
No separate implementation fee. Every IntelliFabric plan — Starter, Growth and Enterprise — bundles delivery: source connection, Fabric Lakehouse setup, the Power BI semantic model, dashboards and user onboarding, with no professional-services line billed on top. Microsoft licensing is bought from Microsoft directly: a Fabric capacity of F2 or above, plus a per-consumer Power BI licence below F64. Custom pipelines, KPIs outside the pre-built library and industry modules beyond the first sit in higher tiers.
- 01Implementation sits inside the plan fee rather than on top of it. All three tiers include source connection using the pre-built connector templates, the Fabric Lakehouse setup, the Power BI semantic model in Direct Lake mode, the dashboards and user onboarding — first module live in four to six weeks. Custom Data Factory pipelines beyond the connector templates start at the Growth tier.
- 02For a 30-user deployment — the Growth tier, since Starter caps at 10 report consumers — the work that normally arrives as a separate statement of work (connect the sources, build the pipelines, build the semantic model, build the dashboards, onboard the users) is inside the plan fee. Microsoft invoices capacity and per-consumer licences. Nobody invoices professional services.
- 03The lines a consulting project itemises are precisely what the plan fee replaces: discovery workshops, data-architecture design, pipeline development priced per source, report development priced per dashboard, UAT support, training days, and a change-request rate for anything found mid-build.
- 04Genuinely extra, and quoted as defined work before it starts: KPIs that fall outside the 200+ pre-built library and need new business logic, additional industry modules beyond the one in scope, and white-glove migration of a legacy report estate — which the Enterprise tier bundles, but which is priced as scope below it.
- 05The licensing side is bought direct from Microsoft, which keeps the levers with you. A Fabric capacity at F2 or above runs the workloads, and each report consumer needs a per-user Power BI licence until the capacity is large enough that Microsoft drops that requirement — F64 at the time of writing. Confirm current thresholds and rates against Microsoft before modelling them.
- 06Wrong fit if you want implementation itemised and steered hour by hour, or if your modelling is non-standard enough that pre-built KPI definitions are a constraint rather than a head start. A time-and-materials consultancy is the better buy in both cases, and it is a reasonable reason to walk away from this one.
Where to go deeper
For the full explainer on this topic rather than this specific question, see the detailed guide on the blog.
Related questions, answered
What do we pay Microsoft, and what do we pay for IntelliFabric?
Two invoices. Microsoft bills the Fabric capacity, sized from F2 upward, plus a per-consumer Power BI licence for the people who open reports. Folio3 bills one IntelliFabric plan fee covering delivery and the ongoing operation of the pipelines, semantic model and KPI layer. Confirm current Microsoft rates and capacity terms against Microsoft’s own pricing page before you budget.
What would a traditional implementation have billed for separately?
Discovery workshops, data-architecture design, pipeline development per source, semantic-model build, report development per dashboard, UAT support, training days, and a change-request rate for anything found mid-build. On a three-to-six-month custom build those lines are the majority of the spend. A bundled plan collapses them into one fee, which is also why the scope is defined up front rather than discovered.
What genuinely costs extra?
Three things. KPIs outside the 200+ pre-built library that need new business logic written and validated. Additional industry modules beyond the one in the original scope. Custom data pipelines and white-glove migration of a legacy report estate, which the Enterprise tier bundles but lower tiers price as scope. Each is quoted as defined work before it starts, not billed as it accrues.
What internal cost should we budget that appears on neither invoice?
Your own people’s time. Expect a data or IT owner for a few hours a week during the build to arrange read-only source access and credentials, a business owner per KPI area for a similar commitment to confirm definitions, and a decision-maker who can settle a metric disagreement. Underfunding that second role is the most common cause of slippage.
How do we get an actual number?
Five inputs produce a quote: your source systems and their versions, the number of report consumers versus report authors, which industry module you start with, how many KPIs sit outside the pre-built library, and whether governance requires private networking or a specific Azure region. With those, a plan price and an estimated Fabric capacity size take one call.
When is a bundled implementation the wrong model?
When the implementation itself is the point. If you need a bespoke platform with non-standard modelling, you already employ data engineers who should own the build, or your metric definitions are genuinely unique, then time-and-materials or an internal team gives you control a fixed-scope plan will not. Bundled delivery trades that flexibility for a known date and a known price.
Sources
- Microsoft Fabric — licenses and capacity concepts · checked 2026-10-06
- Buy Fabric capacity Azure SKUs · checked 2026-10-06
- Power BI service features by license type · checked 2026-10-06
- Microsoft Fabric pricing (Azure) · checked 2026-10-06
Figures on this page: 4–6 weeks · 3–6 months · 200+ · 50+ · F2 · F64
What this costs for an operation your size
Three engagement tiers, what each includes, and the Microsoft licensing you need alongside it.
See what shapes the pricePeople also ask
- What does Microsoft Fabric capacity cost for a 30-user company?
- Does every Power BI report viewer need a paid per-user licence?
- Which partner can deliver a Fabric implementation for a fixed fee?
- How long does an analytics implementation take from kickoff to go-live?
- What is usually excluded from an analytics implementation quote?