Built for sales leaders tracking the right numbers
The 15 sales metrics that actually drive the business, calculated from live pipeline data.
Most sales organizations track 40 to 70 metrics across dashboards built in Salesforce reports plus Looker plus Google Sheets plus a slide the VP maintains personally. The team spends more time measuring than selling. Strkr ships the 15 sales metrics that genuinely drive the business with automated calculation, benchmarked targets, and risk alerts when a metric slips.
Over-measurement is the quiet tax on most sales organizations. The Series C fintech VP of Sales told us her team tracked 68 distinct metrics across 11 dashboards last quarter. Pipeline velocity, pipeline aging buckets, win rate by rep, win rate by segment, win rate by product, average deal size trending, forecast accuracy versus commit, forecast accuracy versus best case, SDR activity volume, SDR SQL conversion, SQL to opportunity conversion, opportunity to closed-won conversion, sales cycle by stage, sales cycle by segment, pipeline coverage ratio, booked bookings, net new ARR, expansion ARR, churn ARR, net revenue retention, gross revenue retention, cohort retention by month cohort, cohort retention by quarter cohort. The list continued. By the end of the quarter nobody at the exec meeting could point to which three metrics actually moved the business, because the 68-metric list obscured the pattern. The honest industry assessment: most sales organizations are over-metricized and under-focused. The 15 metrics that actually drive the business are known; the rest are vanity or operational detail that belongs in a tactical dashboard, not in the exec review. Strkr ships the 15 as the default.
The 68-metric dashboard trap
Too many metrics obscure the pattern.
A typical sales org tracks 40 to 70 metrics across multiple dashboards. The exec team walks into the Monday meeting and sees a wall of numbers with no clear signal. The CRO cannot answer "what are the three metrics that moved this week" because the dashboard shows 23 metrics with varying significance. Strkr ships the 15 metrics that genuinely matter as the default with the rest available in tactical views.
Dashboards in 4 places
Salesforce plus Looker plus Sheets plus the VP's slide.
Metrics live in 4 to 6 places: Salesforce reports, Looker or Tableau dashboards, Google Sheets maintained by RevOps, and a slide the VP of Sales updates personally. The numbers do not match across sources because each pulls at a different time or calculates slightly differently. Strkr runs one source of truth with every metric calculating from the same pipeline state at the same moment.
Benchmarks are missing
Is 42 percent win rate good or bad?
A metric without a benchmark is a number without context. Is a 42 percent win rate good or bad? Depends on the segment, the product, the sales motion, and the industry. Most dashboards show the metric and leave the benchmark question to the reader. Strkr ships industry benchmarks per segment (B2B SaaS, services, hardware, financial services) so the CRO sees 42 percent against the 48 percent benchmark and understands the gap.
Lagging indicators dominate
By the time win rate drops, the quarter is over.
Most sales metrics are lagging indicators: closed-won revenue, win rate, sales cycle, average deal size. By the time these metrics shift, the quarter is already decided. Leading indicators (pipeline coverage, pipeline-generation velocity, early-stage conversion, activity volume on at-risk deals) predict the lagging metrics 30 to 90 days ahead. Strkr surfaces leading indicators with the specific predictive signal visible.
Metrics drift gradually. Forecast accuracy at commit confidence slips from 92 percent to 81 percent over 6 weeks and nobody notices until the quarter-end miss. Pipeline coverage drops from 3.2x to 2.4x and the signal is buried in the weekly deck. Strkr fires alerts on metric drift against configurable thresholds so the CRO knows at the exact moment a leading indicator shifted.
The attribution gap
Which metrics moved which outcomes.
Teams track outcomes (revenue, pipeline, deals won) and activities (calls, emails, meetings) separately. The attribution between them is manual or missing. Strkr runs multi-touch attribution across lead sources, SDR activity, marketing touches, and the specific interaction patterns that correlate with closed-won. The CRO sees which activity patterns actually move pipeline instead of which activities are being measured.
The 15 metrics group into 5 categories: pipeline health (what is in the pipeline), forecast accuracy (how reliable is the forecast), conversion (how deals progress), retention (how customers stay), and activity (what the team is doing). The cards below are the specific 15 with the formula, the benchmark, and why each matters.
Pipeline coverage ratio
Pipeline divided by quota, by stage.
Pipeline coverage is pipeline dollars divided by remaining quota, usually sliced by stage weight. Benchmark for B2B SaaS: 3x to 4x on commit-stage pipeline for the current quarter. Below 2.5x signals risk; above 5x suggests pipeline hygiene issues. Strkr calculates coverage per rep, per segment, per quarter with the drift alert at configurable thresholds.
Win rate
Closed-won divided by closed deals, by segment.
Win rate is closed-won deals divided by total closed deals (won plus lost). Benchmark varies by segment: enterprise B2B SaaS 15 to 25 percent, mid-market 25 to 40 percent, SMB 35 to 55 percent. Strkr pivots win rate by segment, rep, product, competitor, and lead source so the CRO sees which combinations win and which lose.
Sales cycle length
Average days from created to closed-won.
Sales cycle is average days from opportunity created to closed-won, sliced by segment and deal size. Benchmark for B2B SaaS: enterprise 90-180 days, mid-market 45-90 days, SMB 14-45 days. Shortening the cycle by 20 percent increases revenue capacity by roughly 20 percent at the same win rate. Strkr tracks cycle by stage so the specific stages extending surface clearly.
Forecast accuracy
Commit versus actual, best-case versus actual.
Forecast accuracy is commit forecast divided by actual closed, plus best-case forecast divided by actual closed. Benchmark: commit at 90 to 95 percent accurate, best-case at 70 to 85 percent accurate, worst-case as a floor. Strkr calculates accuracy per rep and per segment so the specific reps or segments with unreliable forecasts surface for coaching.
Quota attainment
Percent of reps hitting quota.
Quota attainment is the percent of quota-carrying reps hitting 100 percent of plan for the period. Benchmark: 60 to 70 percent of reps hitting quota is healthy; below 50 percent signals quota set too high or coverage issues; above 85 percent signals quota set too low. Strkr tracks per rep, per segment, per quarter with the cohort view showing new-hire ramp.
Pipeline velocity
Pipeline dollars divided by sales cycle.
Pipeline velocity is pipeline dollars times win rate divided by sales cycle length. The metric answers "how much revenue the pipeline generates per day" and lets reps and managers compare across teams and segments. Benchmark varies widely; the useful comparison is trend over time rather than absolute number.
Average deal size
Mean and median closed-won by segment.
Average deal size tracks mean and median closed-won by segment, product, and time period. Benchmark varies widely by business; the useful signal is trend. Rising average deal size with flat win rate signals strong motion; rising deal size with falling win rate signals over-reaching. Strkr tracks the trend with the specific deals above and below segment median surfaced.
Lead-to-opportunity conversion
MQL to SQL to opportunity.
Lead-to-opportunity conversion tracks MQL to SQL rate, SQL to opportunity rate, and the combined MQL-to-opportunity rate. Benchmark: B2B SaaS MQL-to-SQL 10 to 25 percent, SQL-to-opportunity 40 to 70 percent. Strkr pivots by lead source so the specific sources driving conversion surface clearly, which drives marketing-spend allocation.
Net revenue retention
Expansion plus churn, cohort-based.
NRR is (starting ARR plus expansion minus churn) divided by starting ARR, cohort-based. Benchmark for B2B SaaS: 100 percent is break-even, 110+ percent is strong, 120+ percent is exceptional. Below 90 percent signals customer-success issues. Strkr tracks NRR by cohort, segment, and product with the specific accounts driving expansion or churn surfaced.
Gross revenue retention
Churn only, cohort-based.
GRR is (starting ARR minus churn) divided by starting ARR, cohort-based. Separates churn from expansion to show the actual customer retention. Benchmark for B2B SaaS: 85 percent is average, 90+ percent is strong, 95+ percent is exceptional. Strkr tracks GRR separately from NRR so the churn story is visible without expansion masking.
CAC payback period
Months to recover customer acquisition cost.
CAC payback is sales and marketing cost per new customer divided by average monthly contribution margin per customer. Benchmark for B2B SaaS: 12 to 18 months is healthy, under 12 months is strong, over 24 months signals efficiency issues. Strkr calculates by segment with the specific CAC per segment visible so marketing-spend allocation decisions have data behind them.
Pipeline-generation velocity
Dollars created per week.
Pipeline-generation velocity tracks net new pipeline dollars created per week by source, segment, and rep. The leading indicator for 60 to 90 days out revenue. Benchmark varies; the useful signal is week-over-week trend. Strkr fires alerts when pipeline-generation velocity drops below the trailing 8-week average by a configurable threshold.
Activity volume
Calls, emails, meetings per rep per week.
Activity volume tracks calls, emails, meetings, and total touches per rep per week. Benchmark varies by segment; the useful signal is the correlation with pipeline and closed-won. Strkr shows the activity-to-outcome correlation per rep so the specific pattern (volume rep with high conversion, low-volume rep with low pipeline) surfaces.
Deal risk is a composite of signals: stakeholder silence (no outbound email reply in 7+ days), pricing-page views dropping to zero, procurement workflow delays, competitor mentions in meeting notes, discount request without stakeholder alignment. Each signal is a leading indicator of deal slippage. Strkr fires alerts on risk flags firing so the AE engages before the deal is lost.
Rep ramp-time
Months to full productivity.
Rep ramp-time tracks months from hire to full-quota productivity. Benchmark: enterprise reps 6 to 9 months, mid-market 3 to 6 months, SMB 1 to 3 months. Strkr tracks cohort ramp with the specific milestones (first discovery call, first deal closed, 50 percent of quota run-rate, 100 percent of quota run-rate) so onboarding effectiveness surfaces as data.
How to actually use the 15 metrics
The weekly, monthly, quarterly cadence.
The 15 metrics do not get the same attention at every cadence. Weekly pipeline review focuses on pipeline health and risk indicators. Monthly business review covers conversion and attainment. Quarterly review covers retention, CAC payback, and the ramp cohorts. The cards below walk through what to look at and when.
Weekly pipeline review
5 metrics for the Monday meeting.
The weekly review focuses on 5 metrics: pipeline coverage ratio (versus quota for current quarter), pipeline-generation velocity (net new this week), forecast accuracy (commit versus best case), deal risk indicators (flags firing on specific deals), and activity volume (calls, emails, meetings this week by rep). The exec meeting takes 30 to 45 minutes with the specific actions clear.
Monthly business review
8 metrics for the exec team.
The MBR covers the weekly 5 plus win rate (by segment, product, rep), sales cycle (trend by segment), and average deal size (trend). Monthly cadence lets patterns emerge from noise. The 90-minute MBR with the exec team covers these 8 metrics and the specific strategic actions (coaching, hiring, pricing, product).
Quarterly business review
15 metrics for the board.
The QBR covers the full 15 metrics with the trailing 8-quarter trend visible. The board sees retention (NRR, GRR), unit economics (CAC payback), and the ramp cohorts in addition to the operational pipeline metrics. The 2-hour board meeting covers the full picture with the strategic recommendations for the next quarter clear.
Alerts on drift
The metric slipped by 11 points, now.
Alerts fire on metric drift against configurable thresholds. Pipeline coverage slipping below 2.5x fires an alert. Forecast accuracy dropping more than 10 points week-over-week fires an alert. Pipeline-generation velocity falling below the 8-week moving average fires an alert. The CRO gets the signal when it happens rather than at the end-of-quarter miss.
Benchmarks per segment
Industry baseline per segment.
Each metric displays against the industry benchmark for the specific segment (B2B SaaS, services, hardware, financial services, healthcare, specific vertical). The CRO sees the current number plus the benchmark plus the delta, so a 42 percent win rate against a 48 percent benchmark reads as "we are 6 points below segment median" rather than "we have a 42 percent win rate" with no context.
Drill-down to records
The metric is a stack of specific deals.
Every metric drills down to the specific records that compose it. Pipeline coverage shows the specific deals in commit stage. Win rate drills to the specific closed-won and closed-lost deals. Forecast accuracy drills to the specific deals that pushed, pulled, or slipped. The CRO investigates the specific pattern instead of debating the abstract metric.
The metrics most teams track that do not matter
Vanity metrics and over-measurement.
Not every metric is useful at the exec level. Some are vanity (feel good but do not drive decisions), some are operational detail (useful to a manager but not to the CRO), and some are correlated with real metrics without being causal. The cards below walk through the specific metrics to deprioritize.
Total pipeline dollars
A big number that includes dead deals.
Total pipeline dollars without staging weight is a vanity metric because it includes dead deals, old deals, and never-going-anywhere deals. The useful metric is pipeline coverage ratio with stage weighting. Teams that report "total pipeline" at exec reviews are usually hiding pipeline hygiene issues behind a bigger number.
Call volume
A proxy for activity, not outcomes.
Call volume is a useful operational metric for sales managers coaching on activity, but it is not a useful exec metric because volume does not correlate directly with outcomes. A rep making 80 calls per day with 2 percent connect rate performs worse than a rep making 20 calls per day with 20 percent connect rate. The useful metric is activity-to-outcome correlation per rep.
Open opportunities count
A proxy for pipeline that misleads.
Open opportunity count treats all opportunities equally and inflates when reps create speculative pipeline. The useful metric is pipeline-weighted-by-stage dollars with the probability curves applied. Teams that fixate on opportunity count miss the quality signal buried in the stage-weight distribution.
Email open rates
Noisy after Apple Mail Privacy.
Email open rates became unreliable after Apple Mail Privacy and iOS 15, which auto-opens emails before the user reads them. Open rate inflated 2 to 3x across most email tools. The useful metrics are click rate, reply rate, and the specific pipeline attribution from email engagement.
Pipeline age
Useful as a signal, not as a decision.
Pipeline age (days in current stage, total days from creation) is a useful signal for sales managers to spot stuck deals, but it is not a useful exec metric because age alone does not determine health. A 180-day enterprise deal is normal; a 180-day SMB deal is dead. The useful pattern is age-by-stage against the segment benchmark.
NPS as a sales metric
Useful for product, not for pipeline.
NPS (Net Promoter Score) is useful as a product and customer-experience metric but it is not predictive of sales outcomes. Companies with low NPS can grow fast if the market is strong; high NPS companies can shrink if the product is undifferentiated. NPS belongs in the product dashboard, not the sales metrics dashboard.
Head-to-head
Strkr sales metrics vs the hand-built dashboard pattern.
Most sales organizations build sales metrics in Salesforce reports or HubSpot reports plus Looker or Tableau plus Google Sheets maintained by RevOps. The honest head-to-head on the metrics layer specifically:
The common thread across customers: cut the 68-metric dashboard mess to 15 metrics that drive decisions, with the drift alerts and the benchmarks and the drill-down that let the exec team actually operate against the numbers. The playbooks below are motions live on customer accounts right now.
Series C fintech
Replaced 11 dashboards with the 15 metrics default.
A Series C fintech consolidated 11 dashboards (across Salesforce reports, Looker, Tableau, Google Sheets) to the Strkr 15-metric dashboard. The exec team's weekly review dropped from 90 minutes to 35 minutes because the metric set was focused. The RevOps analyst recovered 24 hours per month of dashboard maintenance which converted to strategic analysis. The CRO specifically called out "we spent more time measuring than selling before Strkr."
40-rep B2B SaaS
Drift alert caught forecast accuracy slipping.
A 40-rep B2B SaaS activated Strkr drift alerts on forecast accuracy. In Q2 the alert fired when commit-stage forecast accuracy dropped from 92 percent to 83 percent over 3 weeks. The CRO investigated and found two reps were systematically over-committing deals. Coaching ran immediately. Q3 forecast accuracy recovered to 91 percent and the quarter closed within 2 percent of commit for the first time in 4 quarters.
Mid-market company
Benchmarks surfaced win-rate gap by segment.
A mid-market company evaluated win rate against the segment benchmarks shipped with Strkr. The enterprise segment win rate ran at 18 percent against a 24 percent benchmark; the mid-market win rate ran at 42 percent against a 35 percent benchmark. The pattern surfaced that enterprise deals were being pursued without adequate account strategy, while mid-market execution was strong. The CRO reallocated SDR capacity to lean into mid-market and the quarter attainment rose 11 percentage points.
A PE-backed services firm looked at CAC payback by segment and found enterprise CAC payback ran 28 months (above the 18-month target) while mid-market ran 11 months (strong). The CRO reallocated $340K of enterprise marketing spend to mid-market and SDR hiring. Over the next 2 quarters, mid-market pipeline rose 48 percent and enterprise pipeline held flat, which the board approved as the right rebalancing.
Growth-stage SaaS
Rep ramp cohort analysis caught onboarding gap.
A growth-stage SaaS tracked rep ramp cohorts and found the Q2 2025 cohort was hitting 50 percent of quota run-rate at month 6, versus the Q1 cohort hitting 50 percent at month 4. The onboarding team investigated and found the Q2 cohort had been shorted on specific product-training sessions. Remediation ran through the next 3 cohorts and ramp times normalized. The Head of Enablement called the cohort analysis "the thing that let us catch the onboarding regression before it affected a full year of hiring."
The 15 sales metrics that actually drive the business, calculated from live pipeline data.
Start a 14-day trial with the sales metrics dashboard enabled: 15 pre-built metrics (pipeline coverage, win rate, sales cycle, forecast accuracy, quota attainment, velocity, deal size, lead conversion, NRR, GRR, CAC payback, generation velocity, activity, risk indicators, ramp), industry benchmarks per segment, configurable drift alerts, drill-down to specific records, multi-touch attribution, and cohort analysis for retention and ramp.
Sales metrics are quantitative measurements that evaluate the performance of a sales organization. They cover pipeline health (how much pipeline exists and how it is distributed), forecast accuracy (how reliable is the forecast), conversion (how deals progress through stages), retention (how customers stay and expand), and activity (what the sales team is doing). Sales metrics group into leading indicators (predict future outcomes: pipeline-generation velocity, early-stage conversion, deal risk indicators) and lagging indicators (measure past outcomes: closed-won revenue, win rate, sales cycle, average deal size). Modern sales organizations track 15 to 20 metrics across these categories with specific benchmarks per industry segment and specific drift alerts when metrics slip below thresholds. Most organizations over-track; the useful metric set is smaller and more focused than the dashboard suggests.
What are the most important sales metrics to track?
The 15 sales metrics that genuinely drive the business are: pipeline coverage ratio (pipeline divided by quota, by stage weight), win rate (closed-won divided by closed, by segment), sales cycle length (days from created to closed-won), forecast accuracy (commit versus actual), quota attainment (percent of reps hitting quota), pipeline velocity (dollars times win rate divided by cycle), average deal size (mean and median by segment), lead-to-opportunity conversion (MQL to SQL to opportunity), net revenue retention (NRR, with expansion and churn), gross revenue retention (GRR, churn only), CAC payback (months to recover acquisition cost), pipeline-generation velocity (net new per week), activity volume (calls, emails, meetings per rep per week), deal risk indicators (stakeholder silence, pricing-page activity, procurement delays), and rep ramp-time (months to full productivity). The specific 15 cover pipeline health, forecast reliability, conversion efficiency, retention economics, and activity-to-outcome correlation.
How does Strkr compare with Salesforce reports for sales metrics?
Salesforce reports are strong at single-metric pulls and standard dashboards; the gap is the metric set definition and the benchmarking. Salesforce ships with pipeline reports and some default dashboards, but the specific 15 metrics with industry benchmarks per segment and drift alerts and leading indicators require manual build. A typical Salesforce sales metrics layer takes 30 to 60 hours of RevOps time to build and 20 to 40 hours per month to maintain. Strkr ships the 15 metrics as the default with benchmarks per segment and configurable drift alerts, which replaces the manual build and the ongoing maintenance. For organizations already on Salesforce, Strkr complements via API integration to pull the pipeline data; for organizations evaluating Salesforce replacement, Strkr covers both the CRM and the metrics layer.
What is pipeline coverage ratio and what should it be?
Pipeline coverage ratio is pipeline dollars divided by remaining quota for the period, usually sliced by stage weight to reflect probability of closing. For B2B SaaS, the standard benchmark is 3x to 4x coverage on commit-stage pipeline for the current quarter, meaning the team needs $3-4M of weighted pipeline to deliver $1M of quota. Below 2.5x signals risk of missing the quarter; above 5x suggests pipeline hygiene issues (speculative deals inflating the number). Coverage ratio varies by segment: enterprise B2B SaaS often targets higher coverage (4-5x) because the deal count is smaller and the variance is higher, SMB often targets lower coverage (2.5-3.5x) because the cycle is faster and the volume compensates. The useful pattern is tracking coverage ratio weekly against the segment-specific benchmark with drift alerts firing when the ratio slips.
How do you measure sales forecast accuracy?
Sales forecast accuracy measures the delta between forecasted revenue and actual closed revenue at each confidence tier (commit, best case, worst case). The standard calculation is actual closed divided by forecast with the result as a percentage; 95 percent means the forecast was 5 percent low, 105 percent means the forecast was 5 percent high. Benchmark for mature sales organizations: commit forecast at 90 to 95 percent accurate (meaning the quarter lands within 10 percent of commit), best case at 70 to 85 percent accurate, worst case as a floor the team should not miss. Accuracy tracks per rep so coaching surfaces for reps whose forecasts are systematically unreliable (over-committing or under-committing by more than 15 percent for 2+ consecutive quarters). Strkr calculates forecast accuracy automatically with the drift alert firing when accuracy slips below the configured threshold.
What is net revenue retention and what should it be?
Net revenue retention (NRR) is a cohort metric measuring (starting ARR plus expansion minus churn) divided by starting ARR for a cohort, typically expressed as a percentage. For B2B SaaS, 100 percent NRR means the cohort generated the same revenue in the next period despite churn; 110+ percent is strong (expansion exceeds churn by a meaningful margin); 120+ percent is exceptional and typical of top-performing SaaS companies. Below 90 percent signals customer-success issues or product fit problems. NRR distinguishes from gross revenue retention (GRR), which measures churn only without expansion credit. Public SaaS companies with NRR above 115 percent trade at premium valuations because the growth compounds without proportional sales and marketing investment. The useful pattern is tracking NRR by cohort (customers acquired in a specific quarter) and by segment (enterprise, mid-market, SMB) to see which cohorts and segments drive the economics.
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.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
