Why we built this

Every BI tool assumes someone on your team knows SQL and has time. At a twenty-person company, that person is a founder, and they don't.

So the reporting request becomes a ticket, the ticket sits for three weeks, and by the time the chart exists nobody remembers why they wanted it.

The obvious fix, letting AI write the SQL, turns out to be the easy half. Every tool on the market does it now. The hard half is everything after: choosing an encoding that doesn't mislead, laying out a dashboard someone can read at a glance, and knowing when the question was too vague to answer honestly. That's what we've spent our time on. It's the “kraft” in the name.

We're a small team. We don't have a sales org, we don't do six-month implementations, and we're not trying to sell you an intelligence layer. You should be able to connect a database and have a dashboard worth keeping before your coffee gets cold.

What we're deliberately not building: forecasting, statistical testing, and automated “insights” that tell you why a number moved. Those require judgment about your business that we don't have. We'd rather do one thing properly.