Creating quote from opportunity versus creating opportunity from quote

According to the way I was taught to use sugar while working at sugar, was to convert a lead into an account/contact/opportunity and then to go back in and create the quote. This process has always worked for me and I have carried it over into my new job. However, the new job has been using sugar differently and I want them to convert to my process. As such, they asked me to put my process onto paper in a step-by-step guide. As opposed to reinventing the wheel, I searched through the sugar website and found a article in the support section on how to create an opportunity from a quote. What I did not find, was anything detailing the opposite on how to create a quote from an opportunity. Have I been doing it wrong all this time? What is the best practice? I'd be curious to get others feedback. Even better, if somebody already has a step-by-step guide written out on how to create a quote from an opportunity. 

Parents
  • Want to add to what Ben Hamilton mentioned in his reply.

    When you have sales persons who needs to generate quotes often, they tend to go to Quotes first and then create an Opportunity. When you have a product catalog that has 100s and 1000s of products and you need to churn many quotes a day, the sales person tendency is to get the Quote out from his side to the customer.

    However if the sales cycles are much longer and needs lot of nurturing, it is better to have Opportunity first and then Quote. 

    Sugar might have created  "Quote to Opportunity" button to address the need of the sales person who churns quotes during the peek period.  After the quote is sent they can happily create the opportunity and manage their pipelines. 

    We happen to implement as a proof of concept and internal research, an Opportunity to Quote conversion and then synching Opportunities with Quotes if there are more changes in the Quote.

    But as a best practice, if your business is having big product catalog and your sales team's core activity is to send many quotes a day / week, following "Quote and convert to Opportunity" process is better.

    Otherwise you create the opportunity, nurture it and when the right time manually create the Quote. But again if your product catalog is large and you want to avoid the manual element, then you can get the "Opportunity to Quote conversion" features for your CRM.

    I think your developer or your partner should be able to help you out since it is not a configuration but customisation.

    With Warm Regards
    Ram Kumar

    www.bhea.com

    Ram Kumar LK

    Sr Solution Architect

    https://www.bhea.com

Reply
  • Want to add to what Ben Hamilton mentioned in his reply.

    When you have sales persons who needs to generate quotes often, they tend to go to Quotes first and then create an Opportunity. When you have a product catalog that has 100s and 1000s of products and you need to churn many quotes a day, the sales person tendency is to get the Quote out from his side to the customer.

    However if the sales cycles are much longer and needs lot of nurturing, it is better to have Opportunity first and then Quote. 

    Sugar might have created  "Quote to Opportunity" button to address the need of the sales person who churns quotes during the peek period.  After the quote is sent they can happily create the opportunity and manage their pipelines. 

    We happen to implement as a proof of concept and internal research, an Opportunity to Quote conversion and then synching Opportunities with Quotes if there are more changes in the Quote.

    But as a best practice, if your business is having big product catalog and your sales team's core activity is to send many quotes a day / week, following "Quote and convert to Opportunity" process is better.

    Otherwise you create the opportunity, nurture it and when the right time manually create the Quote. But again if your product catalog is large and you want to avoid the manual element, then you can get the "Opportunity to Quote conversion" features for your CRM.

    I think your developer or your partner should be able to help you out since it is not a configuration but customisation.

    With Warm Regards
    Ram Kumar

    www.bhea.com

    Ram Kumar LK

    Sr Solution Architect

    https://www.bhea.com

Children
No Data