<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: What if your reseller went away?</title>
	<atom:link href="http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 10:01:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kent Henderson</title>
		<link>http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/comment-page-1/#comment-7732</link>
		<dc:creator>Kent Henderson</dc:creator>
		<pubDate>Fri, 05 Feb 2010 20:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=6350#comment-7732</guid>
		<description>Great topic and just to type of blog I was intending to find when I set up a feed to pull &quot;SaaS &amp; Channel.&quot;  At Cisco (specifically Cisco WebEx), we also see XaaS as a departure from your father&#039;s channel model, but primarily different only for the HW and SW integrators at whom we&#039;re looking to get our offering most effectively broadcast to the market.  These partners are used to seeing sku&#039;s on pricelists and the self-sufficiencies that come with buy-for-9-sell-for-10-add-ProfServ model.&lt;br&gt;&lt;br&gt;XaaS agreements are generally 12-month contracts--several pages each-- with nits and gnats all needing negotiation.  Not so easy on the uptake for partners who have so many other things to worry about outside of our offerings.  SXaaS also require billing systems supportive of monthly recurring revenue, overages, upsells, etc.  These systems generally don&#039;t exist.  And adoption services?  Even more requirements that the channel isn&#039;t quite ready to meet.&lt;br&gt;&lt;br&gt;SaaS providers are service providers, so we&#039;ve chosen to take a page from the SP/Telco channel program playbook.  Most commonly, this model sees orders written on SP paper, with a commission being paid to the partner.  We feel that as long as there are significant requirements for professional services, that the Integrators will cross the chasm to embrace a commission-based model, and hence bring SaaS into their bucket of competencies.</description>
		<content:encoded><![CDATA[<p>Great topic and just to type of blog I was intending to find when I set up a feed to pull &#8220;SaaS &#038; Channel.&#8221;  At Cisco (specifically Cisco WebEx), we also see XaaS as a departure from your father&#39;s channel model, but primarily different only for the HW and SW integrators at whom we&#39;re looking to get our offering most effectively broadcast to the market.  These partners are used to seeing sku&#39;s on pricelists and the self-sufficiencies that come with buy-for-9-sell-for-10-add-ProfServ model.</p>
<p>XaaS agreements are generally 12-month contracts&#8211;several pages each&#8211; with nits and gnats all needing negotiation.  Not so easy on the uptake for partners who have so many other things to worry about outside of our offerings.  SXaaS also require billing systems supportive of monthly recurring revenue, overages, upsells, etc.  These systems generally don&#39;t exist.  And adoption services?  Even more requirements that the channel isn&#39;t quite ready to meet.</p>
<p>SaaS providers are service providers, so we&#39;ve chosen to take a page from the SP/Telco channel program playbook.  Most commonly, this model sees orders written on SP paper, with a commission being paid to the partner.  We feel that as long as there are significant requirements for professional services, that the Integrators will cross the chasm to embrace a commission-based model, and hence bring SaaS into their bucket of competencies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Henderson</title>
		<link>http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/comment-page-1/#comment-7731</link>
		<dc:creator>Kent Henderson</dc:creator>
		<pubDate>Fri, 05 Feb 2010 15:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=6350#comment-7731</guid>
		<description>Great topic and just to type of blog I was intending to find when I set up a feed to pull &quot;SaaS &amp; Channel.&quot;  At Cisco (specifically Cisco WebEx), we also see XaaS as a departure from your father&#039;s channel model, but primarily different only for the HW and SW integrators at whom we&#039;re looking to get our offering most effectively broadcast to the market.  These partners are used to seeing sku&#039;s on pricelists and the self-sufficiencies that come with buy-for-9-sell-for-10-add-ProfServ model.XaaS agreements are generally 12-month contracts--several pages each-- with nits and gnats all needing negotiation.  Not so easy on the uptake for partners who have so many other things to worry about outside of our offerings.  SXaaS also require billing systems supportive of monthly recurring revenue, overages, upsells, etc.  These systems generally don&#039;t exist.  And adoption services?  Even more requirements that the channel isn&#039;t quite ready to meet.SaaS providers are service providers, so we&#039;ve chosen to take a page from the SP/Telco channel program playbook.  Most commonly, this model sees orders written on SP paper, with a commission being paid to the partner.  We feel that as long as there are significant requirements for professional services, that the Integrators will cross the chasm to embrace a commission-based model, and hence bring SaaS into their bucket of competencies.</description>
		<content:encoded><![CDATA[<p>Great topic and just to type of blog I was intending to find when I set up a feed to pull &quot;SaaS &amp; Channel.&quot;  At Cisco (specifically Cisco WebEx), we also see XaaS as a departure from your father&#039;s channel model, but primarily different only for the HW and SW integrators at whom we&#039;re looking to get our offering most effectively broadcast to the market.  These partners are used to seeing sku&#039;s on pricelists and the self-sufficiencies that come with buy-for-9-sell-for-10-add-ProfServ model.XaaS agreements are generally 12-month contracts&#8211;several pages each&#8211; with nits and gnats all needing negotiation.  Not so easy on the uptake for partners who have so many other things to worry about outside of our offerings.  SXaaS also require billing systems supportive of monthly recurring revenue, overages, upsells, etc.  These systems generally don&#039;t exist.  And adoption services?  Even more requirements that the channel isn&#039;t quite ready to meet.SaaS providers are service providers, so we&#039;ve chosen to take a page from the SP/Telco channel program playbook.  Most commonly, this model sees orders written on SP paper, with a commission being paid to the partner.  We feel that as long as there are significant requirements for professional services, that the Integrators will cross the chasm to embrace a commission-based model, and hence bring SaaS into their bucket of competencies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Henderson</title>
		<link>http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/comment-page-1/#comment-9731</link>
		<dc:creator>Kent Henderson</dc:creator>
		<pubDate>Fri, 05 Feb 2010 15:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=6350#comment-9731</guid>
		<description>Great topic and just to type of blog I was intending to find when I set up a feed to pull &quot;SaaS &amp; Channel.&quot;  At Cisco (specifically Cisco WebEx), we also see XaaS as a departure from your father&#039;s channel model, but primarily different only for the HW and SW integrators at whom we&#039;re looking to get our offering most effectively broadcast to the market.  These partners are used to seeing sku&#039;s on pricelists and the self-sufficiencies that come with buy-for-9-sell-for-10-add-ProfServ model.

XaaS agreements are generally 12-month contracts--several pages each-- with nits and gnats all needing negotiation.  Not so easy on the uptake for partners who have so many other things to worry about outside of our offerings.  SXaaS also require billing systems supportive of monthly recurring revenue, overages, upsells, etc.  These systems generally don&#039;t exist.  And adoption services?  Even more requirements that the channel isn&#039;t quite ready to meet.

SaaS providers are service providers, so we&#039;ve chosen to take a page from the SP/Telco channel program playbook.  Most commonly, this model sees orders written on SP paper, with a commission being paid to the partner.  We feel that as long as there are significant requirements for professional services, that the Integrators will cross the chasm to embrace a commission-based model, and hence bring SaaS into their bucket of competencies.
</description>
		<content:encoded><![CDATA[<p>Great topic and just to type of blog I was intending to find when I set up a feed to pull &#8220;SaaS &amp; Channel.&#8221;  At Cisco (specifically Cisco WebEx), we also see XaaS as a departure from your father&#8217;s channel model, but primarily different only for the HW and SW integrators at whom we&#8217;re looking to get our offering most effectively broadcast to the market.  These partners are used to seeing sku&#8217;s on pricelists and the self-sufficiencies that come with buy-for-9-sell-for-10-add-ProfServ model.</p>
<p>XaaS agreements are generally 12-month contracts&#8211;several pages each&#8211; with nits and gnats all needing negotiation.  Not so easy on the uptake for partners who have so many other things to worry about outside of our offerings.  SXaaS also require billing systems supportive of monthly recurring revenue, overages, upsells, etc.  These systems generally don&#8217;t exist.  And adoption services?  Even more requirements that the channel isn&#8217;t quite ready to meet.</p>
<p>SaaS providers are service providers, so we&#8217;ve chosen to take a page from the SP/Telco channel program playbook.  Most commonly, this model sees orders written on SP paper, with a commission being paid to the partner.  We feel that as long as there are significant requirements for professional services, that the Integrators will cross the chasm to embrace a commission-based model, and hence bring SaaS into their bucket of competencies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff D.</title>
		<link>http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/comment-page-1/#comment-7733</link>
		<dc:creator>Geoff D.</dc:creator>
		<pubDate>Fri, 05 Feb 2010 09:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=6350#comment-7733</guid>
		<description>great post!</description>
		<content:encoded><![CDATA[<p>great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff D.</title>
		<link>http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/comment-page-1/#comment-7730</link>
		<dc:creator>Geoff D.</dc:creator>
		<pubDate>Fri, 05 Feb 2010 04:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=6350#comment-7730</guid>
		<description>great post!</description>
		<content:encoded><![CDATA[<p>great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff D.</title>
		<link>http://www.accmanpro.com/2010/02/04/what-if-your-reseller-went-away/comment-page-1/#comment-9729</link>
		<dc:creator>Geoff D.</dc:creator>
		<pubDate>Fri, 05 Feb 2010 04:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=6350#comment-9729</guid>
		<description>great post!</description>
		<content:encoded><![CDATA[<p>great post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

