Skip to content
Anil Thapa
Anil Thapa

Anil Thapa

Data & AI Platform Leader

Both halves of the data problem.

The platform, and the strategy it is supposed to serve.

I'm Anil Thapa. Fifteen-plus years across both: query plans and partition schemes early, then data functions hired from zero, warehouses consolidated out of silos and mergers, and ingestion rebuilt and proven before anyone was asked to trust it.

The hard part is usually the second half, and you don't get a hearing for it without the first. This site is where I write it down: the patterns that held, the ones that didn't, and what I'd tell someone facing the same call. No tutorials; a model answers those faster than I can.

Hands on
Still in the query plan when that is what the problem needs
Built from zero
Central data functions, hired and structured from scratch
Boardroom
Strategy with executives, not reporting to them
Run more than once
Patterns repeated across engagements, not a single project
01Greenfield data function, analysts embedded across departments

Building a data function from zero

No data team. Engineers working in a vacuum, product managers asking developers for numbers, and every department with its own analyst producing a different answer to the same question. The platform was the straightforward part.

  • Centralize the definitions first, the people second, the tools last
  • Analysts join the centre for governance and stay close to their department
WarehouseTransformationOrchestrationBIGovernance
Read it
02Executive partnership across departments and at board level

Data in the boardroom

Being in the room is not the same as being useful in it. Most of the work is not C-suite set pieces. It is department heads, one at a time, and the argument is never really about metric definitions.

  • Executives do not want the number, they want the decision it implies
  • Align on the strategy first; metric definitions are the mechanism, not the point
Read it
03Data quality and reliability as an operating discipline

Earning trust in the numbers

Trust in a data platform does not degrade gracefully. It holds, then one confidently wrong number in a visible setting, then everyone checks everything manually forever. Treating quality as a discipline rather than a side effect.

  • Trust is a step function, not a gradient, protect the step
  • Cover the numbers your most skeptical stakeholder uses, first
TestingFreshness monitoringLineageAlerting
Read it

What I write about

Recent writing

All writing
Architecture & economics

The tools I use

The current working set, kept alongside the 2025 list rather than edited over it. The gap between the two is the interesting part: the core barely moved, a compliance tool became a runtime dependency, and a third of the list stopped being data tooling at all.

Read the post
Data in the business

What BI means, revisited

I defined business intelligence in 2021, revisited it in 2024, and I'm revisiting it again. What changed, what didn't, and which of my own definitions aged worst.

Read the post

Speaking, podcasts, and advisory

I speak about building data functions from zero, what changes when data reaches the boardroom, and agentic systems against warehouses that carry real history. I also advise a small number of data leaders, either on a specific decision or as a standing sounding board. If that fits your event or your problem, get in touch.