<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Saas model will collapse in two years &#8211; What?</title>
	<atom:link href="http://productmanagementtips.com/2008/09/02/productmanager-lawson-saas/feed/" rel="self" type="application/rss+xml" />
	<link>http://productmanagementtips.com/2008/09/02/productmanager-lawson-saas/</link>
	<description>Practical software product management tips</description>
	<lastBuildDate>Fri, 25 May 2012 06:55:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: David Locke</title>
		<link>http://productmanagementtips.com/2008/09/02/productmanager-lawson-saas/#comment-630</link>
		<dc:creator><![CDATA[David Locke]]></dc:creator>
		<pubDate>Thu, 11 Sep 2008 20:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://gopalshenoy.wordpress.com/?p=289#comment-630</guid>
		<description><![CDATA[SaaS fits into the technology adoption lifecycle in the late market where price pressure dominates everything the vendor does. Even for a product company, making money in that market required huge amounts of cash, change, and cost elimination. It was never an easy place to do business. 

SaaS fits nicely with the notion that you have to sublimate your interface for the late market. Most product companies don&#039;t bother and end up killing their offerings quickly once they enter this market. Still, are SaaS vendors even aware of what they are doing, or do we get the same kind of interfaces in a SaaS application that we used to see on the desktop. Ajax or not isn&#039;t the point of the question. It&#039;s a matter of de-feature-bloating. Even web apps have features. And, going one more step towards getting rid of software artifacts that are only involved in a task, because the task is being performed on the computer. Task sublimation requires more than a different user interface. The code will be more complicated regardless of form factor. 

When a vendor can&#039;t make money, it stops being about the customer&#039;s pain points. Go through a stall, if you live say thanks, don&#039;t blame it on technology, because it won&#039;t be about technology at all. BTW, all companies stall. CEOs say strange things on the way down.]]></description>
		<content:encoded><![CDATA[<p>SaaS fits into the technology adoption lifecycle in the late market where price pressure dominates everything the vendor does. Even for a product company, making money in that market required huge amounts of cash, change, and cost elimination. It was never an easy place to do business. </p>
<p>SaaS fits nicely with the notion that you have to sublimate your interface for the late market. Most product companies don&#8217;t bother and end up killing their offerings quickly once they enter this market. Still, are SaaS vendors even aware of what they are doing, or do we get the same kind of interfaces in a SaaS application that we used to see on the desktop. Ajax or not isn&#8217;t the point of the question. It&#8217;s a matter of de-feature-bloating. Even web apps have features. And, going one more step towards getting rid of software artifacts that are only involved in a task, because the task is being performed on the computer. Task sublimation requires more than a different user interface. The code will be more complicated regardless of form factor. </p>
<p>When a vendor can&#8217;t make money, it stops being about the customer&#8217;s pain points. Go through a stall, if you live say thanks, don&#8217;t blame it on technology, because it won&#8217;t be about technology at all. BTW, all companies stall. CEOs say strange things on the way down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyner Blain</title>
		<link>http://productmanagementtips.com/2008/09/02/productmanager-lawson-saas/#comment-629</link>
		<dc:creator><![CDATA[Tyner Blain]]></dc:creator>
		<pubDate>Thu, 11 Sep 2008 02:15:41 +0000</pubDate>
		<guid isPermaLink="false">http://gopalshenoy.wordpress.com/?p=289#comment-629</guid>
		<description><![CDATA[&lt;strong&gt;Is the SaaS Market Broken, or Just Efficient?...&lt;/strong&gt;


Is SaaS a broken model, with integral flaws, doomed to failure in the next two years?  Lawson Software&#8217;s CEO, Harry Debes, thinks it is.  Perhaps the structural elements of the SaaS reality just break Debes&#8217; business models.

Reports of ...]]></description>
		<content:encoded><![CDATA[<p><strong>Is the SaaS Market Broken, or Just Efficient?&#8230;</strong></p>
<p>Is SaaS a broken model, with integral flaws, doomed to failure in the next two years?  Lawson Software&#8217;s CEO, Harry Debes, thinks it is.  Perhaps the structural elements of the SaaS reality just break Debes&#8217; business models.</p>
<p>Reports of &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Agile and SaaS &#171; Lead on Purpose</title>
		<link>http://productmanagementtips.com/2008/09/02/productmanager-lawson-saas/#comment-628</link>
		<dc:creator><![CDATA[Agile and SaaS &#171; Lead on Purpose]]></dc:creator>
		<pubDate>Wed, 10 Sep 2008 16:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://gopalshenoy.wordpress.com/?p=289#comment-628</guid>
		<description><![CDATA[[...] (e.g. Google and Salesforce.com). Gopal Shenoy takes on a critic who makes a prediction that the SaaS model will collapse in two years. He says: &#8220;While I totally agree that Saas is not the panacea to solve everything that is [...]]]></description>
		<content:encoded><![CDATA[<p>[...] (e.g. Google and Salesforce.com). Gopal Shenoy takes on a critic who makes a prediction that the SaaS model will collapse in two years. He says: &#8220;While I totally agree that Saas is not the panacea to solve everything that is [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

