Built for RevOps borrowing from projections that worked

A sales projection example that does not show the math is not an example.

Most published projection examples give a cover-page scenario and a final number without the formula walk. This page walks four worked sales projection examples across SMB SaaS, mid-market SaaS, enterprise SaaS, and expansion motions, with each formula component traced from pipeline to final number. Steal the structure that fits your motion.

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

The pains that bring buyers here.

The problem with most published sales projection examples: they skip the math. The example says "a mid-market SaaS team projected 3.2M for Q2 and closed at 3.1M," without showing how the 3.2M was built. The reader cannot trace the formula or borrow the structure. This page shows four worked examples with the inputs, the formulas applied, the component outputs, the risks subtracted, and the final projection. The point is not that these specific numbers transplant verbatim; it is that specific worked examples let you see the shape of the math and adapt it to your motion.

The abstract example

The example gives a final number with no formula walk.

Published sales projection examples typically give a final projection number without showing the formula that produced it. The reader sees "we projected 3.2M" and no information about how. The worked example shows the pipeline, the stage weights, the pacing math, the rep commits, the risk subtractions, and the final number. Without the walk, the example is a cover-page scenario, not a usable reference.

The one-motion example

The example is SMB; the reader runs enterprise.

Many published examples do not clearly name the motion they are modeling. The reader applies an SMB example to enterprise projection or vice versa and gets structurally wrong math. The examples below name their motion explicitly (SMB SaaS, mid-market SaaS, enterprise SaaS, expansion) and calibrate the components to the motion specifics.

The missing cross-check

The example runs one formula and reports one number.

Single-formula examples miss the cross-check that multiple formulas provide. The worked examples below run four formulas in parallel (weighted pipeline, pacing, rep commits, risk-adjusted) and surface where they disagree. The disagreements are usually where the actual projection insight lives.

The stale-weight example

The example uses stage weights that nobody updated.

Examples that use stage weights set once and never updated model projection math that would be stale in production. The worked examples below note the calibration source (trailing-four-quarter conversion) and the current weight values. Teams borrowing from stale-weight examples usually inherit the calibration problem.

The post-hoc example

The example was written after the quarter closed.

Projection examples written after the quarter closed cherry-pick the components that match the actual outcome. The example looks accurate because the author selected the version that matched. The worked examples below show the projections as they would have been built mid-quarter, with the uncertainty acknowledged and the subsequent outcome noted for context.

The missing provenance

The example cannot show which deals produced which number.

Examples that give final numbers without deal-level provenance leave the reader guessing about structure. The worked examples below surface the top five deals contributing to each formula component, which is where real projection work happens. Provenance makes the example inspectable rather than mysterious.

Four worked sales projection examples

Specific pipelines, specific math, specific outputs.

Each example below gives the pipeline input, the stage weights, the pacing math, the rep commits, the risk subtractions, and the final projection. The teams are composite but the math reflects real-looking motions. Steal the structure that fits.

Example 1: SMB SaaS projection, 50 reps

Short-cycle velocity motion, Q2 at week 6.

Pipeline: 180 deals in open stages, average deal 18K, total 3.24M. Stage weights (trailing-4Q conversion): Qualification 25 percent, Trial 48 percent, Proposal 72 percent, Negotiation 88 percent. Weighted pipeline: 1.52M. Pacing (closed-to-date plus commit): 920K actual plus 410K commit = 1.33M; pacing math projects 2.17M by quarter end. Rep commits: 1.46M bottom-up. Risk-adjusted (subtract deals under 55 percent discovery depth): 1.38M. Blended projection: 1.42M. Actual close: 1.44M. Variance: 1.4 percent.

Example 2: Mid-market SaaS projection, 32 reps

Named-champion motion, Q3 at week 9.

Pipeline: 95 deals in open stages, average deal 120K, total 11.4M. Stage weights: Discovery 18 percent, Demo 35 percent, Proposal 58 percent, Negotiation 82 percent. Weighted pipeline: 4.1M. Pacing: 2.3M closed plus 1.2M commit = 3.5M actual; pacing math projects 5.1M. Rep commits: 4.7M bottom-up. Risk-adjusted (subtract deals missing economic buyer engagement, 22 percent of weighted pipeline): 3.2M. Blended projection: 3.8M. Actual close: 3.9M. Variance: 2.6 percent.

Example 3: Enterprise SaaS projection, 18 reps

Multi-threaded strategic motion, Q1 at week 7.

Pipeline: 48 deals in open stages, average deal 650K, total 31.2M. Stage weights: Qualification 11 percent, Discovery 23 percent, Technical 41 percent, Business Case 58 percent, Procurement 76 percent. Weighted pipeline: 11.8M. Pacing: 2.1M closed plus 3.4M commit = 5.5M; pacing math projects 10.2M by quarter end. Rep commits: 11.4M bottom-up. Risk-adjusted (subtract single-threaded deals, 28 percent weighted): 8.5M. Blended projection: 9.4M. Actual close: 9.1M. Variance: 3.2 percent.

Example 4: Expansion projection, 24 CSMs

Install-base expansion motion, Q4 at week 10.

Pipeline: 140 expansion deals, average deal 65K, total 9.1M. Stage weights (expansion-specific): Signal 32 percent, Qualified 51 percent, Proposal 71 percent, Negotiation 89 percent. Weighted pipeline: 4.6M. Pacing: 3.1M closed plus 1.4M commit = 4.5M; pacing math projects 5.3M. Rep commits: 4.9M bottom-up. Risk-adjusted (subtract deals with retention risk flags, 15 percent weighted): 3.9M. Blended projection: 4.4M. Actual close: 4.3M. Variance: 2.3 percent.

How to adapt these examples to your motion

The five calibration points before borrowing anything.

The worked examples above are calibrated for specific motions. Before borrowing stage weights or risk factors, calibrate the five points below for your actual motion. Mismatches between the example and your motion will show up as projection error inside a quarter.

Calibration 1: pull your trailing-four-quarter conversion rates

Replace the example stage weights with your actual conversion.

The stage weights in the examples above are calibrated per motion. Your weights come from your trailing-four-quarter stage-to-stage conversion rates per segment. The calibration is a one-time pull with ongoing quarterly refresh. Teams running on borrowed weights produce structurally miscalibrated projections.

Calibration 2: match the pacing baseline to your cycle

Pacing math assumes typical weekly velocity.

Pacing math projects from current closed-plus-commit to end of quarter using typical weekly velocity. If your motion has stronger quarter-end concentration or weaker mid-quarter velocity than the example assumes, pacing math will systematically mislead. Pull your trailing-four-quarter weekly velocity distribution.

Calibration 3: identify your risk factors

Risk subtractions depend on your signals.

The risk factors in the examples (discovery depth under 60 percent, no economic buyer engagement, single-threaded) are the usual high-impact signals for most B2B motions. Your motion might have additional factors (regulatory review not initiated, security attestation pending, procurement contact not identified). Calibrate the risk factors to your actual loss patterns.

Calibration 4: tune the rep-commit weighting

How optimistic are your reps on commit?

Rep commits are structurally optimistic across most organizations, but the magnitude varies by team. Pull your trailing-four-quarter commit-versus-actual ratios. If reps commit 1.2x their actual close rate, apply a 0.83 factor to rep-commit projection output. If reps commit near-actual, no adjustment is needed. Calibration to your floor keeps the bottom-up signal usable.

Calibration 5: define the blended-projection weighting

Which formula carries the most weight for your motion?

The blended projection in each example combines the four component outputs with weighting. For SMB with high-velocity transactional cycles, pacing math carries most weight. For enterprise with longer cycles, weighted pipeline and risk-adjusted carry more weight. Define the blend weights per segment based on which component has historically been most accurate for that motion.

Common copy-the-example mistakes

What goes wrong when teams borrow projection math literally.

Five mistakes we see repeatedly when teams borrow projection examples without calibration. If any apply, pause the borrow and calibrate first.

The borrowed-weight mistake

Copying stage weights from a published example.

Stage weights are motion-specific and segment-specific. Teams that copy stage weights from a published example without recalibrating against their own conversion data produce structurally miscalibrated projections. The weights are usually the first thing to recalibrate when borrowing an example.

The borrowed-risk-factor mistake

Copying risk factors that do not match loss patterns.

Risk factors in the examples (discovery depth, economic buyer engagement, single-threaded) are high-impact for most B2B motions. But each organization has motion-specific loss patterns. Teams that borrow risk factors without analyzing their own loss data miss the signals that actually predict their losses.

The one-component borrow

Borrowing only the weighted pipeline formula.

Teams that borrow one component (usually weighted pipeline) without the cross-check components miss the architectural benefit of the examples. The four-formula structure is where the error-catching happens. Borrowing one formula is better than nothing but much worse than borrowing the structure.

The static borrow

Borrowing weights and never updating them.

Weights, risk factors, and blend weightings all need periodic recalibration against trailing data. Teams that borrow the examples and never recalibrate drift into the same stale-weight problem the examples themselves warn against. The borrow is a starting point; the calibration is the ongoing discipline.

The methodology-only borrow

Borrowing the formulas without the data infrastructure.

The examples assume live pipeline data, structured discovery capture, named economic buyer fields, and engagement telemetry. Teams that borrow the formulas without the underlying data infrastructure produce projections on top of incomplete data. The infrastructure is prerequisite; borrowing the methodology without it produces disappointing output.

Head-to-head

Strkr vs reference-example-only resources.

Published projection examples live in blog posts and PDFs. Here is the comparison on operational applicability.

Feature Strkr Published projection example (blog post / PDF)
Full formula walk per example Four formula components traced per motion Usually one component, often skipped
Named motion per example SMB / mid-market / enterprise / expansion Often unnamed
Stage weight calibration source Trailing-4Q conversion noted per example Usually fixed or unnamed
Deal-level provenance Top deals contributing to each component Not supported
Risk factors specified Named per example with weighting Usually omitted
Actual-close variance disclosed Variance between projection and actual noted Often post-hoc selection bias
Operational deployability Live calculator with calibration workflow Reference only
Pricing for 50 users with example-based deployment Flat per-seat; projection stack included Not applicable
How teams use Strkr

Teams that borrowed from these examples.

Four teams that adapted the worked examples above into their own projection methodology.

Series B SaaS, 24 reps

Borrowed Example 2 structure; calibrated weights produced 7 percent variance.

A Series B SaaS team was running single-formula projection on borrowed stage weights. The RevOps lead rebuilt projection using the Example 2 structure (four formulas, trailing-4Q calibration, risk subtraction) with weights pulled from the team's own conversion data. Within two quarters, projection variance tightened from 18 percent to 7 percent. The structural borrow worked because the calibration step was done carefully; teams that borrow the structure without calibration usually see less improvement.

Enterprise SaaS, 42 reps

Example 3 risk factors caught 25 percent of commit as structurally weak.

An enterprise SaaS team was projecting commit without a risk-adjusted component. The team added the Example 3 risk factors (single-threaded, economic buyer not engaged, business case missing). The first quarter showed 25 percent of commit carried structural risk by these factors. The CRO ran inspection and remediation; projection accuracy rose by material margin inside two quarters.

Dev-tools PLG, 16 AEs

Expansion example calibration shaped CSM projection methodology.

A dev-tools team with a PLG expansion motion had no formal projection methodology for CSM-driven expansion deals. The team borrowed the Example 4 structure (expansion-specific stage weights, retention-risk subtraction, usage-signal weighting). The methodology produced trustable expansion projection numbers within one quarter. The CFO started treating expansion as a plannable revenue stream for the first time.

FinServ, 28 reps

Example 3 structure plus compliance-review risk factor fit regulated motion.

A FinServ team adapted Example 3 structure for enterprise but added a risk factor (regulatory review not initiated by week 10 of cycle). The additional factor matched the motion's actual loss pattern. Projection accuracy within one quarter was within 4 percent variance; the compliance-specific risk factor was the key adaptation that made the enterprise example fit the regulated motion.

Four worked projection examples. One platform that runs them.

Start a 14-day Strkr trial with reference projection examples, automatic calibration workflow, and multi-formula cross-check live on your pipeline. See how a projection methodology grounded in worked examples actually runs.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

Can I copy the projection math from one of these examples directly?

You can borrow the structure (four parallel formulas, trailing-4Q calibration, risk subtraction) but you must calibrate the specifics (stage weights, risk factor magnitudes, blend weightings) to your own motion. Direct copy without calibration produces structurally miscalibrated projections that are worse than no projection methodology at all. The borrow is a starting point; the calibration is the ongoing discipline.

Which worked example is closest to a typical B2B SaaS motion?

Example 2 (mid-market SaaS, 32 reps, named-champion motion) is the closest match for most mid-market B2B SaaS projections in the 50K to 250K ACV range with a 60 to 120 day cycle. Teams below that range will find Example 1 more applicable; teams above will find Example 3. Expansion-heavy motions should borrow from Example 4 regardless of segment.

How long does it take to adapt a projection example into working methodology?

Four to eight weeks for the first version, two to three quarters for stable operation. The first version requires pulling trailing-4Q conversion data, defining risk factors against actual loss patterns, calibrating blend weightings. The stable version requires rolling the methodology through the sales floor, running the inspection cadence, iterating on components that are producing error.

Do these examples work for an outbound SDR or BDR motion?

The examples above cover AE-level projections from pipeline to closed revenue. SDR and BDR projection is upstream: meetings booked, qualified leads, pipeline added. The structure (four parallel formulas, calibration, risk adjustment) holds but the components are different (meeting-set rate per rep, qualified-lead conversion, pipeline-add velocity). SDR projection examples deserve their own worked walk; the AE examples above do not transplant directly.

What is the single most predictive formula component in a projection?

For most B2B motions, weighted pipeline with correctly calibrated stage weights is the single most predictive component. The qualifier is "correctly calibrated"; weighted pipeline with stale weights is misleading. The risk-adjusted component usually adds the most incremental accuracy once weighted pipeline is in place; it catches the structural weakness that pipeline math alone misses.

Does Strkr ship these worked examples as reference templates?

Yes. The Strkr projection module ships four reference examples matching the four motions above, with the calibration workflow built in. Teams can import a reference example and the system runs the calibration (pulls trailing-4Q conversion, defines initial risk factors) in the background. The reference examples are a starting point for calibration, not a copy-paste replacement for calibration.

Also built for

Related audiences.

Sales Projection Sales Projection Calculator Sales Projection Template Business Sales Projection Sales Prediction For RevOps

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