<?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: Learning How To Price Your Web App</title>
	<atom:link href="http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/</link>
	<description>Digital Media Engineering</description>
	<pubDate>Thu, 04 Dec 2008 19:55:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Robin Blandford [ ByteSurgery.com ] &#187; Finding That Price Point</title>
		<link>http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/#comment-22322</link>
		<dc:creator>Robin Blandford [ ByteSurgery.com ] &#187; Finding That Price Point</dc:creator>
		<pubDate>Wed, 15 Oct 2008 14:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=382#comment-22322</guid>
		<description>[...] IRELAND - Today I&#8217;m looking at pricing Decisions For Heroes. I wrote this post about the beauty of unlimited during the summer. Time to dive deeper now and project figures from our beta [...]</description>
		<content:encoded><![CDATA[<p>[...] IRELAND - Today I&#8217;m looking at pricing Decisions For Heroes. I wrote this post about the beauty of unlimited during the summer. Time to dive deeper now and project figures from our beta [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin Blandford</title>
		<link>http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/#comment-22297</link>
		<dc:creator>Robin Blandford</dc:creator>
		<pubDate>Mon, 06 Oct 2008 10:04:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=382#comment-22297</guid>
		<description>Hey Jeremiah - Useful tips. Thanks!

Your additional at a micro-costs idea has given me something interesting to play with.</description>
		<content:encoded><![CDATA[<p>Hey Jeremiah - Useful tips. Thanks!</p>
<p>Your additional at a micro-costs idea has given me something interesting to play with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremiah Ryan</title>
		<link>http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/#comment-22283</link>
		<dc:creator>Jeremiah Ryan</dc:creator>
		<pubDate>Thu, 02 Oct 2008 22:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=382#comment-22283</guid>
		<description>Comforting seeing someone else fighting with the same issues.  Our small app has just launched so I don't have enough data (or customers) to give good anecdotal advice, however here are some basic rules we found useful to clarify our final (current) position:-

(a) don't offer too many choices/'packages for the user to wring their hands over. Basecamp originally presented 5 or 6 but now publicly show 3 options. We had about five variations, hoping to hit the majority of what we though our customer base might need, but settled back to two basic packages in the end.

(b) Each app market is different in subtle ways generally understood by the entrepreneur, however rather than having an unlimited use quota, give a usable quantity as part of a package and then additional at a micro-cost. (easily justifiable, but gives you a revenue ratchet. Same with resources)</description>
		<content:encoded><![CDATA[<p>Comforting seeing someone else fighting with the same issues.  Our small app has just launched so I don&#8217;t have enough data (or customers) to give good anecdotal advice, however here are some basic rules we found useful to clarify our final (current) position:-</p>
<p>(a) don&#8217;t offer too many choices/&#8217;packages for the user to wring their hands over. Basecamp originally presented 5 or 6 but now publicly show 3 options. We had about five variations, hoping to hit the majority of what we though our customer base might need, but settled back to two basic packages in the end.</p>
<p>(b) Each app market is different in subtle ways generally understood by the entrepreneur, however rather than having an unlimited use quota, give a usable quantity as part of a package and then additional at a micro-cost. (easily justifiable, but gives you a revenue ratchet. Same with resources)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: darrylxxx</title>
		<link>http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/#comment-21884</link>
		<dc:creator>darrylxxx</dc:creator>
		<pubDate>Mon, 23 Jun 2008 16:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=382#comment-21884</guid>
		<description>Robin,

Good read. I've been on the same journey and can recommend you read these:

http://www.joelonsoftware.com/articles/CamelsandRubberDuckies.html
http://avc.blogs.com/a_vc/2008/01/the-long-tail-o.html
http://redeye.firstround.com/2007/03/the_first_penny.html

Love the tour on the new site too!

Rgds
Darryl Collins
http://www.banjax.com</description>
		<content:encoded><![CDATA[<p>Robin,</p>
<p>Good read. I&#8217;ve been on the same journey and can recommend you read these:</p>
<p><a href="http://www.joelonsoftware.com/articles/CamelsandRubberDuckies.html" rel="nofollow">http://www.joelonsoftware.com/articles/CamelsandRubberDuckies.html</a><br />
<a href="http://avc.blogs.com/a_vc/2008/01/the-long-tail-o.html" rel="nofollow">http://avc.blogs.com/a_vc/2008/01/the-long-tail-o.html</a><br />
<a href="http://redeye.firstround.com/2007/03/the_first_penny.html" rel="nofollow">http://redeye.firstround.com/2007/03/the_first_penny.html</a></p>
<p>Love the tour on the new site too!</p>
<p>Rgds<br />
Darryl Collins<br />
<a href="http://www.banjax.com" rel="nofollow">http://www.banjax.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant Watson&#8217;s links for 2008-06-16</title>
		<link>http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/#comment-21874</link>
		<dc:creator>Grant Watson&#8217;s links for 2008-06-16</dc:creator>
		<pubDate>Mon, 16 Jun 2008 22:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=382#comment-21874</guid>
		<description>[...] Robin Blandford [ ByteSurgery.com - Digital Media Engineering ] » Blog Archive » Learning How To P... Unlike many traditional models, it seems web app prices are not pay as much as you eat. You do not get charged per item, rather you buy a bundle that has limits. Prices have to be made very simple to up-sell the user as their requirements increase (tags: web2.0 business-models) [...]</description>
		<content:encoded><![CDATA[<p>[...] Robin Blandford [ ByteSurgery.com - Digital Media Engineering ] » Blog Archive » Learning How To P&#8230; Unlike many traditional models, it seems web app prices are not pay as much as you eat. You do not get charged per item, rather you buy a bundle that has limits. Prices have to be made very simple to up-sell the user as their requirements increase (tags: web2.0 business-models) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Sweeney</title>
		<link>http://www.bytesurgery.com/blog/2008/06/05/learning-how-to-price-your-web-app/#comment-21860</link>
		<dc:creator>Paul Sweeney</dc:creator>
		<pubDate>Mon, 09 Jun 2008 07:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytesurgery.com/blog/?p=382#comment-21860</guid>
		<description>Happy to share some learning here. 

(1) The pricing will ultimately only come clear in actual customer conversations. Some customers may want to buy in "gigs" some will want monthly some will want to per year etc. What we at VoiceSage found, was that once we found the right customer-type, the pricing gained uniformity in structure;

(2) Its not about "price" for the business customer, its ability to demonstrate value. If you are "in the pricing conversation", they don't see the value. Lets face it, if you walked away from that conversation, would they follow you out the door?

(3) In enterprise, I've heard this more than once: "in Pricing, ask for one third of what you can prove you made or saved for the customer". Doesn't seem a bad metric to me anyway.</description>
		<content:encoded><![CDATA[<p>Happy to share some learning here. </p>
<p>(1) The pricing will ultimately only come clear in actual customer conversations. Some customers may want to buy in &#8220;gigs&#8221; some will want monthly some will want to per year etc. What we at VoiceSage found, was that once we found the right customer-type, the pricing gained uniformity in structure;</p>
<p>(2) Its not about &#8220;price&#8221; for the business customer, its ability to demonstrate value. If you are &#8220;in the pricing conversation&#8221;, they don&#8217;t see the value. Lets face it, if you walked away from that conversation, would they follow you out the door?</p>
<p>(3) In enterprise, I&#8217;ve heard this more than once: &#8220;in Pricing, ask for one third of what you can prove you made or saved for the customer&#8221;. Doesn&#8217;t seem a bad metric to me anyway.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
