In my previous post of this series, we discussed how to implement ACME’s sales pipeline through the creation of a business process flow (BPF) considering both the Lead and Opportunity entities. We created two business processes, one for opportunities that originated from leads, and another for opportunities that did not originated from leads.
In this post we will discuss how to implement ACME’s opportunity probability matrix through the creation of business rules.
(more…)In my previous post of this series, we discussed some fundamental concepts of the sales pipeline and how Dynamics CRM handles the sales process. While considering the requirements of ACME (a fictitious company), we defined the stages of their sales pipeline, and started to outline the functional specification of the opportunity entity, including the elaboration of an opportunity probability matrix.
In this post we will discuss how to implement ACME’s sales pipeline through the creation of a business process flow. (more…)
No matter how orthodox and customisation-free you want your Dynamics CRM implementation to be, there is always one aspect of Dynamics CRM that must be customised: The Sales Pipeline. Such customisation is required if you want the default sales pipeline to work properly, as well the sales pipeline report.
The issue at hand is, how can we set-up a functional sales pipeline with charts and reports, yet keeping Dynamics CRM as close as possible to its out-of-the-box functionality?
In this series of posts, we will be covering the implementation of a sales pipeline based on the requirements of a fictional organisation, called ACME. Dynamics CRM 2013 provides new tools and functionality that enable us to create a streamlined business processes, including a sales pipeline.
Because there’s so much to discuss here, I’m going to break this up into multiple parts. And in this first part of the series, I’d like to address the fundamental concepts of the sales pipeline and introduce some key points on how to conduct a requirement assessment.
(more…)In Dynamics CRM, no entity tends to cause more confusion to like the Lead entity. I do get that newcomers to CRM might be confused, and after many training sessions and constructive feedback I reckon I came up with a nice approach to explain the importance of this entity. Most people get it, but some companies still decide not to use the lead entity. Sometimes they genuinely don’t need to use it; but quite often then don’t use it because they don’t understand the true potential of leads.
For Dynamics CRM 2013, Microsoft has performed some significant changes in the Lead entity with the intuit to address those issues, which I will be covering in this post.
(more…)