

EXAMPLE: A new sales person in the team is told by the prospective buyer that a decision will be made by March 1 (60 days into a sales cycle) in an effort to have the solution tested by April 11. If he does not make the decision by end of March he will loose his budget. Seems valid enough right?.
Well the experienced QBS having dealt with this many times before, knows the deal will get stuck in legal and that as a result a senior executive will approve budget re-alignment, he also knows that engineering can already start testing the product to ensure April 11 date is met.
In effect the experienced QBS is aware of the average sales cycle and it taking into account constants such as average time it takes legal to agree, time it takes the proposal team to write the offer up, etc.
In my opinion there is far more constants in a sales cycle than well compensated sales staff like to let a company belief, here are some of them:

- Time it takes from first meeting to proper follow-up
- Time it takes to get an NDA established
- Time it takes to put a proposal together
- Time it takes for a response to a proposal
- Time it takes to work an agreement through legal
- Time it takes to do a DnB/Financial analysis

- Time it takes for the prospective buyer to make decisions
End.