The summer pipeline lie: it freezes on contact.

It's the second week of June. You look at the dashboard. The number is bigger than it was in April. Coverage clears 3x. Pipeline by stage looks balanced. The leaderboard has movement. Nothing in any one cell screams problem.

Nothing screams problem because the calendar is doing the screaming for everyone.

June is the worst month of the year to trust your pipeline number. Not because the deals are bad. Because the calendar inflates the number on the way in and pulls the floor out from under it on the way out, and your dashboard is not built to tell you which one is happening.

Three things the calendar quietly does.

Three things happen between June and August in every B2B sales motion. None of them show up on a coverage report.

1. Buyer absence stretches your cycle silently. Your champion takes their two weeks. Their boss takes their two weeks. Procurement takes their three. By the time anyone is in a room together to make a decision, you've burned six weeks of cycle time you didn't plan for. The deal didn't die. It just slid. But your June close date didn't slide with it, because reps don't push close dates in June. Every push looks like sandbagging. So the date holds, and the number rolls forward looking healthy, right up to the moment July misses.
2. Sandbagged Q2 deals inflate June coverage. Reps know June is the make-or-break month for Q2. Anything that should have been added in April or May (but wasn't, because the rep wanted optionality on quota timing) lands in your dashboard in the first two weeks of June. The pipeline doesn't reflect what your team built. It reflects what your team revealed. Composition didn't change. Visibility did. You're looking at a confession dressed as growth.
3. Q3 inputs already happened, and aren't happening now. The pipeline that closes in Q3 is mostly built in April, May, and the first week of June. Late June and all of July do almost no pipeline construction in a normal B2B motion. The number you're staring at in mid-June is structurally the peak, not because the team is performing, but because the inflow tap is about to close. If you don't recognize you're looking at a peak, you'll treat it as a baseline.

The dashboard can't see this.

The standard pipeline report is built around a snapshot. It tells you what's sitting in stages on the day you pulled it. It cannot tell you which deals are sitting because they're progressing and which are sitting because the buyer is on a beach. It cannot tell you which line items are real net-new and which are just May activity reported in June.

Coverage clears 3x. The story is internally consistent. Every cell in the dashboard agrees with every other cell. The dashboard is not wrong. The dashboard is just answering the wrong question.

The question you actually need answered in June: what does this pipeline look like in eight weeks, after the slide we always pretend won't happen this year?

Run the August number.

Take the pipeline you're carrying today. Apply three filters honestly.

First, isolate the deals with a champion currently out of office or with a planned absence longer than a week between now and forecasted close. Push those by four weeks minimum. Most leaders refuse to do this in June because of the optics. The math doesn't care about optics.

Second, isolate the deals where the buyer's fiscal calendar puts the decision in a different quarter than yours. A deal that needs to close on the buyer's Q3 boundary, not yours, is not in the quarter you've placed it in. Move it.

Third, separate the May-built pipeline from the June-built pipeline. May-built is real. June-built (anything that hit your dashboard in the first two weeks of this month) is overwhelmingly sandbagged inventory, which means it was already mature, which means it's closer to close than your stage indicates. Pull those forward, not push them back. The composition correction usually cancels itself out in dollars, but it tells you something you can't see otherwise: the pipeline didn't grow in June. It appeared in June.

What's left, after those three corrections, is your actual Q3-survivable pipeline. Take that number, multiply by your real conversion rate by play (not your blended rate; see the coverage lie), and you have your honest August forecast.

In almost every team I've worked with, the corrected number lands between 55% and 70% of the reported number. Not because anyone is lying. Because the calendar lies on everyone's behalf.

A worked example.

Picture a team carrying $9M in pipeline against a $3M Q3 number on June 9. Coverage reads 3x. The dashboard glows green. The team is calm.

Apply the filters. $2.1M has champion summer absence the team hadn't called out. Push four weeks. The closeable June-through-September number is now $6.9M. Of that, $1.4M sits on the buyer's Q4 fiscal boundary: that's an October deal in a Q3 column. Move it. Now $5.5M. Of that, $1.8M is May-built deals the rep added to CRM after the May 30 forecast call, and $700K is true June-built net-new.

Split them out and you see the truth: the team built $700K of new pipeline in the first eight working days of June, against a forecasted need of roughly $1.5M per fortnight to maintain the trajectory.

Same dashboard. Same number. Different story.

The first lie was that coverage means safety. The second lie is that pipeline you can see in June is pipeline you'll close in Q3.

The first lie gets told to boards. The second one gets told to ourselves.