How we see data.
How we work with clients.
These aren't values on a wall. They're the principles we apply on every engagement — the things that drive how we scope work, how we challenge clients, and how we measure whether we've actually succeeded.
What we actually believe.
We believe data without a decision isn't data — it's cost.
We think pragmatism is a professional virtue, not a compromise.
We believe clients deserve candour, not comfort.
We think the best indicator of a successful engagement is whether the client still needs us.
We believe a simple model that gets used beats a perfect model that doesn't.
We think responsible use of AI is a delivery standard, not a policy statement.
Data is a means, not an end.
We start from the business outcome — the revenue target, the risk exposure, the customer experience gap — and work backwards. Technology is in service of that. A dashboard nobody uses is a failure regardless of how well it's built.
Evidence over opinion — including ours.
We believe in measurement, experimentation, and changing course when the data disagrees with the hypothesis. That applies to client recommendations as much as it applies to product decisions. If we're wrong, we want to know.
Simple and adopted beats sophisticated and ignored.
A semantic model that the business understands and trusts outperforms a technically perfect one that nobody uses. We have a strong preference for solutions that survive a personnel change, a Monday morning, and a year of production traffic.
We're here for the long relationship, not the invoice.
The most valuable thing we can build is trust. That means saying no to work that isn't right for the client, flagging problems before they're asked about, and measuring success by outcomes — not by how much we billed.
A major insurer brought us in for a single Fabric migration. Three years later, we're their de facto data architecture team. No retainer. Just trust built over time.
We'll tell you what you need to hear.
Candour is non-negotiable. If a project is in trouble, if an architecture decision is wrong, if a stakeholder is blocking progress — we say it clearly and early, not in a post-mortem. Clients hire senior practitioners partly because they want a professional second opinion.
We build capability, not dependency.
Every engagement should leave the client's team more capable than we found it. We document obsessively, run knowledge transfer sessions, and avoid creating lock-in — architectural or commercial. A client that doesn't need us is a client that trusts us.
After an 18-month Power BI programme at a national retailer, the internal team could own, deploy and extend everything we built. That was the brief. It was also the right thing to do.
Define the problem before you build anything.
We always agree on scope, success metrics, and constraints before a single line of DAX is written. Scope creep and rework are usually symptoms of a problem definition that was skipped. We're stubborn about this.
Small increments, real feedback, continuous refinement.
We bias hard toward delivering usable things early. A working report in week two beats a perfect one in month four. Real users interacting with real output is the fastest path to the right outcome.
Responsible use of data and AI — always.
We have an explicit position on privacy, ethics, and model transparency. We won't build systems that obscure how decisions are made, that aggregate personal data carelessly, or that embed bias we haven't actively tested for. This isn't marketing. It's a constraint we apply to every engagement.
Beliefs made concrete.
In writing.
The principles above aren't abstractions — they show up in the work. The blog is where we write about specific problems, real decisions, and what we actually learned.
Browse all articles →If this is how you want your data work done,
let's talk.
We take on a small number of engagements at any time. Tell us about your situation and we'll tell you honestly whether we can help.
Start a conversation →