Free: The Ultimate Sales Forecasting Guide

What's the difference between a weighted forecast and a bottom-up forecast, and do I need both?

A weighted forecast multiplies each deal's amount by its stage probability to produce a number automatically — no human judgment required. A bottom-up forecast is a rep or manager submitting a deliberate call for what they believe will close in a given period. Most mature SaaS teams run both in parallel because the weighted view catches what reps are sandbagging or over-committing, and the bottom-up view captures context the math can't see.

What CRM data do I actually need in place before any of this is worth running?

At minimum, you need close dates, deal amounts, stage data, and next step fields updated within the last 14 days — those four inputs drive the pipeline hygiene scoring framework covered in the guide. If your reps aren't logging activity or updating next steps consistently, your weighted forecast will be garbage and your bottom-up calls will have no baseline to check against. Fix data capture before you build any forecast process on top of it.

Do I need a dedicated forecasting tool, or can I run this process in Salesforce and spreadsheets?

You can run a basic bottom-up process in Salesforce, but the guide is direct about the gaps: Salesforce doesn't support manager adjustment tracking, and spreadsheets have no reliable way to snapshot pipeline changes week-over-week. If you need to track forecast call changes, manager overrides, or deal-by-deal inclusion logic, you'll hit the ceiling of native Salesforce fast and spreadsheets won't hold up under any real scrutiny.

How do I know if my forecast accuracy is actually improving or if I'm just getting lucky?

Track forecast accuracy by rep over rolling periods — not just whether the team hit the number, but how close each individual's submitted call was to their actual closed amount. The guide notes that only 25% of sales teams hit above 75% forecasting accuracy, so that's a reasonable benchmark to work toward. If accuracy is inconsistent rep-to-rep, the problem is usually pipeline hygiene or stage exit criteria, not the forecasting method itself.

Which parts of the forecast process should stay human-led versus being handed off to automation?

The forecast call submission and manager adjustment should stay human — those are judgment calls that carry accountability, and removing humans from them kills the cultural discipline that makes forecasting useful. Automation belongs in the operational layer: locking forecast snapshots, sending hygiene reminders, rolling up numbers across the hierarchy, and flagging deals that haven't had activity in 14-plus days. Use tooling to reduce the admin burden so managers spend their time inspecting deals, not chasing submissions.

How often should we be running forecast reviews, and who actually needs to be in the room?

The cadence in the guide maps it out by role: reps submit calls on Tuesday, managers run deal inspection with reps on Wednesday, and the CRO runs a cross-functional forecast meeting Thursday with RevOps and marketing. RevOps owns Monday analysis and Thursday action item formulation, then chases follow-through on Friday. The right cadence for your team depends on sales cycle length — weekly for SMB with sub-30-day cycles, monthly or quarterly for mid-market and enterprise.