August 23, 2026

Last February a founder I work with archived twenty-six deals in one afternoon. Nearly half his pipeline. The two quarters since have been the best in the company's history. He credits the cut.
I work with B2B founders at the 5 to 100 person stage who run the sales motion themselves, and the advice they hear everywhere is the same. Build more pipeline. Three times coverage, four to be safe. Volume as insurance.
Past a point, volume is a tax. Every dead deal you keep costs attention your live deals needed. Worse, it costs you an honest read of the business. A pipeline padded with maybes cannot tell you anything true.
The evidence runs the other way too. Jen Allen-Knuth shared won-lost data this year: won deals averaged seventeen stakeholder relationships, lost deals averaged five. Read that carefully. The gap between winning and losing was not how many deals got worked. It was the depth of work inside the deals that mattered. Seventeen relationships in one account is a serious investment of founder time. You cannot make it across a bloated pipeline. The maths does not allow it.
To be fair to the coverage crowd, there is an exception. If your close rate is stable and everything in the pipeline passed real qualification, more volume does scale revenue. That is rare at this stage. The pattern that fails is adding volume to escape qualification: more names in, so the hard questions about what is already there never get asked.
The afternoon exercise, the same one that founder ran. Rank your open deals by the last action the buyer took. Their action, not yours. A meeting they booked. A stakeholder they introduced. Anything with no buyer action in thirty days moves to a separate list. Those deals stopped moving. The pipeline had no way to say so.
What is left is your actual pipeline. It will be smaller. It will also be workable at seventeen-relationships depth, and it will produce a forecast you can say out loud without flinching.
Cutting is the doorway. A pipeline you can read is where a revenue operating system starts, because everything else it runs works on what is in there.