<?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: Sales Presentations:  No demos&#8230;.EVER!</title>
	<atom:link href="http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/feed/" rel="self" type="application/rss+xml" />
	<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/</link>
	<description>Accelerating Sales in Start-ups</description>
	<lastBuildDate>Fri, 27 Jan 2012 16:09:41 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brandon</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-96</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Thu, 11 Mar 2010 21:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-96</guid>
		<description>Mark, thanks for the reply!  With the broader explanation (and also digging to find a related post on this blog), I see where you are coming from.  I understand firsthand the pitfalls of demos (along with talking price before we talk needs / wants / pain / value) and have no desire for Murphy to interfere with an otherwise good dialog.  Thanks!</description>
		<content:encoded><![CDATA[<p>Mark, thanks for the reply!  With the broader explanation (and also digging to find a related post on this blog), I see where you are coming from.  I understand firsthand the pitfalls of demos (along with talking price before we talk needs / wants / pain / value) and have no desire for Murphy to interfere with an otherwise good dialog.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-217</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Thu, 11 Mar 2010 21:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-217</guid>
		<description>Mark, thanks for the reply!  With the broader explanation (and also digging to find a related post on this blog), I see where you are coming from.  I understand firsthand the pitfalls of demos (along with talking price before we talk needs / wants / pain / value) and have no desire for Murphy to interfere with an otherwise good dialog.  Thanks!</description>
		<content:encoded><![CDATA[<p>Mark, thanks for the reply!  With the broader explanation (and also digging to find a related post on this blog), I see where you are coming from.  I understand firsthand the pitfalls of demos (along with talking price before we talk needs / wants / pain / value) and have no desire for Murphy to interfere with an otherwise good dialog.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark I LaRosa</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-95</link>
		<dc:creator>Mark I LaRosa</dc:creator>
		<pubDate>Wed, 24 Feb 2010 02:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-95</guid>
		<description>Brandon,&lt;br&gt;&lt;br&gt;You are right that at some point you need to show that the product is real.  The point of this post; however, is that it is very easy for a salesperson to run to the demo.  If you are in a sales meeting, then the meeting should be about sales not demos.  If they want to see it, schedule some separate time to provide a demo - preferably with a technical resource or sales engineer.&lt;br&gt;&lt;br&gt;If you are in a sales meeting, don&#039;t go for the easy demo unless you have taken all of the necessary time to understand the problem, the pain, and hear what the customer needs to say.&lt;br&gt;&lt;br&gt;My post is extreme on purpose to help get my point across.  Once you have exhausted all of the talking, and truly understand the problem and how and if your solution applies, then you can prove its real.</description>
		<content:encoded><![CDATA[<p>Brandon,</p>
<p>You are right that at some point you need to show that the product is real.  The point of this post; however, is that it is very easy for a salesperson to run to the demo.  If you are in a sales meeting, then the meeting should be about sales not demos.  If they want to see it, schedule some separate time to provide a demo &#8211; preferably with a technical resource or sales engineer.</p>
<p>If you are in a sales meeting, don&#39;t go for the easy demo unless you have taken all of the necessary time to understand the problem, the pain, and hear what the customer needs to say.</p>
<p>My post is extreme on purpose to help get my point across.  Once you have exhausted all of the talking, and truly understand the problem and how and if your solution applies, then you can prove its real.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark I LaRosa</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-216</link>
		<dc:creator>Mark I LaRosa</dc:creator>
		<pubDate>Wed, 24 Feb 2010 02:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-216</guid>
		<description>Brandon,&lt;br&gt;&lt;br&gt;You are right that at some point you need to show that the product is real.  The point of this post; however, is that it is very easy for a salesperson to run to the demo.  If you are in a sales meeting, then the meeting should be about sales not demos.  If they want to see it, schedule some separate time to provide a demo - preferably with a technical resource or sales engineer.&lt;br&gt;&lt;br&gt;If you are in a sales meeting, don&#039;t go for the easy demo unless you have taken all of the necessary time to understand the problem, the pain, and hear what the customer needs to say.&lt;br&gt;&lt;br&gt;My post is extreme on purpose to help get my point across.  Once you have exhausted all of the talking, and truly understand the problem and how and if your solution applies, then you can prove its real.</description>
		<content:encoded><![CDATA[<p>Brandon,</p>
<p>You are right that at some point you need to show that the product is real.  The point of this post; however, is that it is very easy for a salesperson to run to the demo.  If you are in a sales meeting, then the meeting should be about sales not demos.  If they want to see it, schedule some separate time to provide a demo &#8211; preferably with a technical resource or sales engineer.</p>
<p>If you are in a sales meeting, don&#39;t go for the easy demo unless you have taken all of the necessary time to understand the problem, the pain, and hear what the customer needs to say.</p>
<p>My post is extreme on purpose to help get my point across.  Once you have exhausted all of the talking, and truly understand the problem and how and if your solution applies, then you can prove its real.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-94</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Wed, 24 Feb 2010 01:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-94</guid>
		<description>Not sure I agree with this in every context.  When deploying a new service or technology (NEW, not a &quot;new &amp; improved&quot; or &quot;slightly modified&quot; version), you better be able to show a customer what they&#039;re getting unless you have the chops of the blog author to be able to sell something that a customer can&#039;t see.  This goes doubly, IMHO, for new companies that need to establish credibility with a prospect.  There&#039;s a fine line between salesmanship &amp; selling to the right person without HAVING to demo and being perceived as a purveyor of vapor.  Which mistake is the worse to make?  Having a demo boot up and then crap out (to which one can easily talk to Murphy&#039;s law) or not having anything to show the prospect other than vapor?  If you can sell vapor, I need you on MY team!!!!  &lt;br&gt;&lt;br&gt;And I agree on separating your firm from the competition, but how about focusing on the points that resonate with the customer?  This may be a differentiator vs others, but it could also be a point of value that nobody else has, restated in the customer&#039;s point of view.  In other words - separate YOUR product and YOUR firm from the competition the right way.  If you don&#039;t have to compare your firm to the competition, why invite the comparison and inevitable evaluation by the prospect after the call?  &lt;br&gt;&lt;br&gt;The above also all assumes that Engineering gives you a &quot;demo-ready&quot; unit in the first place - if this can&#039;t happen, there are other issues in the organization. &lt;br&gt;&lt;br&gt;$0.02&lt;br&gt;&lt;br&gt;/ ramblings&lt;br&gt;&lt;br&gt;Great post - definitely thought provoking.</description>
		<content:encoded><![CDATA[<p>Not sure I agree with this in every context.  When deploying a new service or technology (NEW, not a &#8220;new &#038; improved&#8221; or &#8220;slightly modified&#8221; version), you better be able to show a customer what they&#39;re getting unless you have the chops of the blog author to be able to sell something that a customer can&#39;t see.  This goes doubly, IMHO, for new companies that need to establish credibility with a prospect.  There&#39;s a fine line between salesmanship &#038; selling to the right person without HAVING to demo and being perceived as a purveyor of vapor.  Which mistake is the worse to make?  Having a demo boot up and then crap out (to which one can easily talk to Murphy&#39;s law) or not having anything to show the prospect other than vapor?  If you can sell vapor, I need you on MY team!!!!  </p>
<p>And I agree on separating your firm from the competition, but how about focusing on the points that resonate with the customer?  This may be a differentiator vs others, but it could also be a point of value that nobody else has, restated in the customer&#39;s point of view.  In other words &#8211; separate YOUR product and YOUR firm from the competition the right way.  If you don&#39;t have to compare your firm to the competition, why invite the comparison and inevitable evaluation by the prospect after the call?  </p>
<p>The above also all assumes that Engineering gives you a &#8220;demo-ready&#8221; unit in the first place &#8211; if this can&#39;t happen, there are other issues in the organization. </p>
<p>$0.02</p>
<p>/ ramblings</p>
<p>Great post &#8211; definitely thought provoking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-215</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Wed, 24 Feb 2010 01:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-215</guid>
		<description>Not sure I agree with this in every context.  When deploying a new service or technology (NEW, not a &quot;new &amp; improved&quot; or &quot;slightly modified&quot; version), you better be able to show a customer what they&#039;re getting unless you have the chops of the blog author to be able to sell something that a customer can&#039;t see.  This goes doubly, IMHO, for new companies that need to establish credibility with a prospect.  There&#039;s a fine line between salesmanship &amp; selling to the right person without HAVING to demo and being perceived as a purveyor of vapor.  Which mistake is the worse to make?  Having a demo boot up and then crap out (to which one can easily talk to Murphy&#039;s law) or not having anything to show the prospect other than vapor?  If you can sell vapor, I need you on MY team!!!!  &lt;br&gt;&lt;br&gt;And I agree on separating your firm from the competition, but how about focusing on the points that resonate with the customer?  This may be a differentiator vs others, but it could also be a point of value that nobody else has, restated in the customer&#039;s point of view.  In other words - separate YOUR product and YOUR firm from the competition the right way.  If you don&#039;t have to compare your firm to the competition, why invite the comparison and inevitable evaluation by the prospect after the call?  &lt;br&gt;&lt;br&gt;The above also all assumes that Engineering gives you a &quot;demo-ready&quot; unit in the first place - if this can&#039;t happen, there are other issues in the organization. &lt;br&gt;&lt;br&gt;$0.02&lt;br&gt;&lt;br&gt;/ ramblings&lt;br&gt;&lt;br&gt;Great post - definitely thought provoking.</description>
		<content:encoded><![CDATA[<p>Not sure I agree with this in every context.  When deploying a new service or technology (NEW, not a &#8220;new &#038; improved&#8221; or &#8220;slightly modified&#8221; version), you better be able to show a customer what they&#39;re getting unless you have the chops of the blog author to be able to sell something that a customer can&#39;t see.  This goes doubly, IMHO, for new companies that need to establish credibility with a prospect.  There&#39;s a fine line between salesmanship &#038; selling to the right person without HAVING to demo and being perceived as a purveyor of vapor.  Which mistake is the worse to make?  Having a demo boot up and then crap out (to which one can easily talk to Murphy&#39;s law) or not having anything to show the prospect other than vapor?  If you can sell vapor, I need you on MY team!!!!  </p>
<p>And I agree on separating your firm from the competition, but how about focusing on the points that resonate with the customer?  This may be a differentiator vs others, but it could also be a point of value that nobody else has, restated in the customer&#39;s point of view.  In other words &#8211; separate YOUR product and YOUR firm from the competition the right way.  If you don&#39;t have to compare your firm to the competition, why invite the comparison and inevitable evaluation by the prospect after the call?  </p>
<p>The above also all assumes that Engineering gives you a &#8220;demo-ready&#8221; unit in the first place &#8211; if this can&#39;t happen, there are other issues in the organization. </p>
<p>$0.02</p>
<p>/ ramblings</p>
<p>Great post &#8211; definitely thought provoking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tyler frieling</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-93</link>
		<dc:creator>tyler frieling</dc:creator>
		<pubDate>Fri, 20 Feb 2009 19:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-93</guid>
		<description>interesting.  I am just learning about sales process and strategies and this really magnifies some of my faulty logic.  I really need to stop jumping straight into a demo or providing a trial.&lt;br&gt;&lt;br&gt;Your experience confirms my ideas that our demos occurred too early in the sales process, before the customer really trusted us and before we really knew what the customer needed.   To me it is becoming more important to listen, listen, validate and then address the specific stress points and build the relationship before advocating any solution.   If only I read this years ago.</description>
		<content:encoded><![CDATA[<p>interesting.  I am just learning about sales process and strategies and this really magnifies some of my faulty logic.  I really need to stop jumping straight into a demo or providing a trial.</p>
<p>Your experience confirms my ideas that our demos occurred too early in the sales process, before the customer really trusted us and before we really knew what the customer needed.   To me it is becoming more important to listen, listen, validate and then address the specific stress points and build the relationship before advocating any solution.   If only I read this years ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tyler frieling</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-218</link>
		<dc:creator>tyler frieling</dc:creator>
		<pubDate>Fri, 20 Feb 2009 19:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-218</guid>
		<description>interesting.  I am just learning about sales process and strategies and this really magnifies some of my faulty logic.  I really need to stop jumping straight into a demo or providing a trial.&lt;br&gt;&lt;br&gt;Your experience confirms my ideas that our demos occurred too early in the sales process, before the customer really trusted us and before we really knew what the customer needed.   To me it is becoming more important to listen, listen, validate and then address the specific stress points and build the relationship before advocating any solution.   If only I read this years ago.</description>
		<content:encoded><![CDATA[<p>interesting.  I am just learning about sales process and strategies and this really magnifies some of my faulty logic.  I really need to stop jumping straight into a demo or providing a trial.</p>
<p>Your experience confirms my ideas that our demos occurred too early in the sales process, before the customer really trusted us and before we really knew what the customer needed.   To me it is becoming more important to listen, listen, validate and then address the specific stress points and build the relationship before advocating any solution.   If only I read this years ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tyler frieling</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-92</link>
		<dc:creator>tyler frieling</dc:creator>
		<pubDate>Fri, 20 Feb 2009 14:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-92</guid>
		<description>interesting.  I am just learning about sales process and strategies and this really magnifies some of my faulty logic.  I really need to stop jumping straight into a demo or providing a trial.&lt;br&gt;&lt;br&gt;Your experience confirms my ideas that our demos occurred too early in the sales process, before the customer really trusted us and before we really knew what the customer needed.   To me it is becoming more important to listen, listen, validate and then address the specific stress points and build the relationship before advocating any solution.   If only I read this years ago.</description>
		<content:encoded><![CDATA[<p>interesting.  I am just learning about sales process and strategies and this really magnifies some of my faulty logic.  I really need to stop jumping straight into a demo or providing a trial.</p>
<p>Your experience confirms my ideas that our demos occurred too early in the sales process, before the customer really trusted us and before we really knew what the customer needed.   To me it is becoming more important to listen, listen, validate and then address the specific stress points and build the relationship before advocating any solution.   If only I read this years ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark I LaRosa</title>
		<link>http://quotacrush.com/2008/12/01/sales-presentations-no-demosever/comment-page-1/#comment-219</link>
		<dc:creator>Mark I LaRosa</dc:creator>
		<pubDate>Thu, 18 Dec 2008 22:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.quotacrush.com/?p=164#comment-219</guid>
		<description>OH so exactly true!  When you have sales management that doesn&#039;t get the sales process, you can see them using metrics like this to judge activity.&lt;br&gt;&lt;br&gt;But... its not about activity - its about results.&lt;br&gt;&lt;br&gt;If I have a salesperson that comes to the office early, does 22 demos a day, meets with 1,000 companies in a year - and hits 10% of quota, he will probably not have a job the next year.&lt;br&gt;If I have a salesperson who takes an extra 4 weeks of vacation, but has happy customers and hits 200% of quota, he will be retained.&lt;br&gt;&lt;br&gt;Proper sales management is key.</description>
		<content:encoded><![CDATA[<p>OH so exactly true!  When you have sales management that doesn&#39;t get the sales process, you can see them using metrics like this to judge activity.</p>
<p>But&#8230; its not about activity &#8211; its about results.</p>
<p>If I have a salesperson that comes to the office early, does 22 demos a day, meets with 1,000 companies in a year &#8211; and hits 10% of quota, he will probably not have a job the next year.<br />If I have a salesperson who takes an extra 4 weeks of vacation, but has happy customers and hits 200% of quota, he will be retained.</p>
<p>Proper sales management is key.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

