You Might Be Wondering ...

Yesterday I sat in, as a “dummy guest”, on a remote demonstration and presentation that my newest client had set up. As part of my Discovery process I often like to listen in on a typical sales call. This call was going wonderfully, to the point where I was wondering what I could contribute as feedback other than a few minor cosmetic changes. The team had performed an admirable job of discovery, had identified two painful key business issues of their prospect, and had tailored their pitch to solving those problems and showing the economics of their solution.

There was budget, there was pain, and there was an agreed-upon approval process. I was seeing a deal leap forward in the sales cycle towards a successful close. The pre-sales engineer executed a masterful finish and handed back to the rep.

Who then said “you might be wondering..”

Everything fell apart because the salesperson decided to answer a question that had not been asked about deployment and support. The question was NEVER going to be asked because the customer was in “lets-go-mode”. The entire atmosphere of the call changed into suspicion and uncertainty over this late revelation, and ended with the dreaded “Thanks - we’ll think it over.” Disaster. Deal gets de-committed from the quarterly forecast.

Two lessons learnt from this call.

1.       It’s not always the Pre-Sales Engineer who opens his mouth at the wrong time and supplies too much information.

2.       There is a place for a rhetorical “you might be wondering” when it logically leads onto the next topic of conversation, and it is early in the sales cycle. But never at what was essentially the solution proposal phase.

Beware.