Forecasting & Deal Inspection Basics
After reading this guide, you will know how to choose a forecasting method that fits your outbound motion, run a structured deal inspection with consistent criteria, and set a weekly cadence that converts CRM snapshots into reliable revenue calls.
TL;DR
The short version
Forecast accuracy for outbound teams breaks at three points: pipeline stages that do not separate active engagement from passive presence, deal inspection questions that rely on rep judgment instead of binary criteria, and a weekly cadence that reviews outcomes instead of leading indicators.
How to choose between commit-based, coverage-ratio, and activity-based forecasting and when each breaks. Four deal inspection criteria that remove rep subjectivity from pipeline reviews. How to structure a weekly forecast cadence around leading indicators, not just CRM snapshots. Which CRM and revenue intelligence tools support native forecasting and deal inspection workflows.
Forecasting Methods
Three forecasting approaches compared
| Method | What it measures | Works best when | Core failure mode |
|---|---|---|---|
| Commit-based | Rep-stated confidence on individual deals closing this period | Reps have strong pipeline discipline and update CRM after every meaningful interaction | Sandbagging or overconfidence skews the number without leaving a data trail |
| Coverage ratio | Total pipeline value as a multiple of quota | Stage conversion rates are stable and stage definitions are consistently applied by all reps | Late-stage stale deals inflate coverage without representing real closes |
| Activity-based | Outreach volume as a leading indicator of future pipeline | Forecasting 60 to 90 days out, before deals enter mid-pipeline stages | Becomes unreliable when activity-to-meeting conversion drops due to targeting or deliverability problems |
Why Forecasts Break
Forecasting & deal inspection basics: where outbound accuracy collapses
Outbound forecasts break because pipeline stages feeding them do not distinguish between a prospect who opened an email and one who asked a pricing question. Both sit in the same stage, so forecast models treat them identically and the coverage number looks healthier than it is.
The second failure point is timing. Most forecast reviews happen weekly against a CRM snapshot that reps updated inconsistently throughout the week. The forecast call becomes a conversation about data gaps rather than a structured revenue discussion.
Before running any coverage-ratio calculation, filter the pipeline for deals with rep activity in the last 14 days. Anything older is a liability on the forecast, not an asset. If your CRM does not surface this filter natively, build a saved view before your next pipeline review.
Deal Inspection
How to run a deal inspection that removes subjectivity from the pipeline
Deal inspection is not a manager review of whether a deal is in the right stage. It is a structured conversation about whether the deal has met specific, verifiable progression criteria before the rep commits it to the forecast.
Four dimensions cover most outbound deals. Run through each in order and record the answer as binary: confirmed or not confirmed. Any deal with two or more unconfirmed dimensions should not appear in the current-period commit.
- Economic buyer access
Has the economic buyer been identified by name and has the rep spoken to them directly? A champion who promises to escalate internally does not satisfy this criterion. The rep must have direct confirmation that the buyer is aware of and engaged in the evaluation.
- Prospect-owned next step
Is the next step in the deal owned by the prospect, not just the rep? A rep who has sent a follow-up email is not the same as a prospect who has committed to completing a security review by a specific date. One is activity. The other is deal momentum.
- Competitive landscape confirmed
Does the rep know whether a competitor is in the deal, and if so, which one? Unknown competitive status at mid-pipeline is a gap, not a neutral condition. A deal where the rep has not asked the prospect about alternatives does not belong in the current commit.
- Timeline stated by the prospect
Was the close timeline stated by the prospect or assumed by the rep? Rep-assumed timelines are the single biggest source of late-stage pipeline inflation. Require a prospect-stated date, confirmed in writing or on a recorded call, before any deal enters the committed forecast category.
Pick a deal value threshold (e.g., anything over 50% of quota) and apply these four criteria to every deal above it in the same weekly meeting slot. Consistency matters more than the exact question set. A team that applies a simpler framework every week will outforecast a team using a sophisticated model applied irregularly.
Forecast Cadence
How to build a forecasting & deal inspection cadence that uses leading indicators
A forecast cadence is a recurring meeting structure that converts CRM data into a directional revenue call. The mistake most teams make is structuring the cadence around lagging indicators, reviewing what closed or slipped last week rather than what is about to enter or exit each stage.
Three meeting slots cover most outbound team setups without adding significant overhead. Each slot has a different job: one monitors activity output, one reviews deal progression, one produces the committed forecast number.
- Daily SDR standup (10 minutes): activity and blockers
Review outbound volume metrics from the previous day: sequences started, calls attempted, replies received. The goal is catching activity shortfalls before they compound into pipeline gaps 30 to 60 days out. This is the earliest leading indicator available.
- Weekly pipeline review (30 minutes): deal inspection by stage
Apply the four-criterion inspection framework to every deal in SQL and Active Opportunity stages. Flag stale contacts in earlier stages for archival or re-engagement. Output: an updated list of committed deals with confirmed criteria, and a list of at-risk deals with a defined next step and owner.
- Monthly commit review (45 minutes): forecast call by team
Roll up the weekly inspection outputs into a team-level forecast call. Compare the current coverage ratio against the target multiple for the period. The commit number should reference only deals that passed the four-criterion inspection. Anything else goes into the upside or pipeline category, not the commit.
Daily activity metrics are leading indicators: they predict pipeline health 30 to 90 days out. Stage conversion rates are lagging indicators: they explain what already happened. A forecast cadence that uses only lagging indicators catches problems after they have already damaged the quarter. Build both into the rhythm, not just the weekly pipeline review.
Recommended Tools
Tools that support forecasting and deal inspection natively
Gong, HubSpot Sales Hub, Salesforce, and Pipedrive all support some form of native forecasting or deal inspection. The key differences are in how much the tool surfaces deal risk automatically versus requiring manual manager review.
Common Questions
Frequently asked questions
Most outbound teams target 3x to 4x coverage against quota in the current period. The right multiple depends on your stage-to-close conversion rate. If your SQL-to-close rate is below 30%, a 3x coverage ratio is likely insufficient and closer to 5x is a safer buffer.
Weekly for deals in SQL and Active Opportunity stages. Bi-weekly for deals in Meeting Booked that are not yet past their scheduled date. Any deal that misses two consecutive inspection cycles without a documented next step should be marked at-risk and reviewed separately before it reaches the commit forecast.
A commit is a deal the rep is highly confident will close in the current period based on confirmed criteria: economic buyer access, a prospect-owned next step, and a prospect-stated close date. Upside is pipeline that could close but lacks one or more of those confirmations. Both categories belong in the forecast call, but only commits inform the official revenue call number.
Yes, but the sample size needs to be sufficient to produce reliable conversion rates. A team of two or three reps will have too much variance in week-to-week activity output to build a statistically meaningful model. Activity-based forecasting becomes reliable when a team has at least 6 to 8 months of consistent tracking data and a minimum of 5 to 6 active reps.
Start with the four-criterion inspection framework in this guide applied to every deal above your average deal size. For the forecast, use a simple coverage-ratio calculation: total pipeline value in SQL and Active Opportunity stages divided by remaining quota for the period. Both are practical without requiring a dedicated tool beyond a CRM with custom stage configuration.
Need a CRM that supports your outbound forecast model?
Compare CRM and revenue intelligence tools by forecast capability, deal inspection support, and outbound fit.