<?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: Monday’s Musings: It’s The Relationship, Stupid! (Part 4) &#8211; Stop Under-investing In R&amp;D</title>
	<atom:link href="http://blog.softwareinsider.org/2009/04/27/monday%e2%80%99s-musings-it%e2%80%99s-the-relationship-stupid-part-4-stop-under-investing-in-rd/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.softwareinsider.org/2009/04/27/monday%e2%80%99s-musings-it%e2%80%99s-the-relationship-stupid-part-4-stop-under-investing-in-rd/</link>
	<description>Your buy side advocate for enterprise apps strategies, vendor selection, &#38; contract negotiations</description>
	<lastBuildDate>Fri, 18 May 2012 17:16:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Rebecca Gill</title>
		<link>http://blog.softwareinsider.org/2009/04/27/monday%e2%80%99s-musings-it%e2%80%99s-the-relationship-stupid-part-4-stop-under-investing-in-rd/comment-page-1/#comment-1712</link>
		<dc:creator>Rebecca Gill</dc:creator>
		<pubDate>Tue, 12 May 2009 12:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareinsider.org/?p=2121#comment-1712</guid>
		<description>Great post Ray.  Last week I was at our annual conference, which is my opportunity to immerse myself with customers.  While I love the interaction, I do become so saddened by the stories I hear on our industry as a whole.  While we do not personally take part in those vendor practices you described, I have heard similar tales from our new customers and their respective consultants.
For those of us who take pride in our product and our industry, such activities are truly upsetting.</description>
		<content:encoded><![CDATA[<p>Great post Ray.  Last week I was at our annual conference, which is my opportunity to immerse myself with customers.  While I love the interaction, I do become so saddened by the stories I hear on our industry as a whole.  While we do not personally take part in those vendor practices you described, I have heard similar tales from our new customers and their respective consultants.<br />
For those of us who take pride in our product and our industry, such activities are truly upsetting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#8220;Walk in my shoes&#8221; - Vendor/Stakeholder Relationship Strategies &#171; Business Process Management (BPM) - InSights</title>
		<link>http://blog.softwareinsider.org/2009/04/27/monday%e2%80%99s-musings-it%e2%80%99s-the-relationship-stupid-part-4-stop-under-investing-in-rd/comment-page-1/#comment-1648</link>
		<dc:creator>&#8220;Walk in my shoes&#8221; - Vendor/Stakeholder Relationship Strategies &#171; Business Process Management (BPM) - InSights</dc:creator>
		<pubDate>Thu, 30 Apr 2009 22:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareinsider.org/?p=2121#comment-1648</guid>
		<description>[...] Part 4: Under-investing in R&amp;D and then repackaging existing content as new innovation  [...]</description>
		<content:encoded><![CDATA[<p>[...] Part 4: Under-investing in R&amp;D and then repackaging existing content as new innovation  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Martin</title>
		<link>http://blog.softwareinsider.org/2009/04/27/monday%e2%80%99s-musings-it%e2%80%99s-the-relationship-stupid-part-4-stop-under-investing-in-rd/comment-page-1/#comment-1625</link>
		<dc:creator>John Martin</dc:creator>
		<pubDate>Mon, 27 Apr 2009 20:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareinsider.org/?p=2121#comment-1625</guid>
		<description>Ray:  This &quot;bad behavior&quot; is endemic to the badly broken (from the customer&#039;s point of view) relationship experience with on-premise software.  First the client invests a huge amount on up-front software licenses, infrastructure (prod &amp; test &amp; dev), and an implementation project run by a third-party who is motivated to make it as complex and costly as possible... and then the customer has no options to move off the on-premise solution, so must keep paying 22% in ongoing maintenance for no ongoing value-add (because upgrading is really a re-implementation with customized on-premise software).

On-premise software vendors spend huge amounts on R&amp;D, but for existing customers their return on R&amp;D is close to zero because:
- The on-premise vendor&#039;s efforts are diluted by supporting ten years of old versions across dozens of different platforms and versions.  All that patching, porting and testing takes a big chunk (70-80%?) of a mature on-premise vendor&#039;s R&amp;D efforts.
- The on-premise vendor is always focused on the NEXT customer, rather than the customers they already have - customers who have given them their license fees already and have no alternatives.  So the vendor works on the next market segment, or repackages a release to re-sell into their installed base.  Here&#039;s a proposed Software Law of Attention:  The attention you get from a software vendor is directly proportional to the amount of future discretionary revenue the vendor can get from you.  (Note that maintenance fees are almost always not discretionary).  When on-premise software is purchased all up-front, zero future discretionary revenue means zero attention.

SaaS fixes the fundamental dynamics here, and customers are realizing that long-term relationships with SaaS vendors are much more positive - customers get ongoing upgrades for free, ever-expanding functionality and value, and a vendor who is motivated to have customers use and expand their use of the product.   And customers have a way out if the vendor doesn&#039;t perform.

- John Martin, BuildingSaaS.com</description>
		<content:encoded><![CDATA[<p>Ray:  This &#8220;bad behavior&#8221; is endemic to the badly broken (from the customer&#8217;s point of view) relationship experience with on-premise software.  First the client invests a huge amount on up-front software licenses, infrastructure (prod &amp; test &amp; dev), and an implementation project run by a third-party who is motivated to make it as complex and costly as possible&#8230; and then the customer has no options to move off the on-premise solution, so must keep paying 22% in ongoing maintenance for no ongoing value-add (because upgrading is really a re-implementation with customized on-premise software).</p>
<p>On-premise software vendors spend huge amounts on R&amp;D, but for existing customers their return on R&amp;D is close to zero because:<br />
- The on-premise vendor&#8217;s efforts are diluted by supporting ten years of old versions across dozens of different platforms and versions.  All that patching, porting and testing takes a big chunk (70-80%?) of a mature on-premise vendor&#8217;s R&amp;D efforts.<br />
- The on-premise vendor is always focused on the NEXT customer, rather than the customers they already have &#8211; customers who have given them their license fees already and have no alternatives.  So the vendor works on the next market segment, or repackages a release to re-sell into their installed base.  Here&#8217;s a proposed Software Law of Attention:  The attention you get from a software vendor is directly proportional to the amount of future discretionary revenue the vendor can get from you.  (Note that maintenance fees are almost always not discretionary).  When on-premise software is purchased all up-front, zero future discretionary revenue means zero attention.</p>
<p>SaaS fixes the fundamental dynamics here, and customers are realizing that long-term relationships with SaaS vendors are much more positive &#8211; customers get ongoing upgrades for free, ever-expanding functionality and value, and a vendor who is motivated to have customers use and expand their use of the product.   And customers have a way out if the vendor doesn&#8217;t perform.</p>
<p>- John Martin, BuildingSaaS.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Naomi Bloom</title>
		<link>http://blog.softwareinsider.org/2009/04/27/monday%e2%80%99s-musings-it%e2%80%99s-the-relationship-stupid-part-4-stop-under-investing-in-rd/comment-page-1/#comment-1623</link>
		<dc:creator>Naomi Bloom</dc:creator>
		<pubDate>Mon, 27 Apr 2009 18:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareinsider.org/?p=2121#comment-1623</guid>
		<description>Ray, this really resonates.  And the issue becomes more complicated when the maintenance revenues from legacy product lines, developed or acquired, are used to fund new product lines to which those legacy customers may not be able to migrate. While it&#039;s clear that all vendors must invest constantly in R&amp;D, this will be a tough period for HR software vendors because of regulatory activism.</description>
		<content:encoded><![CDATA[<p>Ray, this really resonates.  And the issue becomes more complicated when the maintenance revenues from legacy product lines, developed or acquired, are used to fund new product lines to which those legacy customers may not be able to migrate. While it&#8217;s clear that all vendors must invest constantly in R&amp;D, this will be a tough period for HR software vendors because of regulatory activism.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

