Ask in plain English. Trust the answer.
Type the question the way you would say it out loud. Get the chart back in seconds, and see which definition it used.
Which channels drove the most new customers in July?
Organic search brought 1,284 new customers, a third of the 3,891 total. Paid social added 962 at a blended cost of $41.20 each.
New customers by channel
July 2026 · first touch attribution
Where the question actually gets asked.
Not in a planning session. In the meeting, in the thread, on the way to a decision.
Answered in the meeting
Someone asks why the number moved. You ask iDash and answer while the room is still on the slide, instead of promising to find out by Thursday.
Follow-ups keep context
Ask for the split by channel, then by month. Each follow-up keeps the filters from the answer above it, so you refine rather than start over.
No ticket, no queue
Routine questions stop waiting on someone else's calendar. Your data team keeps the definitions and loses the queue of one-off report requests.
Harder maths handled
Cohorts, retention curves and heavier number crunching run as Python in a throwaway workspace that only ever sees the results, never a password to your database.
Net revenue by region
Quarter to date
Why you can trust it
The number is checked before you see it.
Most tools in this space let the model improvise the answer. iDash makes it pick from the definitions your team already agreed on.
Picks from agreed measures
The agent chooses from the measures and breakdowns your team has already agreed on, instead of making up a way to work out revenue on the spot.
Each customer counted once
A customer with twenty orders is still one customer. iDash sorts that out before it adds anything up, so the same sale is never counted twice.
It says when it cannot
When there are two ways to connect your data and they disagree, iDash stops and tells you why. It will not hand you a number it cannot stand behind.
Every answer shows its source
You can see where the number came from and which definition produced it. Nothing arrives unlabelled, so nobody has to take a figure on faith.
The question
What was revenue by campaign last quarter?
Two ways to connect the data
- Through the last ad someone clicked
- Through where their visit came from
Both ways are valid and they give different numbers. Rather than pick one and hand you a total that looks fine, iDash stops and tells you.
How to get an answer
- Ask for one of them by name, for example revenue by last touch campaign.
- Or decide once which of the two should be the default, and it stops asking.
What one question turns into.
An answer is the start. It pins to a dashboard, it repeats on a schedule, and it keeps its context for next week.
Pin it to a dashboard
Any chart in the conversation pins to your project dashboard with its question attached, so the tile asks again against live data instead of ageing.
Threads you can reopen
Every conversation lives in its project and is tied to one data source you choose, named at the top. Pick last week's thread up where you left it.
Send it on a schedule
Turn the question you ask every Monday into a scheduled run that lands in Slack or an inbox, with the chart and the number attached.
Revenue analytics
Saved 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
- Organic search37.0%
- Paid social24.0%
- Email19.0%
- Referral12.1%
- Direct7.9%
Revenue by region
Quarter to date
Ask something you already know.
Connect a read-only copy of your data, ask a question you have the answer to, and compare.