|
| |
 "Our Take"
| | About
"Our Take"
"Our Take" is a collection of daily
vignettes covering a wide range of CRM topics. It's an attempt to add our own spin to the world of CRM. We will use the column to share our perspectives, opinions,
epiphanies, web nuggets, or quite frankly anything that moves us. Get ready to expect the unexpected. And, don't be shy about sharing your thoughts.
|
9/20/06 - A New Type of Suite
In the past, common thinking describes a suite solution as a portfolio of applications available from a single vendor. One reader suggested that we need to broaden our definition of suite solutions.
He writes, "A suite does not necessarily mean that you have a single-vendor solution. For example, when Microsoft finishes re-coding the Great Plains program in .NET so that it becomes part of the CRM product, then I would consider that a suite. The suite would consist of modules sharing a single database and single code base, covering sales, support, marketing, general ledger, AP, AR, etc.
The Microsoft example with Great Plains still fits in the single vendor category but what about the ecosystem created by Salesforce's AppExchange? That involves countless companies adding functional extensions to the core Saleforce offering. Maybe we shouldn't count the suite solution as out of favor forever.
Gary Lemke, Publisher
(Share your thoughts)
| |
|
