The 30-minute monthly pipeline review that doesn't get postponed

The prospect from week 2 of last month was supposed to make a decision by month-end. You sent the proposal, they said "yes, this looks great, let me sync with my CFO," and you marked it as a probable close. That was 38 days ago. You haven't followed up because you got busy with the other client work, then the other prospects, then the things you wanted to ship for yourself.

The deal is dead. It's been dead for two weeks; you just haven't noticed yet. The dies-of-neglect pipeline pattern is the single most common reason solo consultants' revenue lags their proposal quality. The deals are real; the closes don't happen; the difference is the absence of a monthly review that surfaces stuck deals before they die.

This article is the 30-minute review that fixes it. Four steps, run on the first business day of each month, on a recurring calendar block. Most months it surfaces two or three actions. Three or four times a year, it saves a deal that would otherwise have died.

Why the quarterly retrospective isn't the same job

Solo consultants who do review their pipeline usually do it quarterly — they sit down at the start of Q2 with last quarter's data and look at patterns. That's a different job, and it shouldn't replace the monthly version.

The quarterly retrospective is strategic: which pipeline sources actually produced revenue, what ICP changes are showing up in the data, the one change you'll make next quarter. It's the practice-level review. Article 4 — the quarterly retrospective for solo consultants — covers the shape of that work.

The monthly version is tactical. It's about the deals that exist right now, what's true about them today, and what specific action this month should produce. Quarterly is "is my pipeline working." Monthly is "what's stuck and what's next."

Both belong on the calendar. Different cadences, different jobs. Solo consultants who do only the quarterly version watch deals die in the gaps; consultants who do only the monthly never zoom out to fix the structural problems. Both. Different days.

The 30-minute procedure

The whole review fits inside 30 minutes if you've kept reasonable notes during the month. Four steps.

Step 1 (8 minutes) — Pull the pipeline data. Open whatever you track prospects in. If it's an inbox plus your memory: open a new doc and list every prospect you've had contact with in the last 60 days. For each one, note name + company, source (referral / inbound / content), last contact date, stage (discovery scheduled / discovery done / proposal sent / decision pending / won / lost / open), next-step ownership (yours or theirs), estimated close date if there is one, and a one-line note from the last touch.

Eight to fifteen rows is normal. If you have more than 25, your pipeline is wider than your delivery capacity — that's a structural problem for the quarterly retrospective, not this review.

Step 2 (5 minutes) — Classify each row. Apply one of four labels:

• HOT — proposal out or in active discovery, expected to close within 30 days.
• WARM — early-stage interest, follow-up scheduled, probably progresses.
• STUCK — last touch more than 2 weeks ago, ball is on their side, no clear forcing function.
• DEAD — last touch more than 6 weeks ago, no engagement signal, ICP-marginal or never going to close.

Be honest about STUCK and DEAD. The temptation is to label optimistically. Resist it. Dead deals labeled "warm" distort how full your pipeline actually is and make the entire review useless.

Step 3 (5 minutes) — Run the pipeline-pattern prompt. Paste the table into Claude. The prompt asks for: a short read on what's actually true about the pipeline this month, the one or two patterns worth noticing, and the single highest-leverage action to take in the next 30 days. Not strategic analysis — tactical, specific, "do this thing by Friday."

The prompt's output is usually some version of: "You have three STUCK deals from the same source (referral from Marcus). All three have been on their side for 3+ weeks. The pattern suggests Marcus's referrals don't tend to close — worth a 5-minute conversation with him about why. Highest-leverage action: send the day-21 nudge to all three before end-of-week."

Step 4 (12 minutes) — Execute the actions Claude surfaced and the ones you already knew about. This is the step most solo consultants skip — they do the analysis and don't do the work. The point of the review is the action, not the spreadsheet.

For each STUCK deal: send the appropriate nudge (warm professional follow-up, not apologetic re-introduction). For each DEAD deal: archive cleanly, no last-ditch saves. For each HOT deal: confirm the next step is on the calendar.

By minute 30, every prospect on the list has either advanced, been archived, or has a specific next-touch on the calendar.

A worked example of the 30-minute output

Concrete shape. A solo consultant runs the review on June 1. Twelve prospects in the last 60 days. After Step 2 (classification), the pipeline looks like:

• HOT (2): Acme Widgets proposal sent May 22, CFO sign-off pending. Lattice Provisions, discovery done May 28, proposal due June 6.
• WARM (3): Two referrals from Marcus, both with discovery scheduled for week of June 9. One inbound from the latest article, discovery on June 4.
• STUCK (4): Three of the four are Marcus's prior referrals (May 1, May 5, May 12), all ghosted after sending the proposal. The fourth is an inbound from April that engaged on the proposal then went silent.
• DEAD (3): Two from March that never re-engaged. One from April that was always ICP-marginal.

Step 3 prompt output: "Three of your four STUCK deals are referrals from the same source (Marcus). All three went silent after proposal. The pattern suggests Marcus's referrals don't tend to close — possibly an ICP mismatch, possibly a budget framing issue Marcus isn't setting up. Single highest-leverage action: send a 21-day nudge to all three this week, AND have a 10-minute call with Marcus before the next batch of his referrals comes in."

Step 4 actions: three nudges drafted (4 min using the Pack's follow-up prompt), Marcus call scheduled for the following Tuesday (2 min), two DEAD prospects archived to a "lost" folder (2 min), the inbound-from-article warm one moved to the calendar (1 min). Total step 4: 9 minutes. Total review: 28 minutes.

A month later, the consultant runs the review again. Two of Marcus's three referrals replied to the nudge — one with "actually we're going in a different direction" (clean close-out, archive), one with "timing got pushed, can we restart in July" (move to follow-up). The Marcus call surfaced that he's been describing the engagement to his referrals in a way that's setting wrong expectations — fixable. The dies-of-neglect pattern, caught.

This is what the 30 minutes produces in practice: surfaced patterns, sent nudges, archived dead deals, recovered timing on a stalled one. None of it would have happened without the recurring block.

What the nudge looks like for a STUCK deal

The most common output of the review is "X deals are stuck and need a touch." The touch is the same shape regardless of which prospect it goes to: brief, specific, no apology, no "just checking in."

Bad: "Hi! Just wanted to circle back on the proposal from last month — let me know if you have any questions! No rush, just wanted to see where you're at!"

Good: "Hi [name] — wanted to surface this is back in your queue. The proposal from [date] would mean a [date+30] start; if that's still the right timing, I can hold the slot. If something's shifted on your end, happy to know that too. No pressure either way."

The difference: the good version names a date, surfaces a forcing function (the slot won't be held forever), and explicitly invites the no. You'd rather hear "actually, we're going in a different direction" on day 21 than wonder for another month. The nudge is the way to get the answer in either direction.

This is the same family of nudge as the late-payment cadence covered in Article 17, with the same operating principle: scripted, dated, professional, ends in an unambiguous next step.

Pitfalls

Doing the review and not doing the actions. This is the dominant failure mode. The review feels productive in itself; the actions are where the revenue lives. Block the 30 minutes; the analysis is the first 18, the actions are the last 12. Don't end the block until the actions are sent.

Optimistic labeling. Marking a deal "WARM" when it's been silent for 3 weeks and has no scheduled next-touch is fooling yourself. The point of the labels is honesty with yourself about what's real. A pipeline that's 70% STUCK is a real signal; a pipeline that's 70% WARM-by-fiat is a fiction.

Skipping the prompt step. The pattern-recognition is the part Claude does best — looking at 12 rows and noticing "three of these are from the same source and none of them are progressing." You'd notice the same pattern eventually, but probably two months later when revenue lags. The 5-minute prompt step accelerates the noticing.

Doing the monthly review only when the pipeline feels stressed. The point of the recurring cadence is that the review happens whether or not you feel like you need it. Months when the pipeline is full are still months where deals are dying — they're just easier to ignore.

Letting the review expand into the quarterly retrospective. Stay tactical. "What action this month" not "what should I change about my entire practice." The strategic version is the quarterly retro and belongs on a different day on the calendar.

The compound effect after six months

A solo consultant who runs this review monthly for six months ends up with three durable changes. First, the dies-of-neglect pattern stops — every deal either advances, gets archived, or has a forcing function on the calendar. Second, the pipeline list itself becomes accurate enough to base decisions on, which means choices about marketing investment, capacity planning, and pricing become data-informed instead of vibes-informed. Third, the quarterly retrospective improves because the monthly inputs are clean.

The trickiest part isn't the procedure — it's the recurring calendar block. Most solo consultants don't have a "first business day of each month, 30 minutes" event on their calendar. The first install is to create that event. Without the block, the review slips. With the block, the review happens whether you feel like it or not.

Where the procedure lives

The operational version — the pipeline-state template, the four-label classification, the paired Claude prompt for pattern recognition, the action-execution checklist, and the pitfalls list — is SOP 10 in The Solo Operator's SOP Bundle. Drop it into your operations folder, copy the recurring calendar event from the SOP, and the review fires on the first of every month automatically.

For the strategic complement, Chapter 8 of The Solo Consultant's AI Playbook covers the quarterly retrospective — the practice-wide review that this monthly review feeds into. Run both. The monthly is tactical; the quarterly is strategic; together they're the discipline that makes pipeline luck stop being luck.

Thirty minutes a month. The cheapest defense against the dies-of-neglect pattern, which is the single largest source of preventable revenue loss in solo consulting.