Built for sales leaders looking up the sales forecast definition fast

The sales forecast def you came for, and the operating shape that makes the forecast actually useful once a team runs it every week.

A sales forecast is a projection of revenue a sales team expects to close within a defined period, grounded in current pipeline, historical conversion rates, and a stage-weighted methodology. That is the def. The rest of this page is the operating shape: how teams actually run the forecast weekly so the exec deck shows a defensible number.

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

The pains that bring buyers here.

Teams land on the "sales forecast def" lookup for a reason: the current forecast is not working, the exec team is asking harder questions, and the Google Sheet methodology has started falling over. The six pains below are the operating problems that show up right after the definition clarifies.

The def is clear; the operating practice is not

Everyone agrees what a forecast is; nobody agrees how to run it.

The sales forecast def is well-settled: projection of expected revenue over a defined period, grounded in pipeline and historical conversion. Where teams differ is the operating practice: which stages count as commit, how weighting applies, how risk adjustment lands, how the rep view reconciles with the exec view. The def gives language; the operating practice is where the Monday exec meeting lives or dies.

The methodology is informal

The forecast categories live in the RevOps lead's head.

Teams running without encoded methodology have the rules in someone's head: which stages count as commit, which as best case, what the default probability is per stage, how multi-year contracts book, when a judgment override is appropriate. When the RevOps lead takes a vacation, the forecast quality drops. When the lead rolls off the role, the methodology walks out the door. Strkr encodes the methodology in admin configuration so the next lead inherits the full stack.

The forecast number swings week to week

The commit was 2.4M last Friday and 1.9M this Friday.

Forecast volatility week to week is a signal that the methodology or the data is not stable. The number should move incrementally as deals progress; a 500K swing in a week on a 3M quarter signals either a late-stage deal slipped, a stage definition shifted, or a rep updated their commit list without a clear trigger. Strkr's snapshot history makes the week-to-week movement visible and auditable so the VP of sales can trace the deal moves driving the delta.

Historical accuracy is unmeasured

We cannot tell if commit historically hits 70 or 85 percent.

Forecast accuracy improvement requires historical data: when deals in commit stage closed historically, at what percentage, with what cycle time. Teams running the forecast in a Google Sheet that overwrites weekly have no way to measure historical accuracy. The methodology tuning stays guesswork. Strkr preserves weekly snapshots: every Friday's forecast state is a datapoint, and after 2 quarters of accumulated snapshots the accuracy analysis becomes concrete.

The exec read is a quarterly surprise

The forecast said 3.1M in week 10; the quarter closed at 2.4M.

A forecast that confidently predicts 3.1M in week 10 and lands at 2.4M at quarter-close has either methodology drift, data quality issues, or systemic over-forecasting. The exec team loses faith in the number. The CFO starts discounting the forecast with a shadow adjustment factor. Strkr's snapshot history exposes the drift: the week-by-week forecast movement renders a chart that shows where the number slipped and the deals that drove the slip.

The rep forecast and the exec forecast disagree

Reps say 2.3M commit; the exec deck shows 1.7M.

Reps update deals in the CRM. The RevOps lead maintains the exec forecast in a parallel sheet with manual risk adjustments and judgment overrides. The two numbers drift. The Monday exec meeting burns 15 to 30 minutes reconciling. Strkr runs one forecast that both the rep view and the exec view read, with the risk-adjustment and override logs visible to all parties so the reconciliation discussion never starts.

The sales forecast def expanded into working parts

What each part of the def actually means in operation.

The sales forecast def references several concepts: pipeline, period, methodology, weighting, risk adjustment. Each concept has an operating definition that teams need to make concrete. The cards below are the specifics for each.

Pipeline

Open opportunities with amount, stage, and expected close date.

Pipeline is the set of open opportunities with an amount, a current stage, and an expected close date. For forecasting purposes only opportunities with a close date in the forecast period count toward the forecast. Opportunities past expected close are either closed-won, closed-lost, or pushed; the push cycle is where many forecasts drift because deals keep moving forward 2 weeks at a time without a disciplined date reset.

Period

The time window the forecast covers.

Period is the time window the forecast projects over: typically the current fiscal quarter for mid-market teams, the current fiscal month for shorter-cycle motions, or the current fiscal year for enterprise or longer-cycle motions. The period should match the sales cycle length: for a 90-day sales cycle, a quarterly forecast works; for a 240-day enterprise cycle, an annual forecast with quarterly checkpoints works better.

Methodology

The rules that convert pipeline into a forecast number.

Methodology is the rule set that converts pipeline into a forecast: which stages count as commit, which as best case, which as upside, which as omit; what the probability weight is per stage; how discounts affect the amount; how multi-year contracts book. The methodology is the operating decision each team makes; the def does not prescribe it. Common methodologies include MEDDPICC, BANT, commit-best-upside, and calibrated probability.

Weighting

The multiplier applied to amounts by category.

Weighting is the multiplier applied to opportunity amounts based on the forecast category: commit commonly weights at 100 percent (full amount counts), best case commonly weights at 50 to 70 percent (partial amount counts), upside commonly weights at 20 to 30 percent (small amount counts), omit weights at 0 percent (not forecasted). The weighting formula lets the exec read one number that reflects the probability-adjusted expected revenue.

Risk adjustment

The adjustment for historical win rate variance.

Risk adjustment is the additional multiplier applied for historical variance: if the commit stage historically closes at 78 percent (not 100 percent as the weighting assumes), the risk-adjusted commit multiplies by 0.78. The exec reads two numbers: the raw methodology number and the risk-adjusted number. Teams that measure accuracy over time tune the risk-adjustment factors continuously.

Pacing

The ratio of actual to pace target.

Pacing is where the team should be in the period versus where it actually is: days-elapsed divided by total-days-in-period times the period quota equals the pacing target; actual closed won divided by the pacing target equals the pacing ratio. A ratio over 1.0 is ahead of pace; under 1.0 is behind. The pacing metric answers whether the team is tracking to hit without regard to pipeline strength.

Rollup

The aggregation across dimensions.

Rollup is the forecast number aggregated across dimensions: by rep (per-rep attainment), by segment (SMB, mid-market, enterprise), by product line (core, add-on, pro services), by region (NA, EMEA, APAC), by manager hierarchy (team to department to company). The exec picks the dimension for the conversation; the rollup math stays consistent across dimensions.

Snapshot

The preserved state at a point in time.

Snapshot is the preserved forecast state at a point: typically every Friday close of business. The snapshot captures the forecast categories, amounts, stages, and risk-adjusted rollup. Historical snapshots enable accuracy analysis (how did the forecast move week to week within a quarter) and methodology tuning (which stages systematically over-forecast or under-forecast). Teams running the forecast in a sheet rarely preserve snapshots; CRM-native forecasts do by default.

Short-tail vs long-tail: picking the right def

What a "sales forecast def" looks like for each buyer context.

The sales forecast def shifts depending on who is asking: a founder looking up the term for the first time, a RevOps lead running the forecast weekly, a VP of sales presenting to the board, a CFO stress-testing the number. The cards below are each context's working def.

Founder def

The number we tell the board we will land.

For an early-stage founder, the sales forecast def is practically: the number we commit to the board for the quarter, grounded in current pipeline and historical close rates. The founder operates the forecast with a lean methodology: deals above 70 percent probability count as commit, deals 40 to 70 percent count as best case, deals under 40 percent count as upside. The forecast runs in a Google Sheet until the team hits 10 to 15 reps and the maintenance burden forces the move to CRM-native.

RevOps lead def

The methodology-encoded rollup with risk adjustment.

For a RevOps lead, the sales forecast def is: the stage-weighted, risk-adjusted rollup of in-period pipeline against quota, maintained with weekly snapshot history for accuracy analysis. The RevOps lead operates the forecast with full methodology encoding, pacing math, segment and rep rollups, snapshot preservation, and attribution per deal movement. The forecast is the operating artifact for the weekly rhythm.

VP of sales def

The weekly commit the exec team can defend.

For a VP of sales, the sales forecast def is: the weekly commit number the exec team presents to the board, grounded in rep inputs with judgment overrides for risk and upside, defensible at quarter-end against actuals. The VP operates the forecast as the manager of the methodology, the judgment-call owner, and the narrative writer. The weekly rhythm is the forecast cadence; the quarterly review is the accuracy audit.

CFO def

The revenue projection for cash and board planning.

For a CFO, the sales forecast def is: the revenue projection used for cash runway modeling, board updates, hiring plan validation, and investor communication. The CFO reads the forecast with a stress-test mindset: what is the downside scenario, what is the base case, what is the upside, and how has the forecast tracked historically against actuals. The CFO applies a shadow adjustment when the historical accuracy is weak.

How Strkr operationalizes the def

What the native CRM forecast ships for teams past the def stage.

Once a team moves past "what is the sales forecast def" into "we need to actually run one", the operating requirements get specific. The cards below are what Strkr's native forecast ships for teams ready to run.

Stage-to-forecast mapping

Admin configuration for commit, best, upside, omit.

Each pipeline stage maps to a forecast category in admin configuration. The mapping survives role turnover because it lives in CRM state, not in someone's head. Teams running multiple segments (SMB, mid-market, enterprise) with different methodologies configure per-segment mapping.

Risk adjustment from live data

Historical win rate per stage, auto-updating.

The risk-adjustment factor per stage computes from the actual historical win rate observed in the deployment. As deals close, the win rate updates and the risk factor shifts. Teams see the current risk factor inline and can override with a judgment adjustment that logs for audit.

Weekly snapshot history

Every Friday's state preserved.

Strkr snapshots the forecast state every Friday at close of business. Historical snapshots render in the forecast history view and feed accuracy analysis. Teams get real forecast accuracy metrics after 2 quarters of accumulated snapshots.

Pacing math with holidays

Business days, ramp quotas, holiday calendar.

Pacing uses business days by default with admin-configured holidays. Ramp quotas for new hires apply per-period, so a new rep's pacing bar measures against their ramp quota, not the senior rep's target.

Multi-dimensional rollup

Segment, product, region, manager views.

The forecast rolls up by rep, team, manager hierarchy, segment, product line, and region. The exec picks the dimension for the conversation; the rollup math stays consistent across every dimension.

AI-drafted narrative

The exec summary generated for VP review.

Strkr AI drafts the weekly forecast narrative: committed number with change from last week, risk calls on the biggest moving deals, upside on the deals that could expand, pacing commentary. The VP edits for 10 to 15 minutes instead of writing from scratch on Sunday night.

Head-to-head

Running a sales forecast on definition alone vs on native CRM infrastructure.

Teams that start with "what is the sales forecast def" and build a spreadsheet from scratch hit specific operating pains. Teams running CRM-native from day one skip those pains. The comparison below is the head-to-head.

Feature Strkr Spreadsheet-based forecast from the def
Methodology location Admin configuration (survives role turnover) Formulas plus RevOps lead's informal rules
Snapshot history Weekly auto-snapshot preserved Overwrites each week typically
Risk adjustment Live historical win rate per stage Static formula or guess
Rep view vs exec view One number both views read CRM number plus Sheet number plus manual reconcile
Accuracy measurement Native with snapshot comparison Not measurable without snapshots
Multi-year deal handling ARR / TCV / ACV views native Hand-calculated per deal
Pacing math Business days with holidays and ramp Formula in a cell that can drift
Weekly maintenance time 15 to 20 minutes review 2 to 4 hours RevOps time
Methodology turnover resilience Config survives when the lead leaves Methodology walks out with the lead
AI-drafted narrative Native with VP edit VP writes Sunday night
How teams use Strkr

How teams moved from def to working forecast.

The pattern across teams: the first-time VP of sales or founder looks up the sales forecast def, builds a spreadsheet, runs it for 2 or 3 quarters, hits the maintenance ceiling, and moves to CRM-native. The playbooks below are the common shapes.

First-time VP of sales, Series A startup, 12 reps

Googled "sales forecast def", built a sheet, moved to Strkr at quarter 3.

A first-time VP of sales at a Series A startup inherited no forecast infrastructure. The VP looked up the sales forecast def, read a dozen articles on methodology, built a 4-sheet Google Sheet forecast (deal detail, stage mapping, rollup, pacing). The sheet ran for 2 quarters with the VP maintaining it personally every Friday. By quarter 3 the maintenance burden hit 3 hours a Friday and the methodology was inconsistent across the 12 reps. The VP migrated to Strkr's native forecast. The 4-sheet logic encoded in admin in 2 hours. The weekly maintenance dropped to 15 minutes. The VP redirected the recovered time to deal review and rep coaching.

Mid-market RevOps hire, 48-rep team

Took over a 300-formula sheet, moved it to Strkr in 6 weeks.

A new RevOps lead at a 48-rep mid-market B2B services firm inherited a 300-formula Google Sheet forecast that the prior lead had maintained for 2 years. The sheet broke on sort operations, the methodology was undocumented, the historical snapshots did not exist. The new lead spent 2 weeks reverse-engineering the methodology from the formulas, built the equivalent in Strkr's admin surface in week 3, ran parallel in weeks 4 and 5, and cut over in week 6. The forecast accuracy measurable in Strkr's snapshot history gave the lead the data to tune the methodology for the first time since the firm started tracking a forecast.

B2B SaaS founder, 8 reps

Skipped the sheet stage and went direct to CRM-native from the def.

A B2B SaaS founder with prior experience at a larger company looked up the sales forecast def with the goal of avoiding the Google Sheet trap. The founder evaluated Strkr's native forecast capability and configured it on day 2 of CRM setup. The forecast ran clean from the first quarter with 8 reps, encoded methodology, and snapshot history. By the time the team grew to 20 reps the forecast infrastructure was mature and the founder had never maintained a sheet. The CFO cited the forecast quality as a positive factor in the Series B due-diligence conversation.

Enterprise B2B, 180-rep team, head of GTM operations

Standardized the forecast def across 3 regions.

An enterprise B2B team with 180 reps across NA, EMEA, and APAC had three regional forecast methodologies that each regional VP ran independently. The exec forecast required manual reconciliation across the three. The head of GTM operations led a methodology standardization: one shared def, one shared stage-to-forecast mapping, one shared risk-adjustment approach, with configurable regional variants where the business required (longer cycles in EMEA, different stage names in APAC). The project ran 90 days in Strkr's admin surface. The exec reconciliation discussion stopped and the forecast rolled up cleanly across regions.

Services company, 15-rep team

Learned the def, picked quarterly periods, got the exec read working.

A 15-rep professional-services firm had a founder who had never run a formal forecast. The founder looked up the sales forecast def, learned that period length should match sales cycle (the firm's cycle averaged 70 days), and picked a quarterly forecast. The methodology landed as a lean 3-category commit-best-upside with calibrated probability per stage. The forecast ran in Strkr from the first quarter. The CFO (first-time hire 2 quarters later) adopted the Strkr forecast as the single source of truth for cash planning and board updates. The founder credited the def-to-working-forecast journey as a key moment in the firm's operational maturity.

From the sales forecast def to a working weekly cycle.

Start a 14-day Strkr trial with the native forecast: configurable stage mapping, pacing with holidays, risk adjustment from historical win rate, weekly snapshot history, and AI-drafted narrative ready to configure in a day.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What is the shortest working sales forecast def a new VP of sales should start with?

A sales forecast is a projection of revenue a sales team expects to close within a defined period, grounded in current pipeline, historical conversion rates, and a stage-weighted methodology. The practical def for a new VP of sales adds the operating requirements: run it weekly, maintain snapshot history for accuracy measurement, encode the methodology so it survives role turnover, reconcile the rep view with the exec view before the Monday meeting, and tune the risk-adjustment factors based on historical accuracy. The def alone is the opening frame; the operating practice is where the forecast becomes useful. A new VP should start with the def, pick a methodology (commit-best-upside is a solid default), build it in the CRM (not a spreadsheet past the first 2 quarters), and iterate on accuracy as snapshot history accumulates.

How is the sales forecast def different from a sales projection or sales plan?

The three terms get conflated but have operating distinctions. A sales forecast is a near-term projection (quarter or year) of revenue the team expects to close, grounded in current pipeline and historical conversion. A sales projection is commonly a longer-horizon estimate (annual or multi-year) built from top-down assumptions (market size, penetration rate, growth multiplier) rather than bottom-up pipeline. A sales plan is the strategic document (annual) that sets targets, headcount, territories, quota structure, and the operating cadence that includes the forecast. Teams run all three: the plan sets the target, the projection estimates the long-horizon trajectory, the forecast tracks against the plan weekly or quarterly. Mixing them up creates confusion in exec reviews because the def and the operating rhythm differ.

Does the sales forecast def apply the same way for subscription SaaS versus one-time services?

The def is the same; the application differs. For subscription SaaS the forecast commonly tracks new ARR (first-year ratable revenue) separately from total contract value (TCV). The two metrics answer different questions: ARR drives valuation and investor conversations, TCV drives commission and cash forecasting. For one-time services the forecast tracks the contract revenue in the period, with no ratable split. Teams running mixed motions (SaaS plus services plus product sales) commonly maintain multiple forecast views: ARR for SaaS, TCV for services, product revenue separately. Strkr's multi-year deal handling supports both views natively so the forecast reconciles across the motion mix.

What belongs in the forecast def that teams commonly leave out?

Three operating elements commonly missing from informal forecast defs: snapshot preservation (the forecast state at a point in time, so historical accuracy becomes measurable), risk adjustment grounded in historical win rate (not a static probability guess), and multi-dimensional rollup (segment, product, region, manager views that reconcile against the same deal records). Teams that leave these out run forecasts that cannot be measured, cannot be tuned, and cannot be reconciled against the exec deck. The def should include the operating practice, not just the conceptual definition. Strkr's native forecast includes all three by default so teams starting fresh pick up the right practice without having to learn by failing.

How does the forecast def change at different team sizes?

The core def stays the same at every team size; the operating infrastructure scales. For a 5 to 15 rep team the forecast runs cleanly in a spreadsheet or a lean CRM with simple commit-best-upside methodology. For a 15 to 50 rep team the maintenance burden on the spreadsheet becomes a bottleneck and the move to CRM-native pays back; methodology adds risk adjustment and multi-segment rollup. For a 50 to 200 rep team the forecast adds per-segment variants, product-line rollup, deeper risk adjustment, and AI-drafted narrative to support the exec rhythm. For 200-plus rep teams the forecast infrastructure extends to predictive AI (Clari, Aviso) and specialized sales planning (Varicent, Fullcast) layered on top of the CRM-native base. The def frames the activity; the scale determines the infrastructure depth.

What is the fastest path from sales forecast def to a working weekly forecast?

For a team with pipeline already in a CRM, the fastest path runs about 2 weeks: week 1 configures the methodology (define forecast categories, map stages, set initial risk-adjustment factors from historical win rate, configure pacing calendar, set up quota per rep per period); week 2 runs the first weekly cycle with the rep updates landing, the manager review happening, and the exec forecast rolling up to the Friday snapshot. By end of week 2 the team has one working forecast cycle in the books. Over the following 4 to 6 weeks the methodology tunes based on reality (specific stage definitions sharpen, risk factors adjust, judgment overrides pattern), and by week 8 the operating cadence is stable. Strkr's configuration surface is the fastest path from def to working weekly forecast available for mid-market teams.

Also built for

Related audiences.

sales forecast definition 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