A framework for B2B SaaS leaders who need to forecast organic growth in pipeline terms — not traffic terms.

Most SEO forecasts follow the same formula: take a keyword's search volume, multiply by an estimated click-through rate, and present a traffic number that makes everyone feel good but means nothing to the business.
The problem isn't the math. It's the starting point.
When you start with keywords, you end with traffic. When you start with your revenue model, you end with pipeline.
Your CFO doesn't care that you'll get 5,000 more organic sessions next quarter. They care whether those sessions will generate enough pipeline to justify the investment — and when.
That's what this framework does. It works backwards from your deal economics and maps keyword opportunities to actual revenue potential. No vanity metrics. No fictional traffic numbers.
Before you forecast anything, you need four numbers from your current data:
That last number is the one most teams don't know. If you can't answer it, your forecast is already built on sand. Check your CRM attribution data. If it's not set up, that's job one — before any forecasting happens.
Search volume tells you how popular a query is. It tells you nothing about what it's worth to your business.
Instead, score each keyword opportunity on three dimensions:
Here's a practical example. Say your SaaS product has an average deal value of €50K ARR. A keyword that brings 10 visitors per month at a 5% conversion rate to demo request is worth €25K/month in pipeline potential. That's true whether the keyword has 50 or 5,000 monthly searches.
The keyword with 5,000 volume and zero buyer intent? Worth nothing to your pipeline.
Never present a single forecast number. Present three:
Conservative — You rank positions 6-10 for target keywords within 6 months. Use a 2-3% CTR (adjusted for AI Overviews). Assume no improvement in conversion rates. This is your floor.
Realistic — You reach positions 2-5 within 6 months, top 3 within 9. Use a 5-8% CTR. Factor in a 15-20% conversion rate improvement from landing page optimization. This is what you plan for.
Ambitious — You hit position 1-2 within 6 months and capture featured snippets. Use a 10-15% CTR. Assume conversion rate gains from both page optimization and increased brand trust. This is your stretch target.
For each scenario, multiply: monthly visitors × conversion rate × MQL-to-SQL rate × close rate × average deal value = monthly pipeline contribution.
Pro tip: you can also map your CTR data based on your own GSC property.
Organic conversions
80/mo
234/mo
Low-Intent Pages
400+
<120
Indexed Pages
3,200
1,500
Indexed Pages
3,200
1,500
Indexed Pages
3,200
1,500
Indexed Pages
3,200
1,500
Based on a €50K average deal value, 20% MQL→SQL, 25% close rate. Adjust to your own numbers.
This is the step nobody else includes, and it's the most important adjustment for 2026.
Google's AI Overviews are changing click-through rates dramatically — but not equally across all queries. Here's how to adjust:
High impact (discount 30-50%): Definitional queries ("what is SEO forecasting"), simple how-to queries, and any question Google can answer directly in the AI Overview. These queries still have value for brand awareness, but clicks are dropping.
Medium impact (discount 10-20%): Comparative queries ("best SEO forecasting tools"), methodology queries. Users see the AI Overview but still click through for depth.
Low impact (discount 0-10%): High-intent commercial queries ("SEO consultant for B2B SaaS"), complex problem queries, and anything requiring personal context. These are your money keywords — AI Overviews can't replace the need to evaluate and engage.
Apply these discounts to your three scenarios. A realistic forecast that accounts for AI Overviews is far more credible than one that ignores them.
The final step is the one that matters most: convert your forecast into an investment case.
Your one-page business case needs four numbers:
Present it as: "For an investment of €X over 9 months, we project organic to contribute €Y–€Z in annual pipeline, with breakeven expected at month 5-7."
That's a sentence a CFO can act on. "We'll increase organic traffic by 40%" is not.
This is exactly what the SEO ROI Calculator automates. Input your baseline metrics, deal economics, and keyword targets — it runs all three scenarios and gives you the pipeline projections. No spreadsheet required.
👉 Try the SEO ROI Calculator
If your forecast model hasn't been updated since 2023, your CTR assumptions are wrong.
This is actually good news for B2B. Your highest-value keywords (the ones closest to a buying decision) are the least affected by AI Overviews. Your forecast should reflect that: discount the top-of-funnel informational keywords more aggressively, and be more confident in the bottom-of-funnel commercial ones.
I'm seeing 15-40% CTR drops on informational queries where Google now shows AI Overviews. But commercial and transactional queries? Barely affected. The searcher who types "SEO consultant for Series B SaaS" isn't satisfied by an AI-generated summary — they need to evaluate, compare, and engage.
Company: B2B SaaS/FinTech, Series A → Series B
Challenge: Organic traffic was growing, but conversions had stalled. The team was producing content, but none of it was connected to buyer intent. Paid CAC was €380 and climbing.
What we did: Applied this exact framework. Audited the baseline, discovered that 0% of pipeline was attributed to organic (it was all "direct" in the CRM — a common attribution problem). Mapped keywords to buyer intent stages. Built three scenarios. Focused execution on the 20% of keywords driving 80% of pipeline potential.
Results in 6 months:
The forecast predicted breakeven at month 5. Actual breakeven: month 5.
Revenue-first forecasting beats traffic-first guessing.
Three scenarios always — one number is a guess, three is analysis.
Pipeline language gets CFO buy-in. Traffic charts don't.
See what your organic channel could contribute to pipeline, in 5 minutes, with real numbers.

The classes and uneasiness, his ticking service, what something it bear extended had sooner sort we're of one possible to found switching the h.

The classes and uneasiness, his ticking service, what something it bear extended had sooner sort we're of one possible to found switching the h.

The classes and uneasiness, his ticking service, what something it bear extended had sooner sort we're of one possible to found switching the h.