Close the month without the rebuild.
Two versions of the same quarter is how a close goes wrong. Ask in plain English, and see exactly what went into the figure.
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
The questions the close turns on.
Finance questions are rarely one number. There is the figure, then the reason behind it, then the version somebody else is holding.
Where the month landed
What was net revenue by entity in July, and how does that track against forecast? The answer splits the way your P&L splits.
Why it moved
Which product lines are behind the drop in gross margin this quarter? Ask the follow up in the same thread instead of rebuilding a pivot.
Two versions, one quarter
Every recut of a figure starts another workbook. By the board meeting there are two answers to the same question and no way to say which is current.
Waiting on an extract
The number is already sitting in the warehouse. The wait for somebody with time to pull it out outlasts the close it was meant to support.
Why the total holds up
A total you can sign off.
One customer with twelve invoices is still one customer. Getting that wrong is how a total quietly doubles, and it is settled before the adding starts.
Counted once, then added
Before anything is added up, iDash reduces the data to one line per customer. A customer with twelve invoices is counted once, not twelve times.
It stops when data disagrees
When there are two ways to connect the data and they give different answers, iDash stops and tells you, rather than quietly picking one.
Every figure keeps its receipt
Open any number and you see the question that produced it, so a board figure can be re-run in front of whoever is asking.
Nothing writes back
The connection is allowed to read and nothing else. iDash can look at the ledger and has no path to change a line of it.
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 close.
A board pack that re-runs
Pin the tiles once. Refresh asks every question again against live data, so the pack is as current as the ledger on the morning you present it.
Variance answered on the spot
When someone questions a line, ask the follow up in the meeting and get the split behind it, instead of promising a note afterwards.
One number, one definition
Revenue, margin and cash mean the same thing wherever they are asked, so the version in the deck matches the version in the thread.
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
Close on numbers you can defend.
Connect a read-only copy of your data, ask for last quarter, and check it against the figure you already signed off.