<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Knives Your Sales People Should Have</title>
	<atom:link href="http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html</link>
	<description></description>
	<lastBuildDate>Tue, 14 Feb 2012 01:23:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sağlık</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-35118</link>
		<dc:creator>Sağlık</dc:creator>
		<pubDate>Sun, 25 Jul 2010 20:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-35118</guid>
		<description>no no no ..&#231;ok yanlış </description>
		<content:encoded><![CDATA[<p>no no no ..&ccedil;ok yanlış</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: replcia handbags</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-32360</link>
		<dc:creator>replcia handbags</dc:creator>
		<pubDate>Tue, 02 Mar 2010 13:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-32360</guid>
		<description>Such a good article, caught my sympathy! </description>
		<content:encoded><![CDATA[<p>Such a good article, caught my sympathy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: martin_edi18731</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10711</link>
		<dc:creator>martin_edi18731</dc:creator>
		<pubDate>Sat, 31 Jan 2009 04:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10711</guid>
		<description>The IT comment was really more about their insistence on &#039;owning&#039; the data which isn&#039;t an option in our case. Fortunately we sell to marketing people...;-) </description>
		<content:encoded><![CDATA[<p>The IT comment was really more about their insistence on &#039;owning&#039; the data which isn&#039;t an option in our case. Fortunately we sell to marketing people&#8230;;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Has SaaS Killed OSS? &#124; CloudAve</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10688</link>
		<dc:creator>Has SaaS Killed OSS? &#124; CloudAve</dc:creator>
		<pubDate>Fri, 30 Jan 2009 14:58:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10688</guid>
		<description>[...] The Knives Your Sales People Should Have [...]</description>
		<content:encoded><![CDATA[<p>[...] The Knives Your Sales People Should Have [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Feld</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10466</link>
		<dc:creator>Brad Feld</dc:creator>
		<pubDate>Wed, 21 Jan 2009 21:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10466</guid>
		<description>That&#8217;s  a good example. It&#8217;s conceivable that you should still do a license like this  under a perpetual model where the customer pays a single payment for a specific  number of &#8220;uses&#8221; or &#8220;proofs&#8221;. You&#8217;d have to build this into the license key  which is incremental work (but trivial on a SaaS deployment), but I think you  could simulate the same affect. However, I doubt this will be anywhere as easy  or logical as in a SaaS model.&lt;br /&gt; </description>
		<content:encoded><![CDATA[<p>That&#8217;s  a good example. It&#8217;s conceivable that you should still do a license like this  under a perpetual model where the customer pays a single payment for a specific  number of &#8220;uses&#8221; or &#8220;proofs&#8221;. You&#8217;d have to build this into the license key  which is incremental work (but trivial on a SaaS deployment), but I think you  could simulate the same affect. However, I doubt this will be anywhere as easy  or logical as in a SaaS model.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mat</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10449</link>
		<dc:creator>Mat</dc:creator>
		<pubDate>Tue, 20 Jan 2009 22:51:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10449</guid>
		<description>Brad 
 
The subscription vs. perpetual analysis is sound, but missed out one key innovation of SaaS, which is the pay-as-you-use model. 
 
As you point out, perpetual and fixed rate subscriptions are really two side of the same coin, although the ability to cancel a fixed price subscription makes it much more flexible. 
 
At ProofHQ we have gone to market with a fixed rate month;y subscription model.  We have different levels of pricing for different profiles of user based primarily on the number of documents that they send for &quot;proofing&quot; each month.  All familiar stuff for users of Basecamp, Freshbooks, etc.  Of course in a minority of cases we are asked for a more traditional perpetual license, even when we are hosting or managing the service and we don&#039;t turn those deals down. 
 
However, what has surprised us has been the number of people who want to buy a &quot;block&quot; of proofs to consume as and when they want.  To me this is the most interesting direction that the SaaS payment model is going in - &quot;pay as you consume&quot;.  I guess the mobile phone companies got there first, then Google with Adwords and Amazon with S3 etc. 
 
They key to maintaining flexibility in pricing models is being able to define a product&#039;s &quot;unit of value&quot;.  In our case &quot;proofs&quot;.  If you get that right then you can apply it across a wide range of license models without too much conflict or inconsistency. </description>
		<content:encoded><![CDATA[<p>Brad </p>
<p>The subscription vs. perpetual analysis is sound, but missed out one key innovation of SaaS, which is the pay-as-you-use model. </p>
<p>As you point out, perpetual and fixed rate subscriptions are really two side of the same coin, although the ability to cancel a fixed price subscription makes it much more flexible. </p>
<p>At ProofHQ we have gone to market with a fixed rate month;y subscription model.  We have different levels of pricing for different profiles of user based primarily on the number of documents that they send for &quot;proofing&quot; each month.  All familiar stuff for users of Basecamp, Freshbooks, etc.  Of course in a minority of cases we are asked for a more traditional perpetual license, even when we are hosting or managing the service and we don&#039;t turn those deals down. </p>
<p>However, what has surprised us has been the number of people who want to buy a &quot;block&quot; of proofs to consume as and when they want.  To me this is the most interesting direction that the SaaS payment model is going in &#8211; &quot;pay as you consume&quot;.  I guess the mobile phone companies got there first, then Google with Adwords and Amazon with S3 etc. </p>
<p>They key to maintaining flexibility in pricing models is being able to define a product&#039;s &quot;unit of value&quot;.  In our case &quot;proofs&quot;.  If you get that right then you can apply it across a wide range of license models without too much conflict or inconsistency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Schnaars</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10444</link>
		<dc:creator>Scott Schnaars</dc:creator>
		<pubDate>Tue, 20 Jan 2009 16:50:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10444</guid>
		<description>In my company, Socialtext, it is a bit easier.  We have a managed appliance that, in 95+% of cases is deployed behind the firewall and licensed in a traditional SaaS model.   
 
While the appliance is installed behind the firewall, as Brad points out, once you stop paying for &#039;maintenance&#039;, there goes support / updates.   </description>
		<content:encoded><![CDATA[<p>In my company, Socialtext, it is a bit easier.  We have a managed appliance that, in 95+% of cases is deployed behind the firewall and licensed in a traditional SaaS model.   </p>
<p>While the appliance is installed behind the firewall, as Brad points out, once you stop paying for &#039;maintenance&#039;, there goes support / updates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Feld</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10442</link>
		<dc:creator>Brad Feld</dc:creator>
		<pubDate>Tue, 20 Jan 2009 15:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10442</guid>
		<description>Remember  &#8211; it&#8217;s &#8220;licensing / pricing&#8221;. So &#8211; in this case, the buyer has to pay the  maintenance to continue to get the service. If it&#8217;s SaaS and they don&#8217;t pay  the maintenance, the service stops. It&#8217;s a different case than desktop  software (like Windows XP) where you &#8220;can&#8217;t turn off the service easily.&#8221; &lt;br /&gt; </description>
		<content:encoded><![CDATA[<p>Remember  &#8211; it&#8217;s &#8220;licensing / pricing&#8221;. So &#8211; in this case, the buyer has to pay the  maintenance to continue to get the service. If it&#8217;s SaaS and they don&#8217;t pay  the maintenance, the service stops. It&#8217;s a different case than desktop  software (like Windows XP) where you &#8220;can&#8217;t turn off the service easily.&#8221; </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Sugar</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10441</link>
		<dc:creator>Phil Sugar</dc:creator>
		<pubDate>Tue, 20 Jan 2009 14:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10441</guid>
		<description>There are four quadrants...two are the norm.   
 
SaaS subscription model, Behind the Firewall perpetual license.   
 
The next one is harder but doable.  I&#039;ll agree that you can go behind the firewall subscription.  In fact, I think its better to start that way, but given you&#039;re in a perpetual model and you want to move to subscription ok, get ready to feel the pain from the finance types but doable. 
 
I want to see how you deliver SaaS in a perpetual license.   The definition of perpetual is continuing forever.  So the organization can buy once refuse the 20% support and continue to use.  Just like Windows XP.  How does that work? </description>
		<content:encoded><![CDATA[<p>There are four quadrants&#8230;two are the norm.   </p>
<p>SaaS subscription model, Behind the Firewall perpetual license.   </p>
<p>The next one is harder but doable.  I&#039;ll agree that you can go behind the firewall subscription.  In fact, I think its better to start that way, but given you&#039;re in a perpetual model and you want to move to subscription ok, get ready to feel the pain from the finance types but doable. </p>
<p>I want to see how you deliver SaaS in a perpetual license.   The definition of perpetual is continuing forever.  So the organization can buy once refuse the 20% support and continue to use.  Just like Windows XP.  How does that work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html/comment-page-1#comment-10438</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Tue, 20 Jan 2009 06:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.feld.com/wp/archives/2009/01/the-knives-your-sales-people-should-have.html#comment-10438</guid>
		<description>We&#039;ll I&#039;ll just add that Brad and I disagreed on this for about 3 years. He finally won me over about 6 months ago. Sales have gone up as a result. We sell On-Prem and Hosted. We sell 1 year term, 3 year term and perpetual both hosted and on-prem. Sell the way customers want to buy! </description>
		<content:encoded><![CDATA[<p>We&#039;ll I&#039;ll just add that Brad and I disagreed on this for about 3 years. He finally won me over about 6 months ago. Sales have gone up as a result. We sell On-Prem and Hosted. We sell 1 year term, 3 year term and perpetual both hosted and on-prem. Sell the way customers want to buy!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache 0.8.9.1 -->
