<?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: Telcos and SaaS, a happy fit&#8230;</title>
	<atom:link href="http://www.diversity.net.nz/telcos-and-saas-a-happy-fit/2008/05/05/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.diversity.net.nz/telcos-and-saas-a-happy-fit/2008/05/05/</link>
	<description>Commentary and Analysis for User-Centered Technology</description>
	<lastBuildDate>Fri, 10 Feb 2012 03:02:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Another telco creates a SaaS aggregation platform at diversity.net.nz</title>
		<link>http://www.diversity.net.nz/telcos-and-saas-a-happy-fit/2008/05/05/comment-page-1/#comment-4732</link>
		<dc:creator>Another telco creates a SaaS aggregation platform at diversity.net.nz</dc:creator>
		<pubDate>Tue, 24 Jun 2008 19:16:10 +0000</pubDate>
		<guid isPermaLink="false">http://diversity.net.nz/?p=1042#comment-4732</guid>
		<description>[...] to see that, fresh after the British Telecom move into creating a SaaS aggregation platform, Telstra has done similarly for Australia. The idea is [...]</description>
		<content:encoded><![CDATA[<p>[...] to see that, fresh after the British Telecom move into creating a SaaS aggregation platform, Telstra has done similarly for Australia. The idea is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Kepes</title>
		<link>http://www.diversity.net.nz/telcos-and-saas-a-happy-fit/2008/05/05/comment-page-1/#comment-3787</link>
		<dc:creator>Ben Kepes</dc:creator>
		<pubDate>Sun, 04 May 2008 22:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://diversity.net.nz/?p=1042#comment-3787</guid>
		<description>There are some shared benefits to a Telco/SaaS partnership
1) For SaaS companies they get brand, marketing spend and access to  potential customers
2) For telco&#039;s in this environment of huge threats to their business viability they get some protection of core revenue plus some benefits around the power of the network and community effects</description>
		<content:encoded><![CDATA[<p>There are some shared benefits to a Telco/SaaS partnership<br />
1) For SaaS companies they get brand, marketing spend and access to  potential customers<br />
2) For telco&#8217;s in this environment of huge threats to their business viability they get some protection of core revenue plus some benefits around the power of the network and community effects</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Telcos and SaaS - Interesting Article &#124; julian101.com - ProWorkflow - Project Management Software CEO's Blog</title>
		<link>http://www.diversity.net.nz/telcos-and-saas-a-happy-fit/2008/05/05/comment-page-1/#comment-3786</link>
		<dc:creator>Telcos and SaaS - Interesting Article &#124; julian101.com - ProWorkflow - Project Management Software CEO's Blog</dc:creator>
		<pubDate>Sun, 04 May 2008 22:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://diversity.net.nz/?p=1042#comment-3786</guid>
		<description>[...] just read an interesting article over at http://diversity.net.nz/ about Telcos and SaaS business that caught my attention. It&#8217;s an area of interest globally [...]</description>
		<content:encoded><![CDATA[<p>[...] just read an interesting article over at <a href="http://diversity.net.nz/" rel="nofollow">http://diversity.net.nz/</a> about Telcos and SaaS business that caught my attention. It&#8217;s an area of interest globally [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian Stone</title>
		<link>http://www.diversity.net.nz/telcos-and-saas-a-happy-fit/2008/05/05/comment-page-1/#comment-3785</link>
		<dc:creator>Julian Stone</dc:creator>
		<pubDate>Sun, 04 May 2008 22:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://diversity.net.nz/?p=1042#comment-3785</guid>
		<description>I&#039;ll be interesting to see how the Telcos approach the SaaS model. Contrary to popular belief, SaaS is hard work and many players don&#039;t have large margins - especially early stage SaaS players as they&#039;re spending heavy in Marketing/Dev to get established. Even SalesForce is still working on improving margins...

So how can a Telco partner with a tight margined SaaS player? It&#039;ll be interesting to watch these Telco/SaaS M&amp;A&amp;P&#039;s over time.

Google/Salesforce is a good example of two different models coming together (Sales model vs Free model) - but would a similar deal be struck with a telco?

Unsure... They could be a technology partner sure, but could they be a software partner? if sales or support (or custom dev) were moved from the SaaS business to the Telco, would the service to customers be lessened? I don&#039;t know if the Telco would have the same product knowledge/passion/experience to deliver equivalent service to a SaaS&#039;s current service?

I mean, you can&#039;t have a Telco support or sales worker working on Internet plans, or dialup packages, then switching to CRM product support...

The Telco would need a specialist team for a &#039;service&#039; partnership to be feasible. and then if they have a specialist team, what becomes of the SaaS company&#039;s role? Does it revert to a simple R&amp;D focus? If so, then there&#039;s an issue that R&amp;D &amp; dev teams are removed from customer frontend, so the product development angle suffers...

Telco and SaaS business in partnership. Whilst I like the idea of marketing a solution down the Telco&#039;s channel, there are some questions:

1. What&#039;s in it for the Telco (Because the revenue won&#039;t cover the cost for them)
2. What&#039;s in it for the SaaS (Because service and Product dev may suffer)

Just my thoughts. I&#039;m open to ideas on this.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll be interesting to see how the Telcos approach the SaaS model. Contrary to popular belief, SaaS is hard work and many players don&#8217;t have large margins &#8211; especially early stage SaaS players as they&#8217;re spending heavy in Marketing/Dev to get established. Even SalesForce is still working on improving margins&#8230;</p>
<p>So how can a Telco partner with a tight margined SaaS player? It&#8217;ll be interesting to watch these Telco/SaaS M&amp;A&amp;P&#8217;s over time.</p>
<p>Google/Salesforce is a good example of two different models coming together (Sales model vs Free model) &#8211; but would a similar deal be struck with a telco?</p>
<p>Unsure&#8230; They could be a technology partner sure, but could they be a software partner? if sales or support (or custom dev) were moved from the SaaS business to the Telco, would the service to customers be lessened? I don&#8217;t know if the Telco would have the same product knowledge/passion/experience to deliver equivalent service to a SaaS&#8217;s current service?</p>
<p>I mean, you can&#8217;t have a Telco support or sales worker working on Internet plans, or dialup packages, then switching to CRM product support&#8230;</p>
<p>The Telco would need a specialist team for a &#8216;service&#8217; partnership to be feasible. and then if they have a specialist team, what becomes of the SaaS company&#8217;s role? Does it revert to a simple R&amp;D focus? If so, then there&#8217;s an issue that R&amp;D &amp; dev teams are removed from customer frontend, so the product development angle suffers&#8230;</p>
<p>Telco and SaaS business in partnership. Whilst I like the idea of marketing a solution down the Telco&#8217;s channel, there are some questions:</p>
<p>1. What&#8217;s in it for the Telco (Because the revenue won&#8217;t cover the cost for them)<br />
2. What&#8217;s in it for the SaaS (Because service and Product dev may suffer)</p>
<p>Just my thoughts. I&#8217;m open to ideas on this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

