How do I measure sales pipeline velocity with iDBQuery?
Ask iDBQuery 'How fast is revenue moving through our pipeline, using deal count, win rate, average deal size, and sales-cycle length?' It computes pipeline velocity across your CRM stages, returns the trend as a chart, and cites each input back to its source deals.
Pipeline velocity measures how quickly deals turn into revenue, combining the number of open opportunities, win rate, average deal size, and sales-cycle length into a single throughput figure. iDBQuery calculates it and, more importantly, shows what is moving it.
- You'd ask iDBQuery: 'Calculate pipeline velocity this quarter from open deals, win rate, average deal value, and average days-to-close, and compare it to last quarter.'
- It derives each input from your opportunity and stage-history tables, computes velocity, and returns a chart with the quarter-over-quarter change.
- Every component is cited to its source rows, so 'average cycle = 47 days' traces to the specific deals measured.
The payoff is diagnosis. Ask 'Which of the four inputs changed most since last quarter?' and iDBQuery decomposes the movement, keeping context in the thread. Because stage timestamps, deal values, and rep assignments may span a CRM and a finance export, the one live model joins them with no ETL. You can pin velocity to a live sales dashboard, or let the Analyst agent investigate where deals stall longest in the funnel and cite the opportunities stuck at that stage. This is sharper than a static pipeline report because every figure is verifiable, not a rolled-up estimate.
Updated 2026-06-22