SugarCRM's biggest problem is Matt Asay.
You see, SugarCRM has made its software too easy to use. I have become my company's SugarCRM administrator, which is a fairly scary thought. I'm the last person you want managing your IT. But SugarCRM is so easy to install, customize (I build custom fields all the time now, which makes SugarCRM highly tailored to my company, not anyone else's), and use that it has been simple for even a simpleton like me to manage.
But this can be a bad thing.
As a case in point, I recently upgraded our SugarCRM implementation from a stable 4.2.1 release to the beta 4.5 release...not realizing (fool that I am) that production instances of SugarCRM (or of any software, especially software that includes important customer/partner information that I'd rather not lose) should not be upgraded willy-nilly to beta versions of a product. SugarCRM, of course, had this posted all over their website. But I viewed upgrading my Sugar in the same way I upgrade my browser: early and often, to whatever the latest and greatest is, even if it doesn't work. :-)
In this case, the SugarCRM's 4.5 Beta version works great. We haven't had a single problem with it. This has not helped me to learn my lesson, but stern rebukes from Clint and the guys has at least helped me to realize that I'm a complete bozo.
Still, it does raise an important question: as great development teams (like SugarCRM's) make enterprise software easier and easier to use, what's to stop bozos like me from misusing the software? Perhaps SugarCRM's next job is to actually make it harder to use their software, so that I will not be tempted to quit my day job and become a full-time IT administrator.
Now there's a frightening thought.
Posted by Matt Asay on September 2, 2006 05:01 AM












