<?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:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Engaged, Broadsoft? Or just shacked up.</title>
	<atom:link href="http://www.saunderslog.com/2008/04/25/engaged-broadsoft-or-just-shacked-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.saunderslog.com/2008/04/25/engaged-broadsoft-or-just-shacked-up/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=engaged-broadsoft-or-just-shacked-up</link>
	<description>An outcome-driven leader, proven technology product developer, and  marketer with over 20 years of hands-on experience including start-up, small and large business environments, and the board room. This is my blog.</description>
	<lastBuildDate>Thu, 26 Jan 2012 17:15:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: The Big Cheese</title>
		<link>http://www.saunderslog.com/2008/04/25/engaged-broadsoft-or-just-shacked-up/#comment-6712</link>
		<dc:creator>The Big Cheese</dc:creator>
		<pubDate>Sun, 27 Apr 2008 04:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/?p=3992#comment-6712</guid>
		<description>SimpleSignal is a Broadsoft service provider that I founded in 2004 and am leading into web 2.0 today. We are a &quot;real life&quot; example of what Omar was talking about with regard to &quot;non-carriers&quot; using web 2.0 apps to differentiate. For example, we suggested to Braodsoft there was a need for an app that would allow salesforce.com users to be integrated into our switch. Their developers responded quickly and we have been selling this added functionality to salesforce users for the last 6 months.

We&#039;ve capitalized on our ability to be nimble and fast to market with new functionality.  This gives us a distinct advantage over the carriers that can only &quot;move their ship only 10 or 20 degrees&quot; Thank God for the &quot;jetskiers&quot; that are hard at work creating new and innovative ways to use the phone. The Broadsoft facebook connector can connect vast markets to our company. However, new and really cool apps like I saw at web 2.0 in SF last week are still being created everyday without a telephony component. That oversight must be corrected soon. We can bring a market to a developer, help them monetize it and put it into the market in a very short time.

Web 2.0 needs a voice. SimpleSignal intends to give it one.</description>
		<content:encoded><![CDATA[<p>SimpleSignal is a Broadsoft service provider that I founded in 2004 and am leading into web 2.0 today. We are a &#8220;real life&#8221; example of what Omar was talking about with regard to &#8220;non-carriers&#8221; using web 2.0 apps to differentiate. For example, we suggested to Braodsoft there was a need for an app that would allow salesforce.com users to be integrated into our switch. Their developers responded quickly and we have been selling this added functionality to salesforce users for the last 6 months.</p>
<p>We&#8217;ve capitalized on our ability to be nimble and fast to market with new functionality.  This gives us a distinct advantage over the carriers that can only &#8220;move their ship only 10 or 20 degrees&#8221; Thank God for the &#8220;jetskiers&#8221; that are hard at work creating new and innovative ways to use the phone. The Broadsoft facebook connector can connect vast markets to our company. However, new and really cool apps like I saw at web 2.0 in SF last week are still being created everyday without a telephony component. That oversight must be corrected soon. We can bring a market to a developer, help them monetize it and put it into the market in a very short time.</p>
<p>Web 2.0 needs a voice. SimpleSignal intends to give it one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JoeDeveloper</title>
		<link>http://www.saunderslog.com/2008/04/25/engaged-broadsoft-or-just-shacked-up/#comment-6711</link>
		<dc:creator>JoeDeveloper</dc:creator>
		<pubDate>Sat, 26 Apr 2008 20:10:35 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/?p=3992#comment-6711</guid>
		<description>Hi Alec,

    I got into the VoIP development space about 4 years ago while working for a carrier. After leaving the carrier awhile back I started developing applications against the knowledge that I had learned.

You&#039;re right, it&#039;s not easy to monetize apps or to get carriers on board with your ideas. From my point of view I&#039;m not as much interested in actually getting carriers on board with the mashup(s), because unless it really boosts their core business (and revenue) they won&#039;t touch it.

However, carriers have a lot of customers that are very much into the web 2.0 space and are friendly to these kind of things. This I think is the area to reach out to.

By leveraging the carrier network and it&#039;s features (specifically broadsoft in this respect), you can then deliver (as they call it) &quot;Carrier Grade&quot; applications to the web 2.0 space. Is it easy to monetize social apps? Simply put, no not really. Is it possible? yes.

Additionally, understanding a carriers&#039; problems in relation to their customers needs will provide you with a honeypot of solutions that will sell.

Just my .02 as another developer in this space.

-JoeDeveloper</description>
		<content:encoded><![CDATA[<p>Hi Alec,</p>
<p>    I got into the VoIP development space about 4 years ago while working for a carrier. After leaving the carrier awhile back I started developing applications against the knowledge that I had learned.</p>
<p>You&#8217;re right, it&#8217;s not easy to monetize apps or to get carriers on board with your ideas. From my point of view I&#8217;m not as much interested in actually getting carriers on board with the mashup(s), because unless it really boosts their core business (and revenue) they won&#8217;t touch it.</p>
<p>However, carriers have a lot of customers that are very much into the web 2.0 space and are friendly to these kind of things. This I think is the area to reach out to.</p>
<p>By leveraging the carrier network and it&#8217;s features (specifically broadsoft in this respect), you can then deliver (as they call it) &#8220;Carrier Grade&#8221; applications to the web 2.0 space. Is it easy to monetize social apps? Simply put, no not really. Is it possible? yes.</p>
<p>Additionally, understanding a carriers&#8217; problems in relation to their customers needs will provide you with a honeypot of solutions that will sell.</p>
<p>Just my .02 as another developer in this space.</p>
<p>-JoeDeveloper</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alec</title>
		<link>http://www.saunderslog.com/2008/04/25/engaged-broadsoft-or-just-shacked-up/#comment-6710</link>
		<dc:creator>Alec</dc:creator>
		<pubDate>Sat, 26 Apr 2008 13:12:23 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/?p=3992#comment-6710</guid>
		<description>Omar,

I can appreciate, and indeed would expect, that Broadsoft make no money from the developer program. Supporting developers is the price of entry for a platform player.

Except for specialized IT vendors, however, I am having trouble believing that developers are making serious money with even very clever mashups in the carrier space.  Carriers are nearly universally rear-vision businesses, as we discovered to our surprise after spending two years marketing products that we had built to them.

But you know, I would be happy (nay ecstatic) to be proven wrong.  Keep me posted!</description>
		<content:encoded><![CDATA[<p>Omar,</p>
<p>I can appreciate, and indeed would expect, that Broadsoft make no money from the developer program. Supporting developers is the price of entry for a platform player.</p>
<p>Except for specialized IT vendors, however, I am having trouble believing that developers are making serious money with even very clever mashups in the carrier space.  Carriers are nearly universally rear-vision businesses, as we discovered to our surprise after spending two years marketing products that we had built to them.</p>
<p>But you know, I would be happy (nay ecstatic) to be proven wrong.  Keep me posted!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Omar</title>
		<link>http://www.saunderslog.com/2008/04/25/engaged-broadsoft-or-just-shacked-up/#comment-6709</link>
		<dc:creator>Omar</dc:creator>
		<pubDate>Fri, 25 Apr 2008 21:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/?p=3992#comment-6709</guid>
		<description>Fair point, about the carrier telco-space and Web 2.0 space not mixing well.  BroadSoft dealt with it first-hand when we decided last year to move along this path, its one thing to say you can mash voice with some cool website, and its another to give a carrier the tools along with it to protect their network.  We started out by enhancing the core platform with non-buzzy but extremely useful things like overload rate limiting, URL filtering, etc...before launching the actual RESTful API set.

Specific to my quote, what we saw was one carrier customer see an application done and posted on the Marketplace, understand its relevance to what they were offering their customers and come ask us and that developer how it works, would it hurt them to deploy that, would it need enhancing, etc...

Also, since our customer base does consist of non-carriers as well; they&#039;re actually way more eager in the near term to use this, because it allows them to differentiate their phone service - &quot;its not just a phone number you get from us, you also get the ability to integrate into your daily apps&quot;.  Some of these service providers are using their IT resources to integrate BroadSoft into a target vertical markets&#039; popular apps, and sell that as a value add-on to voice.

BroadSoft makes no money from the dev program nor the marketplace.  We&#039;d make money when our customers buy more user licenses and seats on the core BroadWorks platform, when they see more customers signing up because voice-as-a-web 2.0-service is possible over a BroadSoft-based VoIP offering.

Not easy, clearly.  But necessary to initiate...and frankly we&#039;d rather be giving our customers the tools now than later.</description>
		<content:encoded><![CDATA[<p>Fair point, about the carrier telco-space and Web 2.0 space not mixing well.  BroadSoft dealt with it first-hand when we decided last year to move along this path, its one thing to say you can mash voice with some cool website, and its another to give a carrier the tools along with it to protect their network.  We started out by enhancing the core platform with non-buzzy but extremely useful things like overload rate limiting, URL filtering, etc&#8230;before launching the actual RESTful API set.</p>
<p>Specific to my quote, what we saw was one carrier customer see an application done and posted on the Marketplace, understand its relevance to what they were offering their customers and come ask us and that developer how it works, would it hurt them to deploy that, would it need enhancing, etc&#8230;</p>
<p>Also, since our customer base does consist of non-carriers as well; they&#8217;re actually way more eager in the near term to use this, because it allows them to differentiate their phone service &#8211; &#8220;its not just a phone number you get from us, you also get the ability to integrate into your daily apps&#8221;.  Some of these service providers are using their IT resources to integrate BroadSoft into a target vertical markets&#8217; popular apps, and sell that as a value add-on to voice.</p>
<p>BroadSoft makes no money from the dev program nor the marketplace.  We&#8217;d make money when our customers buy more user licenses and seats on the core BroadWorks platform, when they see more customers signing up because voice-as-a-web 2.0-service is possible over a BroadSoft-based VoIP offering.</p>
<p>Not easy, clearly.  But necessary to initiate&#8230;and frankly we&#8217;d rather be giving our customers the tools now than later.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

