Seasonality Adjustments

Q4 is not the same as Q1. Every B2B company knows this intuitively but most models treat quarters as interchangeable. Budget flush drives Q4 purchasing. Q1 brings new budgets but slow procurement. Summer months suppress enterprise buying committees. These patterns are not random — they are structural, and a forecast that ignores them will overestimate Q1 and Q3 while underestimating Q4 every single year.

1. Calculate Seasonal Indices Take three years of monthly revenue data. Calculate the average monthly revenue. Divide each month's actual by the average. The result is a seasonal index: 1.0 is average, 1.3 means 30% above average, 0.7 means 30% below. Apply these indices to your annual forecast to distribute it monthly. December at 1.4 and January at 0.6 is typical in enterprise B2B.
2. Adjust for One-Time Events Before calculating seasonal indices, remove one-time anomalies: a single large deal that distorted March, a product launch that accelerated June, a pricing change that pulled revenue forward into September. Seasonality should reflect structural patterns, not historical accidents.
3. Validate with Pipeline Data Cross-reference your seasonal forecast with pipeline creation patterns. If Q1 historically generates 20% less pipeline than Q3, your Q2 close numbers will reflect that lag. Pipeline seasonality leads revenue seasonality by one sales cycle length.