4 Sales Metrics Leaders Should Review Weekly

Most sales leaders look at the wrong things every Monday morning. They open the CRM, scan total pipeline coverage, glance at quota attainment, and call it a review. Then they spend the rest of the week reacting to whatever deal slipped or rep complained loudest.

The weekly cadence is the most powerful diagnostic window a sales leader has. Long enough to filter noise, short enough to intervene before a quarter goes sideways. But only four metrics actually deserve a recurring slot. The rest can stay in dashboards.

1. Stage-to-stage conversion velocity, not just conversion rate

Conversion rate alone is misleading because it tells you nothing about timing. A 28% stage-two-to-stage-three conversion looks healthy until you notice the deals that converted took an average of 41 days, when your historical baseline was 19.

Every week, pull stage-to-stage conversion alongside median time-in-stage for each transition. Look at the last rolling four weeks against the prior quarter.

Say your team typically moves opportunities from discovery to technical evaluation in 12 days, and last week's cohort is sitting at 23. That's a leading signal — usually one of three things: discoveries are going wide without surfacing a real compelling event, your champion isn't getting internal traction, or your competitor is being invited late and stalling the cycle. None of these show up in raw pipeline coverage. All of them are fixable in week one if you catch them.

The tactical move: build a simple two-column weekly view per rep — conversion percentage and median days. When days inflate without conversion dropping, you have a stalling problem. When conversion drops without days changing, you have a qualification problem. The fix is different for each.

2. New pipeline created by source, weighted by historical close rate

Total new pipeline is a vanity number. A $2M week sounds great until you realise $1.6M of it came from a single inbound channel that closes at 9%, while the outbound-sourced pipeline that closes at 31% was flat.

Each week, segment new pipeline by source — outbound, inbound, partner, expansion, event — and multiply each bucket by its trailing close rate. That gives you expected revenue created, not pipeline created. Two very different numbers.

This metric does something most weekly reviews fail at: it forces an honest conversation about where your team's effort is actually paying off. If outbound expected revenue has been declining for three weeks in a row, no amount of activity coaching will fix what is probably a targeting or messaging problem. If partner-sourced expected revenue is climbing quietly, you have a case for reallocating headcount before the next planning cycle.

A worked example. Imagine a team that created $4.2M in raw new pipeline last week across four sources. Outbound contributed $900K at a 26% historical close rate ($234K expected). Inbound contributed $2.1M at 11% ($231K expected). Partner contributed $700K at 34% ($238K expected). Events contributed $500K at 18% ($90K expected). The raw numbers say inbound is dominant. The weighted numbers say three channels are roughly tied, and the partner channel is punching far above its weight per dollar of input. That's a completely different staffing conversation.

3. Deal slip rate on commit and best-case categories

If you forecast weekly, the only forecast metric that matters at the leader level is how often your commit and best-case deals actually close in the period they were called.

Track two numbers: percentage of commit deals that close in the called month or quarter, and percentage that slip to the next period (versus losing entirely). Do the same for best-case.

The healthy pattern is high commit closure, moderate best-case closure, and a slip rate that's stable and predictable. The unhealthy pattern is the one most teams have and rarely measure: commit deals slip at roughly the same rate as best-case deals. When that happens, your forecast categories are theatre. Reps are calling deals "commit" because pressure demands it, not because the deal mechanics support it.

The weekly review question becomes specific. For any deal that slipped from commit last week, what changed in the deal between the commit call and the slip? If the answer is "nothing, it just didn't sign," the rep didn't have signature mechanics confirmed when they committed. That is a coachable, repeatable issue, and it shows up nowhere in pipeline coverage reports.

Teams that run this discipline for a quarter typically see forecast accuracy tighten meaningfully, not because reps got better at predicting, but because the definition of "commit" finally has teeth.

4. Active opportunity coverage per rep, normalised by deal size

Pipeline coverage as a global ratio (3x, 4x, whatever your team uses) hides the rep-level reality that actually drives the quarter.

What you want to see weekly: for each rep, how many active opportunities they're personally working, sorted by deal size band. A rep with two $400K deals and nothing else is in a different risk position than a rep with eighteen $50K deals, even if their coverage ratio looks identical.

The pattern to look for is concentration risk. When a rep's top three deals represent more than half their committed number, your quarter is being run by three buying committees you don't control. That's not necessarily wrong — enterprise motions concentrate by design — but it should be visible, named, and have an explicit mitigation plan.

The contrarian insight here, and the one most leaders miss: a rep with too much low-value pipeline is often a worse problem than a rep with too little. They look busy. Their activity metrics are fine. But they're spread across deals that won't move the number, and they have no time to work the two or three that would. Finding these reps requires deal-size segmentation, not coverage ratios.

The takeaway

• Replace your Monday pipeline coverage scan with a four-metric view: stage velocity, weighted new pipeline by source, slip rate on commit, and rep-level deal concentration. Build it once, reuse it weekly.
• For every slipped commit deal, document what changed between the call and the slip. After four weeks, you will have a coachable pattern that no forecasting tool surfaces automatically.
• Identify the rep on your team with the highest opportunity count and the lowest median deal size. Have one conversation this week about which three deals they should stop working.