<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The Road Ahead for Sage</title>
	<atom:link href="http://summitdiary.com/2012/07/29/the-road-ahead-for-sage/feed/" rel="self" type="application/rss+xml" />
	<link>http://summitdiary.com/2012/07/29/the-road-ahead-for-sage/</link>
	<description>Your #1 Source for Sage Information, Technology Tips, and Random Odd Stuff</description>
	<lastBuildDate>Sun, 10 Feb 2013 21:12:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Saying goodbye to Tom Miller – or – what do you do when Superman retires? by Peter Wolf on February 6, 2013 &#124; Bill&#039;s Views From Sunny San Diego</title>
		<link>http://summitdiary.com/2012/07/29/the-road-ahead-for-sage/#comment-1484</link>
		<dc:creator><![CDATA[Saying goodbye to Tom Miller – or – what do you do when Superman retires? by Peter Wolf on February 6, 2013 &#124; Bill&#039;s Views From Sunny San Diego]]></dc:creator>
		<pubDate>Sun, 10 Feb 2013 21:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://summitdiary.com/?p=1793#comment-1484</guid>
		<description><![CDATA[[...] channel advocate, he has overseen a very difficult transition as Sage has made controversial (some would say necessary) moves to a more aggressive and more self-deterministic future that has changed the Sage channel [...]]]></description>
		<content:encoded><![CDATA[<p>[...] channel advocate, he has overseen a very difficult transition as Sage has made controversial (some would say necessary) moves to a more aggressive and more self-deterministic future that has changed the Sage channel [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saying goodbye to Tom Miller &#8211; or &#8211; what do you do when Superman retires? &#124; Summit Diary</title>
		<link>http://summitdiary.com/2012/07/29/the-road-ahead-for-sage/#comment-1474</link>
		<dc:creator><![CDATA[Saying goodbye to Tom Miller &#8211; or &#8211; what do you do when Superman retires? &#124; Summit Diary]]></dc:creator>
		<pubDate>Wed, 06 Feb 2013 14:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://summitdiary.com/?p=1793#comment-1474</guid>
		<description><![CDATA[[...] channel advocate, he has overseen a very difficult transition as Sage has made controversial (some would say necessary) moves to a more aggressive and more self-deterministic future that has changed the Sage channel [...]]]></description>
		<content:encoded><![CDATA[<p>[...] channel advocate, he has overseen a very difficult transition as Sage has made controversial (some would say necessary) moves to a more aggressive and more self-deterministic future that has changed the Sage channel [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On pissing in the punchbowl and NetSuite &#124; Summit Diary</title>
		<link>http://summitdiary.com/2012/07/29/the-road-ahead-for-sage/#comment-1249</link>
		<dc:creator><![CDATA[On pissing in the punchbowl and NetSuite &#124; Summit Diary]]></dc:creator>
		<pubDate>Thu, 02 Aug 2012 01:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://summitdiary.com/?p=1793#comment-1249</guid>
		<description><![CDATA[[...] suppose the management at NetSuite has seen some of the changes at Sage and in the Sage channel and felt that this is a great opportunity for them to pick up some [...]]]></description>
		<content:encoded><![CDATA[<p>[...] suppose the management at NetSuite has seen some of the changes at Sage and in the Sage channel and felt that this is a great opportunity for them to pick up some [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne Schulz</title>
		<link>http://summitdiary.com/2012/07/29/the-road-ahead-for-sage/#comment-1245</link>
		<dc:creator><![CDATA[Wayne Schulz]]></dc:creator>
		<pubDate>Mon, 30 Jul 2012 12:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://summitdiary.com/?p=1793#comment-1245</guid>
		<description><![CDATA[Peter I think you are missing a few details of how Sage has attempted to cross-sell in the past. 

Cross selling is most definitely not a brand new &quot;holy crap look at the opportunity to cross sell&quot; moment for Sage.

Rather I would submit it&#039;s been introduced several times before in the mid-market space.

Back in the Y2k&#039;ish era there was a strong push to cross sell upgrades from MAS90 to MAS500.

Similarly several years back (in 2008)  Sage announced Project Diamond ( http://www.s-consult.com/2008/05/14/sage-extended-enterprise-for-sage-mas-90-and-200-pricing-announced/ )   --- which became Sage Extended Enterprise Suite and bundled in FAS (Fixed Assets) and CRM at not additional cost in a pretty price competitive bundle. I believe this was canned in version 4.4 of Sage ERP MAS 90 aka Sage 100 ERP.

http://www.s-consult.com/wp-content/uploads/2008/10/extended-enterprise-suite-customer-faq-10-23-08.pdf



Rather the issue here is not the cross sell. That&#039;s been done. It&#039;s the customer benefit of the cross sell which will be defined in several ways:

a. How&#039;s the integration - does it require an army to setup? 

b. What&#039;s the expected benefit - easy to determine ROI or do you need to use bogus worksheets like the SaaS folks do which assume you fire every tech person and no longer maintain a server.

c. How is the support and upgrade process?


I think Sage is focussing on the areas that have worked well in cross sell - specifically payments and hopefully they are going to learn that good quality integration that provides ROI and does not require an army to install and upgrade is the path they should follow.]]></description>
		<content:encoded><![CDATA[<p>Peter I think you are missing a few details of how Sage has attempted to cross-sell in the past. </p>
<p>Cross selling is most definitely not a brand new &#8220;holy crap look at the opportunity to cross sell&#8221; moment for Sage.</p>
<p>Rather I would submit it&#8217;s been introduced several times before in the mid-market space.</p>
<p>Back in the Y2k&#8217;ish era there was a strong push to cross sell upgrades from MAS90 to MAS500.</p>
<p>Similarly several years back (in 2008)  Sage announced Project Diamond ( <a href="http://www.s-consult.com/2008/05/14/sage-extended-enterprise-for-sage-mas-90-and-200-pricing-announced/" rel="nofollow">http://www.s-consult.com/2008/05/14/sage-extended-enterprise-for-sage-mas-90-and-200-pricing-announced/</a> )   &#8212; which became Sage Extended Enterprise Suite and bundled in FAS (Fixed Assets) and CRM at not additional cost in a pretty price competitive bundle. I believe this was canned in version 4.4 of Sage ERP MAS 90 aka Sage 100 ERP.</p>
<p><a href="http://www.s-consult.com/wp-content/uploads/2008/10/extended-enterprise-suite-customer-faq-10-23-08.pdf" rel="nofollow">http://www.s-consult.com/wp-content/uploads/2008/10/extended-enterprise-suite-customer-faq-10-23-08.pdf</a></p>
<p>Rather the issue here is not the cross sell. That&#8217;s been done. It&#8217;s the customer benefit of the cross sell which will be defined in several ways:</p>
<p>a. How&#8217;s the integration &#8211; does it require an army to setup? </p>
<p>b. What&#8217;s the expected benefit &#8211; easy to determine ROI or do you need to use bogus worksheets like the SaaS folks do which assume you fire every tech person and no longer maintain a server.</p>
<p>c. How is the support and upgrade process?</p>
<p>I think Sage is focussing on the areas that have worked well in cross sell &#8211; specifically payments and hopefully they are going to learn that good quality integration that provides ROI and does not require an army to install and upgrade is the path they should follow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
