Re: How does Sugar Work???
Bruce,
Due to my lack of knowledge in ERP & CRM systems this is why I’m struggling a bit. I was asked to administer Sugar simply from an IT perspective, set new users up, change permissions (roles) etc. Sugar was going to be set up and fully customised for our needs by an external company for me to administer.
Our sales team currently use an application called ACT which they can manage all their clients, prospects & opportunities in. ACT doesn’t work very well as its too slow and falls over more times than it works hence the reason we turned to Sugar.
So I was asked to get involved with the customisation of Sugar for our sales team so sugar looks and reads like ACT. This meant the sales team don’t have to re-learn a different system. They wanted the menus, drop down boxes & layout to be roughly the same. Bear in mind I have no sales experience and no one really was willing to help me out learning the process of how out company sales process works. I then realised the person who was helping me implement all the customisation wasn’t really that bothered and it all got dumped on me.
So I set everything up as per what they wanted. I hit a few bugs along the way & realised I simply couldn’t change everything what they wanted me to. As an example they wanted everything with “Leads” on to be changed to “Opportunities”. I found when re-designing the modules you simply can’t change some bits without editing the pages in Dreamweaver, or editing the PHP script which is not something I have enough time or know how to do. I can do it, but I don’t know if it’s going to mess other thing s up and don’t have the time to test things out.
I’ve since had another meeting with the sales team and demanded I need to know what their sales process is and need a design spec on paper of exactly what they want. I go this and drew up a flow chard of out company sale process from stat to finish and wanted to compare this against how sugar works. If the 2 systems are too radical and simply work in different ways then it will be a case of saying to sales you will have to learn sugar and treat it as a different system from ACT. Maybe even draft up a glossary of terms from ACT into Sugar. So in ACT it would be called this but in sugar it’s called this etc…
So that’s why I wanted a simple overview of sugar, just to see if it actually can be done. One of the main points they made was, in Sugar you add a companies details into the contacts section and then the life cycle of making a sale and following it through starts from there. They wanted the contact section re-naming to “Clients” which I did. But this meant in their view a client is only a client when they have been successful in acquiring their business and this should come at the end of all the other processes and not at the start.
In my view it would be easier and a lot less messy if they just learnt the sugar way and this view is backed up by other sugar users in our company but the sales team really don’t want to change and to say they are digging their heels in would be an understatement. One of the main reasons for this is the company who were installing Sugar & supposed to be customising it said everything they wanted could be done so they are adamant on making all the changes.
So based on this info what are your thoughts?
.
OS = Win 2003 Server Std Edtn
Webserver = Apache 2.0.59
Sugar Version = 4.5.0h
MySQL = 5.0.27
PHP = 5.1.6
Bookmarks