Feature · Sales Forecasting Models

Sales forecasting models that fit your business, run side by side.

There is no single best forecasting model. There is a right set of models for a given business shape, cycle length, and history depth. The page below surveys the six model families mature revenue orgs run, where each one earns its seat, where each one breaks, and how Strkr composes them on the live pipeline inside the paid tier.

Start free trial See pricing
The six families

Six model families mature revenue orgs run.

A sales forecasting model is not a single thing. It is a family of approaches, each tuned to a signal and a context. The six families below are what a working revenue org eventually ends up composing, with the conditions under which each one earns its seat. Strkr renders every family on the forecast page side by side, which lets the VP see the agreement across models before committing a number.

Historical model

Last period plus or minus a growth factor.

The simplest model: take the trailing period revenue and adjust by a growth factor (plus 15 percent year-over-year, for example). The model works for stable businesses with steady growth. It breaks on regime shifts (new product, new segment, pricing change) because the past does not inform the future. Useful as a sanity check against more sophisticated models.

Pipeline-weighted model

Stage probability times open amount.

Each open deal gets a stage-based probability from the historical close rate per stage per segment. The weighted amount per deal sums to the forecast. The model is the single most common B2B SaaS forecasting model because it balances rigor and simplicity. It breaks when stages are polluted or when regime shifts invalidate the baseline probabilities.

Time series model

Trend and seasonality on historical revenue.

Statistical models (ARIMA, exponential smoothing, Prophet) extract trend and seasonality from the historical revenue stream. The model works for transactional businesses with high deal volume and stable patterns. It breaks for enterprise businesses with low deal count and lumpy revenue, where seasonality is noise rather than signal.

Regression model

Revenue as a function of leading indicators.

Multivariate regression that predicts revenue from leading indicators: pipeline coverage, meetings booked, demo-to-close conversion, marketing spend. The model works for teams with 2 to 4 years of weekly data and stable business shape. It breaks when the input variables change meaning (demo definition evolves) or when the leading indicators themselves become unreliable.

AI/ML model

Composed signals with explainable scores.

Strkr AI reads the activity timeline, stage history, engagement profile, and firmographic payload to compose a per-deal probability score with the top signals exposed. The model works when signal density is high and history depth is at least 100 closes per segment. It breaks on new segments or regime shifts, which widen the confidence band automatically.

Bottoms-up model

Account-by-account build from the AE.

The AE builds the forecast account by account: which deals will close, which are at risk, which are stretch. The model works for enterprise businesses with low deal count where every deal is a story. It breaks when the team scales past 20 reps and the roll-up becomes a spreadsheet nightmare. Useful as the final layer under more structured models.

How to compare models

Seven dimensions that pick the right model for your shape.

Picking a model is not about picking the most sophisticated option. It is about matching the model to the business shape, the data quality, and the audience. The seven dimensions below are what mature RevOps leads evaluate when standing up a forecasting program. Strkr runs the full set so a team does not have to pick a single model and live with the trade-off.

Data requirement

How much history each model needs.

Historical: 1 to 2 years. Pipeline-weighted: 50 to 100 closes per segment. Time series: 2+ years of weekly or monthly data. Regression: 2 to 4 years of consistent inputs. AI/ML: 100+ closes per segment plus signal density. Bottoms-up: no history needed but requires rep discipline. Pick the model that fits the data you actually have.

Deal volume

High-volume versus low-volume motions.

High-volume (SMB SaaS, transactional, marketplace) favors statistical and ML models that handle large populations. Low-volume (enterprise, services, long cycles) favors pipeline-weighted and bottoms-up because every deal matters and specific context dominates the aggregate pattern.

Cycle length

Short cycles versus long cycles.

Short cycles (under 30 days) favor activity-based ML and statistical models because recent engagement predicts close. Long cycles (90 to 180+ days) favor pipeline-weighted and bottoms-up because the deal review captures context the data cannot see. The right model matches the cycle, not the fashion.

Interpretability

How well the model explains its number.

Historical and pipeline-weighted score high on interpretability (every number traces to a historical base rate). Time series and regression score medium (statistical outputs with coefficients). AI/ML can score low unless the signals are exposed, which Strkr AI does on every score. Boards and CFOs reward interpretability.

Accuracy

Which models land tightest on average.

Based on observed accuracy across Strkr customers: AI/ML composed with weighted stage typically lands tightest (MAPE 5 to 10 percent on mature segments). Weighted stage alone lands at 8 to 15 percent. Historical lands at 10 to 20 percent. Time series lands at 10 to 15 percent on steady businesses. Bottoms-up lands at 5 to 10 percent on low-volume motions with disciplined reps.

Build cost

How much effort to stand up.

Historical and pipeline-weighted stand up in a day of configuration. Time series and regression require a data scientist and 2 to 4 weeks. AI/ML in Strkr stands up automatically with trailing closed data. Bottoms-up requires the sales motion to already run disciplined weekly deal reviews. The build cost shapes which models a team actually runs.

Maintenance

How much upkeep each model needs.

Historical: low (annual review). Pipeline-weighted: medium (quarterly stage recalibration). Time series: medium (seasonal retraining). Regression: high (variable drift requires attention). AI/ML in Strkr: automatic (monthly baseline refresh). Bottoms-up: ongoing (weekly deal review discipline). Pick the model you will actually maintain.

How Strkr composes the models

Eight surfaces that render the model portfolio side by side.

A single-model forecast is fragile. A multi-model forecast is defensible. The eight surfaces below are how Strkr composes the model families on the shared pipeline so the forecast call reads the agreement across models before committing a number. The composition is the point: when four models agree, confidence is high. When they disagree, the disagreement is the agenda.

Model panel

Four methods, side by side on the forecast page.

The forecast page renders rep commit, weighted stage, pipeline coverage, and Strkr AI side by side with the spread shown. When the methods agree within 10 percent, confidence is high. When the methods disagree by 20 percent or more, the forecast call opens with the driver of divergence.

Weighted stage

Stage probability times open amount, by segment.

The weighted stage model renders per rep, per team, per segment, and per product. Each stage carries the segment-specific baseline probability from the trailing 12 to 24 months. The baseline recomputes monthly to track motion changes. The output is the most common B2B SaaS forecast number.

Strkr AI

Composed signals with explainable scores.

Strkr AI reads the activity timeline, stage history, engagement profile, and firmographic payload to compose a per-deal probability score. The score renders with the top three positive and top three negative signals exposed, which keeps the math auditable. Reps who disagree log an override that feeds the next cycle.

Time series

Historical trend and seasonality on booked revenue.

The time series model extracts trend and seasonality from the trailing 24 months of booked revenue. The model runs for transactional and high-volume businesses as a cross-check against the pipeline-weighted number. The output renders on the forecast page alongside the pipeline methods.

Bottoms-up

Rep commit by deal, rolled to the team.

The bottoms-up model aggregates the per-deal rep commit into a team roll-up. The AE commits each deal to a bucket (will-close, likely, best case, upside) and the roll-up sums the buckets. Managers calibrate the roll-up against the Strkr AI median on the Thursday pre-brief.

Confidence band

Range on each model that keeps the forecast honest.

Each model renders with a confidence band (low, median, high). The band widens on noisy pipeline and tightens on seasoned pipeline. New segments produce wide bands. Mid-regime shifts widen bands temporarily. The band is the artifact that lets the forecast call read the number with the right amount of hedging.

Reconciliation report

Why the models disagree and what that means.

When the models disagree by 20 percent or more, Strkr surfaces the driver: stage pollution, regime change, new segment, bias pattern on a rep. The reconciliation report explains the disagreement and lets the VP commit a number with the context, not just the output.

Variance report

Accuracy by model on a rolling four quarters.

The variance report tracks forecast versus actual by model on a rolling four-quarter window. The ops lead sees which models land tightest on which segments and tunes the method composition for the next cycle. The weighted ensemble of models usually outperforms any single model.

How to combine the models

Four composition patterns that outperform single models.

A single model is a point estimate. A composed set of models is a defensible forecast. The four composition patterns below are what Strkr customers run most often, each with a trade-off. The patterns compound because the shared pipeline lets every model read the same data at the same time, which eliminates the reconciliation overhead that breaks multi-model forecasts in other systems.

Weighted ensemble

AI plus weighted stage, averaged.

The most common composition: Strkr AI and weighted stage average to the median forecast. The composition absorbs the strengths of both: AI catches signal density nuances, weighted stage holds the historical anchor. The weighted ensemble typically produces the tightest forecast on mature segments with 2+ years of history.

Hierarchical

Top-down time series plus bottom-up pipeline.

A hierarchical composition uses the top-down time series as the aggregate forecast and reconciles the bottom-up pipeline-weighted forecast against it. When the two agree, confidence is high. When they disagree, the segment driving the gap surfaces for review.

Scenario tree

Base case plus two side cases.

The CRO submits three forecasts: base case (what we expect), bear case (what if the top three deals slip), bull case (what if the top three deals accelerate). The tree lets finance plan for a range instead of a point and surfaces the deals driving the spread.

Segment stratified

Different model per segment.

The enterprise segment runs bottoms-up (every deal is a story). The mid-market segment runs weighted stage plus Strkr AI (the ensemble handles the volume). The SMB segment runs time series (high volume, stable patterns). Different model per segment matches the shape and improves aggregate accuracy.

Every forecasting model family on every paid tier.

Historical, pipeline-weighted, time series, regression, Strkr AI, and bottoms-up compose on the shared pipeline. Side-by-side method view, confidence band, reconciliation report, and variance tracking all ship on every paid tier. Threshold tuning lands on Pro.

Start free trial See pricing
Common questions

What buyers ask about this feature.

What are the main types of sales forecasting models?

The six families mature revenue orgs run: historical (last period plus or minus a growth factor), pipeline-weighted (stage probability times open amount), time series (trend and seasonality from historical revenue), regression (revenue as a function of leading indicators), AI/ML (composed signals with explainable scores), and bottoms-up (account-by-account build from the AE). Each family earns its seat under specific conditions: historical for stable businesses, pipeline-weighted for B2B SaaS, time series for transactional, regression for teams with 2 to 4 years of consistent data, AI/ML for high signal density, bottoms-up for enterprise with low deal count. Mature teams run multiple families side by side and reconcile the spread.

Which sales forecasting model is most accurate?

Based on observed accuracy across Strkr customers, the weighted ensemble of AI/ML and pipeline-weighted typically lands tightest on mature segments with 2+ years of history (MAPE 5 to 10 percent). Pipeline-weighted alone lands at 8 to 15 percent. Historical lands at 10 to 20 percent. Time series lands at 10 to 15 percent on steady transactional businesses. Bottoms-up lands at 5 to 10 percent on low-volume motions with disciplined reps. The accuracy depends heavily on segment stability, cycle length, history depth, and signal density, so a single-number answer is misleading. The right question is which composition fits the business shape, which Strkr renders on the forecast page.

When should I use a statistical sales forecasting model?

Statistical models (time series, regression) fit transactional and high-volume businesses with 2+ years of weekly or monthly data and stable business shape. A SaaS business selling to SMBs through a self-serve motion typically runs time series as the primary model. An ecommerce brand runs time series on booked revenue plus a regression on marketing spend. The models break for enterprise businesses with low deal count and lumpy revenue, where every deal is a story and seasonality is noise. For those teams, pipeline-weighted and bottoms-up outperform. Strkr runs the statistical models alongside the pipeline models so the team sees the agreement, which is where the signal lives.

Should I use an AI/ML sales forecasting model?

An AI/ML model earns its seat when signal density is high (every deal has an activity timeline, stage history, and engagement profile) and when history depth is at least 100 closes per segment. In those conditions, the composed signal typically produces tighter accuracy than any single traditional method. The model breaks on new segments or mid-regime shifts, where the historical pattern does not inform the future. Strkr AI handles those cases by widening the confidence band on affected segments and surfacing the context on the forecast call. Teams that treat the AI model as an input to the forecast call (not a replacement for the call) see model accuracy climb cycle over cycle through the override loop.

Can I run multiple sales forecasting models at the same time?

Yes, and running multiple models side by side is the single most reliable methodology upgrade for a mature revenue org. Strkr renders rep commit, pipeline-weighted, pipeline coverage, Strkr AI, and the time series model side by side on the forecast page with the spread shown. When the models agree within 10 percent, confidence is high. When they disagree by 20 percent or more, the forecast call opens with the driver of divergence (stage pollution, regime change, new segment, rep bias). The reconciliation is the artifact that makes the submitted number defensible to finance. The weighted ensemble of models usually outperforms any single model, which is why mature teams run the composition.

How does Strkr compare to other forecasting model tools?

Dedicated forecasting platforms (Clari, BoostUp, Aviso) overlay their own models on top of the CRM through an integration layer, with per-seat subscription costs on top of CRM spend. The models sit on a snapshot of the pipeline, which lags the live record. Spreadsheet-based models (Excel, Google Sheets) are flexible but drift between the build and the forecast call because the pipeline moves. Strkr runs the full model portfolio on the live pipeline inside the CRM at the pricing shown on the pricing page, with no per-seat add-on and no integration lag. Every model renders with its reasoning, every disagreement surfaces its driver, and the variance report tracks accuracy by model on a rolling four-quarter window.

Related features

Pair this with...

Sales Forecasting Model Sales Forecast Sales Forecasting Methods AI Sales Forecasting Sales Forecasting Techniques Sales Analytics CRM Forecasting

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