By Denis Pombriant CRM Buyer Part of the ECT News Network
05/13/09 4:00 AM PT
Is it fair for Salesforce to charge ISVs and SIs for support? Yes. If people are using your development environment to make new applications and functions, then answering their questions and helping them out requires smart -- in other words, expensive -- personnel. However, Salesforce may do well to diversify its pricing structure to charge small, medium and large developers differently.
How Much is 'Free' Costing You? Learn how DaveRamsey.com saw a 567% uplift in ROI with Omniture. This complimentary guide and webinar cover the most important factors in selecting an analytics solution. Download Now.
"If you can't make money at it, you don't have a business, you've got a hobby."
-- Words of wisdom from my dad.
I was surprised by the mini-storm that blew up over Salesforce.com's (NYSE: CRM) apparent decision to charge ISVs (independent software vendors), SIs (system integrators) and other types of developers for support using its development environment. Two primary arguments have cropped up -- one, that support ought to be free, and the other that it's hard to make money if you can't charge 22 percent for service.
OK, let's tease these things apart. Free support is a good and noble idea, and it is encompassed in the basic premise of on-demand or cloud computing or SaaS or whatever you choose to call it. Subscribe to the application service and you have the right to call in as many times as you want to ask dumb and not-so-dumb questions. In Salesforce's case, they won't tell you how to sell, but they will help you untangle the differences between leads, contacts and opportunities. Then they will probably direct you to some of their basic-level training. That's only fair.
Salesforce, as we all know, also has this on-demand development environment, and with it you can build any number of database applications and reports or integrate with whatever else there is in the universe. At that level, you are playing with the innards, and you are dealing with an application that the vendor -- i.e., Salesforce -- has no control over. It's like me putting a turbo on my Honda. I am free to do that, but -- understandably -- my dealer won't be happy to see me, and all warranties on the power train would, I am sure, be toast. From then on, if I need to get anything fixed, I will probably become a regular caller on Tom and Ray's NPR show
"Car Talk."
Get What You Pay For
It seems to me that charging for support when people are using the development environment to make new applications or even new functionality is like putting the turbo on my Honda, and it is fair (though I might quibble with the pricing structure). Supporting smart people building applications in this new environment requires smart people, gear and real estate on the other side. That has to be paid for.
Now, as far as pricing is concerned, I do believe they (Salesforce) need more than pricing for levels of service and response time. They also need to build out a matrix for small, medium and big developer customers. That's only fair, given that the more developers you have, the more support you'll need. Spare me the argument that your developers are smarter than mine. Sheesh!
Finally, my friend Barney Beal wrote recently that "Oracle CEO Larry Ellison and many an SAP (NYSE: SAP) executive have long maintained that the SaaS business model can be very difficult to turn a profit with. One would imagine it's especially difficult if you can't charge those maintenance fees of 22 percent of net licensing ..."
That's true as far as it goes, but keep in mind that even though Salesforce is now a successful CRM provider, making a few bucks, the company is a neophyte in the application tools business. It gets confusing because it's all one company, but if Salesforce CRM were a distinct entity from Salesforce tools and hosting, then I think most people would not expect the nascent company to be profitable. In company- and category-building eras, few companies make money, though many are cash flow positive. Oracle (Nasdaq: ORCL) and SAP didn't make a ton of money when they were new either.
Wrong Paradigm
Last point: It's especially hard for conventional software companies to make a profit from on-demand, but there are different reasons for that, which include fundamentally different business paradigms. Conventional companies are bloated, compared to the on-demand companies that I have seen. Their structural costs are higher. I find the whole idea that on-demand companies can't be profitable to be nothing more than a case of the wrong paradigms being applied.
So, all of this brings me back to dear old dad -- you have to make a profit. I don't have a problem with what Salesforce is doing as long as there is adequate value being exchanged. Of course, I am just an analyst in all this. No customer likes a price increase or the imposition of a fee for something that had been free, and some feathers may need to be smoothed here. Because the other thing you need to have if you want a business and not just a hobby is happy customers.
Denis Pombriant is the managing principal of the Beagle Research Group, a CRM market research firm and consultancy. Pombriant's research concentrates on evolving product ideas and emerging companies in the sales , marketing and call center disciplines. His research is freely distributed through a blog and Web site. He is working on a book and can be reached at denis.pombriant@beagleresearch.com.
Project Success vs. Fear of Leading May 12, 2009
It takes more than management skills to lead an IT project to a successful conclusion. In fact, it takes courage -- plus the ability to influence others and a temperament that doesn't permit the option of giving up when the going gets tough. Project management without project leadership is likely to result in project failure.
Related Stories
The Salesforce Departures: Much Ado About Very Little February 11, 2009
Three high-ranking Salesforce executives left the company recently, and immediately much of the SaaS knowledge-sphere began wringing their hands, consulting the tarot cards, and presuming the worst for the firm. But reading about a couple of layoffs and resignations and making overly broad inferences about a company, an industry or an entire economy helps nothing, writes CRM Buyer columnist Denis Pombriant.
'I Feel Your Pain' vs. 'The Vision Thing' February 04, 2009
Comparing the respective strategies of Salesforce and Oracle leaves CRM Buyer columnist Denis Pombriant with no clear-cut favorite, but it does reveal some distinct contrasts. Salesforce has the vision and a penchant for selling the vision. Oracle, on the other hand, has a knack for sales and marketing.
Salesforce and the Service Cloud January 21, 2009
The Service Cloud that Salesforce introduced last week is innovative in how it leverages a network paradigm for service, writes CRM Buyer columnist Denis Pombriant. However, he questions the use of the term "service" rather than "support."
Related News Alerts
More by Denis Pombriant
PaaS and the Democratization of Innovation November 18, 2009
There was a time when it wasn't out of the question for an enterprise -- a large hospital, to give just one example -- to develop its own computer operating system in-house. Application complexity has exploded since then, making such undertakings much less common, but the advent of PaaS and cloud computing is bringing back the ability for users to innovate at a scale that makes sense for them.
A Tale of Two Sages November 11, 2009
Sage seems to be of two minds these days, and only one of them exemplifies the wisdom suggested by the company's name -- that's the SaaS-thinking side. The other seems stuck in an on-premise mindset, pedaling in the wrong direction. The company needs to embrace the inevitability of SaaS. Sage is leveraging Web 2.0 to good effect, though, and it has adopted some impressive new customer outreach initiatives.
From Mainframes to I-Frames November 11, 2009
There are over 6,000 mainframes still in operation in the U.S. For companies looking to save on the costs associated with big iron by moving on to other technologies, Infrastructure as a Service represents an important alternative. However, IaaS also can eventually land you back in a mainframe-like straightjacket.