Why Most Reviews Change Nothing
The default pipeline meeting goes like this: each person walks through their open deals, narrates recent activity ("I emailed them Tuesday, waiting to hear back"), everyone nods, and the meeting ends when the deal list does. It feels like management. It's actually just recitation—a weekly proof that the deals exist.
The tell is what happens afterward: nothing different. The same deals are "waiting to hear back" next week. Nobody killed anything, re-prioritized anything, or changed an approach. The meeting consumed 45 minutes and produced zero decisions.
A working weekly pipeline review inverts the design. It doesn't ask "what's happening with each deal?" It asks three questions, in order: What do the numbers say changed this week? Which deals violate our rules? What are we doing differently next week? Deals only get discussed when they trip a rule—everything healthy is skipped entirely.
The one-sentence test
A pipeline review succeeded if you can complete this sentence at the end: "Because of this review, next week we will ______ instead of ______." If you can't fill both blanks, you held a status meeting, not a review.
Everything below is tool-agnostic—it works whether your pipeline lives in a CRM, a spreadsheet, or a whiteboard. (When you want the operational version wired into a real pipeline—saved views, review checklists, week-over-week deltas—see how Corcava runs the weekly review.)
The Five Metrics That Matter
You need exactly five numbers, each compared to last week. More than that and the meeting becomes a dashboard tour; fewer and you're flying on vibes.
1. New opportunities added
Top-of-pipeline input. If this is zero for two consecutive weeks, nothing downstream matters—your problem is prospecting volume, and the review should spend its time there.
2. Stage conversions this week
How many deals moved forward a stage—contacted to discussion, discussion to proposal, proposal to negotiation. Movement is the pulse of the pipeline. A big pipeline with no movement is inventory, not opportunity.
3. Overdue follow-ups
Count of opportunities whose next-action date is in the past. This is the single best leading indicator of pipeline health, and the only metric with a hard target: zero. Every overdue follow-up is a deal decaying by default.
4. Closed this week: won / lost / no-response, with reasons
Outcomes plus why. Reviewing loss reasons weekly—in small, fresh batches—is how patterns get caught early. If you don't have structured reason codes yet, adopt an outreach outcomes taxonomy first; without it, this agenda item collapses into anecdotes.
5. Weighted pipeline value
Sum of (deal value × stage probability) across open deals. The absolute number matters less than the direction: is next month's likely revenue growing or shrinking? This is the metric that tells a freelancer to start prospecting before the current project ends, not after.
Prep rule: these five numbers get pulled before the meeting, by one person, in under ten minutes. If assembling them takes an hour of spreadsheet surgery every week, that's a tooling problem worth fixing (more on that below).
The 30-Minute Agenda (Copy This)
Same agenda, same order, every week. Predictability is the point—people prep for a meeting they can anticipate.
| Time | Segment | What happens |
|---|---|---|
| 0–5 min | Numbers vs last week | Read the five metrics and their deltas. No discussion yet—just establish the facts. |
| 5–10 min | Clear the overdue list | Every overdue follow-up gets a new dated action or gets closed, live, in the meeting. Nothing leaves this segment overdue. |
| 10–20 min | Rule-breaker deals only | Discuss only deals flagged by the decision rules (next section). For each: keep with a new action, escalate the approach, or kill it. Two minutes max per deal. |
| 20–25 min | Losses and wins, with reasons | Walk this week's closed deals. One insight per deal: what would we do differently, or what should we repeat? |
| 25–30 min | One change for next week | Agree on a single process or strategy adjustment, write it down with an owner, and check last week's adjustment actually happened. |
The discipline is in what's absent: no deal-by-deal narration, no relitigating old decisions, no prospecting brainstorms (that's a different meeting). One change per week compounds to fifty per year—more improvement than any quarterly overhaul delivers.
Decision Rules for Stuck Deals
The 10–20 minute segment only works if "stuck" is defined by rules, not feelings. Feelings always vote to keep hoping. Rules force the conversation. A starter set:
- •14-day stall rule: any deal with no stage change and no prospect reply for 14 days gets discussed. Outcome must be one of: new dated action, changed approach (different channel, different contact, different offer), or close it.
- •Sequence-complete rule: a deal that has exhausted your full follow-up cadence with no reply gets closed as no-response this week—not "one more week."
- •Age ceiling: any deal older than 2× your median win cycle needs an explicit justification to stay open. If your typical win closes in 3 weeks, a 7-week-old deal is a zombie until proven otherwise.
- •Proposal SLA: a proposal with no follow-up sent within 4 business days of delivery is a process failure and gets flagged regardless of the prospect's behavior.
Killing deals feels like losing. It isn't—the deal was already lost; the pipeline just hadn't admitted it. A pipeline padded with zombies produces inflated weighted value, which produces complacency about prospecting, which produces the revenue crater two months later. Closing a dead deal is what makes the weighted-pipeline metric trustworthy.
Calibrate the thresholds to your sales cycle—14 days is right for freelance and agency work with 2–6 week cycles; enterprise-length cycles need looser rules. What matters is that the numbers are written down and applied without exception.
Worked Example: One Freelancer's Friday Review
Maya is a freelance brand designer. Solo, so her "meeting" is 20 minutes with coffee on Friday morning. Her numbers this week:
- New opportunities: 3 (last week: 5)
- Stage conversions: 2—one discovery call booked, one proposal sent
- Overdue follow-ups: 4 (last week: 1)
- Closed: 1 won ($4,800, reason: referral relationship), 2 no-response
- Weighted pipeline: $9,200 (last week: $13,600)
The narration version of this week would be "won a project, feeling good." The review version reads differently:
- •Overdue jumped 1 → 4 in exactly the week she won a project—the classic feast-mode failure where delivery work eats outreach time. She reschedules all four on the spot, and her one-change-for-next-week is a recurring 30-minute outreach block on Tuesday and Thursday mornings, protected from client work.
- •Weighted pipeline dropped 32%. The win removed its value from the pipeline and new adds slowed. $9,200 weighted is below her $12,000 comfort floor, so prospecting gets priority now—six weeks before the current project ends, not after.
- •Both no-responses were Instagram DM leads that never replied to a single message; her last four wins all came from referrals and her portfolio site. Two data points aren't a verdict, but it's a pattern to watch in next week's numbers—and eventually a reason to stop spending Thursday nights on DM outreach.
Twenty minutes, three decisions, one calendar change. That's the entire practice.
Cadence, Timing, and Solo Mode
- •Weekly, same slot, non-negotiable. Monday morning reviews set the week's priorities; Friday reviews close the loop while the week is fresh. Both work—pick by temperament. Biweekly doesn't work: a two-week gap means stalled deals decay for up to a month before anyone acts.
- •30 minutes for teams up to ~5 reps. If it consistently overruns, your rules are flagging too many deals—which is itself the finding: fix follow-up discipline and the meeting shrinks.
- •Solo: run it anyway, out loud or in writing. The written part matters—log the five numbers and the one change in a running doc. The log is what turns twelve reviews into a quarter's trend data, and it keeps you honest about whether last week's change actually happened.
- •Teams: metrics are about the pipeline, not the people. The review diagnoses process; individual performance conversations happen separately, on transparent criteria—that's what a rep scorecard is for. The fastest way to corrupt your pipeline data is to make the weekly review feel like a tribunal: deals will stay open to avoid loss counts, and reasons will get creative.
Running It Without the Prep Hour
The playbook's biggest failure mode isn't the meeting—it's the prep. When the five metrics require exporting three spreadsheets and reconciling them by hand, the review gets skipped the first busy week, then the second, and then it's dead.
The fix is keeping pipeline data in a system where the review views already exist: overdue follow-ups as a live queue, week-over-week deltas computed for you, close reasons enforced at the moment of closing. Corcava's outreach tracking covers the data side, the reporting dashboard serves the five metrics without prep, and the weekly review workflow turns this guide's agenda into a repeatable in-product routine.
Run your first review this Friday
Set up your pipeline in Corcava today and the five metrics—including your overdue queue—will be waiting, no spreadsheet surgery required.
No credit card required