<?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: Should you respond to that RFP?</title>
	<atom:link href="http://inluminent.com/2005/06/01/should-you-respond-to-that-rfp/feed/" rel="self" type="application/rss+xml" />
	<link>http://inluminent.com/2005/06/01/should-you-respond-to-that-rfp/</link>
	<description>my comments on business, marketing, advertising, email, CAN-SPAM, selling as a profession, photography, computers and other stuff...</description>
	<lastBuildDate>Wed, 01 Sep 2010 12:47:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: macdesktops</title>
		<link>http://inluminent.com/2005/06/01/should-you-respond-to-that-rfp/comment-page-1/#comment-3412</link>
		<dc:creator>macdesktops</dc:creator>
		<pubDate>Fri, 03 Jun 2005 17:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://inluminent.com/2005/06/01/should-you-respond-to-that-rfp/#comment-3412</guid>
		<description>John,

There&#039;s an = missing from your link tag  &#039;href&quot;http&#039;. No worky.

Steve has an interesting perspective. My experience working for a 5000-10000 employee biotech company starkly contrasts his view. I have participated in several projects which have included RFIs and RFPs. We sent detailed RFPs to a variety of vendors. Failure to respond, or responses of the type advocated by Mr. Clark removed the vendor from consideration. We analyzed all of the RFPs and did side by side comparisons. The devils were in the details. RFPs which failed to meet our requirements removed those vendors from contention, narrowing the field to 2-4. Only those final 2-4 were invited to provided presentations, and be considered for demos.

Pricing only came into play if we:
A. arrived at a point where two or more vendors met our requirements comparably, or
B. the vendor we selected on the merits was too expensive

Admittedly, not all companies are as comfortable ranking cost below features and timeline, and not all companies put out RFPs as detailed as ours. However, I doubt we&#039;re at the forefront in either regard. Refusing to submit an RFP, no matter how well articulated that refusal is, will probably just get you removed from consideration.

So, my suggestion as a &quot;Prospect&quot; is to weigh heavily who the &quot;Prospect&quot; is and how much detail is in the RFP.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>There&#8217;s an = missing from your link tag  &#8216;href&#8221;http&#8217;. No worky.</p>
<p>Steve has an interesting perspective. My experience working for a 5000-10000 employee biotech company starkly contrasts his view. I have participated in several projects which have included RFIs and RFPs. We sent detailed RFPs to a variety of vendors. Failure to respond, or responses of the type advocated by Mr. Clark removed the vendor from consideration. We analyzed all of the RFPs and did side by side comparisons. The devils were in the details. RFPs which failed to meet our requirements removed those vendors from contention, narrowing the field to 2-4. Only those final 2-4 were invited to provided presentations, and be considered for demos.</p>
<p>Pricing only came into play if we:<br />
A. arrived at a point where two or more vendors met our requirements comparably, or<br />
B. the vendor we selected on the merits was too expensive</p>
<p>Admittedly, not all companies are as comfortable ranking cost below features and timeline, and not all companies put out RFPs as detailed as ours. However, I doubt we&#8217;re at the forefront in either regard. Refusing to submit an RFP, no matter how well articulated that refusal is, will probably just get you removed from consideration.</p>
<p>So, my suggestion as a &#8220;Prospect&#8221; is to weigh heavily who the &#8220;Prospect&#8221; is and how much detail is in the RFP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Meadows</title>
		<link>http://inluminent.com/2005/06/01/should-you-respond-to-that-rfp/comment-page-1/#comment-3411</link>
		<dc:creator>Andy Meadows</dc:creator>
		<pubDate>Thu, 02 Jun 2005 05:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://inluminent.com/2005/06/01/should-you-respond-to-that-rfp/#comment-3411</guid>
		<description>John, excellent reference.  I&#039;m feeling much better about not responding to an RFP that was due today.  The temptation to reply is great, but most RFPs require a dozen hoops to jump through that can often be avoided when you build a relationship with a client.  As mentioned in the article, rarely are RFPs truly weighed side-by-side beyond price, which as we all know, is rarely a good basis for the final decision.</description>
		<content:encoded><![CDATA[<p>John, excellent reference.  I&#8217;m feeling much better about not responding to an RFP that was due today.  The temptation to reply is great, but most RFPs require a dozen hoops to jump through that can often be avoided when you build a relationship with a client.  As mentioned in the article, rarely are RFPs truly weighed side-by-side beyond price, which as we all know, is rarely a good basis for the final decision.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->