Thursday, May 29, 2008
Connecting the Cloud, One Contact at a Time
Ryan Nichols
Most businesses ultimately depend on personal connections. Business people would be lost if they couldn’t connect everyday with the contacts in their address book. And businesses wouldn’t function without the rich web of connections among their employees, partners, suppliers, and customers. But your company’s contact database is almost certainly incomplete. Despite periodic reminders from management to “scan those business cards” and “import those contacts,” most people can't find the time to maintain this information unless they are forced to, regardless of the benefits to the company. Your personal address book is also incomplete. Sure, you may have a rich virtual rolodex of names, mobile phones, and email addresses, but you can't see how this person is related to your business right now.
- Imagine you’re writing a casual email to reconnect with a former colleague—who happens to be in the midst of making a big purchase with another department in your company. What if you had this sort of business context at your fingertips whenever you communicated?
- Now imagine that your company’s sales reps knew about this connection as they were putting together their proposal. You would have been happy to make an introduction—if they’d only known to ask.
As with our other offerings, we’re starting with simple synchronization—you choose which of your contacts you want to share, and how you want them synchronized between your Google and Salesforce address books. This is a valuable start. Today, your Google email account automatically stores the email address of everyone you’ve ever written to, but knows nothing about their companis or roles. Your Salesforce.com contacts are detailed, but you’re missing hundreds of critical business connections. Synchronizing the two solves a real pain point that we hear from our customers today.
Contacts in Context
Sync is just the beginning. Appirio's vision is to bring the business context from all of a company’s on-demand enterprise applications into the productivity tools and social networks that individuals use as they work. We want "Solutions for Business" + "Solutions for People" to finally create "Solutions for Business People."
Contacts is the center of that vision, and sync between Google Apps and Salesforce is a great place to start. Enjoy the offering!
Labels: AppExchange, appirio, g, Google, Google Apps, on-demand, SaaS, SaaS integration, Salesforce for Google Apps, salesforce.com
Monday, March 03, 2008
Insights and Observations from the Pacific Crest On-Demand Conference
Narinder Singh
Last Thursday we had the pleasure of participating in the 3rd Annual Pacific Crest On-Demand Conference, the kickoff to Pacific Crest's Emerging Technology Summit. Salesforce.com CEO Marc Benioff invited us on stage during his keynote to illustrate how partners can harness the power of the Force.com platform, Visualforce and the AppExchange.
The participating companies covered the spectrum from large on-premise software companies such as EMC and SAP, who were describing their expansion into the newest "hot" market, to companies such as NetSuite, Salesforce.com and SuccessFactors that have built their business from the ground up with Software as a Service.
Interestingly, a number of companies there are in the process of trying to radically shift their business model from on-premise to on-demand, and they talked about the challenges. Most of these companies were small and nimble, which enabled them to make the transition cold-turkey. All were very clear that it wasn't an easy switch to make.
Can Companies Have Their SaaS Cake and Eat It Too?
Can companies successfully split their focus between traditional software and on-demand services?
This is a question we've been raising, skeptically, for quite some time in our blog. Our original Services 2.0 position paper in April 2007 described how the disruptive effects of SaaS will impact the economic models of on-premise software vendors. After a year of additional information and insight, it's even more apparent that treating SaaS as just another channel or product feature is a recipe for failure.
Spending a day with companies that have, or are attempting to make the switch from on-premise to SaaS reinforced the major challenges. IDeaS CEO Ed Booth gave a great presentation highlighting the challenges and upside of moving to an on-demand model. Concur Technologies has often been referenced as the best example of a company that successfully made the transition. Some issues raised by them and others included:
- One-time revenue hit: How do you manage through the decline in revenue growth when you move from an up-front license model to a monthly subscription model? With Wall Street and shareholders as panicky as they are today, this is a very difficult proposition for large public companies. Upfront licensing, even with longer term contracts, can drop by as much as 75%. As the Patricia Seybold Group has noted, As a company moves from perpetual licensing - where customers pay a relatively large, one-time licensing fee - to SaaS - where customers pay a relatively small, monthly license fee - financial performance slips in the short-term."
- Internal channel conflict: How do you manage the channel conflict that happens with your own partners, and even your own sales force, when offering both traditional license and on-demand software? Companies like EMC, with established business units focused on driving demand for SaaS or cloud computing, will have a serious challenge with this. The most reliable solution is to completely separate the businesses - which eliminates any synergy of having both models in the same company.
- Shifting to a "month by month" culture: How do you change the way you sell to and support customers when you have to earn their business every month instead instead of every few years when the next big version comes along? This is a huge cultural change for sales and support teams to make. SaaS companies require the culture of the web - where sites like eBay, Amazon, Google and others constantly monitor, serve and improve their customer's experience.
- Speeding up R&D: How do you adapt your product development processes to deliver an on-demand service? Successful on-demand vendors get the benefit of releasing new features quarterly, not every two or three years. When features are released, they are expected to work with other systems indefinitely. Salesforce.com still supports each of its 12 versions of its API. How many on-premise vendors can claim anything even close?
EMC, SAP, Microsoft and Oracle make it clear to customers and stockholders that their foray into SaaS or cloud computing is not a departure from their software strategies, but an expansion of it. They say things like "SaaS is just another delivery model," or "we're giving customers a choice." Yet they keep increasing the on-premise maintenance fees. SAP just increased its maintenance rate from 17% to 22% per year - an increase of 30%! This leads to one of two possible conclusions:
- The cost of supporting a growing legacy of capabilities keeps increasing, which eliminates the benefits of on-premise scale. Compare this to any internet company, where increased scale lowers cost and results in expanded services for customers.
- They are taking advantage of customers' inability to easily switch off of their on-premise software.
Traditional software companies - especially large ones - will certainly have to straddle the fence for a while. Yet the doubletalk and denial will not help in the transition. First, they must acknowledge the need to make a transition. Second, in many cases, dramatic actions, like separating SaaS products into completely independent business units or taking companies private to allow for transition, will be needed to make the change. It's likely that legacy companies will not switch until customers stop tolerating increasing TCO and diminishing innovation from their on-premise systems.
Labels: AppExchange, Concur Technologies, EMC, Force.com, IDeaS, on-demand, Pacific Crest, SaaS, salesforce.com, SAP, software-as-a-service
Wednesday, December 13, 2006
IT Management & Governance In an On-Demand Model
The IT landscape for Salesforce.com customers is quickly growing complex. With over 400 applications on the AppExchange today – with projections of 1,000 by late 2007 – and the upcoming Winter '07 release and the Apex programming language, sound IT management and governance practices are essential. In the past, a single application such as SFA or Service & Support was manageable for a line-of-business leader or an aspiring IT professional. They could gather requirements, build a business case, sell internally and then implement. With the increasingly complex platform now offered by Salesforce.com, where customers have access to applications, extensions, API’s, partners and the platform itself, determining the tradeoffs among building, buying, and partnering requires a thoughtful and collaborative approach among the business, IT, and the Salesforce.com community.
Some Appirio customers have recently completed extensive application and server rationalization exercises as part of the launch of an on-demand strategy. Inventory analysis is a great first step towards on-demand portfolio management, and uncovers a number of obvious opportunities to migrate on-premise applications to the on-demand model. Many traditional project and portfolio management principles apply, but in the on-demand world there are four key strategies for CIO’s to apply:
- Centralize the Approval Process. All new IT project requests should flow through a single, cross-functional, company-wide approval process with common selection criteria. In the past, on-demand software vendors have thrived by working around traditional IT, which creates redundant projects, additional costs, and inefficient use of resources. Under this decentralized model, many departments (often including IT) are finding, promoting, and implementing siloed on-demand applications that solve a specific problem for that particular department, but perpetuate vendor bloat, cost creep and integration headaches. Further, many existing Salesforce.com customers and their IT departments may not be aware of the capabilities and benefits of the AppExchange platform. To take advantage of the benefits of a true on-demand platform, CIOs must have the business, IT, Salesforce.com teams in sync. The CIO should be aware of all projects currently in queue, and knowledgeable of the end-to-end platform capabilities. This linkage is essential to driving adoption, integrating the user experience, ensuring corporate buy-in, and keeping costs down.
- Apply Early Adopter Factors. Let’s face it, we are in “early adopter” territory: standardizing an on-demand platform for a company with thousands of users, hundreds of legacy applications, complex business models and an “on-premise” mentality.. Along with the benefits of the on-demand model, there are inherent risks, with few end-to-end enterprise class success stories today. The development methodologies and assets are far from mature, and for every ten integration challenges, there are twenty solutions presented. Based on the evolving nature of on-demand platforms and applications, CIOs are well advised to estimate timelines somewhat longer than rollouts of a single application, and to anticipate increased costs associated with training, development, integration and data cleansing and migration.
- Keep Up with the Upgrade Roadmap and Partner Ecosystem. Remember that when you use on-demand vendors, your software is automatically upgraded with each new release. New partners and applications appear on the AppExchange every day. In short order, enterprise customers can expect features that they were planning on building to show up in new releases, and will notice applications that they were expecting to buy to show up on the AppExchange or other marketplaces. CIOs making the platform decision should demand early visibility not only into traditional product roadmaps, but also ISV and SI applications. Specifically, power users and CIOs should find out which applications are actually being used - particularly in large deployments of more than 1,000 seats - and how they are scaling in terms of volume, security, integration, and usability. This information, and the ability to talk directly with other companies making similar investments, will have a direct impact on a CIO’s make, buy, or partner decisions.
- Salesforce.com is Not Just for Sales. Education, awareness, and sponsorship are critical. While it seems obvious to those of us who ”get” on-demand vendors like Salesforce.com, most executives, functional leaders, and even salespeople, do not understand the future direction and capabilities of the AppExchange platform. The notion of building an application development platform using an on-demand model is new for most people, and it takes awhile to fully appreciate the profoundness of this change for typical IT operations. To really drive platform adoption across the enterprise, the executive team needs to consistently educate and drive awareness thru sponsorship and active, visible pilots that demonstrate value to end users and the business.
Labels: AppExchange, appirio, cio, on-demand, SaaS, salesforce, salesforce.com
