Feature · Sales Forecasting Examples

Sales forecasting examples that show the real math, not a vibe.

Below are six worked sales forecasting examples by business shape. Each one shows the pipeline, the method, the arithmetic that produces the number, the reconciliation between methods, and the line a Strkr customer runs. Not generic templates. Real numbers you can paste into your own spreadsheet or read into Strkr and verify.

Start free trial See pricing
Six worked examples by business shape

The pipeline, the method, the arithmetic, the final number.

Every forecast lives inside a business shape. A B2B SaaS forecast and a transactional ecommerce forecast use different methods because the shape of the pipeline is different. The six examples below walk through the real math on realistic pipelines. Each example calls out the primary method, the arithmetic that produces the number, and where Strkr runs the forecast as a working customer flow. Numbers are illustrative but shaped against observed customer patterns.

B2B SaaS

12-deal pipeline, weighted stage forecast.

A B2B SaaS AE has 12 open deals totaling 1.4 million. Stage 3 at 30 percent close rate (4 deals, 400K) weights to 120K. Stage 4 at 55 percent (5 deals, 600K) weights to 330K. Stage 5 at 80 percent (3 deals, 400K) weights to 320K. Weighted forecast: 770K. Strkr AI median: 745K. The AE commits 740K and lands at 760K.

Services firm

Project pipeline, confidence-weighted close.

A consulting firm has 8 open projects at various scopes. Three signed statements at 100 percent (420K). Two at 75 percent (300K pipeline, 225K weight). Three at 40 percent (240K pipeline, 96K weight). Weighted forecast: 741K. The partner commits 720K and lands at 735K after a 15K scope expansion.

Transactional ecommerce

Time-series forecast on historical traffic.

An ecommerce brand forecasts Q4 revenue using 24 months of transactional history. Trend plus seasonality produces 4.2 million. Marketing spend lift (new paid channels at 15 percent uplift) adjusts to 4.8 million. The forecast reconciles against the paid pipeline and lands at 4.7 million. Strkr tracks the variance weekly.

Marketplace

Supply-side forecast times demand-side activation.

A two-sided marketplace forecasts GMV from supplier onboarding velocity, listing count, and demand-side activation rate. 400 new suppliers at 85 percent activation yields 340 active. Each active supplier averages 2,100 in trailing 90-day GMV. Forecast: 714K monthly GMV, plus or minus a 60K confidence band.

Mid-market B2B

Three methods, side-by-side reconciliation.

A 50-rep mid-market team runs three methods side by side. Rep commit: 8.4M. Weighted stage: 9.1M. Strkr AI: 8.9M. The spread of 700K between commit and weighted triggers a deal review. The VP commits 8.8M, best case 9.4M. Final attainment: 9.0M, which lands inside the band.

Enterprise with multi-year deals

ACV-weighted forecast with multi-year committed revenue.

An enterprise AE has 4 open deals: 1.2M ACV at 80 percent, 800K ACV at 50 percent, 2.0M ACV at 30 percent, 450K ACV at 95 percent. Weighted ACV: 2.0M. Two of the four are 3-year deals producing 4.8M TCV. Finance reads ACV. The board reads TCV. Strkr renders both.

Three scenarios every forecast meets

What the examples look like when the quarter changes shape.

A forecast meets specific scenarios across the quarter. A deal slips. A new segment lights up. A pricing change invalidates the baseline. The three scenarios below walk through what happens inside Strkr when the quarter deviates from the plan, with the real adjustment math. The pattern is the same across customers because the forecast rhythm already treats deviation as the common case, not the exception.

Scenario 1

A late-stage deal slips to next quarter.

Week 10 of Q3: a 450K deal in Stage 5 (80 percent weighted) pushes close to Q4. The weighted forecast drops by 360K. The AE commit drops by the full 450K because the deal was commit. Strkr AI confidence band widens on the segment. The VP covers the gap by raising coverage on the top 10 Q3 deals. Final gap closes at 90K short.

Scenario 2

A new vertical lights up mid-quarter.

Week 6 of Q3: three deals in a new healthcare vertical land in the pipeline totaling 1.2M. The historical baseline has no healthcare analogs so Strkr AI scores the segment with a conservative prior and a wide confidence band. The AE commit reflects the full 1.2M. Finance plans against the median (720K) with the band flagged.

Scenario 3

A pricing change breaks the historical baseline.

Mid-Q2: the product team ships a 25 percent price increase on enterprise plans. The historical win rate baseline reflects the old pricing. Strkr admin flags the pricing event, which widens the confidence band on enterprise deals and surfaces the context on the forecast call. The team runs on wide bands for the first two quarters until the new baseline settles.

How Strkr renders the examples live

Seven surfaces the examples compose into.

The examples above sit on paper. Inside Strkr, the examples render on live surfaces every forecast role actually uses. The seven surfaces below are how the forecast examples compose into a working motion. Each surface reads from the shared record store so the AE view, the manager view, and the VP view all see the same number without a reconciliation meeting.

Pipeline grid

Every deal with amount, stage, close, weight.

The pipeline grid renders every open deal with the amount, the stage, the close date, the owner, the AI probability, and the weight. The AE sorts by weight to see the deals contributing most to the forecast and works those first. The grid filters by segment, product, close month, and owner.

Commit view

The low-median-high range for the window.

The commit view renders the forecast range (low, median, high) for the current window with the method composition shown. Rep commit, weighted stage, pipeline coverage, and Strkr AI render side by side so the VP reads the method agreement before submitting the final number.

Deal probability

Per-deal score with the top signals shown.

Each open deal carries a win-probability score with the top three positive and top three negative signals exposed on the card. Reps who disagree log an override with a reason code, which feeds the model feedback loop. The next cycle scores closer to team reality.

Risk flag list

Deals that threaten the window.

Deals with elevated slippage risk surface on the risk list: close date in a stage with low historical fit, engagement declining, decision-maker exited the account, late-stage velocity below segment median. The weekly deal review opens on the risk list.

Method reconciliation

The spread between methods, inline.

The spread between rep commit, weighted stage, pipeline coverage, and Strkr AI renders inline on the forecast view. When the methods disagree by 20 percent or more, the forecast call opens with "why do the methods disagree?" and the answer is the driver.

Variance report

Last-quarter accuracy by rep, segment, method.

The variance report shows commit versus actual on a rolling four-quarter window by rep, segment, product, and method. The ops lead flags drivers of drift and feeds the override loop that tightens the next cycle. The report is the quarterly accountability artifact.

Board export

The quarterly deck page with reasoning.

The quarterly board export renders the forecast confidence band, the segment baseline, the method composition, and the plain-language reasoning from Strkr AI. The CFO and the CEO read the deck knowing the math, not just the number, which keeps the board conversation on the right question.

Finance plan feed

Booked revenue export to the operating plan.

The finance plan feed exports the booked revenue number by period with the confidence band and the segment breakdown. The CFO reads the number and the context in the operating plan. Finance plans built on Strkr forecasts hold up better because the context travels with the number.

How the examples run on a Monday

Four weekly rhythms the worked examples drop into.

The worked examples above are not static. They live on a weekly rhythm that compounds the signal cycle over cycle. The four rhythms below are how a mid-market revenue org runs the forecast on top of Strkr. Each rhythm lives on the same page the examples compose on, which keeps the number consistent across cycles.

Monday forecast call

Reps commit against the band, not a point.

The AEs submit commit against the forecast confidence band. Managers see the delta between rep commit and Strkr AI median. A commit above the model high triggers a review conversation. The call runs on shared risk instead of a dueling spreadsheet. The call closes in 20 minutes.

Mid-week deal review

Risk flags focus the coaching hour.

The weekly deal review opens with the risk flag list. Deals with elevated slippage risk get the coaching time. Deals in the 40 to 70 probability band get a lift-focused pass. The 80-plus band gets a close-plan check. The hour of coaching time goes to the deals that benefit most.

Thursday manager pre-brief

Managers roll up to the VP ahead of Monday.

The sales managers roll the team forecast up to the VP on Thursday. The VP calibrates against the manager roll-ups, flags discrepancies against the Strkr AI median, and sets the number for the Monday call. The Monday call opens on an aligned number instead of a surprise.

Quarter-end calibration

Overrides and variance tune the next cycle.

At quarter-end, the variance report shows forecast versus actual by rep, segment, and method. Overrides that correlated with correct outcomes feed the model feedback loop. Overrides that correlated with wrong outcomes get flagged for coaching. The next quarter starts with a tighter model.

Every forecast example above runs inside Strkr on a free trial.

Commit range, deal probability, confidence band, risk flags, method reconciliation, variance report, and board export all ship on every paid tier. Threshold calibration, signal-weight tuning, and model feedback loops land on Pro.

Start free trial See pricing
Common questions

What buyers ask about this feature.

What is a simple example of sales forecasting?

A simple weighted-stage example: a B2B SaaS AE has 12 open deals totaling 1.4 million. Four deals in Stage 3 at a 30 percent historical close rate (400K pipeline, weights to 120K). Five deals in Stage 4 at a 55 percent close rate (600K pipeline, weights to 330K). Three deals in Stage 5 at an 80 percent close rate (400K pipeline, weights to 320K). The weighted forecast is 770K for the window. The AE commit might land at 740K (the AE knows two Stage 5 deals have specific risk the model does not see). The final close often lands between the two numbers, which is why mature teams submit a range instead of a point.

How do you forecast sales for a new product with no history?

A new product has no historical close pattern, so the standard weighted-stage approach does not apply yet. The common pattern is a bottoms-up build: estimate the addressable segments, estimate activation rate from early demos, estimate conversion from activation to paid, estimate average deal size, and multiply. The confidence band is wide (typically plus or minus 40 to 60 percent in the first quarter, narrowing by cycle). Strkr handles the pattern by starting the new product with a conservative prior and widening the confidence band on all new-product deals until the first 20 to 30 closes land, which calibrates the baseline for the next cycle.

What is a good example of a sales forecasting template?

A working template has six columns for each deal: amount, stage, close date, owner, probability (either historical by stage or Strkr AI), and weighted amount (amount times probability). The row sum of weighted amount is the weighted forecast. A second tab tracks the method composition: rep commit, weighted stage, pipeline coverage (total pipeline divided by target), and Strkr AI. The three methods render side by side so the VP reads the agreement before submitting the final number. Strkr renders the full template inside the paid tier so the ops lead does not have to maintain a spreadsheet that drifts from the live pipeline by Friday.

How do you forecast sales in Excel versus a CRM?

Excel forecasts live on a snapshot of the pipeline taken at a moment. By Friday, the pipeline has drifted (new deals, moved stages, updated close dates) and the Excel forecast lags. CRM forecasts read from the live pipeline, which means the number reflects the current reality on every open. The Excel path has one advantage: it is flexible for one-off scenarios the CRM did not pre-build. The CRM path has three advantages: the forecast is always current, the method is auditable (every deal links back to the record), and the variance report tracks accuracy automatically. Strkr is the CRM path. For teams that want to run one-off scenarios, the Strkr forecast exports to Excel for ad-hoc work.

What is an example of forecast reconciliation across methods?

A mid-market 50-rep team runs three methods side by side for Q3. Rep commit lands at 8.4M. Weighted stage lands at 9.1M. Strkr AI lands at 8.9M. The spread of 700K between commit and weighted triggers a reconciliation review. The ops lead opens the method reconciliation view and sees that reps on two teams systematically commit 15 percent below weighted (sandbagging pattern), while reps on the third team commit at parity with weighted. The VP commits 8.8M (midpoint of weighted and AI) with best case 9.4M. Final attainment lands at 9.0M, which lands inside the submitted range. The reconciliation is the artifact that makes the submitted number defensible to finance.

Can I see sales forecasting examples specific to my business type?

Yes. The six worked examples above cover B2B SaaS, services, transactional ecommerce, marketplace, mid-market B2B with method reconciliation, and enterprise with multi-year deals. Each example renders inside Strkr with the method shape the business shape requires. For teams with hybrid shapes (SaaS plus services, for example), the forecast methods compose: the SaaS portion runs on weighted stage, the services portion runs on project confidence, and the final forecast is the sum of both. The method configuration on the Strkr forecast page lets the RevOps lead pick which methods run for which revenue stream, which keeps the forecast reading on the right shape for the business.

Related features

Pair this with...

Sales Forecast Sales Forecasting Methods Sales Forecasting Techniques AI Sales Forecasting Sales Analytics Sales Reporting 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