Pipeline questions, answered in the meeting.
The forecast call asks the same six questions every week. Ask them live, from the source, instead of reading a deck built on Friday.
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 weekly pipeline questions.
Same questions every Monday, rebuilt by hand every Monday. The interesting ones are the follow ups nobody has time to run.
What is actually closing
Which deals slipped out of this quarter since last week, and what are they worth? Ask it in the call rather than after it.
Where new customers came from
Which channels drove the most new customers in July, and what did they convert at? Then split it by segment without opening a new tab.
Coverage against quota
How much open pipeline does each region have against target? The follow up, why one region is short, is the part that never gets answered.
Two numbers, one meeting
The CRM export and the warehouse report disagree, and the first ten minutes go on deciding which one the room is going to use.
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 it survives the room
Challenged out loud, and still right.
A pipeline number gets questioned in front of everybody. It has to hold up when somebody asks what is inside it and what is not.
Both sources, one definition
The CRM and the warehouse answer to the same definition, so qualified pipeline means one thing whichever side of the business asks for it.
Three touches, one deal
A deal that met three campaigns shows up three times. iDash brings it back to one line per deal before anything is added up, so attribution never invents revenue.
Exact, or an estimate
Some questions fall outside what iDash can check end to end. It always shows you which answers are exact and which are estimates, so nothing changes quietly mid meeting.
Each rep sees their book
What a person can see is decided by who they signed in as, not by what they typed. One shared dashboard shows every viewer only their own book.
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 changes about the forecast call.
The follow up gets asked
When the pipeline number looks odd, the next question takes a sentence rather than a request, so the meeting ends on a decision.
Monday's view is already built
Pin the pipeline, conversion and channel tiles once. They refresh before the call, and the digest lands in Slack ahead of it.
One number to argue with
Marketing and sales bring the same figure because it comes from the same definition, and the argument moves on to what to do about it.
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
Bring the source to the call.
Connect a read-only copy of the CRM, ask for last quarter's conversion by channel, and check it against the deck you already trust.