What ASKIQ costs depends almost entirely on which systems it has to read, and a bespoke internal database is a different proposition from a standard accounting connector. Publishing a figure that then moves in the first conversation would waste your time. What follows instead is the shape of the arrangement and exactly what moves the number, so you can judge whether it is in your range before you write to us.
One department, a handful of systems, a fixed scope and a fixed fee.
The whole business asking, across every system worth connecting.
Runs entirely inside your environment, on your infrastructure.
Four things, in roughly the order they matter.
A standard connector to a common platform is quick. A bespoke internal database takes longer, and that difference is most of the variation between two quotes.
A finance team of six and a company of six hundred are different propositions, though the per-person cost falls sharply as the number rises.
Hosted by us is the simplest. Your own cloud tenancy adds setup. Fully self-hosted adds deployment and support arrangements.
Your vocabulary and reporting rules are included. A large curated question set, or connectors written specifically for your in-house systems, is scoped separately.
Sources are read in place with read-only credentials and nothing is migrated. It can be hosted for you, run inside your own cloud tenancy, or self-hosted entirely. Your data is never used to train a model.
No. It reads through your existing permissions, so a person sees only what they could already open in the underlying system. It does not widen access, and every question is logged.
Every answer names the systems it read, the row counts and the timings, and shows the query where one was run. An answer you cannot trace is one you should not trust, so tracing is built in rather than offered.
Connectors go in first and the first questions are answered the same week. A curated question set for your business means day one is useful rather than a blank prompt.
The six in the demo are illustrations, not a product list. The connectors are generic and the questions come from your own data, so the sector only decides which systems get plugged in.
They need to be able to type a question. That is the whole interface, which is the point of building it as a chat rather than another dashboard nobody opens.
A list of the systems you would want it to read is enough to get a real number back. If a pilot makes more sense than a quote, we will say so.