Hi Christo,
mine is just a comment as other users already provided useful links. Normally when I explain a component (as in your case the CRM opportunity) and I fail, it's not only a lack of words or failure to express the concepts, but because I wasn't able to show them
how the component is related to their current business processes or why it can be a good reason to start to use the component if they are not.
Normally the problem is shifted to the company business processes. I make a stupid example: let's say the sales team it's not using opportunities at all, they prefer to create directly an order when they finalize the sales and keep the pre-agreement phase
using appointments and notes. So they will say: why I need to use another entity when my sales process is going fine? A simple reason can be "statistics", tracking using the opportunity can easily provide more useful informations to the sales team:
% of opportunities lost or win, average days from creating an opportunity and create an order (or lost it). and when all these informations can be compared with more data coming from CRM they will think by themselves what they can create (for example volume
of opportunities won/lost for account's country)
I am also a developer and of course not a salesman, but every time I customize a CRM for a client, I absorb a bit how they business processes work and especially why (if they use lead entity or they prefer to use only contact with a boolean flag). I think
this is the knowledge you need to transfer, from a (little sponge) salesman to another.
My blog: www.crmanswers.net -
Rockstar 365 Profile
