<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Comparison Engines and Search Arbitrage</title>
	<link>http://www.jellyfish.com/blog/2007/03/01/comparison-engines-and-search-arbitrage/</link>
	<description>The Official Blog of Jellyfish.com</description>
	<pubDate>Sun, 23 Nov 2008 14:15:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: All Roads Lead to a Compelling User Experience at Starting Up by Rahul Pathak</title>
		<link>http://www.jellyfish.com/blog/2007/03/01/comparison-engines-and-search-arbitrage/#comment-2130</link>
		<pubDate>Fri, 02 Mar 2007 03:48:44 +0000</pubDate>
		<guid>http://www.jellyfish.com/blog/2007/03/01/comparison-engines-and-search-arbitrage/#comment-2130</guid>
					<description>[...] As we&amp;#8217;ve been spending time getting to know the deals/shopping space, it&amp;#8217;s become clear that sticking deals on a page is not sufficient. You need to provide users with a reason to come back to your site. If you have to keep acquiring customers for the first time, every time you want them to visit, you&amp;#8217;re going to have a problem. Arbitrage margins are narrowing and that trend is unlikely to reverse itself anytime soon. There are some great posts on this topic at Bronte Media and Jellyfish&amp;#8217;s blog. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] As we&#8217;ve been spending time getting to know the deals/shopping space, it&#8217;s become clear that sticking deals on a page is not sufficient. You need to provide users with a reason to come back to your site. If you have to keep acquiring customers for the first time, every time you want them to visit, you&#8217;re going to have a problem. Arbitrage margins are narrowing and that trend is unlikely to reverse itself anytime soon. There are some great posts on this topic at Bronte Media and Jellyfish&#8217;s blog. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
