BUILD
Put one agreed Microsoft Fabric outcome into governed production.
The Fabric Accelerator is a fixed-scope build for customers with a selected use case, sponsor and delivery-ready evidence. It creates one accepted production outcome, the governance around it and the handover required to operate it.
- Target duration
- Four weeks after readiness and scope gates.
- Current commercial experiment
- From £25,000 + VAT.
- Scope
- One bounded use case.
- Delivery
- Live virtual or hybrid by agreement.
- Marketplace
- Eligible professional-services route may be available after current checks.
The problem
Pilots often remain disconnected from real ownership, acceptance, deployment and handover. The Accelerator is designed for the moment when the business decision is already made but production execution is still blocked.
Entry criteria
- one priority use case and business sponsor
- named technical/data owner
- bounded data sources and integrations
- security/governance participants
- acceptance criteria
- viable access and procurement route
- scope capable of fitting the delivery envelope
Not suitable where
- the use case or business case is unresolved — start with Strategy & Enablement
- the programme is multi-region, multi-tenant or enterprise-wide — use Complex Fabric Transformation
- the immediate job is capacity accountability — assess FEA fit
- the customer wants an unlimited dashboard or integration factory
What you receive
- agreed delivery and acceptance plan
- governed Fabric workspace/environment design
- ingestion/pipeline for the bounded use case
- model, semantic or reporting outcome as scoped
- access, governance and release controls
- testing and acceptance evidence
- documentation and operational runbook
- team handover
- 90-day roadmap and next-decision record
Four-week delivery shape
-
Week 0
Readiness and scope gate
Data, access, participants, acceptance and exclusions confirmed.
-
Week 1
Foundation and baseline
Environment, data path, governance and acceptance baseline.
-
Week 2
Build
Core pipeline/model/outcome implemented within the agreed envelope.
-
Week 3
Integrate and test
Security, data quality, usability and performance tested.
-
Week 4
Accept and hand over
Outcome demonstrated, exceptions recorded, documentation transferred and next decision agreed.
Customer dependencies, scope change or evidence quality may move dates. QA is not silently compressed to preserve a marketing timeline.
What happens after
Possible outcomes include:
- customer-owned operation
- separately scoped expansion
- private training
- FEA/FabOps where the relevant accountability trigger exists
- AI Agent Accelerator where a qualified workflow exists
- no further Onyx work
Frequently asked questions
Is every Fabric project completed in four weeks?
No. Four weeks is the target for a qualified, bounded Accelerator. Complex migrations and programmes are separately scoped.
Does the Accelerator include ongoing support or FabOps?
Only the handover and support expressly stated in the contract. FabOps software or Operate services are separate and introduced only where the customer’s operating trigger justifies them.
Can this be bought through Marketplace?
An eligible professional-services route may streamline procurement, subject to current seller/customer geography, billing, offer and approval rules. It does not eliminate onboarding or security review.