Ask in plain English. Get a chart in seconds, and see exactly how every number was built.
Revenue analytics
Production PostgresSaved results. Every tile shows what it got when it last ran.
Net revenue
Monthly, trailing 12 months
Orders
12,847
+11.2%vs the prior 90 days
Average order value
$333.30
+4.0%vs the prior 90 days
Revenue by channel
Quarter to date
Revenue by region
Quarter to date
Connects to what you already run.
01How it works
Connect a source read-only. Ask in plain English. iDash works out the right question to run, and draws a chart you can keep.
Connected. Ready to answer questions.
Point iDash at Postgres, MySQL, SQL Server, ClickHouse, Trino or a spreadsheet. It checks the login, reads what tables you have, and never writes.
Which plans grew fastest in the last six months?
Calculating plan, month, and net revenue
Growth was strongest on Scale, up 34% since February. Starter was flat.
Type the question the way you would ask a colleague. iDash picks from the measures your team already agreed on, instead of guessing.
Refreshed 4 minutes ago
Every Monday 08:00 to #revenue
Keep any chart on a dashboard, put it on a schedule, and let it land in Slack or an inbox. Each one asks its question again rather than showing an old picture.
Pulling data from two places can quietly double a total. iDash counts each record once, and stops when it cannot be sure.
Three things stop an answer cold: conflicting paths in your data, data missing unique records, and questions that would count the same thing twice. You get the explanation, not an inaccurate total.
I cannot answer this safely. Orders and support tickets both repeat per customer, so adding them up in one question would inflate the total. Ask for one at a time.
Verified means iDash calculated the number from your team's standard business definitions. Unverified means it used a direct query fallback, and clearly labels it.
02The product
One surface for the whole loop: ask in plain English, explore with charts, and pin to dashboards.
Sessions persist per project and bind to one data source you choose. Follow-up questions inherit the filters you already set.
How many customers ordered more than once in the last 90 days?
2,314 customers placed a second order in the window, 38% of everyone who ordered.
Split that by acquisition channel.
Sales, finance and the board all ask different questions. None of them should get a different number for the same thing.
Ask the way you would ask a colleague. The questions you come back to every week get saved, and after that the answer is waiting for you instead of sitting in someone else's queue.
All of it runs on the same agreed definitions, so a number means the same thing in a chat, on a dashboard, and inside your own product.
What your team uses
03Comparison
Both alternatives break in the same place. The number is right until someone copies it, joins it, or forgets which filter was on.
Getting an answer
Double counting
Freshness
Knowing it is right
Access
