Re: SugarCRM?

Helge Hess <[email protected]>
Newsgroups gmane.comp.cms.opengroupware.discuss.general
Message-ID <[email protected]>
On Jan 5, 2005, at 10:29, Olivier Hallot wrote:
> I don't see however that just revamping the OGo skins will lead us to 
> CRM or PM. There is more to do IMHO.

To have a full CRM or PM system, certainly. To be the best available 
OpenSource system - maybe not.

> We can start by implementing project templates. A sales cycle has 
> many, many activities and information gathering that has to be done 
> again and again on every new sales opportunity. My personnal 
> experience on CRM is that a sales cycle has tens of tasks, gathers 
> same buch of documents each time, and requires lots and lots of 
> information to pour in, to be very effective. Futhermore, all this 
> info is to be gathered to feed the latest business intelligence gizmo 
> brought/bought by your boss. Bosses like it "kiss": red equals bad, 
> blue equals good.
>
> Then we also need a workflow engine. This is necessary if your sales 
> cycle or project management has a team of people with roles to play. 
> (Roles and function are different entities).

All this is true but not relevant in the discussion unless you can 
point to SugarCRM pages which show that the mentioned features are 
indeed implemented by that tool.

I'm not interested (in this thread) in a wishlist what the perfect CRM 
is supposed to do. I'm interested in the least-amount-of-work approach 
to "reapply" OGo in a useful way. If SugarCRM doesn't have 
functionality like you mention, it is still very popular without them!

Chris "hinted" that I'm missing a lot of features in that tool. If this 
is the case, we can just drop the idea and discussion ;-)

Greets,
   Helge
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.