customer zero
We built this because we needed it.
Evalyst started inside a usage-billing video platform, where every revenue question meant someone opening a SQL client and reconstructing what a metric meant from memory.
The problem was never access to the data — we owned the database. It was that the meaning of
the data lived in people's heads. Which user ids are internal test accounts. Which column is
gross usage and which is money actually collected. Which flag was added in 2023 and is
NULL for everything before it. Get one of those wrong and you don't get an error, you
get a number — and numbers are believed.
So the first version of this product answered questions. The version that turned out to matter is the one that refuses to. An agent that says “I can't determine that from this data” is doing its job; an agent that confidently reports zero because a NULL comparison silently dropped a year of rows has cost you more than an analyst's salary in one chart.
That is why the centre of this product is not the chat box. It is a bank of questions with answers a human confirmed, standing between every change and every dashboard, and the number that matters is not accuracy but how many times it was confident and wrong. We run it against our own revenue every time we change a rule.
Where it is now
Private beta, working with a small number of companies shaped like the one it was built for: usage-billing SaaS, real revenue data in Postgres or MySQL, no data team. If that's you and the thing you're nodding at is the NULL story rather than the chat demo, we should talk.