Built for RevOps teams who measure what moves

Most CRM metrics are vanity. These are the eight that predict next quarter.

A CRM full of dashboards does not mean the team is measuring the right things. Freshworks ships a reports screen. HubSpot ships a reports screen. Salesforce ships Tableau. Strkr ships the eight metrics that actually predict revenue, with the hygiene checks that make the numbers honest.

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

The pains that bring buyers here.

Every CRM demo ends with a dashboard screenshot. The screenshot usually shows revenue by month, deals by stage, and a pie chart of lead sources. Three months into production the dashboard is a vanity surface nobody opens before the forecast call. Below are six reasons CRM metrics commonly fail to drive decisions, and the Strkr workflows that make the numbers actionable.

Hygiene breaks the math

40 percent of deals have no close date past this quarter.

The pipeline report is a lie if the underlying hygiene is bad. The common pattern: 30 to 50 percent of deals carry stale close dates (last quarter's date, no update since), 20 percent have no next step logged, 15 percent are stuck in the same stage past the median cycle time. Strkr's hygiene dashboard surfaces these three symptoms per rep and per segment, and the pipeline-review view will not accept a deal into commit without the hygiene gates passing.

Conversion by stage without velocity

The 30 percent stage-to-stage conversion means nothing without time.

The reports screen that shows "qualified to proposal: 32 percent" means little without the time distribution. A 32 percent conversion with a 14-day median is a healthy stage. A 32 percent conversion with a 90-day median is a dying stage. Strkr's conversion metrics couple to velocity: for every stage, you see the conversion rate, the median days in stage for won deals, the median days for lost deals, and the trailing 90-day trend.

Pipeline coverage without quality

"3x coverage" is meaningless if the pipeline is garbage.

The 3x pipeline coverage rule of thumb (pipeline value 3x quota) is a sales ops mantra that stops working when the pipeline is 40 percent stage-1 deals with no champion. Strkr's coverage view breaks pipeline into weighted buckets by stage with hygiene gates applied: a stage-1 deal with no champion is excluded from coverage math by default. The coverage number reflects pipeline that could realistically close.

Forecast accuracy is not measured

Nobody tracks the week-one commit versus the quarter actual.

Most teams forecast weekly and never measure whether last week's number was right. Forecast accuracy (the ratio of weekly commit to final quarter actual, split by week of quarter and by rep) is the single best predictor of leadership trust in the forecast. Strkr tracks forecast accuracy per rep per week per quarter with trend lines, so the team learns which reps lead by 20 percent and which lag by 15 percent as the quarter unfolds.

Attribution without multi-touch

First-touch and last-touch both lie.

Marketing attribution reports pick first-touch or last-touch and pretend one of them is the truth. Both are wrong because B2B buying journeys involve 4 to 12 touches across multiple channels and stakeholders. Strkr's multi-touch attribution weights every touchpoint on the opportunity timeline and surfaces the channel mix that actually produced closed-won revenue, not the channel that happened to be last.

Cohort retention lives in the finance tool

The CRM shows pipeline, the ERP shows retention, neither connects.

Cohort retention (how much of January's new-logo revenue is still active in month 12) is the single most important metric for a SaaS or recurring business and usually lives in the finance tool rather than the CRM. Strkr's cohort view connects to the subscription record and surfaces per-cohort gross retention, net retention, and expansion rate on the same screen as the sales pipeline that produced the cohort.

The eight CRM metrics worth tracking

Each one with the math, the hygiene gate, and the decision it drives.

Below are the eight CRM metrics we see RevOps leads actually use to make quarterly decisions, with the math definition, the hygiene requirement that keeps the number honest, and the specific decision the metric is designed to drive. Strkr ships each one in the native reports layer with per-segment, per-rep, per-time-period splits.

Pipeline velocity

Dollars per day moving through the funnel.

Pipeline velocity equals (opportunities created times average deal size times win rate) divided by average sales cycle. The metric collapses four separate numbers into one that answers "how much revenue is the funnel producing per day." Strkr calculates velocity by segment, rep, and quarter with a trailing-90-day trend. The decision it drives: whether the funnel is accelerating or decelerating, which should land before the quarter ends.

Weighted stage conversion

Stage-to-stage conversion with velocity attached.

Conversion from stage N to stage N+1, split by segment and quarter, with the median days in stage for won deals and for lost deals attached. Strkr surfaces this as a funnel view with time-in-stage distributions. The decision it drives: which stage is the bottleneck and whether the fix is a qualification gate (improve conversion) or a cycle acceleration (reduce time in stage).

Forecast accuracy

Weekly commit versus quarter actual, per rep.

Forecast accuracy equals (quarterly actual revenue) divided by (weekly commit at week N of quarter). Tracked per rep, per team, per quarter. Strkr trends this over four quarters so the pattern of "Sarah's week-four commit is usually 90 percent of actual, Marcus's is 115 percent" shows up as a stable signal. The decision it drives: which rep forecasts can be trusted versus adjusted at the leadership roll-up.

Meeting-set rate

Qualified meetings booked per 100 outbound touches.

For an SDR team, meeting-set rate is the leading indicator two months ahead of pipeline. Strkr tracks meeting-set rate by SDR, by segment, by channel (phone, email, LinkedIn) with the full-cycle attribution back to closed-won revenue. The decision it drives: which SDRs and which channels deserve more time, and which segments are drying up in time to redirect before the pipeline gap shows up.

Pipeline coverage (hygiene-gated)

Weighted pipeline value against quota, with hygiene applied.

Pipeline coverage ratio equals (pipeline value by stage weighting) divided by (quota for the period). Strkr applies hygiene gates: a stage-1 deal with no champion, no close date, or no next step is excluded from the ratio. The number reflects pipeline that could realistically close. The decision it drives: whether to open additional outbound capacity three months out.

Win rate by source

Closed-won percentage by lead source and segment.

Win rate equals (closed-won deals) divided by (opportunities created in the same cohort), split by source (inbound form, outbound SDR, partner, event, referral) and segment. Strkr runs this on cohorts (opportunities created in month N, tracked through close) rather than snapshots (open deals right now) because the cohort view is the only honest measurement. The decision it drives: where to invest marketing and prospecting dollars for the next quarter.

Cohort retention

Gross and net retention by acquisition cohort.

For recurring businesses, cohort retention is the single most important metric. Gross retention (customer MRR after churn) and net retention (gross plus expansion minus contraction) tracked by month-of-acquisition cohort. Strkr connects to the subscription record and surfaces cohort curves on the same screen as the pipeline that produced the cohort. The decision it drives: whether new customer acquisition is replacing retention leakage or compounding into net growth.

Customer acquisition cost payback

Months to recover fully loaded CAC per segment.

CAC payback equals (fully loaded CAC per customer) divided by (gross margin monthly contribution). Strkr computes this with the deal cost (sales plus marketing attributed to the opportunity) and the subscription record so the payback period is a per-segment, per-channel, per-quarter number. The decision it drives: which segments are economically viable at the current CAC level, and which require either a price increase or a channel shift.

The six hygiene gates that make the metrics honest

Without hygiene, the metrics are expensive fiction.

Every metric listed above depends on data hygiene. Strkr ships six hygiene gates that run continuously on the CRM record, with per-rep and per-segment scores on the hygiene dashboard. The gates are the difference between a reports screen that drives decisions and a reports screen that gets ignored.

Close date freshness

No deal in commit with a stale close date.

A deal in commit must have a close date within the current quarter. Deals with past-dated close dates auto-trigger a hygiene flag and fall out of commit. The alternative is a forecast that includes deals that should have been pushed, lost, or won two months ago.

Next-step freshness

Every open deal has a next step within 7 days.

Open deals require a next-step note updated within the last 7 days for inside sales motions, 14 for enterprise. The hygiene flag fires on deals that have gone silent. Pipeline review surfaces the silent deals as the top of the agenda.

Stage-exit evidence

The stage carries evidence that justifies the stage.

Each stage has exit criteria (BANT or MEDDIC or custom). A deal in "qualified" without documented pain, champion, and timeline falls out of the stage and back to "discovery" automatically. The forecast rolls on evidence rather than optimism.

Owner assignment

No orphan deals.

Every open deal has an active owner. When a rep leaves or goes OOO past a threshold, the hygiene gate reassigns to the manager or the designated backup. Orphan deals do not sit in a terminated rep's record pulling down everyone's numbers.

Duplicate detection

The same account does not run as two deals.

When two deals open against the same account domain or company name within the same quarter, Strkr fires a duplicate alert for the ops team to merge or document the dual-motion justification (new division, new product line, parent-subsidiary distinction).

Loss-reason completeness

Every lost deal has a reason code.

Lost deals require a reason code from a controlled list (budget, timing, no decision, lost to competitor, feature gap, poor fit, champion left). Free-form notes allowed but not sufficient. The loss-reason completeness feeds the win-loss analysis and the product feedback loop.

Stakeholder completeness

A late-stage deal has at least two mapped stakeholders.

Any deal past discovery with only one contact fires a multi-threading alert. Enterprise deals require at least two mapped stakeholders by proposal and three by procurement. The pattern of "we lost because the champion changed jobs" happens because the deal was never multi-threaded in the first place.

MAP presence on committed deals

Committed deals have a mutual action plan.

Every deal in commit past discovery requires a mutual action plan with buyer-signed milestones. The absence of a MAP on a committed deal is a hygiene flag that drops the deal from the weighted pipeline until the plan exists.

How the metrics layer actually gets used

The operator-level routines around CRM metrics.

The metrics are only valuable if the team runs on them. The three routines below are the ones we see produce the highest leverage on Strkr: a Monday pipeline-review ritual, a Friday forecast submit, and a monthly cohort review for the finance partner.

Monday pipeline review

Deltas, not snapshots.

Monday pipeline review runs on the Strkr pipeline-review view: per-deal field changes since last Monday (stage, amount, close date, next step, last activity), stuck-deal alerts, hygiene flags, and the top three deals on each rep's commit list. The conversation runs 25 to 35 minutes for a 6-rep team and surfaces specific movement instead of generic status.

Friday forecast submit

Commit, best-case, pipeline, and reason-coded slippage.

Reps submit forecast on Friday by noon: commit (deals the rep stands behind), best-case (deals that could land), and pipeline (open deals outside commit and best-case). Any deal that slipped from the previous week requires a reason code. The sales ops lead reconciles into the Monday leadership number without a last-minute scramble.

Monthly cohort review with finance

Retention curves against pipeline source.

The RevOps lead and the finance partner review cohort retention curves monthly: gross retention by acquisition month, net retention including expansion, and the per-channel attribution of each cohort. The review drives decisions about which channels and segments are economically sustainable at current CAC. The alternative (RevOps looks at pipeline, finance looks at retention, nobody connects them) is where the biggest strategic mistakes live.

Quarterly win-loss analysis

Reason codes drive the product and marketing conversation.

Every quarter the win-loss analysis runs on loss reason codes: how much revenue was lost to competitor X, how much to feature gap Y, how much to no-decision in segment Z. The product team sees the feature-gap signal in dollars rather than anecdotes. The marketing team sees the segment where "no-decision" is the dominant reason and knows the top-of-funnel targeting is off.

Mid-quarter forecast accuracy review

The pattern of week-four commits against the quarter actual.

Mid-quarter (week 6 of a 13-week quarter), the sales ops lead runs a forecast accuracy review: how did each rep's week-four commit compare to the quarter actual over the last four quarters? Reps who consistently commit high get adjusted down at the roll-up; reps who commit low get coaching on confidence. The pattern is more stable than most leaders assume.

Annual attribution rebuild

The channel mix the next year's budget runs against.

Once a year the attribution model gets rebuilt against the trailing 12 months of closed-won deals: multi-touch weighting across inbound, outbound, partner, event, and referral channels. The output is the channel mix the next year's marketing and prospecting budget runs against. Teams that skip this ritual end up spending the next year's dollars against the previous year's model, which is a slow but expensive drift.

Head-to-head

Strkr metrics vs the Freshworks reports screen.

Freshworks ships a reports module with pipeline value, deals by stage, and activity volume. The surfaces look similar at first glance; the depth differs in the places that actually drive decisions. Below is the honest head-to-head on CRM metrics specifically.

Feature Strkr Freshworks CRM Reports
Pipeline velocity Native computation with 90-day trend Available in custom reports with manual math
Weighted stage conversion Conversion + time-in-stage for won and lost Conversion only, time distribution absent
Forecast accuracy per rep Weekly commit vs quarter actual, trend Forecast module shows current commit only
Pipeline coverage hygiene gates Weighted + hygiene-excluded Raw pipeline value
Multi-touch attribution Weighted touchpoints across opportunity timeline First-touch or last-touch
Cohort retention Connected to subscription record Not surfaced in CRM reports
CAC payback by segment Native per-segment per-channel Requires BI export
Hygiene dashboard Per-rep per-segment hygiene score Not shipped
Loss-reason completeness Required with controlled vocabulary Free-form optional field
Pricing basis Flat per seat, reports included Advanced reports gated on higher tier
How teams use Strkr

How RevOps teams actually use CRM metrics to drive decisions.

The pattern across RevOps teams that run on Strkr metrics: they stop debating definitions and start debating decisions. The playbooks below are three motions live on customer accounts right now, with the specific metric that drove the specific action.

32-rep SaaS team

Forecast accuracy exposed the senior AE pattern.

A 32-rep SaaS team tracked forecast accuracy per rep per week per quarter for the first time. Six quarters of data surfaced a stable pattern: three senior AEs consistently committed 110 to 125 percent of actual revenue by week 4 of the quarter, while two newer AEs committed 75 to 85 percent. The leadership roll-up started adjusting senior AE commits down 15 percent and newer AE commits up 15 percent at mid-quarter. Forecast error at the leadership level dropped from 18 percent to 7 percent across the next three quarters.

Mid-market team, 22 reps

Pipeline velocity surfaced the proposal-stage bottleneck.

A 22-rep mid-market team ran weekly pipeline velocity by segment. Three quarters of trend data showed the mid-market segment slowing: average cycle days climbed from 48 to 71 while deal size held steady. The team dove into the time-in-stage distribution and found the proposal stage specifically had expanded by 18 days. Root cause: a security questionnaire that moved into procurement workflow and lost ownership. The team assigned a dedicated security engineer to the mid-market proposals, cycle time dropped back to 54 days within the next quarter, and velocity recovered.

Enterprise sales floor, 60 reps

Cohort retention changed where the marketing budget went.

A 60-rep enterprise team ran monthly cohort retention by acquisition channel. Six months of data showed that partner-sourced customers had 94 percent gross retention at month 12, while event-sourced customers had 71 percent. The marketing budget had been running 60 percent events, 15 percent partner. The team shifted to 30 percent events, 40 percent partner over the next two quarters, with net retention improving three points across the broader book and acquisition CAC payback shortening from 14 months to 11 months in the partner-sourced cohort.

Series B team, 18 reps

Win rate by source redirected the SDR hire plan.

A Series B team ran win rate by source every quarter and discovered referral-sourced opportunities closed at 42 percent versus 14 percent for cold-outbound-sourced. The hire plan called for three more SDRs; the team reduced the SDR hire to one and used the headcount budget to hire a partnerships manager who could build structured referral motion. The next quarter the referral-sourced opportunity volume doubled, win rate held at 40 percent, and the net new revenue from the partnerships hire outperformed the three-SDR plan on a cost-per-deal basis.

Agency with 11 account managers

Loss-reason analysis fed the product roadmap.

An 11-account-manager agency ran quarterly win-loss analysis on controlled loss reason codes. One quarter showed 38 percent of enterprise losses coded as "feature gap: reporting." The product team had been debating whether reporting was a competitive issue for six months; the win-loss data settled the debate with dollar-weighted evidence. Reporting became the next-quarter roadmap priority, and the win rate in enterprise climbed from 22 percent to 31 percent over the two quarters after shipping the reporting rebuild.

Metrics that drive decisions, not vanity dashboards.

Start a 14-day trial with pipeline velocity, weighted conversion, forecast accuracy, cohort retention, and hygiene-gated coverage enabled on every pipeline. Compare the Monday pipeline review to the current Freshworks or HubSpot flow.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What CRM metrics should a small sales team track first?

Pipeline velocity, meeting-set rate, win rate by source, and forecast accuracy, in that order. Pipeline velocity is the one number that collapses opportunity creation, deal size, win rate, and cycle time into a single revenue-per-day signal that trends cleanly over time. Meeting-set rate is the leading indicator two months ahead of pipeline. Win rate by source tells you where to invest. Forecast accuracy tells you whether to trust the number. The rest (cohort retention, CAC payback, multi-touch attribution) matter once the team hits 15 reps and the finance partner starts asking the right questions.

How does Strkr compute pipeline velocity?

Pipeline velocity equals the number of opportunities created in a period, times the average deal size for that cohort, times the win rate for that cohort, divided by the average sales cycle in days. The output is dollars per day. Strkr computes velocity by segment (enterprise, mid-market, SMB), by rep, and by trailing 90-day window with the trend plotted. The hygiene gates (close-date freshness, next-step freshness, stage-exit evidence) exclude bad data from the computation so the number reflects pipeline that could realistically close.

What is a good forecast accuracy number?

Mature inside sales teams run week-four forecast accuracy in the 85 to 95 percent range (meaning the week-four commit is 85 to 95 percent of the quarter actual). Enterprise teams run wider, 75 to 90 percent at week four, because the deal sizes are larger and the slip risk is higher. The direction matters more than the absolute number: a team improving quarter over quarter is building the forecast discipline the leadership needs; a team at 95 percent accuracy that cannot explain why is probably sandbagging. Strkr tracks the trend and the direction, which is where the operational conversation actually lives.

How does cohort retention show up in Strkr if the subscription data lives in Stripe?

Strkr integrates with Stripe (and other subscription systems) to pull customer MRR, plan, and change history onto the customer record. Cohort retention surfaces as a view on the Strkr customer-success dashboard: new customers by acquisition month, gross retention curve, net retention including expansion, and churn reasons. The pipeline that produced each cohort is linked, so you can see which acquisition channels produced the highest-retaining cohorts. For teams on billing systems outside the native integrations, the API pulls the same data; the integration takes a few hours of RevOps time to configure.

Can Strkr metrics be exported to a BI tool?

Yes. Strkr ships a native Looker, Metabase, and Mode integration, and the open API supports any BI tool that reads from a REST or GraphQL endpoint. The honest guidance is that the native Strkr reports layer handles the eight metrics in this doc plus the hygiene dashboard without a BI tool. Teams that need custom cross-tool analytics (combining Strkr with product analytics, finance, support tickets) run the BI integration for that specific use case. Starting with a BI tool before using the native reports is a common mistake that burns 40 to 60 hours of setup to recreate dashboards Strkr already ships.

What is the difference between a CRM metric and a sales KPI?

In practice, nothing. The CRM metric is the data point the system computes; the sales KPI is the data point the team commits to improve. Pipeline velocity is both a CRM metric (the system computes it) and a sales KPI when the team sets a target (grow velocity 15 percent quarter over quarter). The language distinction is more of a vendor marketing habit than an operational distinction. The useful question is which numbers drive decisions, which Strkr handles by surfacing the eight metrics in this doc with the hygiene gates that keep them honest, not which word the metric gets labeled.

Also built for

Related audiences.

Sales Metrics Sales Metrics to Track Sales Report Sales Forecast Template For RevOps For Sales Ops

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