Company One has relatively short sales cycles (weeks or a few months) and fairly small average deals sizes ($12 to $30 thousand average annual value). They have ten sales opportunity stages.
Company Two has long sales cycles (nine to eighteen months) and large average deal sizes ($1 million average annual value). They have four sales stages.
As we have helped each organization work through both current sales pipeline analysis and creating sales forecast models, it became clear to us that each could benefit by realigning their sales stage definitions.
Aligning Sales Pipeline Stages to Customer Buy Cycles
Company One could reduce the number of stages they use since many of their prospects move very rapidly through the sales process. They could also consider increasing the frequency of pipeline reviews to develop a better feel for how deals are moving through their sales pipeline and spot gaps more quickly. Fewer stages would make it more clear for the reps where to place opportunities and this would create more accuracy at all pipeline stages.
Company Two actually needs more pipeline stages because of their longer sales cycles. More stages would improve their measurement of sales pipeline velocity (the time it takes opportunities to progress from stage to stage). Too few stages means opportunities can stay in one stage for a very long time. This makes it hard for sales management to identify those opportunities that are taking longer than average in any one particular stage. Pipeline velocity is a very important measurement in projecting sales revenues.
Along with aligning sales stages to customer buy-cycles, another best practice to improve accuracy is tightly defining each stage by the activities that must occur for a deal to progress. Following is a template we have recommended in the past for companies with medium to long, complex sales cycles. You can reduce the number of stages if your sales cycles are shorter by combining some of the phases.
Opportunity Stage
%
Activity
0
Opportunity ID’d
0%
Potential opportunity identified /