Plain-English questions in, database queries out

Pulling a number meant writing code or waiting on someone who could. Now the question goes in as a sentence and comes back as a finished query, written against the real data.

/ The problem

Getting a specific slice of data, like everyone who signed up this month, or the biggest accounts by revenue, means writing SQL, the language databases understand. If you don't write it, you ask someone who does, and you wait.

For someone answering a dozen small data questions a day, that waiting adds up. Every quick question turns into a small project, so most of them never get asked.

/ What we did

We built a small tool that turns a plain sentence into a finished query. Type what you want to know in ordinary English, and get back a properly written query, ready to paste into the reporting tool.

Ask a follow-up, like "now just this quarter," and it adjusts the same query instead of starting over.

The accuracy comes from the table names. The real names of every table and column are saved in the tool once, so queries are written against what actually exists instead of a guess at what it is probably called. A guessed name fails the moment you run it.

Utility · ask, then paste

Everyone who signed up this month, biggest accounts first

↓

SELECT a.name, SUM(o.total) AS revenue
FROM accounts a
JOIN orders o ON o.account_id = a.id
WHERE a.created_at >= '2026-07-01'
GROUP BY 1 ORDER BY 2 DESC;

Connections to the database0

Who reads the query and decides to run ita person

Client detail is blacked out, not blurred and never swapped for a stand-in name. Every figure shown is one this page already states.

/ What changed

A question that used to mean writing code or waiting on someone is now a sentence and a copy-paste.

Nothing to maintain. It runs on the person's own machine, on demand.

The step it removes is the writing, not the thinking. The person still reads the query and decides to run it.

/ Decisions worth explaining

It writes queries, it never runs them.

The tool has no connection to the database at all. It hands back text for a person to review and run themselves, which keeps a bad or destructive query from ever leaving the page.

The table names are typed in, not read from the live database.

That means the tool never needs the keys to the real system. A little more setup, and it can't touch anything it shouldn't.

It runs locally, for one person.

No server, no login, nothing to keep online. It is treated as a personal tool, not a service the whole company leans on.

Your business has a version of this. Start with a Diagnosis Next: The day’s sales calls, with the homework already done →