Language as the configurator

When a sentence becomes a query, the user can no longer see what was asked. What has to be shown back?

"All car insurance products from March to August with commission to agent under $100" takes an afternoon to assemble across thirty spreadsheets. Written as one line, it becomes SQL in seconds. We have watched people use it and the leverage is real.

The cost is that the user has stopped configuring and started describing. They can no longer check the configuration.

A filter panel is ugly and it is also legible. The state is on screen, so a wrong month gets caught before the number is believed. A sentence hides the same mistake inside a result that looks finished.

So the question is what the interface owes back. Showing the SQL is honest and useless to the person who needs it most. Restating the interpretation in words risks restating the model's own misreading convincingly. We lean towards showing the row count, the date range actually applied, and the rows that were dropped, because those are checkable without being technical. Whether that is enough for a number somebody is about to pay out on, we do not know.