Over the past several years, salesforce.com’s annual user conference Dreamforce has become a highly anticipated and entertaining end-of-the-year fixture for enterprise applications market observers. Well, Dreamforce 2011 was somewhat different as it took place in late August and early September 2011, but the vibrant feel of the event was no different. Indeed, in these prolonged times of bad economic news with businesses and government cutting spending across the board, one could again enjoy the unusually high attendance (45,000, for what it’s worth) and upbeat and “never a dull moment” atmosphere of the multi-day event, courtesy of salesforce.com’s CEO Marc Benioff and his executive team.
While Dreamforce 2009 was mostly about the continued growth of the vendor and the unveiling of Salesforce Chatter, the company’s quickly maturing social platform and collaboration cloud (covered in my mid-2010 blog series), the overall Dreamforce 2010 theme was cloud proliferation as well as salesforce.com’s further diversification and expansion in new frontiers (see my blog series for more details).
Dreamforce 2011 continued with the cloud proliferation theme (with new clouds such as Data.com and Heroku for Java), in addition to the theme of continued growth: salesforce.com is the first cloud company to exceed US$2.1.billion run rate and over 100,000 customers (ironically knocking on the door of the “evil empires” elite club). There have also been some acquisitions since Dreamforce 2010, most notably DimDim and Radian6. Post-Dreamforce 2011, salesforce.com has already acquired Assistly, a customer service social software startup in the lower end of the market.
Part 1 of this blog series talked about my attendance of Dreamforce 2010, salesforce.com’s annual user conference, which has over the past several years become a highly anticipated and entertaining end-of-the-year fixture for enterprise applications market observers. My post concluded that while Dreamforce 2009 was mostly about continued growth of the cloud computing trailblazer and unveiling of Salesforce Chatter, the company’s nascent social platform and collaboration cloud (as duly covered by my blog series), the overall Dreamforce 2010 theme was cloud proliferation (and salesforce.com’s further diversification).
In his blog post, Louis Columbus states that at the center of Dreamforce 2010 was the transformation of salesforce.com into an enterprise cloud platform provider, starting with endorsing open application programming interfaces (APIs) including REST (Representational State Transfer), which its developer community had reportedly been requesting for over a year. Moreover, after realizing the proprietary nature of its Force.com cloud platform (and its Apex code), salesforce.com CEO Marc Benioff and his co-founder Parker Harris have recently decided to decouple Force.com into a more open application layer, for platform as a service (PaaS) purposes and a database layer for providing infrastructure as a service (IaaS).
Dreamforce, salesforce.com’s annual user conference, has over the past several years become a highly anticipated and entertaining end-of-the-year fixture for the enterprise applications market observers (surprisingly, Dreamforce 2011 will take place in late August, and let’s see how that new timing will feel). Namely, in these prolonged times of bad economic news and businesses recoiling across the board, one could always enjoy the unusually high attendance and upbeat and “never a dull moment” atmosphere of the multi-day event, courtesy of salesforce.com’s CEO Marc Benioff and his executive team.
While Dreamforce 2009 was mostly about the continued growth of the vendor and the unveiling of Salesforce Chatter, the company’s nascent social platform and collaboration cloud (as duly covered by my blog series), the overall Dreamforce 2010 theme was the cloud proliferation (and salesforce.com’s further diversification). Needless to say, this was in addition to the theme of continued growth.
In Part 1 of this blog series I admitted to being a late adopter of a sort, in part for not immediately jumping onto the social media bandwagon. In particular, my initial reaction to Salesforce Chatter (a.k.a. Collaboration Cloud) was tepid when it was introduced at the Dreamforce 2009 conference.
However, a few months have passed and this period has helped salesforce.com craft the much clearer cloud computing evolution message that was analyzed in Part 2. The article then also went on to explain my change of heart and discussed Salesforce Chatter’s current state of affairs (in terms of the current number of beta users and third-party solutions).
Salesforce Chatter became generally available (GA) as of June 22, 2010. Salesforce.com is even entertaining the idea that Chatter could be a general enterprise platform on its own. One Chatter-based application was recently announced by FinancialForce.com and is called Chatterbox.
Chatterbox comes within the FinancialForce Accounting product but the idea is to also sell it to accounting departments as standalone. For more information on the product, see the company’s press release (PR), a related blog post from WebCPA, and the product’s dedicated Web page.
The final part of this blog series will explain many design principles and possible use of Chatter and Chatterbox from my dialogue with Jeremy Roche, FinancialForce.com CEO and President, and UNIT4 CODA chairman.
In Part 1 of this blog series I admitted to being a late adopter of a sort, in part for not immediately jumping onto the social media bandwagon. In particular, my initial reaction to Salesforce Chatter (a.k.a. Collaboration Cloud) was tepid. To be frank, Marc Benioff, salesforce.com’s flamboyant and engaging CEO, gave an atypically incoherent and dry keynote speech when he introduced Chatter at the Dreamforce 2009 conference.
However, a few months have passed and this period has helped salesforce.com craft a much clearer message. In addition, Chatter has reportedly been used within salesforce.com’s own organization (as the largest beta site/tester), which has given the vendor much more time and experience to improve and tweak the product.