How do I calculate run rate with iDBQuery?

Run rate takes recent performance and extrapolates it to a full period, most often annualising a month or quarter of revenue to a yearly figure. It is a quick sense of scale, and iDBQuery computes it transparently from your data.

• You'd ask iDBQuery: 'Annualise revenue from the last three months into a run rate, and compare it to last year's actual.'
• It sums the recent period, extrapolates to a year, and returns the run-rate figure with a chart showing the basis.
• Every input is cited to its source rows, so 'run rate = £6.2m' can be traced to the exact months used.

Run rate is a rough projection, and iDBQuery keeps you honest about it: it shows the SQL and the period used, so you can see whether a seasonal spike is inflating the number. That is why the natural follow-up matters: 'Does the run rate change if I use a seasonally-adjusted base?' or 'Show run rate by product line.' iDBQuery keeps the thread. Because the underlying figures may span billing and finance systems, the one live model unifies them with no pipeline. Use it for quick board and investor context, pair it with a proper forecast for planning, and let the Analyst agent flag when the run rate diverges sharply from the trend, with the rows behind it. It complements moving-average and forecast-vs-actual analysis.