Built for sales leaders standardizing the sales forecast definition across teams

The sales forecast definition in full taxonomy: types, methodologies, governance, and how to pick the shape that actually fits a team.

A sales forecast is a projection of expected revenue over a defined period, grounded in current pipeline and historical conversion rates. That is the headline. The taxonomy underneath (bottom-up vs top-down, commit-based vs probability-based, deterministic vs predictive) is where teams make the operating choices that decide whether the forecast actually works. This page is the full breakdown.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

Teams looking up the sales forecast definition commonly do so because the current forecast is contested: reps disagree with the exec view, the CFO applies a shadow adjustment, the board questions the number. The six pains below are the governance and methodology problems that drive the definition lookup.

The definition is not shared across functions

Sales says one thing, finance says another, product says a third.

The sales team defines the forecast as the stage-weighted pipeline rollup. Finance defines it as the booked-revenue projection with contractual terms applied. Product defines it as the demand forecast feeding capacity planning. Each definition is correct for its purpose but the three do not reconcile against each other. Exec reviews commonly spend 20 minutes clarifying which number is being discussed. Strkr's native forecast reconciles across the three views: ARR for finance, TCV for commission, segment and product rollup for capacity planning.

The methodology drifts without governance

A rep changed their commit list and the exec saw a 400K swing.

Without encoded methodology governance, reps change their commit list based on judgment and the exec forecast swings weekly. The governance should define: when a deal can move from best case to commit, when a judgment override applies, what evidence is required to upgrade a stage, who approves commit list additions above a dollar threshold. Strkr's native forecast supports the governance in admin: stage transition rules, override logs, approval workflows for high-value commit additions.

The forecast type is not matched to the sales motion

A 240-day enterprise cycle running on a monthly forecast.

The forecast period should match the sales cycle length. A 240-day enterprise motion running on monthly forecasts generates mostly noise: deals in any given month commonly represent the pipeline that will close 2 to 4 months out, not the current month. A 45-day SMB motion running on quarterly forecasts loses signal because the quarter captures 2 full cycles. Strkr supports multiple forecast period configurations (monthly, quarterly, annual, custom) so the period matches the motion.

The forecast lacks a probability framework

Every deal is either 50 percent or 90 percent probability.

Teams without a probability framework default to using the pipeline stage as a crude proxy: discovery is 20 percent, demo is 50 percent, proposal is 70 percent, verbal is 90 percent. The default probabilities rarely match historical reality and the forecast consistently over-forecasts or under-forecasts. Strkr's risk-adjustment layer computes the actual historical close rate per stage so the probability framework reflects reality.

Multi-year contracts break the simple def

A 3-year 300K deal counts how much in which period?

The basic forecast definition assumes a deal lands in a single period. Multi-year contracts break the simple def because the revenue books across years. For ARR the first-year ratable amount counts; for TCV the full contract value attributes to close period; for ACV the average annual value applies. Teams running mixed-term motions need all three views reconciled. Strkr's multi-year deal handling renders ARR, TCV, and ACV from the same contract record so the three views reconcile.

The definition is not shared across tenure

The methodology drifted with each VP of sales.

Over 3 years with 2 VPs of sales and 1 interim RevOps lead, the forecast methodology commonly drifts. Each new leader brings their preferred approach. The historical forecast records become hard to compare because the methodology shifted mid-stream. Strkr's versioned admin configuration preserves the methodology history: which configuration was in force during which quarter, so historical accuracy comparisons remain valid even across leadership transitions.

The sales forecast definition taxonomy

The forecast types and when each fits.

The sales forecast definition splits across several axes: time horizon, methodology, data source, and the governance layer. The cards below are the taxonomy with guidance on when each type fits a team context.

Bottom-up pipeline forecast

Rep inputs rolling up to the exec number.

The bottom-up pipeline forecast is the standard mid-market shape: reps update their deals weekly with stage, amount, close date, and forecast category. The rollup aggregates to team, department, and company. This is the forecast most CRM-native tools default to. The strength is grounding in rep-level data; the weakness is the methodology varies by rep without encoded discipline. Strkr runs the bottom-up forecast with encoded methodology that enforces consistency.

Top-down target forecast

The annual plan broken down to quarterly and monthly.

The top-down target forecast starts with the annual plan (revenue target set during the planning cycle), breaks it into quarterly targets, and then monthly. Reps and managers see their quota at each level. The top-down target is the plan commitment; the bottom-up pipeline is the operating forecast. Teams compare the two to understand pipeline coverage: pipeline divided by target equals coverage ratio.

Stage-weighted forecast

Each stage carries a default probability.

The stage-weighted forecast applies a probability weight per stage: discovery 20 percent, demo 50 percent, proposal 70 percent, verbal 90 percent (specific weights vary). The forecast number is the sum of weighted amounts. The strength is simplicity; the weakness is the default weights rarely match historical reality. Strkr tunes the stage weights with risk adjustment from live historical data.

Commit-based forecast

Reps commit specific deals; the forecast is the commit sum.

The commit-based forecast is the sum of deals reps explicitly commit to for the period. Deals outside the commit list do not count regardless of stage or amount. The strength is operational clarity (reps make specific commitments); the weakness is upside and best case tracking require separate categories. Strkr's commit-best-upside methodology ships this shape with the three categories tracked separately.

Probability-calibrated forecast

Each deal carries a per-deal probability.

The probability-calibrated forecast assigns a probability per deal based on specific factors: stage, cycle length, stakeholder engagement, recent activity, specific risk signals. The probability is per deal, not per stage. The strength is nuance; the weakness is maintaining per-deal probabilities at scale. Strkr supports probability-calibrated forecasts with per-deal fields and automated signals that inform the probability.

Deterministic forecast

Formulas and rules; no model-driven predictions.

The deterministic forecast uses encoded rules and formulas: stage-to-category mapping, weights, risk adjustment from historical win rate. No model-driven predictions. The strength is explainability (every number traces to a rule); the weakness is the forecast cannot incorporate signals the rules do not encode. Strkr's native forecast is deterministic by default.

Predictive forecast

Model-trained probability per deal from historical patterns.

The predictive forecast uses machine-learning models trained on historical deal patterns to generate per-deal probability predictions. Vendors like Clari, Aviso, and People.ai specialize at this. The strength is model-driven signal pickup (deals that match historical slip patterns flag early); the weakness is explainability and model-training requirements. Strkr integrates with predictive tools but does not currently build a deep predictive model in-house.

Hybrid forecast

Deterministic base plus predictive overlay.

The hybrid forecast runs a deterministic base (encoded rules, stage weights, risk adjustment) with a predictive overlay (model-driven probability per deal). The hybrid shape is common at enterprise scale: the deterministic base provides the explainable floor, the predictive overlay surfaces signals the rules miss. Strkr's architecture supports the hybrid pattern when the predictive layer runs via integration.

Forecast methodologies by name

The methodologies teams encode.

Beyond the taxonomy, specific named methodologies have standardized shapes. The cards below are the methodologies most mid-market and enterprise teams use, with guidance on which fits which motion.

MEDDPICC

Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identified Pain, Champion, Competition.

MEDDPICC is a qualification framework that encodes 8 specific criteria. Deals meeting all 8 criteria qualify for commit; deals missing specific criteria route to best case or upside. The methodology fits enterprise motions where multi-stakeholder complexity requires explicit qualification. Strkr supports MEDDPICC as a configurable methodology with per-criteria tracking on the opportunity.

BANT

Budget, Authority, Need, Timeline.

BANT is a 4-criteria qualification framework that fits mid-market motions. Deals meeting all 4 criteria qualify for commit. The methodology is simpler than MEDDPICC and runs faster to configure. Strkr supports BANT as a configurable methodology with per-criteria tracking.

MEDDIC

Metrics, Economic Buyer, Decision Criteria, Decision Process, Identified Pain, Champion.

MEDDIC is the 6-criteria precursor to MEDDPICC. The methodology fits enterprise motions with multi-stakeholder complexity. Teams running MEDDIC commonly consider upgrading to MEDDPICC as the motion matures. Strkr supports MEDDIC as a configurable methodology.

SPICED

Situation, Pain, Impact, Critical Event, Decision.

SPICED is a 5-criteria framework that emphasizes the critical event (what forces the decision by a date). The methodology fits motions where urgency drives close. Strkr supports SPICED as a configurable methodology with the critical event tracked as a dated field.

Challenger / The Challenger Sale

Teach, tailor, take control.

The Challenger methodology is less a qualification framework and more a sales approach. Teams running Challenger commonly layer the approach on top of a MEDDPICC or BANT qualification framework. Strkr supports the Challenger approach via custom fields on the opportunity record and training content attached to the methodology admin surface.

Commit-Best-Upside

The straightforward categorization used by most mid-market teams.

Commit-Best-Upside is the straightforward 3-category framework most mid-market teams default to: commit (high-confidence close in period), best case (reasonable confidence in period), upside (speculative best outcome). The methodology is the default Strkr ships and supports further qualification refinement when teams add MEDDPICC or BANT on top.

Forecast governance by role

Who owns what in the forecast definition.

The forecast definition is not just a document; it is a governance layer with specific role responsibilities. The cards below clarify who owns which piece and how the roles coordinate.

VP of sales

Owns the forecast number and the methodology.

The VP of sales owns the forecast number presented to the exec team and the methodology that produces it. The VP sets the stage-to-forecast mapping, approves methodology changes, applies judgment overrides on specific deals, and owns the quarterly accuracy review. Strkr's admin surface gives the VP the governance tools: stage configuration, override logs, accuracy reports.

RevOps lead

Operates the forecast and maintains the data.

The RevOps lead operates the weekly forecast cycle: pulls the pipeline, applies the methodology, generates the rollups, drafts the exec summary, maintains the snapshot history. The lead also tunes the methodology (adjusts risk factors, refines segment variants) based on accuracy data. Strkr's native forecast makes the operational work mostly automatic; the lead reviews and tunes.

Managers

Review rep forecasts and apply team-level judgment.

Managers review per-rep forecasts in the Thursday pipeline review, apply team-level judgment adjustments (push a stuck deal to best case, pull a progressing deal to commit), and own the team's pacing performance. Managers are the quality gate between rep inputs and the exec rollup. Strkr's manager view shows per-rep attainment, pacing, and open commit list for the review conversation.

Reps

Maintain deal state and category assignments.

Reps maintain the opportunity record: stage, amount, close date, forecast category, risk notes, next step. The rep inputs are the foundation of the bottom-up forecast. Strkr makes the rep input lightweight: inline on the pipeline view, with keyboard shortcuts and bulk-edit support so the maintenance stays under 20 minutes a week per rep.

CFO and finance

Translate the sales forecast to the revenue forecast.

The CFO reads the sales forecast and translates it to the revenue forecast with contractual terms applied: multi-year ratable, deferred revenue schedule, discount timing, specific GAAP treatment. The two numbers reconcile but are not identical. Strkr's ARR / TCV / ACV views make the translation explicit so the CFO and VP of sales work from reconciled inputs.

Exec team and board

Consume the forecast and apply strategic judgment.

The exec team and board read the forecast and apply strategic judgment: whether to accelerate hiring, whether to launch the new product, whether to pursue the acquisition. The forecast is an operating input to strategic decisions, not the decision itself. Strkr's snapshot history gives the exec team the forecast movement over the quarter so the strategic conversation grounds in trend data not just the latest number.

Head-to-head

Encoded forecast definition versus informal methodology.

Teams running the sales forecast definition as encoded admin configuration versus informal spreadsheet methodology see specific operating differences. The comparison below is the head-to-head on the governance and operating dimensions.

Feature Strkr Informal spreadsheet methodology
Methodology location Admin configuration survives role turnover Formulas plus RevOps lead's informal rules
Stage-to-category mapping Admin-configurable per team or segment Hard-coded in formulas
Named methodology support MEDDPICC, BANT, MEDDIC, SPICED, custom One methodology per sheet, difficult to switch
Risk adjustment Live historical win rate per stage Static formula or guess
Governance versioning Historical config preserved Methodology drift across leadership transitions
Override logging Every judgment override logged for audit Informal notes or no logging
Multi-dimensional rollup Segment, product, region, manager Rebuild the sheet per dimension
Accuracy measurement Native with snapshot comparison Not measurable without snapshots
Multi-year handling ARR, TCV, ACV views reconcile Hand-calculated per deal
Governance across roles Role-specific views and permissions Single sheet with uneven access
How teams use Strkr

How teams standardized the sales forecast definition.

The pattern across teams that standardized the definition: define the methodology explicitly, encode it in admin configuration, govern the stage transitions and overrides, measure accuracy with snapshot history, tune based on data. The playbooks below are the motions.

Enterprise B2B, 220-rep team, VP of GTM operations

Rolled out MEDDPICC across 3 regions with encoded admin configuration.

A 220-rep enterprise B2B team ran 3 regions with different informal qualification frameworks: NA used a loose MEDDPICC variant, EMEA used BANT, APAC used a hybrid. The VP of GTM operations led a 90-day standardization project: picked MEDDPICC as the shared methodology, encoded the 8 criteria as fields on the opportunity in Strkr, defined the forecast category gates (commit requires all 8 populated, best case requires 6 of 8, upside requires 4 of 8). The rollout trained reps on the methodology, trained managers on the governance, and ran parallel for a quarter before the hard cutover. Forecast accuracy improved from 71 percent to 86 percent in the following 2 quarters.

B2B SaaS, 65-rep team, head of RevOps

Encoded the Commit-Best-Upside methodology with risk adjustment from live data.

A 65-rep B2B SaaS head of RevOps inherited an informal commit-best-upside methodology where reps assigned categories by gut. The lead encoded the methodology in Strkr admin: stage-to-category defaults, probability weights per category (commit 100 percent, best case 60 percent, upside 25 percent), and risk-adjustment factors from the actual historical win rate per stage. After 2 quarters the risk factors stabilized: commit stage historically closed at 73 percent (not 100 percent), best case at 48 percent (not 60 percent), upside at 15 percent (not 25 percent). The exec forecast became reliably accurate and the CFO stopped applying a shadow adjustment.

Mid-market services, 32-rep team, CFO

The CFO drove the forecast definition standardization.

A 32-rep mid-market services firm had a chronic forecast reliability problem that frustrated the CFO. The CFO initiated the forecast definition standardization: hired a 2-week consulting engagement to define the methodology, picked a lean SPICED approach, encoded it in Strkr, trained the sales team, launched the first governed quarter. The weekly forecast became reliable within one quarter. The CFO stopped applying the 20 percent shadow adjustment that had been standing practice. The sales team gained credibility with the exec team because the forecast number held.

Startup, 12 reps, first-time VP of sales

Picked BANT and encoded it on day 1 of CRM deployment.

A first-time VP of sales at a 12-rep Series A startup used the CRM deployment as the moment to encode the forecast definition. The VP picked BANT as the methodology (simpler than MEDDPICC, appropriate for mid-market motion), encoded the 4 criteria as fields on the opportunity, defined the forecast category gates (commit requires all 4 populated, best case requires 3, upside requires 2). The forecast ran clean from the first quarter. The CFO cited the forecast quality as a factor in the Series B diligence.

B2B hardware, 48-rep team, VP of sales

Switched methodologies mid-tenure after accuracy analysis.

A B2B hardware VP of sales ran BANT for 2 years. Accuracy analysis against the Strkr snapshot history showed BANT delivered 68 to 72 percent forecast accuracy at quarter close. The VP switched to MEDDPICC to pick up the additional criteria (Decision Process, Paper Process, Competition) that BANT missed. The switch happened at the quarter boundary with the versioned admin configuration preserving the BANT era for historical comparison. The following 2 quarters delivered 82 and 86 percent accuracy; the MEDDPICC criteria caught the decision-process complexity BANT had missed.

The sales forecast definition encoded as working CRM infrastructure.

Start a 14-day Strkr trial with the native forecast: named-methodology support, stage governance, risk adjustment from live historical win rate, snapshot history, multi-dimensional rollup, and AI-drafted exec narrative ready to configure.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What is the full sales forecast definition that covers both the concept and the operating practice?

A sales forecast is a projection of expected revenue a sales team will close within a defined period, grounded in current pipeline, historical conversion rates, a stage-weighted or probability-calibrated methodology, with governance for stage transitions and judgment overrides, snapshot history for accuracy measurement, and multi-dimensional rollup across segment, product, region, and manager hierarchy. The concept is simple; the operating practice has the depth. Teams that treat the forecast as just the headline rollup commonly produce an unreliable number. Teams that build out the full operating practice (methodology encoding, governance, snapshot history, accuracy tuning) produce a forecast the exec team can defend. Strkr's native forecast ships the operating practice as default.

How do named methodologies like MEDDPICC and BANT fit into the forecast definition?

Named methodologies are qualification frameworks that gate the forecast category assignment. MEDDPICC qualifies a deal across 8 criteria: deals meeting all 8 qualify for commit, deals meeting 6 of 8 qualify for best case, deals meeting 4 of 8 qualify for upside. BANT qualifies across 4 criteria with similar gating. The methodology shapes which deals land in which category, which shapes the forecast number. Different methodologies fit different motions: MEDDPICC fits enterprise with multi-stakeholder complexity, BANT fits mid-market with faster cycles, SPICED fits motions where urgency drives close. Strkr supports named methodologies as configurable admin surfaces with per-criteria tracking on the opportunity record.

What role does governance play in the forecast definition?

Governance is the layer that keeps the forecast definition stable in operation. Without governance the methodology drifts: reps change their commit list based on gut, managers apply inconsistent judgment overrides, the forecast swings based on who is maintaining it that week. Governance encodes: when a deal can transition between forecast categories, what evidence is required for the transition, when a judgment override applies, who approves overrides above a dollar threshold, how exceptions are logged for audit. Strkr's admin surface supports governance with stage transition rules, override logs, approval workflows, and the audit trail that stands up in diligence conversations.

How does the sales forecast definition differ from the revenue forecast?

The sales forecast is the pipeline-grounded projection of deals closing in the period. The revenue forecast is the accounting-grounded projection of revenue recognized in the period. The two reconcile but are not identical. A 300K multi-year contract closing in Q3 is 300K TCV in the sales forecast and may be 100K in the Q3 revenue forecast (first-year ratable) or distributed across 36 months in the revenue schedule depending on specific contract terms and recognition rules. Finance commonly runs the revenue forecast with the sales forecast as an input, applying contractual term adjustments, deferred revenue schedules, and GAAP treatment to translate TCV to recognized revenue. Strkr's ARR, TCV, and ACV views make the translation explicit so sales and finance work from reconciled inputs.

Can one team run multiple forecast definitions in parallel?

Yes, and most mid-market and enterprise teams do. Common parallel definitions include: the committed forecast (what sales commits to for the quarter), the plan forecast (what the annual plan calls for), the stretch forecast (the upside scenario if everything lands), the risk-adjusted forecast (the committed number with historical win-rate adjustment applied). The exec team reviews multiple views each week to understand the full picture. Strkr supports multiple forecast views natively with the same underlying pipeline data but different methodology configurations applied. Teams see commit, risk-adjusted, and plan reconciliation in one view.

How often should a team revisit its sales forecast definition?

The core definition stays stable; the operating configuration tunes continuously. Specific tuning points: quarterly review the risk-adjustment factors against actual historical win rate (adjust where drift is observed), semi-annually review the methodology (consider MEDDPICC upgrade from MEDDIC or BANT upgrade to a richer framework as motion complexity grows), annually review the forecast period length against sales cycle length (if cycles shortened to 60 days a quarterly forecast may need to shift monthly), and on-event when the business changes materially (new product line launches, new segment enters, major sales reorg completes). Strkr's versioned admin configuration preserves history across tuning cycles so accuracy comparisons remain valid across methodology changes.

Also built for

Related audiences.

sales forecast def sales forecast formula sales forecast template revops vp of sales

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing