Built for VP of sales and RevOps leaders

The sales KPIs that matter, the ones that do not, and the CRM configuration that produces each number without a weekly spreadsheet rebuild.

Most B2B sales teams track 40-plus metrics on a Monday dashboard and act on 5. The problem is not the metric count; it is which 5. This page is a practical framework on which KPIs matter at which stage, mapped against the Strkr surfaces that produce each number.

What this audience is actually dealing with

The pains that bring buyers here.

The sales KPI problem at most B2B companies is not a measurement problem; it is a signal-to-noise problem. The weekly dashboard shows 40 metrics. The VP of sales acts on 3. The other 37 are either vanity numbers, lagging indicators that cannot be changed in-week, or metrics that duplicate each other. The result: a RevOps team that spends 4 hours a week maintaining a dashboard that drives 15 minutes of actual decision-making. The patterns below are the ones that show up on every VP-of-sales call we take, and they are consistent across team size and ACV.

The dashboard sprawl

Forty metrics on the Monday screen and three decisions a week.

The classic Monday pipeline dashboard carries 40 tiles across pipeline value, deal count, stage distribution, win rate, cycle time, ACV, forecast, pacing, and 30 more cells of vanity. The VP of sales looks at three: this-week pipeline value against goal, this-quarter forecast against plan, and the stale-deal count. The other 37 tiles exist because someone asked for them in 2022.

Lagging versus leading

Win rate is lagging; pipeline coverage is leading.

Win rate is a lagging indicator that cannot be moved in the current week. Pipeline coverage (next-quarter pipeline divided by next-quarter quota) is a leading indicator that drives this-week's outbound activity. Most dashboards weight the lagging metrics heavier because the numbers are cleaner. The dashboard that drives behavior weights the leading metrics heavier.

Metric duplication

Pipeline value, pipeline count, average deal size: the same number three ways.

Pipeline value equals pipeline count times average deal size. Showing all three on the same dashboard is noise. The common pattern: pick pipeline value as the primary metric and treat deal count and average deal size as drill-downs the VP of sales checks when the primary metric moves unexpectedly. Three tiles collapse to one with drill-through.

Rep-level versus manager-level versus exec-level

The same dashboard for three audiences does not work.

The rep needs the queue (today's activities, this-week's meetings). The manager needs the team (per-rep pipeline health, stuck deals, coaching candidates). The VP of sales needs the forecast (next-quarter commit, pacing, variance to plan). One dashboard that tries to serve all three serves none. Strkr ships role-keyed home templates so each role sees the right slice on login.

Cycle time blind spots

The average hides the long tail.

Average deal cycle time at a 60-rep B2B company is often 60 to 90 days. The average hides a bimodal distribution: 60 percent of deals close inside 45 days, 40 percent of deals take 150-plus. The median metric or a stage-dwell distribution tells the real story. The average by itself drives the wrong intervention.

The CAC payback blind spot

The sales dashboard does not know what customer acquisition cost.

Most sales dashboards omit CAC payback because the data lives in finance. The structural problem: a VP of sales can hit a quota number with deals that have 24-month CAC payback periods and still be hurting the business. The dashboard that ties pipeline production to CAC payback (available through finance system integration) is the one that aligns sales incentive with business health.

The 18 KPIs that actually matter

The leading, lagging, and health metrics.

Below are the 18 KPIs that mature B2B sales teams track, grouped by the question each one answers. Each KPI lands as a native Strkr surface. The cards cover 9 primary metrics; the remaining 9 cover support KPIs in the following section.

Pipeline coverage ratio

Next-quarter pipeline divided by next-quarter quota.

The single most-important leading indicator in B2B sales. A healthy pipeline coverage ratio is 3x to 4x for most SaaS motions (meaning 3 to 4 dollars of pipeline for every dollar of quota). A coverage ratio under 2.5x says the quarter is in trouble; a ratio over 5x says the pipeline is bloated with low-probability deals. Strkr ships the metric as a default tile with per-rep and per-manager drill-down.

Win rate by stage

The conversion ladder from stage to stage.

Win rate from Qualified to Closed-Won is the lagging indicator everyone tracks. The more useful cut is win rate stage-to-stage: Qualified to Proposal, Proposal to Negotiation, Negotiation to Closed-Won. The drop-off shows where coaching leverage is highest. Strkr ships the stage-by-stage conversion rate as a default report.

Average sales cycle

Days from lead creation to close.

The median (not the mean) cycle time by segment is the useful cut. Mid-market deals have different cycle times than enterprise deals; new logo has different cycle times than expansion. The median metric by segment answers "is the motion speeding up or slowing down" in a way the average cannot. Strkr tracks cycle time per deal and reports median by segment.

Average contract value (ACV)

The deal-size trend by segment.

ACV by segment answers "are we winning the right size deals." ACV trending down in enterprise says the team is winning but on smaller logos; ACV trending up in SMB says the team is moving up-market. The trend matters more than the current value. Strkr tracks ACV by segment with a 12-month trailing trend as a default view.

Forecast accuracy

Commit versus actual over trailing quarters.

Forecast accuracy at the rep, manager, and CRO level is the metric that credibility is built on. A rep who commits 100 USD and closes 100 USD builds credibility; a rep who commits 100 USD and closes 60 USD erodes it quarterly. Strkr tracks per-rep variance over trailing periods and feeds it as an adjustment overlay on the next forecast.

Quota attainment

Percent of reps hitting plan.

The classic rep-level metric. Target: 60 to 70 percent of reps hitting at least 100 percent of quota in a healthy motion; above 80 percent means quotas are set too low. Below 50 percent means quotas are set too high or the ramp is broken. Strkr tracks attainment at rep, team, and segment level with the historical distribution for context.

Deals in each stage

The current pipeline distribution.

Deal count per stage with aging (how long each deal has been in its current stage). The cut that matters: deals that have dwelled past the typical stage duration are either stalling or need re-stage. Strkr ships stage-dwell alerts as flow triggers so the stale deals surface for review without a manual sweep.

Activity to pipeline

Touches sent per qualified opportunity produced.

The SDR-productivity metric: how many outbound touches (emails, calls, LinkedIn) produce one qualified opportunity. The benchmark varies by segment: SMB cold outbound might take 80 to 120 touches per qualified opportunity, enterprise cold outbound 150 to 300. The ratio tunes the SDR capacity planning.

CAC payback period

Months to recover customer acquisition cost.

The strategic metric that ties sales efficiency to business health. CAC payback under 12 months on new logo is efficient; over 24 months is a problem. The metric requires integration with the finance system (which Strkr supports via the open API) but once wired it is the single highest-leverage filter on which deals the sales team should prioritize.

The nine support KPIs

The next layer down.

The nine support KPIs below are the ones that drill down from the primary 9. Each one is useful in a context, each one is a Strkr-native surface, and each one answers a decision question.

Lead response time

Minutes from inbound to first touch.

The inbound-lead response time correlates strongly with conversion. Leads responded to inside 5 minutes convert at roughly 8 times the rate of leads responded to in 30-plus minutes. Strkr tracks per-rep response time on inbound leads with an alert when the response-time threshold slips, which is the lightweight intervention that most teams never actually install.

Meeting-to-opportunity rate

How many meetings turn into real pipeline.

Meetings held versus opportunities created, cut by SDR and by segment. A meeting-to-opportunity rate under 40 percent says either the SDRs are booking the wrong meetings or the AEs are not qualifying well. The cause informs where the coaching goes.

Deal slippage

Percent of deals that shift close date past the quarter.

Deal slippage is the metric that catches forecast risk earlier than the forecast itself. A deal that slips from this quarter to next is a forecast miss waiting to happen. Strkr tracks per-rep close-date changes and flags slippage as a weekly report.

Pipeline velocity

Pipeline value times win rate divided by cycle time.

The composite metric that captures how fast the team converts pipeline to revenue. Pipeline velocity rising says the motion is accelerating; falling says the motion is slowing. The metric is more sensitive than any single component, which makes it a useful early warning.

Lead source conversion

Which lead source produces the highest-quality pipeline.

Lead source conversion rate (percent of leads that become opportunities, percent that close won) by source. The common finding: inbound demo request converts at 25 to 35 percent; outbound cold at 2 to 5 percent; partner referral at 40 to 55 percent. The ratio informs the marketing budget allocation.

Deal size by source

Which source produces larger deals.

Average deal size by lead source. The common pattern: partner referral and inbound demo request produce larger deals than cold outbound. The finding informs whether to invest in partnerships or in SDR headcount at the next funding round.

Expansion revenue

Net revenue retention from existing customers.

The expansion-revenue metric (growth from existing customers through upsell, cross-sell, or seat expansion) is the health metric for the CS motion. A 115-plus percent NRR is healthy; below 100 percent means churn is outpacing expansion. Strkr tracks expansion deals as a distinct pipeline alongside new logo.

Churn rate

Monthly or annual logo and revenue churn.

Logo churn (customer count lost per period) and revenue churn (dollars lost per period) are the twin metrics on CS health. The two can diverge: losing one large customer spikes revenue churn while logo churn stays flat. Both are default Strkr metrics on the CS motion.

Rep ramp time

Days to full quota attainment.

The metric that measures onboarding effectiveness: days from new-hire start to first full-quota month. Most B2B SaaS teams claim 90-day ramp but actual is 150 to 220 days. The gap is enablement debt that the ramp-time metric exposes. Strkr tracks per-rep ramp as part of the onboarding surface.

How the KPIs ladder to decisions

Which metric drives which action.

The point of a KPI is to drive a decision. The cards below map specific KPIs to specific decisions, which is the ladder that turns a dashboard into a management rhythm rather than a wall of numbers.

Pipeline coverage drives outbound

Below 2.5x triggers an outbound push.

When pipeline coverage drops below 2.5x on next quarter, the SDR team runs an outbound push. The trigger is the metric, not the gut feel. The push is a sequence against a specific ICP for a duration. The practice is a 6-month-ahead early warning system that beats month-of-quarter firefighting.

Win rate drop drives coaching

Below 25 percent at a stage triggers a review.

When win rate at a stage drops below the historical baseline (typically 25 percent at Proposal to Negotiation for a mid-market SaaS), the enablement team pulls recent lost deals at that stage for pattern analysis. The finding (pricing objection, missing feature, competitor pattern) informs the next enablement update.

Cycle time rise drives process review

Median cycle time up 15 percent triggers a process audit.

When median cycle time in a segment rises 15 percent over a trailing quarter, the RevOps lead runs a process audit. The cause is usually one of three: a new stage that is adding friction, a procurement requirement from a industry, or a slow handoff between SDR and AE. The audit scopes the fix.

Attainment distribution drives quota setting

Above 80 percent hitting plan says quotas are too low.

Quota attainment distribution across the team informs quota setting for the next cycle. Above 80 percent of reps hitting plan means quotas are too low (common in a Series A ramp year). Below 50 percent means quotas are too high. The quota-setting conversation is data-driven rather than negotiation-driven.

Lead source cost drives marketing

Partner referral at low CAC drives partnership investment.

When a lead source produces high-ACV deals at low CAC, the marketing budget shifts toward that source. Partner referral at 40 percent close rate with 1.5x average ACV versus cold outbound is the classic finding. The ratio funds a partnership hire or a channel investment at the next planning cycle.

Ramp time drives onboarding

Ramp over 150 days triggers an onboarding review.

When actual ramp time at full quota attainment exceeds 150 days consistently, the enablement team audits the onboarding program. The gaps (product certification depth, call shadowing hours, first-deal manager time) show up in the ramp-step completion report. The audit informs the next onboarding iteration.

Head-to-head

Strkr vs Salesforce Dashboards for the KPI job.

the comparison is on how fast each tool produces the KPIs with maintainable configuration. Here is the head-to-head.

Feature Strkr Salesforce Dashboards (Enterprise edition)
Pipeline coverage ratio Native tile with per-rep, per-manager drill-down Custom report with configuration required
Stage-by-stage win rate Default report with 12-month trend Report Type setup plus dashboard configuration
Forecast accuracy over trailing periods Variance tracking as a native overlay Snapshot Reporting plus custom BI work
Role-keyed home templates Rep, manager, VP, CRO templates with per-user overlay Dashboard permissions plus manual role assignment
CAC payback integration Open API to finance system; metric lands on dashboard Custom integration or export-to-BI
Stage dwell alerts Flow trigger with per-stage threshold configuration Process Builder or Flow setup
Ramp time by rep Native with onboarding checklist completion Custom report plus manual data joining
Mobile dashboard Native mobile with full dashboard access Salesforce mobile with partial dashboard support
Admin burden to configure Templates ship with the defaults; afternoon to tune Weeks of SOQL and dashboard configuration
AI narrative on each KPI Strkr AI drafts the explanation of movement on the flat tier Einstein Analytics at extra seat with Flex credits
How teams use Strkr

How mature teams run KPIs on Strkr.

The common pattern across teams that get KPI reporting right: they picked 5 primary metrics the team acts on, 9 support metrics the manager drills into, and buried the rest. The playbooks below are motions on Strkr customer accounts.

Series A SaaS, 12 reps

Five primary KPIs on the Monday dashboard.

A Series A SaaS runs five primary KPIs on the Monday dashboard: pipeline coverage next-quarter, win rate stage-by-stage, forecast accuracy trailing quarter, quota attainment distribution, and lead response time. The dashboard was built in a half day from Strkr templates. The VP of sales reads it in 10 minutes and runs the Monday team call off three specific numbers. The prior Salesforce dashboard took 2 weeks to configure and nobody referenced it after month two.

Mid-market B2B, 65 reps

Role-keyed templates with per-manager drill-down.

A mid-market B2B runs role-keyed home templates: SDR template shows the activity queue and conversion rate, AE template shows pipeline value and stuck deals, Manager template shows per-rep health and coaching candidates, VP template shows the forecast and the segment cuts. Each role sees the right slice on login. The admin burden to maintain the four templates is roughly 2 hours a month.

Series C SaaS, 180 reps

CAC payback integration drives the deal prioritization.

A Series C SaaS integrated the finance system (Mosaic) into Strkr via the open API. The deal record carries an expected CAC payback period calculated from the ACV, the segment, and the expected close probability. The finding: deals under 18-month payback close at 1.6x the rate of deals over 24-month payback. The AE queue sorts by expected payback first and expected close value second, which shifted team focus toward efficient deals.

Agency, 20 account managers

Pipeline velocity as the primary metric.

A 20-AM agency runs pipeline velocity (pipeline value times win rate divided by cycle time) as the primary metric on the Monday dashboard. The composite metric captures the three underlying drivers in one number, which is easier to communicate to the agency owner than three separate tiles. The weekly review runs 20 minutes against pipeline velocity trend versus plan.

Enterprise SaaS, 300 reps

Ramp-time report drove a 40-day onboarding redesign.

An enterprise SaaS at 300 reps ran the Strkr ramp-time report across the last 12 months of new hires. The actual ramp was 180 days versus the stated 90. The gaps showed up in the step-completion data: product certification was consistently delayed, first-deal manager time was skipped by two specific managers, call-shadowing hours were half the stated target. The onboarding redesign cut actual ramp to 140 days across the next cohort, producing roughly 1.8 million USD of additional ramp-period pipeline.

The KPIs your team acts on, built into the CRM.

Start a 14-day Strkr trial with the KPI dashboard enabled: pipeline coverage, stage-by-stage win rate, forecast accuracy, quota attainment, lead response time, and the role-keyed templates for SDR, AE, manager, and VP.

Common questions

What buyers in this bucket ask most.

Which 5 KPIs should we put on the Monday dashboard?

The default five we recommend: pipeline coverage ratio on next quarter, win rate stage-by-stage with 12-month trend, forecast accuracy trailing quarter, quota attainment distribution, and lead response time. The first three are the leading, lagging, and credibility metrics; the fourth is the team-health metric; the fifth is the single highest-leverage leading indicator at the top of the funnel. Teams that run these five and bury the other 30 drive meaningfully more weekly decision-making than teams that run 40 tiles.

How does Strkr handle KPI differences across sales teams (SDR vs AE vs CS)?

Role-keyed home templates. The SDR template shows the activity queue, meeting-to-opportunity rate, and lead response time. The AE template shows pipeline value, stage distribution, stuck deals, and forecast commit. The manager template shows per-rep health, coaching candidates, and team-level pacing. The VP template shows the quarter forecast, segment cuts, and variance to plan. Each role sees the right slice on login with per-user overlay for personalization. The templates ship with the defaults and tune in an afternoon.

How does CAC payback integration work?

Strkr exposes the deal record through the open API so a finance system (Mosaic, Pigment, Anaplan, or a custom BI layer) can compute expected CAC payback and write it back to a Strkr field. The field renders on the deal view with the computed payback period and the components (ACV, expected gross margin, allocated acquisition cost by segment). The deal prioritization queue sorts by expected payback, which aligns the sales motion with business health. The integration requires 1 to 3 weeks of API work on the finance side.

How often should quota attainment distribution drive quota setting?

Annual with a half-year check-in is the default rhythm at most B2B SaaS companies. The trigger for an off-cycle quota adjustment: more than 80 percent of reps hitting plan for two consecutive quarters (quotas too low) or fewer than 50 percent hitting plan for two consecutive quarters (quotas too high). Strkr tracks the attainment distribution over trailing periods as a default report, which gives the VP of sales the data to bring to the quota-setting conversation rather than the usual negotiation.

Does Strkr AI help with KPI narrative?

Yes. Strkr AI drafts a weekly narrative on each primary KPI: what moved, why it moved, which rep or segment drove it, and what the manager should ask about on the Monday call. The narrative is grounded in the actual record data with inline citation on the deals or activities that drove the movement. The practice replaces 1 to 2 hours of RevOps-generalist time spent writing the Monday commentary with a 15-minute edit on the draft. The AI runs on the flat seat line with no per-call credit meter.

What is the admin burden to maintain a 14-metric dashboard on Strkr versus Salesforce?

On Strkr the initial setup from templates runs 1 to 2 days with an afternoon of tuning per quarter afterward. On Salesforce the same 14-metric dashboard typically takes 1 to 3 weeks of Report Type setup, dashboard configuration, and SOQL work, with weekly maintenance that can run 2 to 4 hours. The admin savings are roughly one quarter of a RevOps FTE on a mid-market team, which is a line most RevOps leads can show the CRO as the single clearest ROI argument for the migration.

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.