<?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: 7 Tips for a Killer Demo</title>
	<atom:link href="http://www.techdemoguy.com/2009/06/7-tips-for-a-killer-demo/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techdemoguy.com/2009/06/7-tips-for-a-killer-demo/</link>
	<description>Making the Technical Sale</description>
	<lastBuildDate>Thu, 20 May 2010 21:06:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John McKenney</title>
		<link>http://www.techdemoguy.com/2009/06/7-tips-for-a-killer-demo/comment-page-1/#comment-140</link>
		<dc:creator>John McKenney</dc:creator>
		<pubDate>Tue, 07 Jul 2009 11:59:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.techdemoguy.com/?p=148#comment-140</guid>
		<description>Be yourself, nobody wants to hear a scripted demo, roll with the punches. I have been demo&#039;ing ECM for over 7 years and being able to perform a demo that does not have a rehearsed path works best. Also, know what you are showing, too often I have witnessed demos where the person presenting has limited knowledge on the subject and cannot answer questions not originally planned for. </description>
		<content:encoded><![CDATA[<p>Be yourself, nobody wants to hear a scripted demo, roll with the punches. I have been demo&#039;ing ECM for over 7 years and being able to perform a demo that does not have a rehearsed path works best. Also, know what you are showing, too often I have witnessed demos where the person presenting has limited knowledge on the subject and cannot answer questions not originally planned for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dsohigian</title>
		<link>http://www.techdemoguy.com/2009/06/7-tips-for-a-killer-demo/comment-page-1/#comment-121</link>
		<dc:creator>dsohigian</dc:creator>
		<pubDate>Tue, 30 Jun 2009 15:36:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.techdemoguy.com/?p=148#comment-121</guid>
		<description>@Scott - great additions! </description>
		<content:encoded><![CDATA[<p>@Scott &#8211; great additions!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Peters</title>
		<link>http://www.techdemoguy.com/2009/06/7-tips-for-a-killer-demo/comment-page-1/#comment-120</link>
		<dc:creator>Scott Peters</dc:creator>
		<pubDate>Tue, 30 Jun 2009 14:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.techdemoguy.com/?p=148#comment-120</guid>
		<description>Dave,   
 
These are great tips.  I would add two more that were the first things I learned when getting into technical sales, and a third that I learned as I developed as a resource.  
 
1. Provide Context -  Does everyone in the room have a clear vision of how the solution you are presenting will affect their lives? Specifically the main ideas you want them to take away from your presentation. 
 
2. Know your data.  Nothing will undermine your credibility faster than going to screens that don&#039;t work, or data that is not appropriate in building to your take aways.   
 
3. Discovery.  Any opportunity you can get to meet with the client to understand their specific issues and business processes, will accelerate your sales cycle.  Doing generic demos can be effective.  Speaking specifically to the issues of the prospect, using the names of the process owners and even using their data is a fantastic way to build a great demo </description>
		<content:encoded><![CDATA[<p>Dave,   </p>
<p>These are great tips.  I would add two more that were the first things I learned when getting into technical sales, and a third that I learned as I developed as a resource.  </p>
<p>1. Provide Context &#8211;  Does everyone in the room have a clear vision of how the solution you are presenting will affect their lives? Specifically the main ideas you want them to take away from your presentation. </p>
<p>2. Know your data.  Nothing will undermine your credibility faster than going to screens that don&#039;t work, or data that is not appropriate in building to your take aways.   </p>
<p>3. Discovery.  Any opportunity you can get to meet with the client to understand their specific issues and business processes, will accelerate your sales cycle.  Doing generic demos can be effective.  Speaking specifically to the issues of the prospect, using the names of the process owners and even using their data is a fantastic way to build a great demo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Kernoczy</title>
		<link>http://www.techdemoguy.com/2009/06/7-tips-for-a-killer-demo/comment-page-1/#comment-117</link>
		<dc:creator>Bill Kernoczy</dc:creator>
		<pubDate>Wed, 24 Jun 2009 23:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.techdemoguy.com/?p=148#comment-117</guid>
		<description>Hi Dave 
i agree with you about feature dumps - theyr&#039;e a great way to send your audience to sleep. 
A day in the life, stories and demos are far more preferable 
Cheers 
Bill </description>
		<content:encoded><![CDATA[<p>Hi Dave<br />
i agree with you about feature dumps &#8211; theyr&#039;e a great way to send your audience to sleep.<br />
A day in the life, stories and demos are far more preferable<br />
Cheers<br />
Bill</p>
]]></content:encoded>
	</item>
</channel>
</rss>
