Microsoft Fabric, applied with architectural discipline.
Kilvora helps organisations make the architectural decisions that determine whether Microsoft Fabric becomes a dependable platform for the long run, or another data estate that's hard to maintain. From platform design and migration through to stabilisation and optimisation, I build environments that remain understandable, reliable, and operable in production.
When the platform works technically but struggles operationally
Many Fabric platforms do not fail outright. Reports still run and dashboards still refresh, while trust, cost control, ownership, and accountability quietly weaken underneath. Success in production depends less on whether individual workloads complete and more on whether the platform remains understandable, governable, observable, and cost effective as it grows.
What worked as a pilot doesn't hold up in production.
Early builds get pushed live without the checks that keep data reliable over time. The platform keeps running, but the numbers coming out of it get harder to explain and trust.
Nobody can explain what's driving the Fabric bill.
Costs keep rising, and nobody can tie what's being spent back to a team, a workload, or a business outcome.
Basic platform decisions were never actually made.
Nobody decided where data should live, who owns what, or how it should be shared. Every new request adds risk instead of clarity.
Nine connected delivery domains
Sequenced to follow how a platform actually lives: build it, secure it, move data through it, serve it out, make it resilient, make it visible, make it trustworthy, make it efficient, and make it sustainable to run.
1. Architecture & Platform Design
Getting the foundational decisions right, since everything else gets built on top of them.
2. Security & Governance
Securing and governing the platform from the start, not bolting it on afterwards.
3. Ingestion & Processing Engineering
Getting data in reliably, whether from new sources or migrated off a legacy platform, without manual rework every time something changes.
4. Semantic Layer & Reporting Governance
Making sure what the business sees in reports is actually trustworthy.
5. Reliability & Recoverability
Keeping pipelines running cleanly, even when something upstream fails.
6. Observability & Failure Detection
Knowing when something's wrong before your business users do.
7. Data Trust & Quality
Catching the runs that succeed technically but quietly produce the wrong numbers.
8. Cost & Performance Optimisation
Keeping spend predictable and easy to explain as the platform scales.
9. Deployment & Operational Readiness
The people, process, and release model that keep everything above sustainable for the long run.
Clarity before speed. Decisions before tools.
Successful Fabric implementations depend more on design decisions than on individual components. Every engagement starts by understanding what needs to change, what must remain stable, where risk sits, and how the platform will be operated after delivery.
Architecture before tooling
Technology choices follow from the operating model, reporting needs, scale, ownership, and risk, not from feature availability.
Make trade offs explicit
Key decisions, constraints, and consequences are explained in plain language so teams understand why the design works the way it does.
Maintainable over clever
Solutions are designed so internal teams can understand, operate, troubleshoot, and extend them without permanent dependency.
Governance by design
Ownership, access, lifecycle, data quality, and cost visibility are built into the platform rather than added after implementation.
Start where the problem is
Some organisations need an architect embedded within the team. Others need a defined platform outcome, an independent readiness decision, or a focused review of an existing Fabric estate. The engagement starts with the problem rather than a predefined package, and every engagement is delivered directly by me.
Architecture & Engineering Delivery
Embedded on a day rate contract basis within your team to design and deliver greenfield platforms, migrations, ingestion and transformation frameworks, semantic layers, governance controls, or the stabilisation of an existing Fabric estate.
Fabric Readiness Assessment
An independent, evidence based answer to whether Microsoft Fabric is right for your organisation, where it fits, and what must be addressed before committing to implementation.
View the Readiness Assessment ↗Fixed Price Platform Delivery
Fixed scope architecture, migration, or platform delivery, delivered against a defined architectural or delivery outcome rather than as additional resource.
Fabric Cost & Performance Audit
A fixed fee review of your Fabric estate, led by evidence, covering capacity, pipelines, governance, and cost, with a prioritised remediation roadmap.
View the audit ↗Evidence from a previous data and analytics engagement
This case predates Kilvora and reflects the broader delivery experience behind the practice.
Stabilising a live Fabric platform for a professional services firm
Situation
A professional services firm's existing Fabric platform was showing strain: rising capacity costs, unreliable ingestion, and governance gaps that made the platform hard to operate with confidence.
What I did
Right sized Fabric capacity and workload placement, rebuilt the ingestion pipelines around incremental loading, brought back governance and CI/CD, and corrected the semantic layer.
What changed
- Fabric capacity spend brought back in line with actual usage, removing cost the client could not previously explain.
- Full dataset reprocessing on every pipeline run replaced with incremental loading, cutting unnecessary reprocessing.
- Manual, ungoverned releases replaced with a governed CI/CD deployment pipeline.
- Client team enabled to operate the platform independently after handover.
Emmanuel Obikili
Lead Architect / Engineer, Kilvora
Emmanuel Obikili is a Microsoft Fabric Architect and Data Platform Consultant with over 10 years of experience across enterprise analytics, data engineering, governance, reporting modernisation, and platform delivery. Kilvora brings that experience together as a focused practice for organisations that need clear architectural judgement alongside hands on implementation.
His work is driven by the belief that successful Microsoft Fabric implementations depend more on architectural decisions than on individual platform features. That principle shapes every engagement, whether designing a new platform, stabilising an existing one, or assessing a live environment.
The work is centred on production reality: platforms that teams can trust, understand, operate, and evolve, without unnecessary complexity or dependence on one individual.
FAQ
What is Kilvora?
Kilvora is Emmanuel Obikili's Microsoft Fabric architecture and engineering practice. It provides embedded delivery alongside a small number of focused assessments for organisations that need independent clarity before making wider platform decisions.
Is this just cost and performance auditing?
No. The Fabric Cost & Performance Audit is one specialist entry service within a broader architecture and engineering practice. My work spans platform design, ingestion, transformation, migration, reliability, observability, governance, semantic modelling, and long term platform operation across the nine domains above.
Do you take day rate contracts?
Yes. Embedded contract architecture and engineering delivery is a core way of working. Scope, rate, availability, and the balance between architecture and hands on implementation are discussed directly.
What's the difference between Architecture & Engineering Delivery and Fixed Price Platform Delivery?
Architecture & Engineering Delivery is day rate work, embedded inside your team on an ongoing basis. Fixed Price Platform Delivery is scoped and priced upfront for a defined outcome, with architecture, migration, or platform stabilisation delivered as a fixed price project rather than a day rate.
What's the difference between the Readiness Assessment and the Audit?
The Readiness Assessment looks at whether and where Fabric is right for your organisation, before you commit. The Cost & Performance Audit examines a Fabric estate that's already live. Full detail on each sits on its own page.
Is this a one person practice?
Yes, currently. Every engagement is delivered directly by Emmanuel, providing continuity from initial diagnosis and architecture decisions through implementation and stakeholder handover.
How do we start?
Start with a 30 minute conversation about the current environment, the decision or problem in front of you, and the outcome you need. From there, I will recommend the most appropriate route, including saying when Kilvora is not the right fit.
Start with the problem, not a predefined package.
Tell me what is stopping the platform from getting where it needs to be. I will give you a direct view on the most sensible next step.
Start a conversation