<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SaaS as Recurring Revenue Justification</title>
	<atom:link href="http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/</link>
	<description>Understanding the Software as a Service Revolution</description>
	<pubDate>Fri, 21 Nov 2008 10:11:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Uri Lederman</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-25472</link>
		<dc:creator>Uri Lederman</dc:creator>
		<pubDate>Fri, 30 Nov 2007 21:04:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-25472</guid>
		<description>I Agree whole heartedly with Joel..

Although you can sell traditional software both as perpetual license model and a subscription model, the fact that true SAAS players go that extra step and take care of delivery means two things:

1) Total cost of Ownership for end users are drastically reduced
2) ISVs are able to capture the hardware &#38; people costs of software as REVENUE.

Just my two cents,</description>
		<content:encoded><![CDATA[<p>I Agree whole heartedly with Joel..</p>
<p>Although you can sell traditional software both as perpetual license model and a subscription model, the fact that true SAAS players go that extra step and take care of delivery means two things:</p>
<p>1) Total cost of Ownership for end users are drastically reduced<br />
2) ISVs are able to capture the hardware &amp; people costs of software as REVENUE.</p>
<p>Just my two cents,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sinclair Schuller</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24330</link>
		<dc:creator>Sinclair Schuller</dc:creator>
		<pubDate>Sun, 25 Nov 2007 00:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24330</guid>
		<description>I agree with your point: extreme cost reduction does generally trump risk, at least in the broad case. The problem is, I'm not sure that it's generally the case that SaaS is "riskier". Rather, it is a question of perceived risk (which you've labelled as emotional), and even then, yes cost will prevail if it is significant.

Framing "recurring revenue" from the customer perspective, however, may attack the perceived risk directly without requiring that a switch be analyzed strictly from a cost analysis perspective.</description>
		<content:encoded><![CDATA[<p>I agree with your point: extreme cost reduction does generally trump risk, at least in the broad case. The problem is, I&#8217;m not sure that it&#8217;s generally the case that SaaS is &#8220;riskier&#8221;. Rather, it is a question of perceived risk (which you&#8217;ve labelled as emotional), and even then, yes cost will prevail if it is significant.</p>
<p>Framing &#8220;recurring revenue&#8221; from the customer perspective, however, may attack the perceived risk directly without requiring that a switch be analyzed strictly from a cost analysis perspective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel York</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24211</link>
		<dc:creator>Joel York</dc:creator>
		<pubDate>Sat, 24 Nov 2007 05:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24211</guid>
		<description>To use a little math terminology from my old days as a student, I think SaaS is a sufficient condition for recurring revenue, but not a necessary one.

In plain English, traditional software can be sold both as a perpetual or rental license (I have done both), but you do not have this option with SaaS, because the customer can never really own the software or hardware infrastructure, i.e., your option 3) above is not really possible...it is a red herring.

From the customer's perspective, it is really a question of risk.  Renting reduces risk by making switching easier. Purchase reduces risks associated with lack-of-control (in most cases inflated and emotional, but real in others).

The real benefit of SaaS is extreme cost reduction, which in most cases trumps risk.</description>
		<content:encoded><![CDATA[<p>To use a little math terminology from my old days as a student, I think SaaS is a sufficient condition for recurring revenue, but not a necessary one.</p>
<p>In plain English, traditional software can be sold both as a perpetual or rental license (I have done both), but you do not have this option with SaaS, because the customer can never really own the software or hardware infrastructure, i.e., your option 3) above is not really possible&#8230;it is a red herring.</p>
<p>From the customer&#8217;s perspective, it is really a question of risk.  Renting reduces risk by making switching easier. Purchase reduces risks associated with lack-of-control (in most cases inflated and emotional, but real in others).</p>
<p>The real benefit of SaaS is extreme cost reduction, which in most cases trumps risk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Zheng</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24209</link>
		<dc:creator>Frank Zheng</dc:creator>
		<pubDate>Sat, 24 Nov 2007 05:41:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24209</guid>
		<description>Very Good Observation! 
There are two other combination of delivery and revenue models:
5)	On-Premise, Perpetual License, &lt;b&gt;pay by installments&lt;/b&gt;. As Competition of business software in China is becoming very severe, many traditional software vendors have already adopted this model.
6)	As a Service, “Lifetime License”, &lt;b&gt;pay by installments&lt;/b&gt;. As a software service provider in China, we adopt this model.

Chinese people don’t like to “pay forever” for something. Recurring model is very difficult to succeed in China. We have to introduce “payment installment” concept to promote SaaS. Hope when customers pay up their balance ( usually after a few years), we will come up with new ideas to make them continue to pay ( Any ideas are welcome :) . 

Frank @ www.oksbt.com</description>
		<content:encoded><![CDATA[<p>Very Good Observation!<br />
There are two other combination of delivery and revenue models:<br />
5)	On-Premise, Perpetual License, <b>pay by installments</b>. As Competition of business software in China is becoming very severe, many traditional software vendors have already adopted this model.<br />
6)	As a Service, “Lifetime License”, <b>pay by installments</b>. As a software service provider in China, we adopt this model.</p>
<p>Chinese people don’t like to “pay forever” for something. Recurring model is very difficult to succeed in China. We have to introduce “payment installment” concept to promote SaaS. Hope when customers pay up their balance ( usually after a few years), we will come up with new ideas to make them continue to pay ( Any ideas are welcome :) . </p>
<p>Frank @ <a href="http://www.oksbt.com" rel="nofollow">http://www.oksbt.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy Wing</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24099</link>
		<dc:creator>Troy Wing</dc:creator>
		<pubDate>Fri, 23 Nov 2007 14:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-24099</guid>
		<description>I agree with your point on separating delivery from revenue model. But I believe that is a benefit of the SaaS model only. I don't believe you can do the same with On Premise. SaaS offers flexibility in choice, although the recurring model should be preferred by vendors due to lower cost of supporting each customer. On Premise incurs a higher cost of ongoing support and maintenance per customer irrespective of user counts, which cannot be covered by recurring revenue, which it makes it tightly bound to a perpetual license plus annual maintenance fee.</description>
		<content:encoded><![CDATA[<p>I agree with your point on separating delivery from revenue model. But I believe that is a benefit of the SaaS model only. I don&#8217;t believe you can do the same with On Premise. SaaS offers flexibility in choice, although the recurring model should be preferred by vendors due to lower cost of supporting each customer. On Premise incurs a higher cost of ongoing support and maintenance per customer irrespective of user counts, which cannot be covered by recurring revenue, which it makes it tightly bound to a perpetual license plus annual maintenance fee.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abe Sultan</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23926</link>
		<dc:creator>Abe Sultan</dc:creator>
		<pubDate>Thu, 22 Nov 2007 13:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23926</guid>
		<description>John,

I think that is exactly what Sinclair is trying to explain.

The benefit of SaaS for a customer is not that it is on a pay as you go basis. It is the fact that you pay as you go because you expect more services so in reality you continue to pay for improvement on the service.

The burden of proof is entirely on the providers; they need to win your business again and again by ever improving the software.

So the important point to outline when you talk about pay as you go; or recurring revenue, is not necesarily the way you pay, but what you are getting in return (All the benefits of SaaS).</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>I think that is exactly what Sinclair is trying to explain.</p>
<p>The benefit of SaaS for a customer is not that it is on a pay as you go basis. It is the fact that you pay as you go because you expect more services so in reality you continue to pay for improvement on the service.</p>
<p>The burden of proof is entirely on the providers; they need to win your business again and again by ever improving the software.</p>
<p>So the important point to outline when you talk about pay as you go; or recurring revenue, is not necesarily the way you pay, but what you are getting in return (All the benefits of SaaS).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John A. Berg</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23866</link>
		<dc:creator>John A. Berg</dc:creator>
		<pubDate>Thu, 22 Nov 2007 07:29:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23866</guid>
		<description>I do not disagree with your observations purely looking at the licensing - but what about hosting and support? These types of services are quite often bundled with a SaaS license.

Also, when selling a SaaS solution the customer will usually anticipate new features and functionality (future versions) being added to the solution without reinvesting in the product - someting I belive points in the direction of a reccuring revenue model. 

All in all I believe traditional software mostly comes with a one-time license fee because most of the investment in the product is up-front. With SaaS solutions there is a need for an ongoing investment in the product - so a recurring revenue model makes more sense.</description>
		<content:encoded><![CDATA[<p>I do not disagree with your observations purely looking at the licensing - but what about hosting and support? These types of services are quite often bundled with a SaaS license.</p>
<p>Also, when selling a SaaS solution the customer will usually anticipate new features and functionality (future versions) being added to the solution without reinvesting in the product - someting I belive points in the direction of a reccuring revenue model. </p>
<p>All in all I believe traditional software mostly comes with a one-time license fee because most of the investment in the product is up-front. With SaaS solutions there is a need for an ongoing investment in the product - so a recurring revenue model makes more sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Kepes</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23758</link>
		<dc:creator>Ben Kepes</dc:creator>
		<pubDate>Wed, 21 Nov 2007 17:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23758</guid>
		<description>Yes - nice post Sinclair, good points</description>
		<content:encoded><![CDATA[<p>Yes - nice post Sinclair, good points</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23666</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 21 Nov 2007 02:37:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2007/11/20/saas-as-recurring-revenue-justification/#comment-23666</guid>
		<description>I think pay as you go, when coupled with the SaaS delivery method has a multiplying effect on decreasing barriers to entry. But OPEX based models only appeal to some companies, some prefer for tax or other reasons to go for upfront models.
I think you're opening point about re-occuring revenue is spot on. Nicely put  Sinclair.</description>
		<content:encoded><![CDATA[<p>I think pay as you go, when coupled with the SaaS delivery method has a multiplying effect on decreasing barriers to entry. But OPEX based models only appeal to some companies, some prefer for tax or other reasons to go for upfront models.<br />
I think you&#8217;re opening point about re-occuring revenue is spot on. Nicely put  Sinclair.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
