Microsoft Fabric.
Live on your data.
In 2 weeks. From $1,500.
A fixed-scope, fixed-fee Fabric engagement for manufacturing, FMCG, and supply chain teams. One source system connected. Bronze and Silver medallion layers built. One Power BI dashboard on your real operational data.
Not a proof of concept. Not a demo workspace with sample data. A production-grade Fabric foundation your team owns at the end of day 10.
2
weeks
From kick-off to live dashboard
$1,500
from
Fixed fee, confirmed before we start
1
source system
SAP, Dynamics, SQL or flat files
0
surprises
Scope locked. Price locked.
What's included
- 1 source system connected — SAP, Dynamics 365, SQL, or flat files
- Bronze ingestion pipeline with scheduled refresh on OneLake
- Silver transformation layer — cleansed, typed, business logic applied
- 1 Power BI dashboard — up to 5 visuals on the KPIs that matter
- 90-min knowledge transfer + full handover documentation
Claim your sprint
Tell us about your setup
Takes 60 seconds. Amit reviews personally and confirms the fee within 1 business day.
Trusted by operations teams at



























The Problem
Why most Microsoft Fabric projects stall before going live
Fabric is not the problem. The problem is the six-week scoping phase, the demo workspace that never touches real data, and the architecture review that produces a diagram but no working pipeline.
You bought Fabric licences through your Microsoft renewal. Nothing has been built.
Microsoft Fabric is now included in most E3 and E5 plans. The licences are there. But activating a Fabric capacity, designing a medallion architecture, and connecting it to SAP or your ERP requires someone who has done it before. Most organisations sit on unused Fabric capacity for 6–12 months before doing anything with it.
The last Fabric POC produced a demo workspace with sample data. It never went live.
This is the most common failure pattern in Fabric projects. A partner builds a technically impressive architecture using sample data, presents it to IT leadership, and disappears. The workspace gets archived. Six months later someone asks what happened. The answer: it never touched real data, never had a real owner, and never produced anything a business user could open on a Monday morning.
SAP, ERP, and operations data sit in separate systems with no single source of truth.
A manufacturing plant running SAP B1 for inventory, a separate MES for production, and spreadsheets for quality reporting has three versions of truth — and they disagree. Month-end close is a reconciliation exercise, not a reporting exercise. Until the data is in one place with consistent transformation logic, every Power BI dashboard has numbers someone argues with.
Power BI reports exist. Nobody trusts the numbers.
The dashboards look professional. But ask the plant manager if the OTIF number on screen matches the SAP report, and the answer is usually "roughly." When the underlying data pipelines are poorly designed — wrong refresh schedules, mismatched grain, no data quality layer — every report carries an asterisk. That is a data engineering problem, not a Power BI problem.
What's included
Two weeks. Fixed scope. Real deliverables.
Every day of the sprint has a defined output. Not a meeting. Not a requirements document. Working infrastructure connected to your operational data.
Foundation
Architecture, ingestion, and Bronze layer
Replaces
The 6-week scoping exercise that ends with an architecture diagram and no working code.
- Day 1–2: Source system audit — connect to your chosen system, map the tables you actually need, define the KPIs the dashboard will show. No assumptions.
- Day 3–4: Medallion architecture designed and signed off — Bronze, Silver schemas, partitioning strategy, and naming conventions documented before a single pipeline is built.
- Day 4–5: Bronze layer ingestion pipeline built and running — raw data landing in OneLake Delta format, scheduled refresh configured, pipeline monitoring alerts set up.
End of Week 1: your real operational data is flowing into Microsoft Fabric. Not sample data. Not a demo — your actual SAP tables, production records, your numbers.
Delivery
Silver layer, Power BI dashboard, and handover
Replaces
The second six-week phase that adds three months to a project that should have been live already.
- Day 6–7: Silver transformation layer — cleansed, typed, and deduplicated Delta tables. Business logic applied: date spine, unit conversions, calculated fields. Data quality checks logged.
- Day 8–9: Power BI dashboard built on Silver layer — up to 5 visuals covering the agreed KPIs (OEE, OTIF, inventory turns, fill rate, or whatever is highest priority). Scheduled refresh configured.
- Day 10: Handover — 90-minute knowledge transfer session with your team, setup documentation handed over, and a prioritised list of what to build next.
End of Week 2: a production Power BI dashboard built on real Fabric infrastructure, owned by your team, with documentation that does not require MDI to maintain it.
Scope
Exactly what is — and isn't — included
Fixed-fee works because the scope is unambiguous. If you need something outside this list, we scope it separately — no hidden costs, no overruns.
Included in the sprint
- 1 source system (SAP B1, S/4HANA, ByDesign, Dynamics 365, SQL Server, SharePoint)
- Bronze ingestion pipeline with scheduled refresh
- Silver layer — cleansed, typed, business logic applied
- 1 Power BI dashboard (up to 5 visuals, agreed KPIs)
- On-Premises Data Gateway setup if required
- 1 × 90-min knowledge transfer session
- Architecture and setup documentation
Not included — scoped separately
- More than 1 source system
- Gold semantic layer / Direct Lake Power BI
- Row-level security
- More than 1 Power BI dashboard
- Real-time streaming ingestion
- Custom ML / forecasting models
- Power Apps, Power Automate, Copilot Studio
Fixed fee
$1,500 – $2,500
Exact fee confirmed after a 15-minute scoping call. Depends on source system complexity.
Common questions
What buyers ask us
Do we need to buy Microsoft Fabric licences before starting?
Microsoft 365 E5 includes Power BI Pro, but neither E3 nor E5 includes paid Microsoft Fabric capacity — that is a separate Azure purchase. Before the sprint starts we check your licence position: if you already have Fabric capacity we work within it, otherwise a Fabric F2 capacity costs around $262/month and is enough for the Starter Sprint. We do not profit from licence sales — we tell you what you actually need.
Can we connect SAP Business One or SAP S/4HANA in the sprint?
SAP is the most common source system we connect. The Starter Sprint supports one source — SAP B1, SAP S/4HANA, SAP ByDesign, Dynamics 365, SQL Server, or a SharePoint-hosted flat file. SAP connections use ODBC or the SAP connector via Fabric Data Factory pipelines. If your SAP instance is on-premises, we set up the On-Premises Data Gateway as part of the sprint.
What happens after the 2-week sprint ends?
You get a working Fabric workspace, Bronze and Silver Delta tables, a scheduled pipeline, and a Power BI dashboard — all documented and transferred to your team. There is no ongoing dependency on MDI to keep the lights on. Most clients then move into a phase 2 engagement: connecting additional source systems, building the Gold semantic layer, adding Direct Lake Power BI models, or layering in AI forecasting. That is scoped and priced separately based on what we found during the sprint.
Is 2 weeks really enough to deliver something meaningful?
For one source system with a clearly defined set of KPIs, yes. The sprint works because the scope is fixed: one source, two medallion layers, one dashboard. We have seen organisations spend six months on a Fabric POC that produced a demo workspace with sample data. Two weeks with real data from your actual source system, producing a dashboard your operations team uses on day 15, is worth more than six months of architecture diagrams.
What is the exact price?
The fee is between $1,500 and $2,500. The exact amount is confirmed after a 15-minute scoping call — it depends on the source system complexity and whether an On-Premises Data Gateway setup is required. The fee is fixed before any work begins. No surprises, no change requests on a fixed-scope engagement.
How do I activate Microsoft Fabric if I already have an E3 or E5 licence?
Having Microsoft 365 E3 or E5 does not switch Fabric on — paid Fabric capacity is a separate Azure resource you assign to a workspace. You activate it by buying a Fabric F SKU (from F2 at around $262/month) or starting a Fabric trial, then assigning it to the workspace; E5 additionally gives users Power BI Pro. In the Starter Sprint we confirm your licence position and stand up the smallest capacity that fits before any build.
What is the minimum viable Microsoft Fabric implementation for a mid-market manufacturer?
The minimum viable build is one source system, Bronze and Silver medallion layers in OneLake, a scheduled pipeline, and one governed Power BI dashboard — exactly the scope of the 2-week Fabric Starter Sprint from USD 1,500. It proves the platform on your real data without a large programme. From there you add sources and the Gold layer in a later phase.
How do I get a Microsoft Fabric proof of concept to go live instead of stalling?
Fix the scope, not the ambition: one source, two medallion layers, one dashboard, on real data with a named business owner who will use it on day 15. POCs stall when they run on sample data with open-ended scope and no owner. The Starter Sprint is built to cross into production in 2 weeks rather than produce another demo.
Why do most Microsoft Fabric POCs fail to move into production?
They run on sample data, carry open-ended scope, and have no business owner committed to using the result — so they end as architecture diagrams, not working reports. We have seen organisations spend six months on a POC that produced a demo workspace nobody used. A fixed 2-week scope on real data, owned by an operations user, is what converts a POC into production.
How do I build a working Fabric lakehouse without a large data engineering team?
You do not need an in-house data engineering team — the Starter Sprint stands up the lakehouse, the pipeline, and the dashboard, then hands it over documented so your team can run it. Microsoft Fabric is SaaS, so there is no infrastructure to manage. We build it, govern it, and train your people to extend it.
What is the fastest way to get SAP data into Microsoft Fabric and Power BI?
The fastest route is one SAP source connected through OData or the SAP connector via Fabric Data Factory (or Mirroring where supported), landing in Bronze and Silver, with a Power BI dashboard on top — the 2-week Starter Sprint. No ABAP, no CSV exports. If SAP is on-premises, we add the On-Premises Data Gateway as part of the sprint.
What is included in a 2-week Microsoft Fabric implementation sprint?
One source system connected, Bronze and Silver Delta tables in OneLake, a scheduled refresh pipeline, and one governed Power BI dashboard — documented and handed to your team. The scope is fixed and the fee is fixed from USD 1,500. You get a working data product on day 15, not a roadmap.
What does a Bronze and Silver medallion layer include in a Fabric Starter Sprint?
Bronze holds the raw source data exactly as ingested from your system; Silver holds the cleaned, typed, and conformed tables ready for reporting. Both are Delta tables in OneLake. The sprint delivers a dashboard built on Silver; a dedicated Gold semantic layer is the usual phase-2 step.
What KPIs can I show in a Power BI dashboard built on Microsoft Fabric in 2 weeks?
With one source and a clear KPI set, the dashboard can show the operational metrics that source holds — OEE, OTIF, fill rate, inventory cover, sales by SKU, or production versus plan. We agree the KPI list in the 15-minute scoping call so the two weeks go to building, not deciding. The dashboard runs on your real data, not samples.
What source systems can be connected in a 2-week Fabric sprint — SAP, Dynamics, SQL?
The sprint connects one source: SAP B1, SAP S/4HANA, SAP ByDesign, Dynamics 365, SQL Server, or a SharePoint-hosted flat file. SAP uses ODBC or the SAP connector via Fabric Data Factory; on-premises sources use the On-Premises Data Gateway. Additional sources are added in a later phase.
What does a Microsoft Fabric F2 capacity cost per month?
A Fabric F2 capacity costs around USD 262/month on pay-as-you-go and is enough to run a Starter Sprint and a first dashboard. Reserved one-year capacity is roughly 40% cheaper. You scale up to a larger F SKU only when workload or user numbers require it.
Is Microsoft Fabric included in Microsoft 365 E3 or E5 licences?
No. Microsoft 365 E5 includes Power BI Pro, but neither E3 nor E5 includes paid Microsoft Fabric capacity — that is a separate Azure purchase starting at an F2 SKU (around USD 262/month). You can trial Fabric, but production workloads need an assigned F capacity. We confirm your exact position before the sprint.
What is the difference between a Fabric F2, F32, and F64 capacity for a small manufacturer?
F2 (around USD 262/month) suits a Starter Sprint and a first dashboard; F32 (around USD 4,205/month) suits a department-scale workload; F64 (around USD 8,410/month) is the threshold where free-licensed users can view Power BI content without a Pro licence each. A small manufacturer usually starts on F2 and moves up only when users or data volume grow. Reserved capacity is about 40% below these pay-as-you-go rates.
How do I add more source systems after the initial Fabric implementation?
After the sprint, additional sources are connected into the same OneLake lakehouse — each landed in Bronze, conformed in Silver, and joined into the model — in a scoped phase-2 engagement. Because the foundation already exists, each new source is incremental rather than a fresh build. We prioritise sources by the decisions they unblock.
How do I build a Gold semantic layer after completing a Bronze and Silver Fabric lakehouse?
The Gold layer is the governed semantic model: business-named measures (OEE, OTIF, margin), calculation groups for time intelligence, and row-level security, built on the conformed Silver tables and read by Power BI on Direct Lake. It is the usual next step after a Starter Sprint. One Gold model gives every report the same definitions.
When should I move from a Starter Sprint to a full Fabric platform engagement?
Move to the full Foundation engagement when one dashboard has proven the value and you need more — additional sources, a governed Gold semantic layer, Direct Lake at scale, or AI forecasting. The full build is first value in 6 weeks, production at 8, from USD 8,000. The Sprint is the proof; Foundation is the platform.
Ready to start
15-minute call. Fee confirmed. Sprint starts within the week.
Tell us which source system you want to connect and which KPIs matter most. We confirm the fixed fee, agree the dashboard scope, and begin on a date that works for your team.