Built for teams running the real number

Sales KPIs are easy to list. Measuring them so the number is reliable in a board meeting is the hard part.

Pipeline velocity, win rate, cycle time, quota attainment, forecast accuracy, cost of acquisition. The textbook list runs 30-plus KPIs. Teams only need the ten or so that drive their specific motion, and they need those ten calculated reliably enough to defend in a CFO meeting. This page covers both.

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

The pains that bring buyers here.

Sales KPI dashboards fail in a predictable sequence. The team installs the 25 KPIs the consultant recommended. The dashboard loads slowly. Half the metrics are off by 10 percent because the underlying definitions drift between reports. The Monday meeting spends 20 minutes debating whether the win rate number is right. The number loses credibility and the team starts quoting their own gut instead. The healthy pattern is the opposite: pick 8 to 12 KPIs that match the specific sales motion, define each one precisely, calculate each one from event-sourced data so the historical numbers are reproducible, and defend each one in the meeting. The six pains below are the ones that show up on sales teams running the wrong KPIs, defining them loosely, or calculating them from mutable snapshots.

KPI inflation

The dashboard has 25 metrics and the team watches three.

A sales ops lead installs the 25-KPI dashboard from the consultant deck and the team watches three. The other 22 metrics clutter the view and slow the load. The three that matter get less attention because they are buried. Strkr dashboards default to 8 to 12 role-specific KPIs with the rest available on drill-down, which keeps the primary view scannable.

Definition drift

Four reports count win rate four different ways.

Win rate counted on created deals divided by closed deals is different from won deals divided by (won plus lost) is different from won revenue divided by created revenue. Each is defensible; mixing them is confusion. Strkr definitions carry an explicit formula with a hover tooltip, and the primary KPIs ship with definitions the team argues about once at install and then follows.

Mutable historical numbers

Last quarters report shows a different number this quarter.

Reports built on mutable snapshots change when the underlying data changes. A deal reclassified from stage 3 to stage 2 corrupts the historical conversion rate from stage 2. The number from Q2 last year now reads differently in Q3 this year. Strkr runs event-sourced reporting on an append-only log, so rerunning a historical report produces the same number every time.

Vanity KPIs

Activity volume looks great but revenue is flat.

A rep making 80 dials a day with no bookings is a vanity metric. The dialing report says the activity target is being hit; the pipeline report shows no pipeline being created. Managers who coach on activity volume without pairing to conversion ratios drive the wrong behaviors. Strkr pairs activity targets with conversion ratios on the same view so the real signal shows.

Forecast accuracy ignored

The commit number is wrong 40 percent of the time.

Forecast accuracy (commit versus actual close) is a KPI most teams track in principle and ignore in practice. A rep whose commits close 58 percent of the time is miscalibrated and the manager coaches the wrong thing. Strkr tracks forecast category trending per rep so the Monday meeting can read who is calibrated and who needs coaching on the forecast itself.

KPIs misaligned to the motion

An SMB team runs enterprise KPIs and vice versa.

An SMB high-velocity team running the enterprise KPI set (pipeline coverage ratio 4x, cycle time 180 days, win rate 22 percent) measures the wrong thing. An enterprise team running SMB KPIs (dials per day, demos per week) misses the strategic motion. Strkr ships role-specific and motion-specific KPI templates so the dashboard matches the actual sales shape.

The pipeline KPIs that matter most

Eight KPIs behind every reliable sales forecast.

The eight below are the pipeline KPIs that show up on every well-run sales dashboard we have reviewed over the last three years. Each pairs with a specific Strkr report that produces the number reliably from event-sourced data. Teams installing all eight typically find the Monday forecast meeting drops from an hour to 20 minutes because the dashboard is the agenda.

Pipeline coverage ratio

Open pipeline divided by remaining quota.

Pipeline coverage ratio is open pipeline divided by remaining quota for the period. Target is typically 3x to 4x for a healthy mid-market SaaS motion, higher for new reps or newer markets. The ratio surfaces the structural health of the pipeline before any individual deal review. A rep at 1.5x coverage with 60 days left is a coaching conversation; a rep at 4x is a confidence call.

Win rate by segment

Closed-won divided by closed decisions.

Win rate counted as closed-won deals divided by (closed-won plus closed-lost) deals, segmented by SMB versus mid-market versus enterprise. Teams that only count a single blended win rate miss the segment story. The segment-level view surfaces where the motion is strong and where coaching or marketing adjustment is needed.

Cycle time

Days from created to closed-won.

Cycle time measures days from opportunity created to closed-won, broken by segment and deal size. The report answers "how long does our pipeline actually take to convert." Teams that track cycle time by segment often find the SMB motion runs twice as fast as the mid-market and three times as fast as enterprise, which calibrates the forecast math per segment.

Average deal size

Won revenue divided by won deals.

Average deal size per segment, per rep, per quarter. Trends matter more than absolute numbers; a rising average with falling win rate suggests the team is chasing bigger deals less effectively, which is a strategic signal. Strkr surfaces the trend over 4 to 8 quarters so the pattern is visible.

Stage conversion rate

Percent of deals that advance each stage.

Stage conversion rate (percent of deals that advance from each stage to the next) across SQL, Qualified, Proposal, Negotiation, Closed-won. The stage with the lowest conversion is often the stage with the weakest definition or the thinnest discovery. Managers coach the specific stage rather than win rate broadly.

Forecast accuracy

Commits that closed divided by commits called.

Forecast accuracy counts the percentage of a reps forecast commits that actually close in the forecast period. Target is 85 percent-plus for a seasoned rep. The report tracks accuracy over time per rep so the roll-up can weight each reps commits by their calibration ratio. Teams running this report find the exec forecast lands within 5 percent of actual close consistently.

Quota attainment distribution

How many reps hit 100 percent versus the shape of the curve.

Quota attainment distribution across the team (number of reps at 0 to 50 percent, 50 to 100 percent, 100 to 150 percent, 150 percent-plus) reveals the shape of the team performance. A healthy team has a right-skewed distribution with a solid middle. A bimodal distribution signals coaching gaps between the top and bottom. Strkr renders the distribution as a histogram with trend over quarters.

Pipeline aging

Days in current stage versus median.

Pipeline aging shows deals currently sitting in a stage past 1.5x the median days-in-stage for that stage. The report surfaces the stuck deals that are usually the first thing a manager works. Strkr pairs the aging report with the hygiene board so the exceptions are visible before the Monday standup.

Activity and effort KPIs that pair with pipeline

Six activity KPIs that signal before the pipeline does.

Activity KPIs show up two to six weeks before the pipeline KPIs change because activity is the leading indicator. The six below pair with the pipeline KPIs above to make a complete picture. Teams that watch activity alongside pipeline catch the problems before they land on the quarterly number.

Dials per rep per day

The leading indicator for outbound SDR teams.

Dials per rep per day with target floors (50 for SDR, 25 for AE). The target varies by motion and segment. The report flags reps under the floor for coaching before the pipeline impact shows up two weeks later. Pair with connect rate to avoid the "80 dials with no connects" vanity metric trap.

Meetings booked

Discovery meetings scheduled per rep per week.

Discovery meetings booked per rep per week with target floors (12 to 15 for a healthy outbound SDR, 8 to 12 for a hybrid AE). The report surfaces the booking rate before it impacts the pipeline. Strkr counts booked meetings from calendar sync automatically rather than relying on manual logging.

Email reply rate

Replies to outbound divided by sends.

Email reply rate per sequence, per segment. Healthy benchmarks run 3 to 8 percent for cold outbound depending on list quality and personalization. Dropping reply rates signal list quality degradation or template fatigue. The report surfaces the sequence step that is leaking.

Connect rate

Live conversations divided by dial attempts.

Connect rate measures live conversations divided by dial attempts. Healthy benchmarks run 15 to 25 percent for business-hours outbound. A dropping connect rate signals data quality (bad numbers), timing (wrong hours), or market conditions. Pair with dials per day to avoid rewarding noise.

Response time on MQLs

Minutes from MQL arrival to first-touch.

Response time on marketing-qualified leads from arrival to first-touch. Target is under 5 minutes for high-intent (demo request, pricing page) and under 2 hours for lower-intent. The report flags leads that exceeded SLA for coaching and the sources that generate SLA-missed volume for marketing-ops attention.

Follow-up compliance

Scheduled next-steps actually completed on time.

Follow-up compliance measures the percentage of committed next-steps completed on or before the due date. A rep with 60 percent follow-up compliance is leaking deals through dropped promises. The report pairs with the hygiene board to surface the specific overdue items.

Revenue and efficiency KPIs for the CFO view

Six KPIs that connect sales to the business.

The six below are the KPIs the CFO and the exec team care about because they tie the sales motion to business efficiency. Each pairs with a Strkr report that reconciles cleanly to the billing system for defensibility in exec review.

Customer acquisition cost (CAC)

Fully-loaded sales plus marketing divided by new logos.

CAC counts fully-loaded sales plus marketing spend divided by new logos (or new customers) acquired in the period. The number anchors the business efficiency conversation. Strkr integrates with the finance system to pull the spend side and reconciles against new-logo count for a defensible number.

CAC payback period

Months to recoup CAC from gross margin.

CAC payback period measures months to recoup the fully-loaded CAC from the gross margin of the new customer. Target is typically under 15 months for SaaS, under 6 months for services. The report answers "are we buying growth at a reasonable price."

Net revenue retention

Expansion plus retained minus churn divided by prior-period base.

Net revenue retention (NRR) measures (expansion revenue plus retained revenue minus churn) divided by the prior-period base. Target is 110 percent-plus for a healthy SaaS motion with expansion. The NRR number is often the most-watched exec metric because it signals both retention health and expansion motion effectiveness.

Revenue per rep

Won revenue divided by average rep headcount.

Revenue per rep (annualized won revenue divided by average rep headcount in the period). The number anchors the hiring conversation: adding a rep should be ROI-positive against the per-rep revenue number. Strkr renders the trend over 4 to 8 quarters so the pattern is visible.

Ramp time

Months for new rep to hit full productivity.

Ramp time measures months for a new rep to hit 80 percent of average quota attainment. The report answers "how long does our enablement actually take to work." Teams running an onboarding playbook aim for 90 to 120 days; teams without a playbook often run 180-plus days without noticing.

Pipeline-to-closed revenue conversion

Won revenue divided by created pipeline value.

Pipeline-to-closed conversion (won revenue divided by created pipeline value in the originating period) is the structural conversion number that drives marketing and sales planning. The number informs how much pipeline the team needs to create to hit the quota. Strkr tracks the number by source so the pipeline-generation plan is a data-driven decision.

Head-to-head

Strkr KPI reporting vs Pipedrive.

Pipedrive is the common comparison because the product targets similar mid-market teams and the reporting approach differs sharply from Strkrs event-sourced model. HubSpot Sales Hub and Salesforce Sales Cloud are the other common comparisons.

Feature Strkr Pipedrive
Reporting basis Event-sourced, historical reports reproducible Snapshot-based, historical rebuilds on data change
KPI templates by role Role-specific dashboards ship as defaults Generic dashboards, role templates per setup
Definition tooltips Formula tooltip on every KPI card Report builder, definition clarity varies
Forecast accuracy tracking Per-rep category trending over time Weighted probability by stage
Pipeline aging report Deals past 1.5x median days-in-stage flagged Days-in-stage field, flagging per workflow
CAC and NRR integration Finance-system integration reconciles spend and revenue Revenue tracked; marketing spend integration limited
Activity plus pipeline pairing Activity ratios and pipeline math on same view Activity dashboards available separately
Ramp-time tracking New-rep productivity curve native Attainment tracked, ramp curve custom
Export to BI Native export to Snowflake, BigQuery, Looker Zapier or app marketplace
Pricing posture Flat per seat, reporting on every tier Insights and reporting gated to higher tiers
How teams use Strkr

KPI implementations running on Strkr right now.

The five playbooks below are from actual KPI dashboard implementations. The teams moved from either no formal KPIs or a messy dashboard to a defensible operating-metrics set. Metrics are real; specifics blurred where asked.

B2B SaaS, 38 reps

Forecast accuracy went from 68 percent to 94 percent in one quarter.

A 38-rep B2B SaaS team ran a weekly forecast meeting with 68 percent accuracy (commit versus actual close). The team installed the Strkr forecast accuracy tracking per rep, with the trending visible to each rep and the manager. Reps saw their own calibration curve weekly. Over one quarter the accuracy climbed to 94 percent as reps calibrated against their own historical pattern. The exec forecast landed within 3 percent of actual close for the first time in two years. The VP of RevOps said the shift was that each rep could see their own calibration and adjust their commit discipline, which no amount of coaching had moved before.

Agency, 16 account managers

Pipeline coverage ratio dashboard surfaced the capacity problem.

A 16-AM agency was approaching the end of Q2 with the pipeline coverage ratio at 1.8x against the Q3 target. The team installed the pipeline coverage ratio dashboard with per-AM visibility. The AMs saw their individual ratios weekly. Three AMs were at 3.5x; six were under 2x. The visible gap drove targeted coaching on the under-covered AMs and a reallocation of inbound leads to the overloaded tier. Q3 landed at 102 percent of plan because the structural capacity problem was surfaced in time. The agency owner said the single highest-leverage move was making the coverage ratio visible rather than reported in aggregate.

Mid-market B2B, 55 reps

Ramp-time dropped from 155 days to 92 days.

A 55-rep B2B team had an informal onboarding playbook and ramp time averaging 155 days to 80 percent of quota. The team installed the Strkr ramp-time report with weekly tracking per new hire. The report surfaced that the two biggest friction points for new reps were qualification coaching (hitting SQL conversion lagged for 90 days) and forecasting (commits were overcalled for 120 days). The team rebuilt the onboarding playbook around those two specific friction points. Ramp time dropped to 92 days inside two quarters. The VP of sales said the specificity of the data drove a specific fix instead of a generic enablement push.

Enterprise B2B, 110 reps

CAC payback dropped from 18 months to 11 months.

A 110-rep enterprise B2B team had CAC payback at 18 months, which was flagged by the board. The team integrated finance-system spend data into Strkr and ran the CAC and CAC payback reports with segment breakdowns. The report surfaced that the SMB segment was carrying a 24-month payback because the acquisition cost was high and the segment ACV was low. The team repositioned the SMB motion to self-serve and refocused the paid acquisition on mid-market where payback ran at 9 months. All-in CAC payback dropped to 11 months inside three quarters. The CFO said the segment-level data was the piece that converted an abstract board request into a specific decision.

Growth startup, 20 reps

NRR climbed to 128 percent after expansion motion rebuilt.

A 20-rep growth startup had NRR at 102 percent, which was leaving expansion money on the table. The team installed the NRR dashboard with expansion opportunity tracking on every active account. The report surfaced that 68 percent of accounts had no identified expansion opportunity and 22 percent had opportunities that had been open 90-plus days. The team installed the expansion funnel with CSM-owned stages, renewal-math forecasting, and health scoring. NRR climbed to 128 percent inside two quarters at the same new-logo count. The founder said the dashboard made the expansion motion as structured as the new-business motion for the first time.

Run the KPIs that defend themselves in a board meeting.

Start a 14-day trial with the Strkr KPI templates loaded by role (SDR, AE, CSM, Manager, VP). Event-sourced reporting on every tier, finance-system integration for CAC and NRR, forecast accuracy per rep, pipeline coverage visibility. Run the Monday meeting on numbers nobody argues about.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What is a sales KPI and how does it differ from a metric?

A KPI (key performance indicator) is a specific metric that measures progress against a defined business goal. A metric is any measurement. Every KPI is a metric; not every metric is a KPI. The practical difference is that a KPI has a defined target, a defined owner, and a defined cadence for review. Teams that treat every metric as a KPI end up with 25-item dashboards nobody watches. Teams that pick 8 to 12 real KPIs with targets and owners run tight.

Which KPIs matter most for a mid-market B2B SaaS team?

Eight anchor KPIs cover most mid-market B2B SaaS motions. Pipeline coverage ratio (3x target for healthy forecast), win rate by segment, cycle time by segment, average deal size trend, stage conversion rate, forecast accuracy per rep, quota attainment distribution, and pipeline aging. Pair with activity KPIs (meetings booked, response time on MQLs, follow-up compliance) and efficiency KPIs (CAC payback, net revenue retention, revenue per rep). The specific weights shift with motion but the anchor set is remarkably consistent across SaaS teams in the 20 to 100-rep range.

How does Strkr ensure historical KPI numbers stay reproducible?

Strkr runs event-sourced reporting on an append-only audit log of all record changes. Stage transitions, field edits, deal creations, and losses are all events. When a report runs for a historical period, the system reconstructs the state as it was at that point from the event stream rather than reading mutable current values. The result is that a Q2 report rerun in Q4 produces the same number as it did in Q2, which is the structural guarantee that lets teams defend the number in exec review.

What is a healthy pipeline coverage ratio?

The standard target is 3x to 4x of remaining quota for a healthy mid-market B2B motion. The exact target depends on win rate: a team with a 25 percent win rate needs 4x coverage; a team with a 40 percent win rate can run at 2.5x. New reps or newer markets typically need higher coverage because the forecast calibration is less reliable. Teams running under 2x coverage with 60 days left in the period are typically going to miss unless something unusual happens.

How often should sales KPIs be reviewed?

Weekly for operating KPIs (pipeline coverage, forecast accuracy, activity targets, pipeline aging). Monthly for trend KPIs (win rate by segment, cycle time, average deal size). Quarterly for strategic KPIs (CAC payback, NRR, revenue per rep, ramp time). Daily is too often for most KPIs and leads to noise-chasing. Yearly is too infrequent and misses the signal. The weekly operating cadence anchors the pipeline review; the monthly and quarterly cadence anchors the planning and strategy discussions.

Can Strkr export KPI data to BI tools like Snowflake or Looker?

Yes. Strkr has native connectors to Snowflake, BigQuery, and Looker for teams that run a dedicated BI layer. The event-sourced data streams out so the BI layer gets the same reproducible historical state. For teams running simpler BI (Google Sheets, basic Looker Studio), Strkr supports direct CSV export of any report and scheduled email delivery. The export is bidirectional for enriched segment data (if the BI layer computes customer-tier scores, those can flow back into Strkr for routing and sequence enrollment).

Also built for

Related audiences.

Sales Management Software Sales Tracking Software For Sales Operations For RevOps For Sales Leaders For VP of Sales

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