<?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: How to price Enterprise Social Computing offerings?</title>
	<atom:link href="http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/feed/" rel="self" type="application/rss+xml" />
	<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/</link>
	<description></description>
	<lastBuildDate>Thu, 08 Sep 2011 02:40: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: Kids Games</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-241</link>
		<dc:creator>Kids Games</dc:creator>
		<pubDate>Tue, 08 Sep 2009 23:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-241</guid>
		<description>Interesting assessment. Developing a pricing strategy can always be a source of contention for companies. You lay out a good outline to follow.</description>
		<content:encoded><![CDATA[<p>Interesting assessment. Developing a pricing strategy can always be a source of contention for companies. You lay out a good outline to follow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kids Games</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-223</link>
		<dc:creator>Kids Games</dc:creator>
		<pubDate>Tue, 08 Sep 2009 18:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-223</guid>
		<description>Interesting assessment. Developing a pricing strategy can always be a source of contention for companies. You lay out a good outline to follow.</description>
		<content:encoded><![CDATA[<p>Interesting assessment. Developing a pricing strategy can always be a source of contention for companies. You lay out a good outline to follow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Club Penguin Cheats</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-217</link>
		<dc:creator>Club Penguin Cheats</dc:creator>
		<pubDate>Wed, 26 Aug 2009 02:32:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-217</guid>
		<description>It summarizes nicely a critical strategic issue for both the enterprise customer and the vendor. As you point out finding this alignment is critical to successful relationships in the long term. Piloting social applications is and interesting exercise given the nature of the value curve.</description>
		<content:encoded><![CDATA[<p>It summarizes nicely a critical strategic issue for both the enterprise customer and the vendor. As you point out finding this alignment is critical to successful relationships in the long term. Piloting social applications is and interesting exercise given the nature of the value curve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How can Prezi penetrate the enterprise market? - Core Edges</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-193</link>
		<dc:creator>How can Prezi penetrate the enterprise market? - Core Edges</dc:creator>
		<pubDate>Thu, 04 Jun 2009 17:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-193</guid>
		<description>[...] forward: As I detailed here, the best strategy is to offer a deployment at cost (this also works for a SAAS version at very low [...]</description>
		<content:encoded><![CDATA[<p>[…] forward: As I detailed here, the best strategy is to offer a deployment at cost (this also works for a SAAS version at very low […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uservoice fails to seize the internal enterprise market (or &#8220;consuprise&#8221; take 3) - Macro Principles</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-187</link>
		<dc:creator>Uservoice fails to seize the internal enterprise market (or &#8220;consuprise&#8221; take 3) - Macro Principles</dc:creator>
		<pubDate>Wed, 20 May 2009 19:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-187</guid>
		<description>[...] Deploy at cost then charge for use: don&#8217;t try to reap all the benefits right-away through license fees, it won&#8217;t work. IT functions and organizations are not yet mature enough to invest a lump sum in these products. Instead, deploy the appliance at cost (at real costs: only hardware and time spent), and price based on the actual activity which creates value. For Feedback 2.0 tools, it could be the number of independent &#8220;forums&#8221; or the number of feedback items. You should also give away the first items for free. (I went in details in Enterprise Social Computing pricing here.) [...]</description>
		<content:encoded><![CDATA[<p>[…] Deploy at cost then charge for use: don’t try to reap all the benefits right-away through license fees, it won’t work. IT functions and organizations are not yet mature enough to invest a lump sum in these products. Instead, deploy the appliance at cost (at real costs: only hardware and time spent), and price based on the actual activity which creates value. For Feedback 2.0 tools, it could be the number of independent “forums” or the number of feedback items. You should also give away the first items for free. (I went in details in Enterprise Social Computing pricing here.) […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sibs</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-132</link>
		<dc:creator>Sibs</dc:creator>
		<pubDate>Thu, 05 Mar 2009 12:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-132</guid>
		<description>Juliene,&lt;br&gt;&lt;br&gt;Great article, thank you for sharing.  I agree with your point of view 100%.  The network effect of social computing in the enterprise is a great way of articulating the argument of volume increasing pricing.  I think there are two barriers to address, however, by vendors and vendors in consultation with their clients.  1) Balancing those elements of a solution that may be construed by organizations as more social-social than social-work and 2) Ensuring that the client marketing/champion is doing a good enough job to drive adoption.  From our experience deploying our next generation directory solution (&lt;a href=&quot;http://gtec.innovapost.com/&quot; rel=&quot;nofollow&quot;&gt;http://gtec.innovapost.com/&lt;/a&gt;), these two issues are a challenge to a volume increasing pricing strategy.&lt;br&gt;&lt;br&gt;For #1, with many social applications there are often features and functionality that don&#039;t have a hard link to business productivity.  I&#039;m an advocate of 2.0 in the workplace as I believe there are productivity (see my whitepaper Beyond Functional Contribution via the link above) and employee engagement benefits to be reaped, but we do have to be careful because some solution elements are, and will be, used for social-social purposes.  If the solution has an abundance of features that drive social-social behaviour and attract users as a result, it&#039;s a tough pill to swallow for organizations to pay more because the organizational value proposition under these circumstances because more tenuous.  Those of us in the Enterprise 2.0 space would still maintain there is value, and I am one of them, but not all of our customers will.&lt;br&gt;&lt;br&gt;For #2, I think we all agree that enterprise 2.0 is largely a cultural paradigm shift about the nature of work and the view of employee behaviour.  So deploying these solutions in the enterprise requires the enterprise to roll up its communications, culture change, and marketing sleeves and promote the internal solution like they would their latest product launch.  As a vendor, we need to help guide these efforts as they will directly impact the use of the solution.  If we don&#039;t provide clients with any help, but we want volume increasing pricing, we&#039;re not doing ourselves any favours.  &lt;br&gt;&lt;br&gt;Just a few rambling thoughts as I read your article.  &lt;br&gt;&lt;br&gt;Warm regards,</description>
		<content:encoded><![CDATA[<p>Juliene,</p>
<p>Great article, thank you for sharing.  I agree with your point of view 100%.  The network effect of social computing in the enterprise is a great way of articulating the argument of volume increasing pricing.  I think there are two barriers to address, however, by vendors and vendors in consultation with their clients.  1) Balancing those elements of a solution that may be construed by organizations as more social-social than social-work and 2) Ensuring that the client marketing/champion is doing a good enough job to drive adoption.  From our experience deploying our next generation directory solution (<a href="http://gtec.innovapost.com/" rel="nofollow">http://gtec.innovapost.com/</a>), these two issues are a challenge to a volume increasing pricing strategy.</p>
<p>For #1, with many social applications there are often features and functionality that don’t have a hard link to business productivity.  I’m an advocate of 2.0 in the workplace as I believe there are productivity (see my whitepaper Beyond Functional Contribution via the link above) and employee engagement benefits to be reaped, but we do have to be careful because some solution elements are, and will be, used for social-social purposes.  If the solution has an abundance of features that drive social-social behaviour and attract users as a result, it’s a tough pill to swallow for organizations to pay more because the organizational value proposition under these circumstances because more tenuous.  Those of us in the Enterprise 2.0 space would still maintain there is value, and I am one of them, but not all of our customers will.</p>
<p>For #2, I think we all agree that enterprise 2.0 is largely a cultural paradigm shift about the nature of work and the view of employee behaviour.  So deploying these solutions in the enterprise requires the enterprise to roll up its communications, culture change, and marketing sleeves and promote the internal solution like they would their latest product launch.  As a vendor, we need to help guide these efforts as they will directly impact the use of the solution.  If we don’t provide clients with any help, but we want volume increasing pricing, we’re not doing ourselves any favours.  </p>
<p>Just a few rambling thoughts as I read your article.  </p>
<p>Warm regards,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Social Computing Pricing: continuing the discussion - Macro Principles</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-127</link>
		<dc:creator>Enterprise Social Computing Pricing: continuing the discussion - Macro Principles</dc:creator>
		<pubDate>Mon, 02 Mar 2009 23:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-127</guid>
		<description>[...] recently asked Olivier Amprimo to examine my argument around pricing for Enterprise Social Computing offerings. He kindly did it with an excellent post, so this is my reply, a bit in the spirit of old-fashioned [...]</description>
		<content:encoded><![CDATA[<p>[…] recently asked Olivier Amprimo to examine my argument around pricing for Enterprise Social Computing offerings. He kindly did it with an excellent post, so this is my reply, a bit in the spirit of old-fashioned […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien Le Nestour</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-126</link>
		<dc:creator>Julien Le Nestour</dc:creator>
		<pubDate>Mon, 02 Mar 2009 20:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-126</guid>
		<description>Hi Jon, many thanks for the already insightful comment, eager to read more :-)&lt;br&gt;&lt;br&gt;Yes, ROI is no longer a meaningful metric. What amazes me now is how many people are judging a tool based on its &quot;features&quot;, which is an even less relevant concept to judge IT offerings.</description>
		<content:encoded><![CDATA[<p>Hi Jon, many thanks for the already insightful comment, eager to read more :-)</p>
<p>Yes, ROI is no longer a meaningful metric. What amazes me now is how many people are judging a tool based on its “features”, which is an even less relevant concept to judge IT offerings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Husband</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-124</link>
		<dc:creator>Jon Husband</dc:creator>
		<pubDate>Sat, 28 Feb 2009 17:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-124</guid>
		<description>I&#039;ll comment more later, but for now ...&lt;br&gt;&lt;br&gt;In general, the argument you have set out has articulated &lt;i&gt;en brouillon&lt;/i&gt; the thinking I have been doing about what I call ROII (&lt;b&gt;Return on Investment in Interaction&lt;/b&gt;).  For that I thank you.&lt;br&gt;&lt;br&gt;Re: &lt;i&gt;Adopt your client’s point of view: if your deployment is very successful, they will pay an expensive price but derive lots of value from it. Additionally, if the deployment needs to be phased to convince stakeholders of the value potential, they will also pay a matching price that will enable them to scale its use. Reversing the price structure lowers significantly the risk for the client, increasing the chances of a pilot happening.&lt;br&gt;&lt;br&gt;A positive externality of such a pricing strategy, at its peak for Enterprise Social Computing offerings, is the credibility and confidence about their product projected by vendors. Nearly all are using arguments about how easy it is to engage employees, how they will want to use it, collaborate with each other, etc. So don’t limit yourself to the market pitch, embed this in your pricing and demonstrate your confidence.&lt;/i&gt;&lt;br&gt;&lt;br&gt;I think that this is essentially the inverse of (for example) a $50 million dollar SAP implementation.&lt;br&gt;&lt;br&gt;Which I think speaks to timing and attention scarcity.  SAP for me is (still) an example of a transition technology, as the evolution of IT applied to business and work processes began the major move from paper to information systems in a real and pervasive sense.  If you think about it, it wasn&#039;t really that complex .. take existing processes, align them horizontally instead of vertically, strip out obvious redundancies (everyone remember the &quot;Spot the Waldo&quot; reengineering stuff ?), and then pour electronic concrete (SAP system) over it.&lt;br&gt;&lt;br&gt;Now we are moving into collaboration applications layered over a dense-and-deep IT infrastructure (let&#039;s leave ERP systems out of this aspect for now), applications that consist of stitching together various web tools and web services (as a generality) that lay on top of the denser, more &quot;permanent&quot; databases and engines.  These applications ands services are becoming both more open and more integrated all the time, to the point where through &quot;open&quot; APIs people can plug the tools they like using into larger applications and systems.  As the concept of &quot;cloud computing&quot; evolves, so too will the mix-and-match personalisation.&lt;br&gt;&lt;br&gt;The former (and current) pricing models assumed amortization of investment over time in something more-or-less permanent (at least, assumed to be for the purposes of ROI hurdles).&lt;br&gt;&lt;br&gt;With large-scale (and over time growing) participation and interactivity, the notion of value obtained and created changes, as you have pointed out.&lt;br&gt;&lt;br&gt;I&#039;ll re-read and think, and come back when I feel I can talk cogently about ROII.</description>
		<content:encoded><![CDATA[<p>I’ll comment more later, but for now …</p>
<p>In general, the argument you have set out has articulated <i>en brouillon</i> the thinking I have been doing about what I call ROII (<b>Return on Investment in Interaction</b>).  For that I thank you.</p>
<p>Re: <i>Adopt your client’s point of view: if your deployment is very successful, they will pay an expensive price but derive lots of value from it. Additionally, if the deployment needs to be phased to convince stakeholders of the value potential, they will also pay a matching price that will enable them to scale its use. Reversing the price structure lowers significantly the risk for the client, increasing the chances of a pilot happening.</p>
<p>A positive externality of such a pricing strategy, at its peak for Enterprise Social Computing offerings, is the credibility and confidence about their product projected by vendors. Nearly all are using arguments about how easy it is to engage employees, how they will want to use it, collaborate with each other, etc. So don’t limit yourself to the market pitch, embed this in your pricing and demonstrate your confidence.</i></p>
<p>I think that this is essentially the inverse of (for example) a $50 million dollar SAP implementation.</p>
<p>Which I think speaks to timing and attention scarcity.  SAP for me is (still) an example of a transition technology, as the evolution of IT applied to business and work processes began the major move from paper to information systems in a real and pervasive sense.  If you think about it, it wasn’t really that complex .. take existing processes, align them horizontally instead of vertically, strip out obvious redundancies (everyone remember the “Spot the Waldo” reengineering stuff ?), and then pour electronic concrete (SAP system) over it.</p>
<p>Now we are moving into collaboration applications layered over a dense-and-deep IT infrastructure (let’s leave ERP systems out of this aspect for now), applications that consist of stitching together various web tools and web services (as a generality) that lay on top of the denser, more “permanent” databases and engines.  These applications ands services are becoming both more open and more integrated all the time, to the point where through “open” APIs people can plug the tools they like using into larger applications and systems.  As the concept of “cloud computing” evolves, so too will the mix-and-match personalisation.</p>
<p>The former (and current) pricing models assumed amortization of investment over time in something more-or-less permanent (at least, assumed to be for the purposes of ROI hurdles).</p>
<p>With large-scale (and over time growing) participation and interactivity, the notion of value obtained and created changes, as you have pointed out.</p>
<p>I’ll re-read and think, and come back when I feel I can talk cogently about ROII.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: carlo</title>
		<link>http://coreedges.com/blog/2009/02/13/how-to-price-enterprise-social-computing-offerings/comment-page-1/#comment-118</link>
		<dc:creator>carlo</dc:creator>
		<pubDate>Sun, 22 Feb 2009 11:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.macroprinciples.com/2009/02/how-to-price-enterprise-social-computing-offerings/#comment-118</guid>
		<description>Hi Julien,&lt;br&gt;&lt;br&gt;thanks for this excellent piece of analysis. At my company Qitera that offers a enterprise social search platform (&lt;a href=&quot;http://www.qitera.com/enterprise&quot; rel=&quot;nofollow&quot;&gt;http://www.qitera.com/enterprise&lt;/a&gt;)  we are currently defining our new pricing shemes and your article brings in some very well-thought perspectives.&lt;br&gt;&lt;br&gt;I am also senior advisor at IT-research firm Experton Group and recommended your post to the readers of our new blog. &lt;a href=&quot;http://experton-group.blogspot.com/2009/02/enterprise-20-pricing-und.html&quot; rel=&quot;nofollow&quot;&gt;http://experton-group.blogspot.com/2009/02/ente...&lt;/a&gt;&lt;br&gt;&lt;br&gt;regards et à bientôt &lt;br&gt;Carlo</description>
		<content:encoded><![CDATA[<p>Hi Julien,</p>
<p>thanks for this excellent piece of analysis. At my company Qitera that offers a enterprise social search platform (<a href="http://www.qitera.com/enterprise" rel="nofollow">http://www.qitera.com/enterprise</a>)  we are currently defining our new pricing shemes and your article brings in some very well-thought perspectives.</p>
<p>I am also senior advisor at IT-research firm Experton Group and recommended your post to the readers of our new blog. <a href="http://experton-group.blogspot.com/2009/02/enterprise-20-pricing-und.html" rel="nofollow">http://experton-group.blogspot.com/2009/02/ente…</a></p>
<p>regards et à bientôt <br />Carlo</p>
]]></content:encoded>
	</item>
</channel>
</rss>

