<?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: Five Things Every RFP Should Contain</title>
	<atom:link href="http://blog.networkats.com/index.php/2006/10/20/thoughts-about-rfps-part-1-or-five-things-every-rfp-should-contain/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.networkats.com/index.php/2006/10/20/thoughts-about-rfps-part-1-or-five-things-every-rfp-should-contain/</link>
	<description>Comprehensive, High Quality Information Technology Services</description>
	<pubDate>Sun, 06 Jul 2008 21:16:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: James Sun</title>
		<link>http://blog.networkats.com/index.php/2006/10/20/thoughts-about-rfps-part-1-or-five-things-every-rfp-should-contain/#comment-17</link>
		<dc:creator>James Sun</dc:creator>
		<pubDate>Sat, 06 Jan 2007 13:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.networkats.com/index.php/2006/10/20/thoughts-about-rfps-part-1-or-five-things-every-rfp-should-contain/#comment-17</guid>
		<description>Asif - Nicely put.  Thanks for your comments.</description>
		<content:encoded><![CDATA[<p>Asif - Nicely put.  Thanks for your comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asif Fayyaz</title>
		<link>http://blog.networkats.com/index.php/2006/10/20/thoughts-about-rfps-part-1-or-five-things-every-rfp-should-contain/#comment-16</link>
		<dc:creator>Asif Fayyaz</dc:creator>
		<pubDate>Sat, 06 Jan 2007 11:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.networkats.com/index.php/2006/10/20/thoughts-about-rfps-part-1-or-five-things-every-rfp-should-contain/#comment-16</guid>
		<description>I have also experienced those cases where we accpeted with a proposal not more than 7 to 8 pages. the factors i usually cared about in initial discussions of the project is to highlight 
&#62;our understanding what the client exactly requires
&#62;how we will cater those requirements i.e. features and fcuntions
&#62;our approach and methodology of work in development and with client.
&#62;our experties and experience to assure client that we can do this.
&#62;cost and constaints (internal and external).
this somewhat matches what you have proposed..and i am agree as i have won clients using this time safely approach , targetting what client want and not focusing much on what we can do and waht we have done.</description>
		<content:encoded><![CDATA[<p>I have also experienced those cases where we accpeted with a proposal not more than 7 to 8 pages. the factors i usually cared about in initial discussions of the project is to highlight<br />
&gt;our understanding what the client exactly requires<br />
&gt;how we will cater those requirements i.e. features and fcuntions<br />
&gt;our approach and methodology of work in development and with client.<br />
&gt;our experties and experience to assure client that we can do this.<br />
&gt;cost and constaints (internal and external).<br />
this somewhat matches what you have proposed..and i am agree as i have won clients using this time safely approach , targetting what client want and not focusing much on what we can do and waht we have done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.447 seconds -->
