Feature improvement - Probability of Winning for Pipeline Stages

We've added "Probability of Winning" to Opportunity pipeline stages. Now you have the option of setting a “Probability of Winning” percentage when you create your pipeline stages and the percentage will automatically update when your Opportunity reaches that stage (see screenshot below).

To learn more, check out our Product News announcement and our Help Article, How to Set up a Pipeline.

This improvement is available on all Insightly plans.

0

Comments

11 comments
  • This is a great feature and you can then export the opportunities to Excel and compute the probable revenue forecasted for the opportunity against a customer field that scoped the overall revenue. In fact, I have used both a "P-go" and a "P-win".....will the opportunity even manifest itself, and if it does what is the probability of really winning the business.

    0
    Comment actions Permalink
  • Hi Brenda, 

    looks like this improvement might have introduced some unwanted side effects.

    Now, when you create a pipeline stage, you can not save it unless you allocate an activity set. Though often (and previously) you just want to use pipelines  and stages to track your work, without activity sets and tasks. 

    Okay, so I created and empty activity set with no tasks in it. But I can not allocate this to the pipeline stage either. It is not even listed in the drop down for allocation alternatives.

    Finally, I created a single task in the activity set, and now I can allocate it as previously. But this is no good. I want no tasks, and now I would have to deal with (clean up) a single dummy task for each stage. 

    I'd be surprised if this is what you intended. 

    And finally, after doing this testing, I'm unable to delete my dummy activity set. I deleted the pipeline, so it's not used anywhere. Even emptied my recycle bin. But the delete option is not available next to me new test only activity set.

    Sure this can be easily fixed, and the stage probabilities idea is a great new feature.

    Cheers, P. 

    0
    Comment actions Permalink
  • Hi Peter,

    You are correct. This was not intended and the team is working on it as we speak. I'll update you here once they have a resolution. Thank you!

    0
    Comment actions Permalink
  • Hi guys, this problem is corrected now. All is good.

    0
    Comment actions Permalink
  • Thanks for letting us know, Peter.

    0
    Comment actions Permalink
  • This worries me - does your development team not do regression testing?

    0
    Comment actions Permalink
  • Forcing us to use the pre-defined probability for each stage makes the functionality completely useless to those of us that are not too lazy to monitor and update our probability of each of our opportunities. Not making this feature optional is absurd!

    One of the primary uses of tracking opportunities and their value is to be able to calculate an Expected Value for our pipelines. By forcing us to use the pre-defined probability you complete disable this critical calculation and force us to go back to tracking opportunities by spreadsheets. 

    **** Before you respond with "you can remove the probability value from the stage", go try it yourself. You cannot do that. It will repopulate with whatever value was there. Even if that worked, it would still reset to null every time we progressed an opportunity to the next stage.

    Way to go, you now completely hobbled one of the primary uses of a  CRM system by rolling out another unannounced feature to unsuspecting users.

    0
    Comment actions Permalink
  • Any response to the final comment? 

    1
    Comment actions Permalink
  • Any response to this disabling of a critical function?

    0
    Comment actions Permalink
  • Hi Adrian:

    The Probability Value field is not a required field when creating a record and you should be able to change the data once you've added it. Can you share steps with screenshots of what happens when you remove the Probability Value? I think you're saying that it repopulates when removed, if this is the case we would like to take a closer look.

    Thank you in advance for your help.

    0
    Comment actions Permalink
  • Here's what happens;

    - I create a new opportunity in the system starting it with a probability of winning related to specific circumstances in the first stage in my Pipeline. 

    - As the Opportunity progresses, I move it to the next stage in my Pipeline. Regardless of the reality of the circumstances that I have worked hard to create, your system forces the Opportunity to reflect the probability that is in the Stage, completely rendering the work I've done to figure out the likelihood of closing the deal out the window. 

    - If I leave the pre-defined probability in the Stage blank, it still gets populated with whatever value was in there previously. There is no way to override the entry for individual Opportunities. 

    - Forcing your users to use the pre-defined probability for each Stage renders the whole Expected Value analysis worthless.

    Have you or anyone on the Product Development team ever try working through some User Case situations to try to understand how your users might use the product? It seems like an obvious first step for a real product team....

    0
    Comment actions Permalink

Please sign in to leave a comment.