The forecast is a story
you tell twice.

Once to your VP. Once to yourself. Most reps only rehearse the first telling.

Here is the position: the forecast you miss was rarely a lie to your boss. It was a lie to yourself that your boss happened to overhear. The commit call just made it official.

The tell is the date. Ask a rep why a deal closes March 28 and the honest answer, more often than anyone admits, is "because our quarter ends March 31." That is not a close date. That is a hope with a calendar attached. The customer does not know your fiscal year exists, and nothing inside their building is conspiring to meet it.

Date the deal to their calendar, not yours

A close date I will defend is anchored to an event on the customer's side that I can verify: a campaign launch they have committed to, a budget cycle that expires, a program their VP has already announced internally, a renewal that lapses. If the deal slips, something visible breaks for them — not just for my quota. When nothing breaks for the customer on a slip, the date is decoration.

Three questions before a deal goes in commit

I put a deal in commit only when I can answer all three, out loud, without hedging:

• Who signs — the named person with authority, not the title I assume has it. If my champion "will find out," I have not done discovery; I have done a demo.
• What happens on their side the week before — legal, security review, procurement queue. If I cannot narrate their internal week, I am forecasting my own optimism.
• What breaks for them if it slips — the customer-side cost of delay. No answer means no urgency, and no urgency means next quarter.

Deals that fail a question do not leave the pipeline. They leave commit. That distinction — commit as a verification standard, pipeline as a working set — is the whole discipline.

Why I hold this line

The year that proved it to me was a merger year. In December 2024, Informa Tech and TechTarget combined mid-cycle around my book — new paper, new systems, contacts moving on both sides of the table. Mergers punish soft forecasts, because every date built on "our quarter end" quietly loses its sponsor. The deals that held were the ones dated to customer events that survived the reorg. I finished the first half at 110% of target, and the forecast — told honestly, twice — is a large part of why.

A forecast is not a persuasion exercise. It is a verification exercise you happen to present. Get the second telling right — the one to yourself — and the first one takes care of itself.