Built for finance and RevOps teams

The projection of sales formula is simple on paper and painful in a spreadsheet.

The projection of sales formula at its base is pipeline value times probability by stage, summed across open opportunities. The formula is easy. The operational problem is that running it manually every week on 200 open opportunities with calibrated probabilities is a half-day job. Strkr runs the formula continuously against the live pipeline.

What this audience is actually dealing with

The pains that bring buyers here.

The projection-of-sales-formula search intent comes from two buyers: finance analysts who need to understand the math before they design the FP&A model, and RevOps leads who have the math memorized and just want it to run against live data without a Monday rebuild ritual. The six pains below show up on both sides of the buyer split.

The formula is simple, the execution is not

Pipeline value times probability sums manually, every week.

The base formula: for each open opportunity, multiply deal value by stage probability, then sum across the pipeline. Easy at 20 opportunities. Painful at 200. A RevOps lead running 500 opportunities spends a half day a week on the manual sum. Strkr runs the formula continuously so the projection updates as the pipeline updates.

Stage probability guesswork

The 10-25-50-75-90 defaults are a guess.

Most teams use the HubSpot or Salesforce default stage probabilities (10 percent at qualified, 25 at discovery, 50 at proposal, 75 at verbal, 90 at verbal commit). The defaults were set by whoever built the template and never calibrated. A team's actual close rate from proposal might be 48 percent, not 50. Strkr calibrates the probabilities from your actual close history so the formula reads defensible.

The formula does not reflect deal size

A 500K deal closes differently from a 15K deal.

The basic projection formula treats all deals at the same stage with the same probability. A 500K deal at proposal closes historically at maybe 32 percent. A 15K deal at proposal closes at maybe 55 percent. Strkr buckets deal size and calibrates per bucket so the formula reflects the actual pipeline shape instead of a size-blind average.

The formula does not reflect days-in-stage

A deal stuck 90 days at proposal is not still 50 percent.

A proposal-stage deal that has sat at the stage for 90 days is not 50 percent likely to close any more. The historical conversion from "stuck 60-plus days at proposal" drops to maybe 20 percent. Strkr applies a decay factor based on days-in-stage so stalled deals get an honest probability instead of inheriting the default stage percentage.

Rep commit is a separate shape

The probability-weighted sum and the rep commit do not agree.

The probability-weighted projection says 1.2M. The rep aggregate commit says 980K. The manager commit says 920K. Which number does the exec team use. Strkr renders all three so the exec team reads the range (committed floor, projected mid, best case ceiling) instead of asking.

Formula audit for the CFO

The CFO wants to see the math, not a black box.

A CFO reviewing the projection asks: show me the deals, show me the probabilities applied, show me the sum. The Excel workbook can show this. A black-box AI prediction cannot. Strkr renders the formula transparently so a CFO can audit any single opportunity's contribution to the projection.

The formula, written out

Projection equals sum of deal value times probability.

The base projection of sales formula is simple. For each open opportunity, multiply the deal value by the probability of closing. Sum across the pipeline for the projection. The variations below (per-rep calibration, deal-size calibration, days-in-stage decay, segment calibration) are refinements of the same base formula. Strkr renders each refinement as an optional dimension so the CFO sees exactly which math is running.

Base formula

Deal value times probability, summed.

Projection equals the sum across open opportunities of deal value times probability. If you have three deals at 100K each with probabilities 25, 50, and 75 percent, the projection is 150K. Simple. The complexity is in choosing the probability and in running the sum weekly on hundreds of opportunities.

Calibrated probability

Probability from your actual close rate.

The calibrated version replaces default stage probabilities with the actual close rate from each stage in your tenant's trailing 12 months of closed-won and closed-lost history. If proposal-stage deals in your pipeline historically close at 48 percent, the formula uses 48 percent instead of a static 50.

Deal-size calibration

Probability by size bucket.

The deal-size version calibrates probability per size bucket (under 25K, 25K to 100K, 100K to 500K, over 500K). A proposal-stage deal under 25K might close at 60 percent. A proposal-stage deal over 500K might close at 28 percent. The formula applies the right probability per deal.

Days-in-stage decay

Probability decays with stall time.

A deal that has sat 90 days at a stage gets a decay factor applied. If proposal-stage closes at 48 percent at normal dwell time, a 90-day-stuck proposal might read 20 percent. The decay curve comes from historical data: how often do deals stuck N days at a stage actually close.

Per-rep calibration

Rep accuracy factor.

Some reps consistently commit more than they close. Some commit less than they close. The per-rep version applies a rep-specific accuracy factor to that rep's pipeline contribution. The sandbagger's pipeline gets lifted; the over-committer's pipeline gets discounted. The formula reads a more honest total.

Segment calibration

Enterprise and SMB probabilities split.

Enterprise deals and SMB deals convert differently at every stage. The segmented version calibrates per segment so enterprise probability reads on enterprise deals and SMB probability reads on SMB deals. Teams running both motions on one pipeline see roughly 10 to 20 percentage points of probability spread by segment.

How Strkr runs the formula

The formula as a live view, not a weekly rebuild.

The hard part of the projection of sales formula is not the math. It is running the math continuously against a live pipeline with hundreds of opportunities, with every refinement applied, with the output audit-ready. Strkr renders the formula as a live view that updates as the pipeline updates. The cards below describe how the view handles the operational mechanics.

Continuous recomputation

Projection updates on pipeline change.

When a rep moves a deal from discovery to proposal, the projection recomputes immediately. The exec view reads the new number without a Monday rebuild. The projection view can show history so the exec sees the arc through the week instead of a single Monday snapshot.

Audit trail per opportunity

Every deal's contribution is visible.

The projection view lets the exec drill into any opportunity to see the deal value, the stage, the probability applied, the deal-size factor, the days-in-stage decay, the rep accuracy factor, the segment calibration, and the resulting contribution. The CFO audit is one click per deal instead of a workbook reconstruction.

Probability override

Admin can override a stage probability.

If a stage has an edge case the historical data does not reflect, an admin can override the calibrated probability with a note. The override is logged in the audit trail so the next CFO review sees why. The formula stays transparent even when the admin judgment overrides the calibration.

What-if filter

Remove deals from the sum.

The exec can filter deals out of the projection to answer board-style questions. The sum updates in seconds. The filter does not change the underlying data; it changes the current view. The "what if the top three slip" answer is a 10-second interaction instead of a half-day rebuild.

Rep commit overlay

Formula vs rep commit side by side.

The formula-based projection renders alongside the rep aggregate commit and the manager commit. The exec reads the range: committed floor, formula mid, best case ceiling. The delta between the three is itself a signal: a wide gap usually indicates pipeline-hygiene issues the manager is correctly discounting.

Historical accuracy tracking

How accurate was last quarter's projection.

The system tracks projection accuracy by quarter: what did the formula project 90 days out, and what actually closed. The quarterly post-mortem shows the gap by segment, by rep, by deal-size bucket. The calibration improves as the sample grows because the accuracy data feeds back into the probability table.

Where the formula output goes

The projection as an input to adjacent decisions.

The projection of sales formula produces a number. The number is only useful if it feeds the decisions downstream: exec review, board deck, capacity planning, comp modeling. The cards below describe where the Strkr projection flows and how it ties to adjacent surfaces.

Weekly exec review

Projection reads live at the Monday meeting.

The Monday exec review opens with the current projection view, updated through Friday's pipeline movement. The VP of sales walks the number and the delta against commit. The exec team reads the same shape every week. The ritual that used to require a Sunday-night rebuild runs on a live view.

Board deck

Projection formatted for board slides.

The quarterly projection exports in a shape ready for board slides: trailing actuals, current quarter commit vs formula projection, forward quarters by segment, pacing commentary. The RevOps lead copies the view into the deck instead of rebuilding the shape in PowerPoint.

Capacity planning

Projection vs ramped capacity.

The projection flows into a capacity planning view that compares projected revenue against ramped-rep productive capacity by quarter. The exec team sees the hiring plan the number requires. The hiring plan reads from the formula rather than a parallel workbook.

Comp modeling

Variable comp cost projected alongside revenue.

The projection feeds a comp cost estimate: variable comp at the projected close rate. The CFO reads revenue and comp cost on one view so the margin impact is visible as the pipeline shifts. The margin view ties the formula to the P&L in a way a static Excel template rarely does.

Open API

FP&A reads the formula output through the API.

The REST API returns the projection, the per-opportunity contribution, the probability applied, and the historical accuracy. An FP&A analyst can run cohort analyses in a Python notebook against the live tenant without a vendor-managed export. The quarterly accuracy post-mortem runs from live data.

Compliance posture

SOC 2 Type II in progress, HIPAA on request.

For regulated teams, SOC 2 Type II controls are in progress through 2026-Q4 and Strkr signs a BAA on request for HIPAA posture. The formula and the pipeline data run on the same tenant without a second compliance stack. The CFO security review covers the projection surface and the underlying CRM in one review.

Head-to-head

Strkr vs an Excel implementation of the projection formula.

Most teams searching for the projection of sales formula are either designing an Excel implementation or trying to improve an existing one. Here is the head-to-head against the Excel approach.

Feature Strkr Excel + CRM CSV export
Formula execution Continuous recomputation against live pipeline Weekly manual rebuild from CSV
Base probability source Calibrated from tenant close history Static table (10-25-50-75-90 default)
Deal-size calibration Per bucket, automatic Available with manual nested formula
Days-in-stage decay Automatic decay factor from historical conversion Rarely implemented in Excel
Per-rep calibration Rep accuracy factor applied automatically Available with manual rep-specific sheets
Audit per opportunity One click to see probability applied and contribution Available via row inspection
What-if analysis UI filter in seconds Workbook rebuild per scenario
Historical accuracy tracking Projection vs actuals captured per quarter Separate workbook or none
API access REST API for FP&A analysis Manual CSV export
Compliance posture SOC 2 Type II in progress, HIPAA BAA available Depends on where the workbook lives
How teams use Strkr

How teams run the formula with Strkr.

The common thread across teams that chose Strkr for the projection formula: they had an Excel implementation that worked at 20 opportunities and broke at 200, they wanted calibrated probabilities instead of a 2022 default table, and they wanted a CFO-defensible audit trail. The playbooks below are common deployment shapes.

Series C SaaS, 48 reps

Calibrated probability closed a 22-point accuracy gap.

A 48-rep SaaS team ran forecast accuracy at roughly 68 percent against the default stage probabilities. The deal-size calibration alone closed 12 points. Adding days-in-stage decay closed another 8 points. The current accuracy sits at 90 percent two quarters later, which supported a larger Series D fundraise narrative on predictable revenue.

Mid-market services, 32 account executives

Segment calibration split enterprise from mid-market.

A 32-AE services firm ran enterprise and mid-market on the same pipeline. The unified Excel formula over-projected mid-market and under-projected enterprise by 8 points each. Strkr's segment calibration split the two: enterprise reads around 30 percent at proposal, mid-market reads around 50 percent. The projection by segment reads defensible to the CFO.

FinServ SaaS, 24 reps

CFO audit of the formula ran in 30 minutes.

A FinServ SaaS CFO reviews the quarterly projection methodology. The review used to take a half day: pulling the Excel workbook apart, verifying probabilities, spot-checking individual deals. The Strkr audit view let the CFO drill into any opportunity's contribution in one click. The review ran in 30 minutes and the CFO signed off on the methodology for the board report.

Agency, 18 account managers

Projection fed capacity planning for the next hire wave.

An 18-AM agency used the formula projection to drive capacity planning. The projection vs ramped-AM capacity view surfaced a six-month gap at projected growth rate. The firm hired two AMs in month one of the quarter instead of month four, which closed the gap before it showed up as missed revenue.

Hardware vendor, 12 field reps

Rep accuracy factor flagged a chronic over-committer.

A 12-rep hardware vendor noticed that one rep consistently committed more than closed. The rep accuracy factor surfaced the pattern (65 percent trailing accuracy on commit calls). The manager coached the rep to a more honest commit shape. The rep's accuracy improved to 85 percent in a quarter, and the forecast reliability for that territory lifted alongside it.

The projection of sales formula, running continuously on your live pipeline.

Start a 14-day trial with the forecast view loaded. Calibrated stage probability, deal-size calibration, days-in-stage decay, per-rep accuracy, segment calibration, CFO-grade audit, all on the flat per-seat line.

Common questions

What buyers in this bucket ask most.

What exactly is the projection of sales formula at its base?

The base formula is the sum across open opportunities of deal value times the probability of closing. If you have three deals at 100K with probabilities 25, 50, and 75 percent, the base projection is 150K (25K plus 50K plus 75K). The math is simple. The complexity is in choosing the probability (static table vs calibrated vs per-size vs with days-in-stage decay vs per-rep vs per-segment) and in running the sum continuously as the pipeline updates. Strkr handles both: the calibration and the continuous recomputation.

Why calibrate probability instead of using the default 10-25-50-75-90 table?

The default table is a starting point from HubSpot and Salesforce documentation. It is rarely accurate for a team. A B2B SaaS team selling 50K ACV typically closes proposal-stage deals at around 45 to 55 percent. A hardware vendor selling 500K deals typically closes proposal-stage deals at around 25 to 35 percent. The default 50 is wrong by 20 points on the hardware example, which produces a projection that is systematically overstated. Calibration from the tenant's own history produces a defensible probability per stage, per segment, per deal size. Accuracy improvement from calibration alone is typically 15 to 30 points at the quarter projection level.

How does days-in-stage decay actually work in the formula?

The decay factor is derived from historical conversion of stuck deals. For each stage, Strkr computes the conversion rate for deals that stayed at the stage for N days before closing. The resulting curve shows that stuck deals convert at a lower rate: a proposal-stage deal at normal dwell might close at 48 percent, but a proposal-stage deal 90 days stuck might close at 20 percent. The formula applies the decayed probability so stalled pipeline does not inflate the projection. The decay curve updates nightly as the historical data grows.

Can the formula show its work for a CFO audit?

Yes. The projection view lets the exec drill into any opportunity to see the deal value, the stage, the probability applied, the deal-size factor, the days-in-stage decay, the rep accuracy factor, the segment calibration, and the resulting contribution. A CFO reviewing the quarterly projection methodology can audit any single deal's math in one click. The admin console shows the calibrated probability table, the override log, and the historical accuracy by quarter. The methodology is transparent, which is the single most important property for a CFO-reviewed forecast.

What is the difference between the formula projection, the rep commit, and the manager commit?

The formula projection is the probability-weighted sum from the pipeline. The rep commit is the aggregate of per-deal commit calls from reps. The manager commit is the manager's weekly submitted number for the team. The three usually produce different numbers: the formula is typically between the committed floor and the best-case ceiling. The exec team reads all three as a range instead of asking which single number to trust. A wide delta between manager commit and formula projection usually indicates pipeline-hygiene issues (stale deals, missing next-steps, over-stage-ranked opportunities) that the manager is correctly discounting against the raw formula output.

How does the formula work for a regulated team like healthcare or financial services?

The formula itself does not change. The operational posture does. Strkr is HIPAA compliant and signs a BAA on request for healthcare and health-tech teams. SOC 2 Type II controls are in progress through 2026-Q4. The projection surface and the underlying pipeline run on the same tenant with claims-based authorization and row-level security, so a CFO security review covers the forecast and the CRM in one review instead of two parallel compliance stacks. The audit log captures every probability override, every commit change, and every rep call so the FP&A and compliance teams can reconstruct the quarterly projection methodology from the system.

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.