Feature · B2B Sales Analytics

The twelve metrics the board asks every quarter.

B2B sales analytics is not a chart library. It is the twelve metrics the board asks about every quarter: pipeline, forecast accuracy, win rate, velocity, ACV, cycle time, stage conversion, LTV/CAC, net revenue retention, rep attainment, pipeline coverage, and leading indicators.

Start free trial See pricing
The twelve board metrics

What CROs actually report every quarter.

Across ten mid-market B2B companies we have worked with on the CRO reporting cadence, twelve metrics recur in every board deck. The specifics matter more than the chart library; these are the numbers that drive the strategic conversation. Strkr Analytics ships live dashboards for each with drill-down to the underlying deal.

Pipeline coverage

Open pipeline divided by remaining quota.

Pipeline coverage is the open-pipeline-amount divided by the remaining-quota-amount for the quarter. Healthy B2B teams run 3x to 4x coverage; teams below 2.5x face a quota miss. Strkr shows live coverage with the trend over the trailing 90 days. Dropping coverage is a leading indicator the board watches more than the headline forecast.

Forecast accuracy

Submitted forecast vs actual close.

Forecast accuracy measures the delta between the rep-submitted forecast at week start and the actual close by quarter end. Healthy teams run 85-92 percent accuracy. Teams below 80 either have process issues (reps optimizing for commissions) or signal issues (deals closing outside the forecasted set). Strkr tracks accuracy by rep and by manager over trailing quarters.

Win rate

Closed won divided by closed total.

Win rate is closed-won deals divided by closed-total deals (won plus lost). Mid-market B2B teams typically run 22-32 percent win rate. The number varies by segment, so Strkr segments win rate by ICP band, by lead source, by rep, and by competitive scenario. Trending win rate reveals qualification quality.

Velocity

Deals times win rate times ACV divided by cycle.

Sales velocity is the standard formula: open deals times win rate times average deal size divided by average cycle time. The number is the dollar-per-day rate of pipeline conversion. Strkr computes velocity live and alerts when any factor degrades. Rising velocity means the engine is accelerating; falling velocity flags attention.

Average contract value

ACV trend over trailing quarters.

Average contract value trending up signals ICP tightening or upmarket motion success. Trending down signals the opposite. Strkr segments ACV by segment, by vertical, by lead source, and by rep. Managers see which segments are driving ACV growth and which are dragging. The segmentation reveals the strategic shift that aggregate ACV would hide.

Cycle time

Days from first touch to close.

Average cycle time (first touch to close won) for the trailing quarter. B2B mid-market cycles run 60-120 days typical. Elongating cycle time without a corresponding ACV lift signals qualification issues. Shortening cycle time with ACV holding steady signals process improvement.

Stage conversion

Where deals get stuck.

Stage-by-stage conversion rate (percentage of deals that move from one stage to the next within the stage SLA). Low conversion from "Discovery" to "Technical Validation" might flag SDR qualification issues; low conversion from "Proposal" to "Negotiation" might flag pricing or legal friction. Strkr's stage conversion dashboard surfaces the choke point.

LTV / CAC

Customer lifetime value over acquisition cost.

LTV divided by CAC is the fundamental SaaS unit economic. Healthy B2B SaaS teams run 3:1 or better. Strkr pulls LTV from the customer success module (retention, expansion) and CAC from marketing attribution plus sales cost allocation. The combined number updates monthly and segments by cohort.

The four more operational metrics

What managers watch day to day.

The twelve board metrics are strategic. The four below are the operational metrics managers watch day to day: activity, response time, pipeline aging, and rep attainment. These feed into the strategic twelve but need their own surface for the Monday standup conversation.

Activity rate

Calls plus emails plus meetings per rep.

Activity rate measures touches per rep per week. Not every B2B team manages to activity, but those that do watch the trend. Falling activity on a rep is a leading indicator of either engagement issues or workload issues. Strkr aggregates activity across the standard touch types with per-rep breakdowns.

Response time

Time from inbound to first touch.

Response time on inbound leads is the SLA metric tied directly to conversion. The five-minute rule still holds; qualify rates fall off a cliff after ten minutes. Strkr shows per-rep response time trend, SLA breach rate, and the leads sitting at risk now. The surface is one of the most-used in the manager dashboard.

Pipeline aging

Deals sitting in a stage too long.

Pipeline aging shows deals by stage with their time-in-stage. A deal in Negotiation for 55 days when the SLA is 21 days needs manager intervention. The aging dashboard surfaces the deals, not just the aggregate. Managers run a weekly aging-review to force decisions on stuck pipeline.

Rep attainment

Percentage of quota by rep.

Rep attainment at any point in the quarter. The forecast is "where do we land"; attainment is "where are we right now." Strkr shows attainment with the quota context and the per-week run rate needed to hit. The dashboard is the one every rep opens Monday morning before their 1:1.

Lead source attribution

Which channels produced the ACV.

Lead source attribution closes the loop with marketing. The dashboard shows which channels (inbound SEO, outbound SDR, paid, partner, event) produced the closed-won ACV in the trailing period. The data drives marketing budget allocation and the sales-marketing SLA conversation.

Lost reasons

Why deals went to competitors or no decision.

Lost-reason analysis segments the lost-pipeline amount by reason: competitor won, no decision, budget, timing, feature gap, implementation concern. Trends in lost reasons drive strategy conversations with product, pricing, and marketing. Classic insight: a shift from "competitor won" to "no decision" means the market is slowing, not that the sales team is losing.

How the dashboards work

Live, drill-down, exportable.

A sales analytics dashboard that is a static picture is less useful than a live one that lets you drill into the underlying deals. Below is the interaction model Strkr Analytics ships with. The design priority is "see the number, then see the deals behind the number" in two clicks.

Live refresh

Numbers update as deals move.

Dashboard numbers refresh live as deals move. A Monday-morning deal moving to Closed Won updates the win-rate chart within seconds. The manager watching the dashboard sees the number change in real time. The pattern replaces the "pull the Monday report at 8 AM" ritual with "the dashboard is always current."

Drill-down

Click a chart, see the deals.

Every chart drills down to the underlying deal list. Click the win-rate bar for Q3; the chart expands into the list of deals that made up the win-rate denominator. Click an open-pipeline wedge; the chart expands into the deals in the segment. The drill-down is one click, not a filter chain.

Segment filters

By rep, segment, vertical, region.

Every dashboard supports segment filters: rep, team, segment, vertical, geography, lead source, deal size band. The filter chain is persistent across the dashboard session, so the manager can look at "North American mid-market SaaS deals above $50k" and see all 12 metrics filtered consistently.

Period comparison

This quarter vs last quarter vs year-ago.

Period comparison shows the metric in the current period alongside the prior period and the year-ago period. A win rate of 28 percent is less interesting than "28 percent this quarter, up from 25 last quarter, flat vs year-ago." The context frames the trend.

Share and schedule

Email, Slack, warehouse.

Dashboards share via scheduled email (Monday 7 AM to the exec team), Slack post (daily digest to the sales channel), or warehouse export (Snowflake, BigQuery, Redshift). The sharing surface is the standard delivery mechanism; nobody opens the dashboard app to read the Monday number.

Export

CSV, Excel, warehouse connector.

Any chart or table exports to CSV or Excel. Dashboards export as PDF for board decks. The warehouse connector pushes the full data to the configured destination on the standard schedule (hourly, daily). Teams that build their own BI dashboards consume the warehouse feed rather than the Strkr dashboard.

What this replaces

The four tools B2B teams typically patch together.

Mid-market B2B teams typically run analytics across four tools: the CRM native reports (HubSpot or Salesforce), a BI tool (Looker, Tableau, Mode), a forecast tool (Clari, Gong Forecast), and a spreadsheet model (the one the CRO maintains personally). The comparison below sticks to the gaps each has.

HubSpot or Salesforce reports

Fine until the question gets complex.

Native CRM reports handle the simple cuts well. The failure mode is cross-object analysis (segment pipeline by lead source by rep by vertical) and the formula-field acrobatics required. Strkr Analytics handles the complex cuts natively without a certified admin writing a report builder exercise. The ops lead builds the dashboard themselves.

Looker, Tableau, Mode

Powerful but data-engineering-heavy.

The BI tools are powerful but require a data pipeline. Pipeline break, dashboard breaks. Dashboard build cycle is 2-6 weeks per report with a data engineer in the loop. Strkr Analytics covers the standard CRO reporting without the pipeline step. For truly custom analytics beyond the standard twelve metrics, the warehouse export feeds the BI tool.

Clari, Gong Forecast

Specialists for the forecast surface.

Clari and Gong Forecast specialize in forecast accuracy with AI-assisted projections. The depth exceeds Strkr's current forecast module at the enterprise end. For mid-market B2B teams, Strkr's forecast coverage (with the standard rep-submitted plus manager-adjusted plus commit view) covers 80 percent of the need. The remaining 20 percent is enterprise-specific territory where the specialists still fit.

CRO spreadsheet

The one everyone knows about.

Every CRO has a spreadsheet model that lives alongside the official reporting. The model has the CRO's judgment baked in (adjustments for seasonality, intuition about specific deals). Strkr Analytics does not replace the CRO's judgment but makes the raw data visible so the adjustments start from accurate baseline. The spreadsheet becomes smaller and more focused on judgment layers, not number compilation.

Not Zapier

Middleware does not do analytics.

Zapier zaps that push data to a Google Sheet dashboard are the SMB pattern. The approach breaks around the mid-market scale because the sheet refresh lag, the complex pivots, and the cross-object analysis exceed what sheets can do cleanly. We do not recommend middleware for analytics at mid-market scale.

Open API

Vertical analytics ships via warehouse.

Vertical analytics (industry-specific metrics for healthcare, manufacturing, legal) ships via warehouse export plus the vertical ISV's BI dashboard. Strkr covers the horizontal B2B analytics; vertical depth sits in the ISV layer. The pattern produces vertical coverage without Strkr building every vertical in-house.

The measured outcomes

What customers saw in year one.

Eight mid-market B2B customers reported year-one outcomes after deploying Strkr Analytics as the primary reporting surface. The measured outcomes below are the median; variance across customers tracked team shape and starting-reporting-maturity differences. The impact lands primarily in decision speed and forecast accuracy.

Decision speed

Weekly review from 2 hours to 25 minutes.

The Monday CRO/CFO/CEO revenue review ran 2 hours average pre-Strkr (because half the time was spent compiling the numbers from four sources). Post-Strkr: 25 minutes average, because the dashboard is ready and the conversation starts on the actual decisions. The time saved reinvests into the strategic conversation that was previously squeezed out.

Forecast accuracy

From 72 percent to 89 percent.

Median forecast accuracy rose from 72 percent (pre-Strkr) to 89 percent (post-Strkr) by end of quarter two. The lift came from the submitted-vs-actual tracking that surfaced individual rep forecasting patterns. Managers coached specific reps on their over-or-under tendencies; the team-level accuracy improved as the individual accuracy improved.

Pipeline hygiene

Stale deal count down 68 percent.

Pipeline hygiene (deals in a stage past the SLA) improved materially. Stale deal count fell 68 percent after the aging dashboard went live, because managers started running weekly aging reviews that forced decisions. The pipeline count got smaller but the quality got higher; forecast accuracy climbed as a result.

Response time

Inbound SLA breach rate halved.

Response time to inbound leads improved materially. SLA breach rate halved from 31 percent to 14 percent after the breach-rate dashboard went live. Reps saw their own breach rate in red when they missed the SLA; the visibility drove behavior change faster than manager coaching did.

Rep leaderboard

Attainment variance tightened.

Rep attainment variance (standard deviation across the team) tightened by 23 percent after year one. The leaderboard surface produced healthy competitive pressure; underperforming reps saw where they stood and either improved or self-selected out. Managers reported fewer surprises on quarter-end attainment calls because the trend was visible all quarter.

Board deck prep

From two days to two hours.

Preparing the sales section of the quarterly board deck ran two full days pre-Strkr (data gathering, chart creation, cross-reference, review loop). Post-Strkr: two hours (export the dashboards, add the narrative, review). The time redirects to the actual strategic analysis instead of the data wrangling.

Walk the full analytics suite against your own data in thirty minutes.

Bring your current reporting state. We will show the 12 board metrics plus the 4 operational metrics against a sandbox tenant with sample data, then discuss migration from your current tool stack.

Book a walkthrough See all analytics features
Common questions

What buyers ask about this feature.

Can we build custom dashboards beyond the standard twelve metrics?

Yes. The standard twelve metrics ship as pre-built dashboards for the fastest time-to-value. Beyond those, Strkr Analytics includes a dashboard builder that supports custom charts, custom segments, custom calculated fields, and custom cross-object joins. Admins build custom dashboards without a BI engineer. For truly specialized analytics beyond what the Strkr builder covers (regression analysis, cohort analysis, predictive modeling), the warehouse export feeds a specialized tool like Mode or Hex.

How does the forecast module work with Strkr Analytics?

The forecast module is a sub-surface of Strkr Analytics with its own dedicated UI. Reps submit weekly forecasts (commit, best case, pipeline) that lock on the configured submit cadence. Managers adjust and the roll-up produces the team forecast. The analytics dashboard then shows forecast-vs-actual over trailing quarters, forecast accuracy by rep, forecast accuracy by segment, and the common forecast risk signals (deals slipping, no-activity-recent, probability drops). The forecast surface is included on every paid tier.

Does the dashboard update include historical reruns on past data?

Yes. When the analytics model changes (new segment definition, new metric formula, new attribution rule), the engine reruns against historical data to produce consistent historical charts under the new model. The rerun does not change the underlying records; it recomputes the aggregate metrics. The admin surface shows the before and after of a model change so the organization can decide to adopt the change. For teams that need to preserve historical charts under the old model, the admin can version the model and compare across versions.

Can managers see rep-level data for their direct reports only?

Yes. Row-level security on the analytics dashboards respects the standard Strkr permission model. Managers see their direct reports plus their own records; VPs see their org tree; the CRO sees the full team. The admin configures the visibility rules once at the permission matrix level; the analytics dashboards inherit. Cross-team visibility (a rep seeing peer data) is tenant-configurable but off by default for mid-market teams.

What is the data residency for analytics storage?

Analytics data (the pre-computed aggregates for dashboard performance) stores in the same tenant residency region as the primary record data. US tenants store in US; EU tenants store in EU (Frankfurt). The analytics engine runs in-region. Cross-region analytics does not happen; a tenant's data stays in the tenant's region. Enterprise tier customers requesting additional regions get them on request. The compliance posture for analytics matches the compliance posture for the core data.

Is this HIPAA-compliant for healthcare sales analytics?

Yes for teams on the BAA. Analytics covering PHI-adjacent data (patient-intake deals, healthcare provider pipeline) runs under the BAA with per-tenant encryption on both the record data and the analytics aggregates. The access log covers every dashboard view with the viewing user, the dashboard, and the filter state. SOC 2 Type II attestation is in progress for 2026-Q4. The analytics engine does not perform analytics on PHI content directly; it reports on CRM metadata (deal stage, amount, close date) which is not PHI by itself in most cases. Healthcare teams clarify the scope with us before go-live.

Related features

Pair this with...

Sales Analytics Sales Reporting Sales Reporting Software Sales Dashboard Sales Performance Dashboard Sales Pipeline Management Sales Forecast

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