Forecast vs. Actuals: The Quarterly Review
Floryn 
Backbase 
Insify 
Mollie - The forecast isn't a one-time business case. It's a management tool that gets recalibrated every quarter.
- Present actuals against the scenario band, not against a single-point estimate. 'Actuals landed in the upper half of our conservative-to-baseline range' is more useful than 'we missed by 15%.'
- First-quarter accuracy will be off by 30-40%. That's expected and you should say so upfront. By Q3, calibrated models typically land within 15%.
- The track record is the asset. Three quarters of forecast-vs-actuals data earns expanded budget without re-arguing the business case.
You funded the first two segments. Content is live. The MQL Prediction Model projected 35-55 MQLs per month by month 6. It’s now month 6. How do you run the review?
This is where most organic programs lose their credibility. They build a business case, get the budget, produce the content, and then revert to reporting traffic and rankings. The forecast that earned the funding quietly disappears from the dashboard. Six months later, when the CMO asks “did organic deliver what we projected?”, nobody has the comparison ready.
The forecast-vs-actuals review is the mechanism that prevents this. It’s how organic proves it’s becoming a predictable channel, and it’s how the model improves from rough estimates to calibrated projections that leadership can actually plan around.
The quarterly review structure
Section titled “The quarterly review structure”This isn’t the team-level diagnostic conversation (your Head of Growth runs that monthly using the prioritization framework). This is the board-level review: what you present to your CFO or leadership team once per quarter.
Four sections. Fifteen minutes. No traffic charts.
1. Forecast vs. actuals by segment
Section titled “1. Forecast vs. actuals by segment”Present the scenario band (conservative to optimistic) and where actuals landed within it. Not “we hit 42 MQLs against a forecast of 45.” Instead: “Actuals landed at 42 MQLs, in the upper half of our baseline-to-optimistic range of 35-55.”
The scenario band is what makes this credible. A single-point estimate invites a pass/fail judgment. A range invites a calibration conversation. “We landed in the lower half of the range, here’s why, and here’s what we’ve adjusted” is a productive conversation. “We missed the target by 15%” is not.
2. Which assumptions drifted and why
Section titled “2. Which assumptions drifted and why”Keep this to the one or two assumptions that had the largest impact. Not a spreadsheet walkthrough. The board doesn’t need to know that your CTR assumption for position 4 was 8% but observed was 6.5%. They need to know:
“Traffic matured slower than projected for the healthcare segment. Our model assumed 50% of steady-state traffic by month 3; actual was closer to 35%. This is consistent with the competitive density of healthcare keywords. We’ve adjusted the maturity curve for this segment, which pushes the steady-state projection from month 6 to month 8.”
One paragraph per material drift. Cause, effect, what you changed. That’s it.
3. Updated projection
Section titled “3. Updated projection”Present the recalibrated forecast for the next quarter. The key difference from the original forecast: this version is built on observed data, not estimates.
The original forecast used industry-benchmark CTR curves and estimated conversion rates. The recalibrated version uses your actual CTR curve (from 6 months of GSC data) and your actual conversion rates (from CRM attribution). The projection is tighter because the assumptions are grounded.
Show the updated scenario band alongside the original one. The band should be narrower. A narrowing band is visual proof that the model is getting more accurate.
4. Investment recommendation
Section titled “4. Investment recommendation”Close with one of three recommendations:
- Continue: Actuals are tracking within the scenario band. The investment thesis holds. No changes needed.
- Expand: Actuals exceeded baseline. The segment is performing. Recommend starting the next segment cluster. Include the projected MQL contribution from the new segment using the calibrated model.
- Adjust: Actuals fell below the conservative scenario. Diagnose whether the issue is structural (segment doesn’t have the demand we assumed) or executional (content was published late, technical issues blocked indexation). Recommend specific corrective action.
How forecast accuracy builds trust
Section titled “How forecast accuracy builds trust”Set expectations upfront. When you present the initial forecast, say explicitly: “First-quarter accuracy will be rough. We’re estimating CTR and conversion rates from benchmarks, not from observed data. Expect 30-40% variance. By Q3, we’ll be working with calibrated assumptions and the variance will narrow to 10-15%.”
This does two things. It inoculates you against the Q1 miss (leadership was warned). And it creates a measurable improvement narrative. Each quarter, the model gets more accurate, and that accuracy improvement is itself evidence that the program is maturing into a predictable channel.
The progression:
Q1 review: “We projected 35-55 MQLs. Actual was 28. We identified two assumptions that drifted: maturity speed was slower than modeled, and TOFU conversion was lower than estimated. We’ve recalibrated both.”
Q2 review: “Updated model projected 40-52 MQLs. Actual was 44. Maturity curve correction was accurate. Conversion rate is stabilizing. Variance is down to 12%.”
Q3 review: “Model projected 43-50 MQLs. Actual was 46. We’re within 7% of baseline. Recommending we start the logistics segment cluster using calibrated assumptions from healthcare.”
By Q3, you’re not arguing the business case anymore. You’re presenting a track record. And a track record that shows improving accuracy is more persuasive than any forward-looking projection.
When actuals miss badly
Section titled “When actuals miss badly”If actuals fall significantly below the conservative scenario, the response depends on the cause. Three categories:
Timing issue. Content matured slower than projected. This is the most common miss and the least concerning. The demand exists, the content is ranking, but the maturity curve was too aggressive. Adjust the curve, extend the projection timeline, and show that the slope of improvement is positive even if the timeline shifted. Board recommendation: continue with adjusted timeline.
Structural issue. The segment doesn’t have the search demand the model assumed, or competition is denser than estimated. This is a more serious miss because it suggests the segment selection was wrong, not just the timing. Board recommendation: assess whether the segment should be deprioritized in favor of one with better fundamentals, or whether the content needs repositioning to capture different keyword intent within the segment.
Execution issue. Content wasn’t published on schedule, technical problems blocked indexation, or the content quality didn’t meet the standard needed to rank. This is an operational failure, not a model failure. The model’s assumptions may be correct; the inputs just weren’t delivered. Board recommendation: fix the execution gap and reassess at next quarter. Don’t recalibrate the model for execution failures.
The diagnostic distinction matters because each category has a different board-level response. Timing adjustments maintain confidence. Structural issues require strategic decisions. Execution failures require operational fixes.
The compound trust effect
Section titled “The compound trust effect”After 3-4 calibration cycles, something shifts in how leadership views organic.
The first forecast was a pitch. “Here’s what we think organic can produce if you fund it.” Leadership approved it with skepticism and an implicit “prove it.”
After four quarters of forecast-vs-actuals reviews, with calibration improving each time, the forecast is no longer a pitch. It’s a planning input. Leadership uses it the same way they use pipeline forecasts from sales or lead projections from paid: as a credible, calibrated estimate they can plan around.
That’s when organic earns expanded budget without a new business case. You’re not asking leadership to fund an experiment. You’re asking them to fund more of something that’s already producing predictable returns. The quarterly review is what makes that transition possible.
Without the review cadence, organic stays an experiment indefinitely. With it, organic becomes infrastructure. The forecast is the tool. The quarterly review is the proof.
What you need before the first review
Section titled “What you need before the first review”CRM attribution by channel and segment. If you can’t answer “how many organic MQLs from the healthcare segment this month?”, the review has no data to present. Build the attribution first.
The MQL Prediction Model running for at least one segment. The review compares forecast to actuals. You need both. If you don’t have the forecast model yet, start with the full model mechanics.
A baseline of 3 months of data. The first review is most useful at month 3 (when the maturity curve should show meaningful ramp) or month 6 (when the first segment approaches steady state). Reviewing at month 1 produces nothing useful.
The full CMO reading path
Section titled “The full CMO reading path”This chapter is the final piece of the CMO cluster. Here’s the logical reading order, though you can start anywhere:
- SEO as a Revenue Channel — the structural argument for why organic belongs in the pipeline conversation
- ABM SEO vs. Traditional SEO — what changes when content is organized by segment
- Channel Economics — how organic CAC compares to paid, and when the crossover happens
- The MQL Prediction Model — the forecast mechanics
- Forecast vs. Actuals (you are here) — the quarterly review that keeps the forecast honest
Get notified when new chapters publish
Summarize with AI
