<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Allyforce: the power of partnership &#187; How do you Select Allies</title>
	<atom:link href="http://blog.allyforce.com/wp/category/how-do-you-select-allies/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.allyforce.com/wp</link>
	<description>Creating revenue-generating partnerships that work</description>
	<lastBuildDate>Sun, 14 Mar 2010 16:12:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Product Partnerships are not Sales Partnerships</title>
		<link>http://blog.allyforce.com/wp/2009/06/01/product-partnerships-are-not-sales-partnerships/</link>
		<comments>http://blog.allyforce.com/wp/2009/06/01/product-partnerships-are-not-sales-partnerships/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 15:55:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[How do you Select Allies]]></category>
		<category><![CDATA[How to you Implement]]></category>

		<guid isPermaLink="false">http://blog.allyforce.com/wp/2009/06/01/product-partnerships-are-not-sales-partnerships/</guid>
		<description><![CDATA[I had a meeting with a VP of Sales discussing potential partners.
One partner they had been looking at as promising, but he said that the partner&#8217;s technology that would complement theirs wouldn&#8217;t be ready yet.
So he said they wouldn&#8217;t be a good fit.
This is a very common approach to partnership: they look at partners from [...]]]></description>
			<content:encoded><![CDATA[<p>I had a meeting with a VP of Sales discussing potential partners.</p>
<p>One partner they had been looking at as promising, but he said that the partner&#8217;s technology that would complement theirs wouldn&#8217;t be ready yet.</p>
<p>So he said they wouldn&#8217;t be a good fit.</p>
<p>This is a very common approach to partnership: they look at partners from a product-fit / product-enhancement perspective.  That&#8217;s because, typically, they are done that way.</p>
<p>However, I then asked:</p>
<p>&quot;So do the sales reps of this partner call on the same kind of companies yours do?&quot;</p>
<p>&quot;Yes.&quot;</p>
<p>&quot;What&#8217;s your primary vertical?&quot;</p>
<p>&quot;Marketing-driven entertainment and gaming industries.&quot;</p>
<p>&quot;And they call on those as well?&quot;</p>
<p>&quot;Yes.&quot;</p>
<p>&quot;Do they call on the same titles within those companies?&quot;</p>
<p>&quot;Yes.  Ah, so they&#8217;ll just be giving each other names.  It might not be a hot-lead.&quot;</p>
<p>&quot;True.  But do your reps ask pertinent questions such as &quot;Do they have budget?  What are they trying to accomplish now if they&#8217;re aren&#8217;t ready for the product you&#8217;re offering?&quot;  Would the answers to those questions, if they were asked by your partner, but useful for your reps?&quot;</p>
<p>&quot;I get it.  They are a good partner!&quot;</p>
<p>There are other ways to discover good partner fits as we&#8217;ve looked at it other posts and will continue to revisit.  The mindset should always be &#8212; whom can I exchange contacts, context, and connection with out in the field, sales rep to sales rep.  Don&#8217;t think product compliment!</p>
<p style="color:#008;text-align:right;"><small><em>Powered by</em> <a href="http://www.qumana.com/">Qumana</a></small></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.allyforce.com/wp/2009/06/01/product-partnerships-are-not-sales-partnerships/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
