Forecast Accuracy Advisory

The one everybody knows is dead
keeps moving.

Next quarter. Then next month. Then next week. Then next quarter again. Your team knows which ones they are. They keep them alive because losing a deal is expensive and nothing about calling it is safe. A full year, two or three companies, spent fixing the thing underneath that.

Book a scoping call
#1 Amazon Bestselling Author · Presales Navigation System Sol/Con 2026 · main stage, Chicago 28 years in presales
Dmitri Lee speaking on stage

Why the forecast drifts.

Calling a loss is expensive

A rep who takes a deal out of the forecast pays for it immediately, in coverage and in how the quarter reads. Keeping it in costs nothing until the last week. The incentive points one way, and people follow it.

Inspection becomes reporting

At quarter end there is never time to give every deal the detail it deserves, so the review turns into a status update. Deals get described rather than tested, and description cannot tell you what is real.

Effort lands in the wrong place

Dead deals are high maintenance. It takes far more effort to drag a deal with no legs than to walk a real one to the finish line, and the healthy pipeline never gets built because nobody has the hours left.

The earliest signal has nowhere to go

Your engineers usually know first. They hear the weak discovery answer and the missing executive. Without a shared standard, that concern arrives as an opinion, and an opinion does not survive contact with someone who needs the deal.

Three buckets, and the middle one matters most.

Real

Protect them and finish them.

Deals that stand up to inspection get the hours, the executive attention and the close plan. Most teams under-serve these because the noisy ones take the room.

Not real

Take them out early.

A dead deal was never yours to lose. Killing it early is the win, and the only real cost of doing it late is everything it consumed on the way.

The middle

Grow legs, or go.

Most of the pipeline sits here. Half real, going nowhere in particular. This is where the year is actually spent: what each one needs to become real, who has to act, and how long it gets before it comes out.

Firm enough to hold, safe enough to say it out loud.

Anyone can run a hard inspection. Anyone can run a comfortable one. Holding both at once is the hard part, and it is most of the work. The structure has to be firm, so nothing gets waved through on confidence alone. Calling a loss has to cost the person nothing, or you have simply taught them to hide it better. Competitive people hate to lose, which is why the distinction matters: losing a real deal is a loss, and taking out a dead one never was.

Same pipeline. Same headcount. Different numbers.

One SE organization, two quarters

Forecast accuracy from 45 to 78 percent. Win rate from 26 to 41 percent. Slipped deals down 31 percent. 18 percent more revenue. No change in headcount.

42 sales engineers, eight months

Forecast accuracy from 52 to 80 percent. Roughly five hours per engineer per week freed from deals that were never real. New-hire ramp from six months to three.

Both figures come from installing this discipline inside sales engineering organizations. The advisory applies the same inspection standard at the leadership layer.

A full year. Two or three companies.

Who it is for

The person who owns the number.

Chief Revenue Officers, VPs of Sales, and the Revenue Operations leaders who carry the forecast with them. Your presales leader is in the room by the second conversation.

What it is not

An advisory role, not an operating one.

I do not run your pipeline and I do not own your forecast. Your leaders keep every call. The point is that the capability stays behind when the year ends.

When it starts

January, each year.

Engagements run on the fiscal year, so scoping conversations happen the quarter before. Capacity is two or three companies, and it is set deliberately.

What leaders ask first.

What is forecast accuracy advisory?

A full year working with the leaders who own the number, installing deal inspection as a rhythm rather than a meeting. The pipeline gets sorted into deals that are real, deals that are not, and the larger group in the middle that could go either way. The outcome the engagement is measured on is forecast accuracy.

How is this different from training the sales engineering team?

Training installs a shared method inside a team. This advisory works with the leadership layer on how deals get inspected, what gets asked, and what happens to the answer. No curriculum is delivered to engineers as part of it, although the two work well together.

Do you take over the forecast or run the pipeline?

No. This is an advisory role, not an operating one. The leaders keep every call. The work is building the inspection rhythm and the judgment that sits behind it, so the capability stays after the year ends.

How many companies do you take, and when does it start?

Two or three companies a year, each for a full year. Engagements start in January, so scoping conversations happen in the preceding quarter.

Start with a scoping call.

Thirty minutes on how your forecast gets built today, where it drifts, and whether this is the right shape for your year.