Lists of sales metrics usually give names without formulas, which leaves teams to invent definitions and produce inconsistent dashboards. This page gives twenty specific metric examples with explicit formulas, fixed measurement windows, and target bands by business stage. Grouped by funnel position for easier adoption.
Teams adopting new sales metrics without precise definitions hit six consistent problems. Formulas drift across teams, windows get confused, and dashboards produce inconsistent reads. Working through these problems is why most sales metric lists do not actually improve measurement.
Most sales metrics lists give you a name (win rate, pipeline velocity, meeting-to-opportunity rate) without the formula. Teams invent their own definitions, which drift team to team. Two reports showing win rate often show different numbers. Explicit formulas fix this.
The same metric measured over trailing-30 days, calendar month, and rolling-12 produces three different numbers. Lists that do not specify the window produce inconsistent dashboards. Fixing the window is part of the metric definition, not an afterthought.
Metrics without target bands are just numbers. Target bands turn metrics into interpretations: good, concerning, excellent, action threshold. Most metric lists omit the bands, which leaves teams tracking numbers they cannot act on.
Many lists mix real outcome metrics (win rate, forecast accuracy) with activity metrics (calls per day, emails sent) without labeling the difference. Teams end up optimizing activity metrics that look busy without moving the outcome layer. Clean grouping fixes this.
Lists giving 50 metrics overload the dashboard. Teams end up tracking everything and acting on nothing. A disciplined set of 15-20 metrics across funnel positions is more useful than 50 metrics across every dimension.
Metrics have different cadences: some weekly (forecast accuracy), some monthly (CAC), some quarterly (NRR cohort). Lists that do not specify the review cadence leave teams either over-reviewing fast-moving metrics or under-reviewing slow-moving ones. Cadence is part of the metric design.
Top-of-funnel metrics measure demand generation effectiveness and lead quality. These four cover 80 percent of what revenue teams actually need at the top of the funnel.
Formula: count of leads marked MQL in the window. Window: trailing 30 days typically, with calendar month for monthly review. Target band: trend-dependent. Watch for drift. Rising MQL volume with declining SQL rate suggests quality is dropping. The volume alone is not meaningful without the next-layer conversion metric.
Formula: SQLs created in window / MQLs created in window. Window: trailing 60 days (allows for conversion latency). Target band: 20-30 percent for B2B SaaS mid-market, 15-25 percent for enterprise motion. Below 15 percent concerning; above 35 percent suggests qualification is too lenient.
Formula: median minutes from lead capture timestamp to first rep touch for inbound leads in the window. Window: trailing 30 days. Target band: under 5 minutes excellent, under 60 minutes acceptable, over 2 hours concerning. The five-minute SLA roughly doubles connect rate vs the 1-hour benchmark.
Formula: leads with populated source attribution / total leads in window. Window: trailing 30 days. Target band: above 95 percent excellent, 90-95 percent acceptable, below 85 percent concerning. Low source attribution clarity poisons marketing budget allocation decisions.
Mid-funnel metrics measure how opportunities progress from qualified pipeline to closed deals. These four surface the health of the sales process itself.
Formula: opportunities created from qualified meetings in window / qualified meetings held in window. Window: trailing 60 days. Target band: 40-55 percent for B2B SaaS mid-market. Below 30 percent concerning; above 65 percent suggests opportunity-creation threshold is too lenient.
Formula: median days from opportunity creation to closed-won for opportunities closed in window. Window: trailing 90 days. Target band: 60-90 days for B2B SaaS mid-market, 120-180 days for enterprise. Median not mean. Watch for drift in both directions.
Formula: opportunities exiting stage N to stage N+1 / opportunities entering stage N, measured per stage over the window. Window: trailing 90 days. Target band varies by stage. Stage 2 to stage 3 typically 40-60 percent; stage 4 to stage 5 typically 70-85 percent. Diagnoses which stage is the bottleneck.
Formula: total contacts linked to opportunities / count of opportunities, measured on open pipeline. Window: current snapshot. Target band: 2.0-3.0 for mid-market deals, 3.0-5.0 for enterprise. Below 1.5 concerning (single-threaded risk). Multi-threading correlates with win rate.
Pipeline metrics measure the health of open pipeline against future quarter targets. These four surface pipeline coverage and quality.
Formula: open pipeline weighted by stage probability / remaining quarterly target. Window: current quarter. Target band: 3x-4x for B2B SaaS mid-market, 2.5x-3x for enterprise motion. Below 2.5x concerning; above 5x suggests strong demand or stage inflation.
Formula: (opportunities * average deal value * win rate) / sales cycle days. Window: trailing 90 days. Target band: trend-dependent. Watch for velocity acceleration or deceleration. Rising velocity means revenue production per unit time is improving; falling velocity signals process issues.
Formula: open opportunities past expected close date / total open opportunities. Window: current snapshot. Target band: below 10 percent excellent, 10-20 percent acceptable, above 25 percent concerning. Aging pipeline predicts late-stage slippage.
Formula: total closed-won ARR / count of closed-won opportunities in window. Window: trailing 90 days. Target band: trend-dependent. Watch for drift. Rising ADS can signal upmarket motion; falling ADS can signal discount pressure or ICP drift.
Forecasting metrics measure how well the team can predict near-term revenue. Retention metrics measure what happens after close. Both sit on the outcome side of the sales measurement.
Formula: (actual closed-won revenue - committed revenue at start of 30-day window) / committed revenue at start of window. Window: 30-day forward from each weekly commit. Target band: within +/- 5 percent at 30-day for strong teams, within +/- 10 percent acceptable.
Formula: same as 30-day but measured at quarterly commit level. Window: 90-day forward from quarter-start commit. Target band: within +/- 10 percent at 90-day for strong teams, within +/- 15 percent acceptable. More variance expected than 30-day due to longer horizon.
Formula: closed-won opportunities / all closed opportunities (won + lost + closed-no-decision). Window: trailing 90 days. Target band: 25-35 percent for B2B SaaS mid-market, higher for product-led, lower for enterprise. Below 20 percent concerning; above 40 percent suggests ICP is too narrow.
Formula: closed-won ARR per rep / rep quota, measured in window. Window: calendar quarter typically. Target band: 60-80 percent of reps hitting quota in healthy teams. Above 90 percent across the team suggests quota is set too low; below 50 percent suggests quota or ramp issues.
Formula: (starting ARR - churn ARR - contraction ARR) / starting ARR, measured on 12-month cohort. Window: rolling 12-month cohort. Target band: above 90 percent for strong B2B SaaS, 85-90 percent acceptable. Gross retention isolates churn from expansion for cleaner diagnosis.
Formula: (starting ARR + expansion ARR - churn ARR - contraction ARR) / starting ARR, measured on 12-month cohort. Window: rolling 12-month cohort. Target band: above 100 percent (expansion offsets churn), 110-120 percent typical for strong B2B SaaS.
Formula: (sales + marketing cost in window) / new customers acquired in window. Window: trailing 90 days typically, with quarterly reporting. Target band: payback period under 12 months excellent, 12-18 months acceptable. Payback-period framing is more useful than CAC alone.
Formula: CAC / (first-year ACV * gross margin). Window: measured per customer cohort. Target band: under 12 months excellent, 12-18 months acceptable, 18-24 months concerning. Payback period above 24 months typically signals unit economics problems.
The comparison for teams choosing between native CRM metrics with enforced definitions and assembling the same metrics in a BI tool.
| Feature | Strkr | Assembling in Tableau or Looker |
|---|---|---|
| Formula enforcement | System-enforced | Analyst-maintained |
| Measurement window explicit | Per metric tile | Dashboard-dependent |
| Target bands visible | Native | Analyst-built conditional |
| Data freshness | Real-time | ETL-dependent lag |
| Formula drift risk | Zero | High across dashboards |
| Analyst FTE requirement | Low | 0.3-0.8 FTE typical |
| Monthly tool spend | Included | $500-$5,000/mo |
Common thread: picked 15-20 metrics across funnel positions, enforced formulas and windows, built target bands, kept the dashboard focused.
A 35-rep Series B team ran a 50-metric Tableau dashboard that nobody checked. Moving to 18 enforced-formula metrics in native Strkr dashboards produced a dashboard that leadership actually used weekly. Decisions got made faster. BI analyst time dropped 0.4 FTE.
A 65-rep mid-market team had three sales teams reporting win rate with three different formulas. Enforcing the single formula (closed-won / all closed) in Strkr made the number comparable across teams. Leadership comparison became meaningful. Team-to-team learning became possible.
A 25-rep growth team added explicit target bands to each metric tile. Win rate good 28-35 percent, concerning below 22 percent, excellent above 40 percent. The bands converted the number from a data point into an interpretation. Weekly reviews started producing decisions rather than questions.
A 180-rep enterprise team restructured their metrics dashboard by funnel position (top-of-funnel, mid-funnel, pipeline, forecasting, retention) rather than by role. Each team member looked at the group most relevant to their job. Adoption rose from 32 percent to 78 percent of eligible users in 90 days.
A 15-rep early-stage team scoped their metrics dashboard to 8 metrics for the first 6 months (MQL volume, MQL-to-SQL, meeting-to-opportunity, cycle length, win rate, pipeline coverage, forecast accuracy, quota attainment). The narrow scope let leadership build intuition before adding more. Metrics added at month 7 got real attention.
Start a 14-day Strkr trial with 20 native sales metrics across top-of-funnel, mid-funnel, pipeline, forecasting, and retention. Formulas and windows enforced, target bands visible. From $15 per seat per month.
Across the funnel: top-of-funnel (MQL volume, MQL-to-SQL rate, lead response time, source attribution clarity), mid-funnel (meeting-to-opportunity rate, cycle length, stage conversion rate, multi-threading rate), pipeline (pipeline coverage, pipeline velocity, aging pipeline share, average deal size), forecasting (30-day and 90-day accuracy, win rate, quota attainment), retention (GRR, NRR, CAC, CAC payback). Each with explicit formula, measurement window, and target band.
15-20 metrics across funnel positions is the right range for most revenue teams. Fewer than 10 misses important diagnostics. More than 25 produces dashboard overload where nothing gets action. A disciplined set grouped by funnel position (4 top-of-funnel, 4 mid-funnel, 4 pipeline, 4 forecasting, 4 retention) covers 90 percent of real sales measurement needs.
Review cadence varies by metric. Weekly: pipeline coverage, forecast accuracy, lead response time, aging pipeline, MQL-to-SQL rate. Monthly: win rate, cycle length, stage conversion rate, average deal size, quota attainment. Quarterly: GRR, NRR, CAC, CAC payback, source attribution analysis. Mixing cadences produces either over-review of fast-moving metrics or under-review of slow-moving ones.
KPIs sit at the outcome layer and get executive attention (new ARR, win rate, forecast accuracy, retention). Metrics sit between activity and outcome, getting manager attention (pipeline coverage, cycle length, meeting-to-opportunity). Activity indicators sit at the input layer, getting rep attention (calls per day, emails sent). Clean sales measurement separates the three layers rather than collapsing them.
Native metrics in the CRM enforce formula and window consistency across teams, surface target bands on every tile, support drill-down from metric to activity, and run in real time without ETL lag. For the common 15-20 sales metrics, native dashboards are more usable than BI, more consistent across teams, and cheaper by $4K-$5K per month at scale. Deeper analytical work (cohort analysis, complex attribution) can still run in a BI tool when needed.
Every metric tile shows the target band for the business: good, concerning, excellent, action threshold. The bands are tunable per tenant to match your business stage, segment, and sales motion. For example, win rate target can be set to 25-35 percent for mid-market SaaS and 15-25 percent for enterprise. The target bands convert raw numbers into interpretations that drive specific actions in weekly reviews.
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.
