Why should you forecast by month instead of by quarter?
A quarterly number hides the shape of the quarter, and the shape is where the risk lives. Two teams can both project the same quarterly figure while one expects a smooth build and the other expects two thirds of the revenue in the final four weeks. Those are entirely different risk profiles, and only one of them can be rescued in week seven.The pattern is consistent enough to plan around. The third month of a quarter usually closes stronger than the first and second, and Q2 and Q4 tend to run stronger than Q1 and Q3. Most teams know this informally and then build models that ignore it, splitting the quarterly target evenly across three months because the spreadsheet does it automatically.
What rows belong in the monthly template?
Seven rows that reconcile to each other, so an error anywhere shows up immediately.| Row | Month 1 | Month 2 | Month 3 | Source |
|---|---|---|---|---|
| Starting qualified pipeline | $4.2M | $4.0M | $3.6M | Prior month ending balance |
| Pipeline created in month | $1.4M | $1.5M | $1.3M | Marketing plus outbound targets |
| Closed won | $0.9M | $1.1M | $1.8M | Bottom-up deal commitment |
| Closed lost | $0.5M | $0.6M | $0.7M | Historical loss rate applied |
| Slipped to a later month | $0.2M | $0.2M | $0.3M | Historical slip rate applied |
| Ending qualified pipeline | $4.0M | $3.6M | $2.1M | Calculated |
| Coverage against next month target | 3.6x | 2.0x | 1.9x | Calculated |
The reconciliation is what makes this useful. Ending pipeline equals starting pipeline plus created minus won, lost, and slipped. When someone raises the closed-won forecast without adding pipeline, the ending balance collapses and the coverage row goes red. That is the check most single-line forecasts lack.
Where does each input come from?
Created pipeline comes from the demand plan, closed won comes from deal-level commitment, and loss and slip rates come from your own history. The mistake is sourcing all three from the same place, usually a manager's judgment, which makes the model an opinion in spreadsheet form.Loss and slip rates deserve real work. Pull twelve months of opportunities that carried a close date in a given month and check what share actually closed in that month. The answer is usually humbling. Across ORM customers, roughly 20% of the pipeline that carries in-quarter close dates on day one of the quarter closes inside that quarter, which leaves 80% of the visible value unrealized.
That single figure changes how you read a monthly template. If month three shows $1.8M of closed-won forecast against pipeline that was already on the books in month one, the model is assuming a conversion rate your history does not support.
How do you split a quarterly target across three months?
Derive the split from closed-won history by month position, not by dividing by three.| Step | What to do |
|---|---|
| 1 | Pull closed-won revenue by month for at least eight quarters |
| 2 | Tag each month by its position in the quarter: first, second, or third |
| 3 | Calculate each position's share of its quarter |
| 4 | Average the shares across quarters and check the spread |
| 5 | Apply the averaged shares to the current quarter target |
| 6 | Adjust for anything structural, such as a comp plan change or a new segment |
How do you check the monthly forecast against reality?
Compare each month's forecast at the start of that month against the actual result, and keep the series. One month of variance is noise. Six months of variance in the same direction is a modeling error you can correct.Watch for the failure mode that catches most teams. A monthly forecast built on assumptions from an earlier period will hold together right up until something in the market moves. New pricing pressure lowers average deal size. Slower buying decisions stretch the time from qualified to closed. A territory change distracts reps while the pipeline still looks healthy on paper. Each of those breaks a model that was calibrated on last year's conditions, and the model will keep producing confident numbers while it does.
Two specific checks catch the drift early. Compare average deal size in open pipeline against average deal size of closed-won deals, because pipeline that carries $80K average deals while closed-won deals average $40K will miss regardless of coverage. And compare the time from qualified to closed this quarter against the same figure two quarters ago.
What should the monthly forecast never be used for?
Explaining the quarter after it ends. A monthly template that gets updated once at the end of each month becomes a reporting artifact rather than a decision tool.The value comes from knowing the likely shape of the quarter on day one, early enough to change it. Manual processes can reach roughly 90% accuracy on new and expansion business, but they take significant effort to produce and they do not respond as conditions change. ORM targets 95% and holds it from day one to day ninety of the quarter without manual adjustment, updating as the quarter progresses, with a model trained on your own historical performance in four to six weeks.
Build the template either way. It forces the reconciliation logic that makes revenue forecasting inspectable, and it gives you a place to put the numbers whether they come from a spreadsheet or a model. If you are starting from nothing, work through how to create a sales forecast first and then convert the output into the monthly structure above. The definitions behind each row are covered in the sales forecasting glossary entry.
Frequently Asked Questions
Why forecast monthly instead of quarterly?
A quarterly number hides the shape of the quarter. Most B2B SaaS teams close disproportionately in the third month, which means a quarter that looks on track in month two may already be lost. Monthly forecasting shows the gap early enough to act, and it makes pipeline creation targets specific rather than annual.
What rows belong in a monthly sales forecast template?
Starting pipeline, pipeline created in month, pipeline closed won, pipeline closed lost, pipeline slipped out, ending pipeline, and the forecast for the following month. Those rows reconcile, which means an error in one shows up immediately rather than hiding inside a single summary number.
How do you split a quarterly target across three months?
Use your own closed-won history by month position within the quarter, not an even split. Pull three to eight quarters of closed-won revenue, tag each month as first, second, or third in its quarter, and average the shares. Even splits systematically overstate month one and understate month three.
Should the monthly forecast use weighted pipeline?
Weighted pipeline is a reasonable cross-check but a poor primary method for monthly work. Stage weights are averages across long periods, and a single month is too short a window for averages to behave. Use bottom-up deal commitment for the current month and weighted or model-based figures for later months.
How often should the monthly forecast be updated?
Weekly for the current month, monthly for the rest of the year. The current month moves fast enough that a stale figure is misleading within days. Outer months move slowly and reforecasting them weekly generates noise that managers start ignoring.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo