Data foundation & agentic evaluation
An ongoing build: modeled data, a typed metric layer, conversational access, and agent runs scored against recorded outcomes.
- Next.js
- TypeScript
- Postgres
- BigQuery
Practice — Data
Most analytics problems are not analytics problems. The numbers exist, but they live in five tools, two of them disagree, nobody trusts the third, and the person who needs the answer cannot write the query. No interface fixes that — the layer underneath has to be boring, typed and reproducible first.
This page is where I keep the data side of my practice: how I build foundations, and where I think this is heading. It is a working position, not a pitch.
There is a tempting shortcut in every data project: build the interface, wire it to whatever tables exist, demo it. It works for exactly one demo, on one dataset, with the person who built it holding the mouse. The order below is slower and holds up.
The bottleneck in most teams is not the dashboard, it is the translation step: someone has a question in business language and someone else has to turn it into a query. Removing that step changes who is allowed to be curious. But it only works if questions resolve against a semantic layer instead of raw tables — otherwise you have built a machine for producing confident mistakes.
Once agents act on data, "does it feel right" stops being an acceptable answer. I treat an agent run like a landing page variant: define the outcome, record the whole run, score it on three axes, keep what wins.
The same foundation serves a creator with one audience and a mid-size company with fifty accounts. Different scale, identical questions: what is working, what is it worth, what should happen next. That overlap is the part I find genuinely interesting.
An ongoing build: modeled data, a typed metric layer, conversational access, and agent runs scored against recorded outcomes.
Why I refuse to build the chat interface before the data layer is boring, typed and trustworthy.
Growth teams already know how to judge a system they cannot fully explain. Agentic evaluation is the same discipline with a different unit of work.
I am always up for comparing notes on modeling, semantic layers and agent evaluation — whether or not there is a project attached.