<?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: Best ROI for marketing dollars</title>
	<atom:link href="http://www.nick-rice.com/blog/2006/best-roi-for-marketing-dollars/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nick-rice.com/blog/2006/best-roi-for-marketing-dollars/</link>
	<description>b2b marketing &#38; sales thoughts by nick rice</description>
	<lastBuildDate>Tue, 02 Mar 2010 13:49:51 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Brown</title>
		<link>http://www.nick-rice.com/blog/2006/best-roi-for-marketing-dollars/comment-page-1/#comment-2</link>
		<dc:creator>Chris Brown</dc:creator>
		<pubDate>Wed, 13 Dec 2006 11:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.nick-rice.com/?p=10#comment-2</guid>
		<description>Nick:
You bring up a great point about print catalogs vs electronic emails.  

I think a comparison between a print catalog and an electronic catalog would be closer -- as in a website.  One big difference is consumers pick up and leaf thru the catalog (or a website)  on the the readers time table.  When an email comes in, it&#039;s read or delete, much more on the senders time table. 

Chris</description>
		<content:encoded><![CDATA[<p>Nick:<br />
You bring up a great point about print catalogs vs electronic emails.  </p>
<p>I think a comparison between a print catalog and an electronic catalog would be closer &#8212; as in a website.  One big difference is consumers pick up and leaf thru the catalog (or a website)  on the the readers time table.  When an email comes in, it&#8217;s read or delete, much more on the senders time table. </p>
<p>Chris</p>
]]></content:encoded>
	</item>
</channel>
</rss>

