A dashboard that is never out of date.
Pinning a chart saves the question behind it. Open the dashboard and every tile asks again, on demand or on the schedule you set.
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
The Monday review, without the rebuild.
The dashboard your team already reads, except every tile can tell you where its number came from.
Pin from the conversation
Any chart in a chat pins in one action, and it carries its question, its filters and the record of where the number came from.
Arranged for the meeting
One dashboard per project, ordered the way your team reads a review: the headline number first, the breakdown under it, detail on request.
Refresh is a re-run
There is no saved picture pretending to be current. Refreshing asks the question again, against live data, under the same read-only access.
Ask a tile a question
Follow a number off the dashboard and back into chat, starting from the tile's own question rather than an empty box.
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
Why you can trust it next month
A wrong number lives longest here.
Nobody re-checks a dashboard tile. So every tile is worked out again each time it runs, with the same care as the first answer.
The question, not a picture
A pin saves the question that produced the chart. Nothing is frozen as an image that nobody can check or take apart.
Checked again every time
Each refresh works the total out from the start, counting each customer once, so a tile cannot quietly drift into a number nobody ever checked.
The source travels with it
The record of where a number came from follows the chart onto the dashboard, so nobody reads a rough answer as an agreed one six weeks later.
A tile can refuse
If your definitions change underneath and the number can no longer be trusted, the tile says so and names the reason instead of showing yesterday's figure.
The question
What was revenue by region last quarter?
- 1Used your definitionNet revenue, the way your finance team already defines it.
- 2Counted each order onceAn order with six items is still one order, so the total is not inflated.
- 3Grouped by regionFollowed the one clear link from an order to the customer's region.
- Only one way to connect orders to regions, so no ambiguity
- Each order counted once, whatever it contains
- Read only connection, capped at thirty seconds
Ask again tomorrow and it runs the same way.
The agent keeps it current.
Between your questions the dashboard is still working: watching thresholds, running on schedule, suggesting the tile you are missing.
Alerts on the metric
Set a threshold on refund rate or pipeline coverage and iDash watches it for you. You hear when the number crosses, and not otherwise.
Delivered where you work
Send the dashboard to a Slack channel or an inbox every Monday at eight, with the chart, the number and where it came from.
Suggested next tiles
The agent proposes the breakdown a reviewer usually asks for next, and adds it when you accept. You approve the addition, not the arithmetic.
Automation
1 trigger · 1 condition · 2 outcomes
Every weekday at 07:00 UTC
Compared with the trailing 4 week mean
#revenue-alerts
No notification sent
Pin your first chart today.
Ask one question, pin the chart, then refresh it tomorrow and watch it ask again.