<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for message communications</title>
	<atom:link href="http://messagecom.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://messagecom.wordpress.com</link>
	<description>Thoughts about non-profit &#38; social services PR</description>
	<lastBuildDate>Wed, 14 Oct 2009 17:00:21 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Should we shred the RFP process? by egads</title>
		<link>http://messagecom.wordpress.com/2009/10/13/should-we-ditch-the-rfp-process/#comment-867</link>
		<dc:creator>egads</dc:creator>
		<pubDate>Wed, 14 Oct 2009 17:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://messagecom.wordpress.com/?p=967#comment-867</guid>
		<description>As one who frequently responds to RFPs, I wish more organizations started with a preliminary Request for Qualifications to help focus and refine their RFP documents.  Under Ideal Circumstances, RFPs will be so clear and comprehensive that a responsive proposal can serve as the administrative review draft for a subsequent contractual Scope of Work.</description>
		<content:encoded><![CDATA[<p>As one who frequently responds to RFPs, I wish more organizations started with a preliminary Request for Qualifications to help focus and refine their RFP documents.  Under Ideal Circumstances, RFPs will be so clear and comprehensive that a responsive proposal can serve as the administrative review draft for a subsequent contractual Scope of Work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should we shred the RFP process? by David</title>
		<link>http://messagecom.wordpress.com/2009/10/13/should-we-ditch-the-rfp-process/#comment-866</link>
		<dc:creator>David</dc:creator>
		<pubDate>Wed, 14 Oct 2009 13:32:18 +0000</pubDate>
		<guid isPermaLink="false">http://messagecom.wordpress.com/?p=967#comment-866</guid>
		<description>Great article!

I&#039;ve written a number of similar/related articles that might interest you and your readers. For some background, I run the RFP Database at http://www.rfpdb.com

RFP Etiquette: Dos and Don’ts for Business Matchmaking
http://blog.confluentforms.com/2009/08/rfp-etiquette-dos-and-donts-for.html

Often maligned, RFPs are a valuable tool and opportunity
http://blog.confluentforms.com/2009/07/often-maligned-rfps-are-valuable-tool.html

Not all Requests for Proposals are worth a proposal
http://blog.confluentforms.com/2008/10/not-all-requests-for-proposals-are.html

Best,

-David</description>
		<content:encoded><![CDATA[<p>Great article!</p>
<p>I&#8217;ve written a number of similar/related articles that might interest you and your readers. For some background, I run the RFP Database at <a href="http://www.rfpdb.com" rel="nofollow">http://www.rfpdb.com</a></p>
<p>RFP Etiquette: Dos and Don’ts for Business Matchmaking<br />
<a href="http://blog.confluentforms.com/2009/08/rfp-etiquette-dos-and-donts-for.html" rel="nofollow">http://blog.confluentforms.com/2009/08/rfp-etiquette-dos-and-donts-for.html</a></p>
<p>Often maligned, RFPs are a valuable tool and opportunity<br />
<a href="http://blog.confluentforms.com/2009/07/often-maligned-rfps-are-valuable-tool.html" rel="nofollow">http://blog.confluentforms.com/2009/07/often-maligned-rfps-are-valuable-tool.html</a></p>
<p>Not all Requests for Proposals are worth a proposal<br />
<a href="http://blog.confluentforms.com/2008/10/not-all-requests-for-proposals-are.html" rel="nofollow">http://blog.confluentforms.com/2008/10/not-all-requests-for-proposals-are.html</a></p>
<p>Best,</p>
<p>-David</p>
]]></content:encoded>
	</item>
</channel>
</rss>
