<?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: &#8220;Can Do&#8221; vs Have Done&#8221;</title>
	<atom:link href="http://www.chrisconrey.com/can-do-vs-have-done/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrisconrey.com/can-do-vs-have-done/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=can-do-vs-have-done</link>
	<description>Because Second Place is a set of Steak Knives</description>
	<lastBuildDate>Sun, 20 Nov 2011 04:24:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: kapil bhatia</title>
		<link>http://www.chrisconrey.com/can-do-vs-have-done/comment-page-1/#comment-1986</link>
		<dc:creator>kapil bhatia</dc:creator>
		<pubDate>Fri, 05 Feb 2010 12:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisconrey.com/?p=728#comment-1986</guid>
		<description>Prospective clients tell us something about the project in initial stages. Based on their information, I try to categorize whether it is a ecommerce application or social network project or something else. Then, I sent them a pdf document which we have created for  industry vertical or problem area client is looking for with the kind of work &quot;we have done&quot;. Obviously those pdfs can not be sent in every case, but for sales, it  really help us to score those &quot;have done&quot; points.  Integrating &quot;have done&quot; in sales process through templates of similar work you have done helps. Its important to continually work on these documents and update them with new projects.

PS: There is a trend we see every year. Every consumer application we have done requires simple to innovative integration with twitter API. So, having a two page document of every thing we have done with twitter API might be a good idea.</description>
		<content:encoded><![CDATA[<p>Prospective clients tell us something about the project in initial stages. Based on their information, I try to categorize whether it is a ecommerce application or social network project or something else. Then, I sent them a pdf document which we have created for  industry vertical or problem area client is looking for with the kind of work &#8220;we have done&#8221;. Obviously those pdfs can not be sent in every case, but for sales, it  really help us to score those &#8220;have done&#8221; points.  Integrating &#8220;have done&#8221; in sales process through templates of similar work you have done helps. Its important to continually work on these documents and update them with new projects.</p>
<p>PS: There is a trend we see every year. Every consumer application we have done requires simple to innovative integration with twitter API. So, having a two page document of every thing we have done with twitter API might be a good idea.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

