Ask your business a question.

“Which customers owe us more than 30 days?” Type it in plain words and get the answer with the records behind it.

It shows its working.

Every answer comes with the query it ran and the records it used, so your accountant can check it. How-to questions cite your own articles.

The query behind the answer
SELECT customer, balance, days_overdue
FROM ai_receivables
WHERE days_overdue > 30
ORDER BY balance DESC LIMIT 200;

Why you can trust it

Four locks, so a wrong answer cannot do harm.

  1. 01

    A door that only opens one way

    It connects with a separate database login that can only read a fixed set of views. It has no other rights at all.

  2. 02

    Every question is checked first

    One read-only statement against approved views. Anything else is refused before it runs.

  3. 03

    Limits on time and size

    A few seconds to finish and a cap on rows, inside a read-only transaction.

  4. 04

    Everything is logged

    Each question and answer goes into a log nobody can edit. Salary views are offered only to HR, accounts and the owner.

It can read.
It cannot change anything.

Your data stays yours

By default it answers common questions itself. A smarter cloud model is a switch you choose, and can switch off.

Sees only what you may see

It works inside your own role. If you cannot open salaries, neither can it.

Never writes

There is no path from a question to a change. Drafts you confirm are the only way anything is created.

Ask it about your own numbers.

Twenty minutes. We follow one order from the first call to the last payment, on numbers like yours.

Book a demo