A governed model
One definition per metric, written down and agreed before it's built. Star schema, documented lineage, no competing versions.
02Service
Data Platform & BI
Every system you run, consolidated into one governed model your team reads from instead of assembling by hand.
Built on a modern data stack in your own tenant — Fabric, Snowflake or Databricks — refreshed nightly, and reconciled against a number you already produce by hand before anyone is asked to trust it. Priced by milestone, each phase accepted in writing before the next is quoted.
Systems opened to read one KPI
8 to 1
A CFO's own account, six weeks after his platform went live.
When this is the right service
You already know what you want to measure. Getting the number is the problem.
Every location on a different instance. A roll-up that takes one person most of a week. Four versions of revenue in circulation and no way to say which is right without opening eight systems.
If instead you're unsure what to measure or in what order, start with Analytics Strategy — it's cheaper and it makes this build shorter.
What you get
Nightly pipelines
Every source ingested on a schedule that runs without anyone watching it, with failures that surface instead of going quiet.
Reporting people open
Built with the operators who'll use it, in the shape they already think in — not a dashboard tour nobody returns to.
A reconciliation
Your own hand-built number against the platform's, line by line, with the variance written down and explained.
The documentation
Metric glossary, model diagram, deployment notes. Written as we go, so it's current rather than reconstructed at the end.
Your tenant, your licenses
Nothing runs on our infrastructure. If we part ways the platform keeps working, which is the point.
How it runs
Each phase is scoped, priced and accepted in writing before the next one is quoted.
You can stop after any phase and keep everything built.
01Weeks 1–2
Inventory
Every system, instance and export cataloged, and every metric defined in your words. One written definition before anything is built.
02Weeks 3–6
First source live
One system end to end in production, refreshing nightly, reconciled against a number you already produce by hand.
03Per SOW
Coverage
The rest of the estate to a coverage figure written into the contract, with acceptance signed off against it.
Then it's yours
Handover
Documented and handed to your team. Keep us on as your analytics partner, or run it yourself.
PE-backed roll-up · 6 systems + Sage
Twenty-eight locations never standardized how they work. They now report one way, from one model the operators audited themselves.
On record
19 → 1
System instances across 28 locations, in one governed model
72 nights
Consecutive automated rebuilds, no missed refresh and nobody watching it
13 days
From credentials to production for a newly acquired company's system
$0
Charged for two systems found mid-build that the contract never listed
Every figure traces to a delivery artifact — acceptance documents, refresh logs, or a reconciliation the client ran themselves. Clients are blinded until they've signed off on being named.
What this isn't
Not a license resale
You buy your own capacity direct, whichever platform you're on. We take no margin on software and no incentive to oversize it.
Not a staffing arrangement
Fixed scope against milestones, not bodies against a rate card. If a phase takes longer than quoted, that's ours to absorb.
Not a migration for its own sake
If your existing warehouse is fine and the problem is the model on top of it, we'll say so and scope the smaller job.
If one KPI still means opening eight systems, that's the build.
Thirty minutes, no deck. If a platform build isn't the right first move, we'll say which service is.