Day 40 · Phase G

"Pipeline is up this month" is usually not good news. It's congestion.

Stages · conversion rates · pipeline value and forecasting · diagnosing funnel health·4 moves · 4 diagrams
Total pipeline value is the least informative number on the board and the easiest one to fool yourself with — and it's the only one most people look at. The quarter is actually decided by three others: your stage criteria, your flow rate, and whether you have the nerve to mark deals dead.
Your pipeline is every deal you haven't closed yet; the funnel is the shape those deals make when you line them up by stage. Both words have been reporting props for so long that most pipeline reviews are really a form of self-consolation. Four moves take it apart, in order. One, redefine stages by what the buyer did — anything you can complete on your own doesn't count. Two, compute win rate on a cohort: the rate you get from "deals closed this month" is almost guaranteed to be inflated. Three, stop trusting the weighted forecast — the number it produces corresponds to no reality that can occur. Four, read health as flow, not stock: when the total goes up, the cause is usually that things got slower, not that more came in.
MOVE 01

Stages are defined by what the buyer did, not by what you did Anything you can complete alone tells you nothing about the outcome.

exit criteriacostly signalsintention–behavior gap
"Proposal sent." "Demo delivered." "Followed up." These stage names share one flaw: the action sits entirely on your side, so you can advance the deal whenever you feel like it. Anything you can do unilaterally is equally likely to appear in a deal that closes and one that dies, which means it carries no information at all. Only one kind of criterion moves a deal: an action the buyer paid for — with time, with disclosed information, or by pulling a third person in.
Whether a stage moves depends only on the right-hand column Lead Discovery Proposal Negotiation Won The costly thing they had to do They replied and booked a first meeting They said a number of their own (cost of the status quo) They gave a budget range, or introduced the payer They sent the papers to legal / procurement They signed ✗ Not criteria: you sent the deck, you ran the demo, you emailed the quote. You can do all three alone, so they show up as often in deals that die as in deals that close. Fallback question: if I do nothing after this step, will they still come to me? No → don't move it.
The meeting ends and the customer says: "This is really interesting. Send me the proposal and I'll push it internally."
✗ Treating a courtesy for progress

You move the deal from Discovery to Proposal and put 50% on it. What you actually received was a polite closing line. "Push it internally" has no name attached, no date, and no next step — yet in your sheet it has become a number, and that number goes into the forecast.

✓ Trade a small ask for real information

"Happy to. Two things before I send it: who's the main reader? (wait for a name) — then I'll build the version they care about. And roughly when could they look at it? Should we just book twenty minutes with the three of us?" A name plus a booked meeting means the stage moves. A vague answer means the stage and the probability both stay exactly where they were — and you've lost nothing.

Script · rewrite each stage name as a buyer action

1. Audit: list the stage names you use now and ask of each, "is this something I complete, or something they must do?"

2. Rewrite: "proposal sent" becomes "they booked the next meeting and named who attends"; "followed up" becomes "they replied with a time."

3. The fallback: if I do nothing after this step, will they still come to me?

4. Forward only on evidence: never advance a stage on an unmet criterion, but do move deals backward when they sit. The most expensive lie in any pipeline is a deal parked in Negotiation for three months.

Why it works

An action is a signal only when it is more expensive for someone who isn't going to buy. Your own actions cost the same either way, so they carry nothing; the buyer clearing calendar time, naming a number or pulling colleagues in has a real price, and only pays off if they intend to proceed. Meanwhile "we're very interested" is an intention — and the gap between intention and behavior has been measured over and over.

  • Hard evidence · intentions move a lot, behavior moves a little: Webb & Sheeran (2006, Psychological Bulletin) meta-analyzed 47 experimental interventions and found that raising intentions by a medium-to-large amount (d ≈ 0.66) produced only a small-to-medium change in actual behavior (d ≈ 0.36). Peer-reviewed meta-analysis — strong. Translated: using "they said they want it" as a stage criterion means forecasting from a measure known to shrink by half.
  • Hard evidence · a signal must cost the pretender more: Spence (1973, Quarterly Journal of Economics) — a signal separates real from fake only when it is costlier for the fake. So "they agreed to a meeting next week and put you in front of finance" is worth many times "they said they were very interested": the first costs calendar time and internal political capital. The work later won a Nobel Prize in economics.
  • Moderate strength · small commitments predict larger ones: Freedman & Fraser (1966, JPSP) — the foot-in-the-door effect, where agreeing to a small request raises compliance with a larger later one. Burger's (1999, Personality and Social Psychology Review) meta-analysis confirms the effect is real but modest and condition-dependent. Use it as a direction (ask for one small commitment in the meeting), not as a lever. Cross-ref psychology.

Boundary: costly actions can mislead too. Some buyers convene a three-way call purely to collect the third quote their process demands, and you are the stalking horse. Add a second test: are they willing to let you meet other people on their side, and to tell you the timeline and the alternatives? A deal where one person controls all contact and volunteers nothing deserves a discount no matter how deep the stage. Spotting a real champion is covered in the piece on mapping the decision chain.

MOVE 02

Measure win rate on a cohort, never on this month's closed deals The largest category of outcome never closes at all.

the denominatorsurvivorship biasbase rates
"Twenty deals closed this month, twelve won, so we're at 60%." That 60% is almost certainly false. The fault is in the denominator: only closed deals get in, and the single largest category of outcome never closes — those deals stall, drag and quietly age, and nobody ever marks them lost. There's only one way to see a real win rate: take one intake of leads and follow that whole cohort to where it actually ended up.
Same deals, two methods, a five-fold difference ① Snapshot · this month's closed deals 20 deals closed this month, 12 of them won Win rate = 12 / 20 = 60% Only deals that reached a verdict are counted ② Cohort · one intake, followed through 100 leads arrived in March. Today: 12 won · 28 lost · 60 still sitting there Win rate = 12 / 100 = 12% The denominator is the entire intake Where those 100 March leads actually ended up: Won 12 Lost 28 No decision 60 — the snapshot never sees this segment Most of those 60 will never close: nobody enjoys clicking "lost", so they just age quietly. The snapshot reports 60%, and every plan built on it rests on a five-fold overestimate. Your biggest competitor isn't a rival. It's no-decision — and it has no column in your report.
Script · four numbers that only mean anything by cohort

1. Cohort win rate: of the N leads that arrived in one month, how many were won six months later — denominator N, not "deals closed."

2. Stage-to-stage conversion: how much falls out between each adjacent pair, so you can find the worst leak.

3. Real cycle length: compute wins and losses separately. Mixed together neither is accurate, and losses usually drag far longer.

4. Share ending in no decision: the deals that were neither won nor lost. Most people are startled the first time they compute it — and that number, not the win rate, is where the improvement lives.

Why it works

Drop an entire class of outcome from the denominator and the estimate is biased upward by construction. This is textbook survivorship bias: you counted the ones that finished the process, and the ones that didn't finish carry the most important information. Layered on top is base-rate neglect — when forecasting a single deal, people substitute "this customer seems really warm" for "historically only two in ten get past this stage."

  • Hard evidence · representativeness crowds out base rates: Kahneman & Tversky (1973, Psychological Review) showed that when people are given an individuating description that "looks like" a category member, they will very nearly ignore how common that category actually is. Peer-reviewed, heavily replicated. The sales version: every line in your pipeline is one of these resemblance judgments, and your stage conversion rate is the base rate you're ignoring. Cross-ref psychology.
  • Classic case, not an experiment · survivorship bias: Wald (1943), working for the wartime Statistical Research Group, analyzed the distribution of hits on returning aircraft and argued the armor belonged precisely where returning planes showed no holes — the planes hit there didn't come back. The original memoranda are real, and Mangel & Samaniego (1984, JASA) give a systematic account. The popular retelling has been dramatized, so use it as an intuition pump, not as evidence.
  • Moderate strength · the outside view beats the inside view: Flyvbjerg (2006, Project Management Journal) argues for reference-class forecasting on large projects — predicting from the historical distribution of similar projects rather than from the details of this one — and reports substantially reduced systematic optimism. The theoretical root is Kahneman and Tversky's inside/outside view distinction. Observational work plus a methodological argument, not randomized: credible in direction, discounted in force.

Boundary: a cohort has to mature before it can be read, so a business with a three-month cycle waits at least three months. This is a retrospective tool, not a weekly dashboard. And when the sample is tiny — five leads in a month — no ratio deserves belief at all; look at absolute counts and days-in-stage instead. Some of that no-decision pile is also made of deals you should never have taken, which is the subject of the piece on qualifying.

MOVE 03

The weighted-pipeline number is a value that never actually occurs Deals are binary. An expected value only converges over many repetitions.

law of small numbersoverconfidencecalibration
Multiply each deal by a probability, add them up, and you get something that looks a lot like an answer. The problem isn't that it's imprecise — it's that the number corresponds to no reality that can occur: deals are binary, the money arrives in full or not at all. An expected value converges only across many repetitions, and eight deals in a quarter is a high-variance gamble, not a forecast. Worse, you wrote those percentages yourself, and self-reported probabilities run systematically high.
8 deals, each a 50% shot. The forecast says "4". Here is what actually happens. probability 0.4% 3.1% 10.9% 21.9% 27.3% 21.9% 10.9% 3.1% 0.4% 0 1 2 3 4 5 6 7 8 deals actually won → "4" is the single most likely outcome — and still only 27%. The 3–5 band covers about 71%. So roughly one quarter in three, you get to explain a number that makes no sense.
Script · replace one number with three tiers

1. Commit: only deals where the buyer has done something costly — gave a date, sent it to legal, named a budget. This is the tier you stand behind.

2. Best case: real movement, but still missing one decisive action.

3. Pipeline: everything else. It doesn't enter the forecast; it only tells you whether you have enough at the top.

4. Keep score: write each forecast down and grade it at quarter end. Of the deals you called 70%, how many actually landed? This is the only move with evidence behind it for making you more accurate.

Why it works

Two errors stack. First, using an expected value as a prediction on a small sample amounts to pretending variance doesn't exist. Second, the probabilities you feed it were never calibrated — people are chronically over-precise, stating more confidence than their hit rate justifies. Fix neither and the weighted pipeline is just your mood, carried to two decimal places.

  • Hard evidence · the law of small numbers: Tversky & Kahneman (1971, Psychological Bulletin) showed that people wrongly expect small samples to display the statistical properties of large ones, and so badly underestimate random fluctuation. "Eight coin-flip deals should give four wins" is the textbook form of that error. Peer-reviewed, classic.
  • Hard evidence · stated probabilities run high: Lichtenstein, Fischhoff & Phillips (1982), reviewing the calibration literature, found confidence routinely exceeds accuracy. Moore & Healy (2008, Psychological Review) separate this into three distinct things — overestimating yourself, believing you're better than others, and stating intervals that are too narrow — and identify over-precision as the most stubborn of the three. Peer-reviewed, strong.
  • Hard evidence · only feedback fixes it: long-running work by Murphy, Winkler and colleagues on weather forecasters found their probability-of-precipitation forecasts remarkably well calibrated — on the days they call 70%, it rains roughly seventy percent of the time. They are one of the few well-calibrated groups in the literature, and the difference isn't intelligence: it's that they get scored, explicitly, every single day. Which is why point 4 above isn't bureaucracy — it's the one route to accuracy the literature actually supports.
  • Contested · where the optimism comes from: Sharot, Korn & Dolan (2011, Nature Neuroscience) reported that people absorb good news more readily than bad when updating beliefs, and tied that asymmetry to signal tracking in the inferior frontal gyrus. The method has drawn substantive criticism — Shah and colleagues (2016) argued the updating paradigm can generate the asymmetry as a statistical artifact. Treat it as a hypothesis, not a settled mechanism. Cross-ref psychology / neuroscience.

Boundary: weighted pipeline isn't useless. With a large enough sample — dozens or hundreds of deals — and probabilities drawn from historical stage conversion rather than typed in by hand, it's a reasonable capacity-planning tool. It goes wrong when it gets treated as the answer to "how much money will arrive this quarter." It's a measure of book size, not a commitment.

MOVE 04

Pipeline health is a flow rate, not a stock When the total grows, the usual cause is that things got slower.

Little's Lawtime in stagestatus quo bias
"We have 2.6 million in pipeline" carries no information, because without knowing how long it takes to clear, 2.6 million can equal zero exactly as easily as 26 million can. Queueing theory settles it: in steady state, work in progress equals arrival rate times average time in system. So a growing total has exactly two possible sources — more arriving, or things moving slower. The second is far more common, and it isn't strength. It's congestion.
Same total, completely different disease Pipeline stock L = arrivals per month λ × average time in system W (Little 1961 — a theorem, not a heuristic) Lead Discovery Proposal Negotiation Healthy narrows evenly, stage to stage time in stage stays stable Top-heavy plenty of leads, none get in the problem is qualification and the first meeting, not volume Jammed in the middle 61 days average after proposal nobody with a budget in the room or no next step ever booked All three totals can be identical while the fixes have nothing in common: add volume on the left, fix qualification in the middle, go get dates on the right. So there are three metrics: days in stage, stage conversion, share aged. The total is their output.
Your manager asks in the weekly review: "Are we safe this quarter?"
✗ Reporting the stock

"We've got 2.6 million in pipeline against a 1 million target. We're fine." What you reported was book size. If 1.8 million of that has been parked in one stage for over ninety days, what will actually land this year may be under 400 thousand — and you've already said the word "fine" out loud.

✓ Report the flow, plus one specific gap

"At our cohort win rate of 22%, 2.6 million is only 2.6× coverage and I need 4.5×. But the gap isn't leads: average time after proposal is 61 days, and seven of twelve deals have no agreed next step. Two things this week — get a date on each of those seven, mark dead the ones that won't give me one, then top up leads against the real gap that leaves."

Script · a ten-minute weekly diagnosis, four questions

1. Which stage leaks hardest? The lowest stage-to-stage conversion is the only thing worth fixing this quarter. Don't spread effort evenly.

2. Which stage sits longest? A stage averaging three times the others isn't slow — it's missing a person or missing a decision.

3. How much is aged? Pull every deal sitting past twice its stage average: each one gets a fresh next-step date, or gets marked dead today.

4. Is coverage enough? Pipeline value ÷ target ÷ cohort win rate. At a 20% win rate you need 5× coverage, and that arithmetic doesn't negotiate.

Why it works

Stock is the result; flow is the cause. And the reason a pipeline only ever swells is that two forces push the same way: status quo bias on the buyer's side, where doing nothing is always the safest option, and sunk cost on yours, where the more you've invested the less you can bear to mark it dead. Both say "leave it in," so absent a deliberate purge, a pipeline drifts steadily toward being a graveyard.

  • A mathematical theorem, not psychology · Little's Law: Little (1961, Operations Research) proved that in a steady-state queueing system, L = λW. This isn't an empirical regularity; it holds unconditionally given the steady-state assumption, regardless of the business. So "the total went up" must decompose into "more arrived" or "things move slower." There is no third explanation.
  • Hard evidence · status quo bias: Samuelson & Zeckhauser (1988, Journal of Risk and Uncertainty) ran a series of experiments showing that merely labeling an option as the current state significantly raises how often it's chosen — and the effect strengthens as the number of alternatives grows. The buyer's default is always "do nothing," which is why the biggest competitor often isn't a competitor. Peer-reviewed, well replicated.
  • A single fMRI study (discount accordingly) · overriding a default takes extra effort: Fleming, Thomas & Dolan (2010, PNAS) found heightened activity in the subthalamic nucleus (STN) and inferior frontal cortex when participants rejected a default option, suggesting that departing from the status quo recruits additional inhibitory control. One study, modest sample — a mechanistic clue, not a settled finding. Cross-ref neuroscience.
  • Hard evidence · why you won't mark it dead: Staw's (1976, OBHDP) escalation-of-commitment experiments and Arkes & Blumer's (1985, OBHDP) work on sunk cost both show that resources already spent push people to keep investing in a deteriorating choice. On a deal you've worked for eleven months, the hard part isn't judging whether it's dead — it's admitting those eleven months are gone. Peer-reviewed, well replicated.

Boundary: Little's Law assumes steady state, so a team with heavy seasonality, or one that has just changed how it sells, will get misleading answers in the short run. And "mark dead" doesn't mean delete the person: it means remove the deal from the forecast, not blacklist the buyer. Some come back six months later on their own — reviving them is covered in the piece on silence and dead deals, and what a valuable follow-up cadence looks like is in the piece on follow-up discipline.

Your Day 40 Action

One hour to turn your pipeline back from a consolation document into a work surface.

One (20 minutes) · redefine the criteria: write out the stage names you use now and ask of each, "is this something I complete, or something they must do?" Rewrite every one of the former as a buyer action, and give each stage the fallback question — if I do nothing after this step, will they still come to me?

Two (20 minutes) · compute two real numbers: take the leads that arrived three months ago and count how many are won today, with the whole intake as the denominator rather than the closed deals. Then compute average days in each stage. Between them, those two numbers will probably overturn your view of whether the quarter is safe.

Three (20 minutes) · purge and tier: pull every deal sitting past twice its stage average, go get a fresh next-step date on each, and mark dead the ones that won't give you one. Split what remains into commit, best case and pipeline — and report only the commit tier.

Boundary: this machinery is for a pipeline with some volume in it. With five or six deals, skip the ratios entirely — the sample can't support any conclusion, and absolute counts and dates will serve you better. And don't treat the purge as self-punishment: the time freed by marking one deal dead is the cheapest new lead you will ever get.
Think It Through
1. I only have five or six deals. Is any of this statistics relevant to me?
The ratios genuinely aren't — a 40% win rate computed from five deals is indistinguishable from a coin. But only the second and third moves depend on sample size; the first and fourth don't.

Redefining stages by buyer action works on a single deal, and it matters more when you have few: with five deals, two of them are probably already dead while still consuming your attention, and that loss hurts far worse for you than for a large team. Time in stage needs no sample either — "the last time this buyer did anything on their own initiative was forty days ago" is already a conclusion.

What five deals should be read by is absolute counts and dates: what is the next step on each, what day is it booked for, and what did they last do. And when you're asked to forecast, don't hand over a weighted number — say "these two I'm confident about, those two depend on next week." An honest range beats a precise fiction.
2. My boss wants a firm number. Won't talking about binary outcomes and variance sound like I'm dodging?
It will — if all you offer is the statistics. So don't deliver it as a disclaimer; deliver it as a more useful structure. Not "I don't know," but "I've split it into three tiers."

Read it out like this: "Commit is 600 thousand — all three buyers have given me dates and I'll be held to that number. Best case adds 400 thousand, and all of it is stuck on the same thing: their finance people aren't in the room yet. Everything else I'm not counting."

That beats a single weighted 1.32 million in three ways. The part you're accountable for is harder — not a discounted soft number but one you'll stand on. The gap has a cause — finance isn't engaged, which is a specific action someone can be assigned. And your boss can make a resource decision from it. There's a fourth benefit that shows up later: people who report tiers get calibrated faster than people who report a weighted number, because tiers can be proven wrong and a weighted number never can.
3. Do freelancers and job seekers have a pipeline?
Yes, and this machinery serves them better than it serves big teams, precisely because individual opportunities are few and each one is expensive. A job search pipeline runs: applications sent → replies received → first interviews → final rounds → offers. Freelancing runs: people you've talked to → people who asked your rate → people who asked for a proposal → people who paid a deposit.

The rules don't change. Stage criteria are still their actions: "HR said they'd keep in touch" is not a stage; "they booked the next round and gave a time" is. Time in stage is still the earliest death signal: two weeks of silence after a final interview means that role gets downgraded in your sheet, rather than continuing to occupy your hope. And coverage still doesn't negotiate: if one final round in five becomes an offer, you need five final rounds, not one that "feels really strong." Most of the pain in a job search comes from staking everything on a single opportunity that hasn't given you a date.

The one thing to change is frequency. When opportunities are scarce, don't compute ratios weekly. Do one thing weekly instead: get a next-step date on every opportunity still alive.