Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Independent Review of Telecom APIs
Sept 20th 2013
Structure: Alan’s Bit
• The Painful Facts!
• Why do telcos need APIs?
• Why all the big numbers?
• Beware the Bait and Swi...
Structure: Jean’s Bit
• TeleStax introduction
• What is RestComm?
• HealthSense Case Study: using Telecom APIs to help bab...
Structure: Juan’s Bit
• Case Study: Bank using joyn API for self-service
• Case Study: Telco using joyn API for self-servi...
Structure: Dan’s bit
• The Tropo story
• Tropo's products in a nutshell
• Some deployed case studies
• Use cases and other...
Structure: Luis’s bit
• APIDAZE: facts & figures
• Presentation of the APIDAZE REST API
• Customer case: How a leading Eur...
No developed market telco
has successfully engaged
mobile application
developers with Telecom
APIs
BUT Telecom API
successes have come from
using APIs internally
AND Telecom API
successes have come from
using APIs with existing
partners
APIs reduce business
friction. This means the
value is not ‘in the API’ it’s
in the service or data
delivered through the ...
Mobile Application Developers
ONLY care about direct access to
a large engaged customer base
that is prepared to pay. Appl...
This is the Most Important Slide in the PackRevenue
Product
Internal Telco Developers
Partner Developers
Telecom App Devel...
Why? graphic
Why do Telcos need APIs?
Without APIs Telecoms will become irrelevant as Service Providers because
customers will expect c...
What is an API?
• http://www.telco.com/api.php?action=remove_friction
APIs reduce business friction by making it easy for ...
Why do Telcos need APIs?
1995 2000 2005 2010
Why do we need a
Web site?
Of course we have
a Web site
Why do we need
an API...
Easy and Economical 90%
Global comms clouds Laggards 10%
Telco becomes the “path of last
resort” as apps use “easy and
eco...
Offers
services
direct
Offers
services
direct
Consumers
Business
Commoditizes
pricing
Easy and Economical 90%
Global comms...
Reality graphic
Market Requirements: Why are operators spending
money on API?
• M2M to support provisioning and management
• Wishful think...
Dos and don’t of telco API success?
• Focus on internal and partner innovation with APIs
o DO NOT chase long tail develope...
Mapping graphic
Mapping Telcos across the API Implementation
Landscape
Internal APIs External APIsBoth
Experiment
Broad
Focused
BusinessUs...
Mapping vendors across the API landscape
Cloud /
BOSS
Assets
IT /
Service
Assets
Network
Assets
IMS
Assets
Transactional A...
Where are External Telco APIs going?
• External Telecom API Roadmap
o Payments: whether to expand beyond digital downloads...
Brown-Nosed
Middle Manager!
Market Chatter
is Monopolized
Mobile
Everything,
WebRTC
Customers
Services
Fixed
Voice
($325B)
Mobile
Voice
($615B)
Fixed
Data
($275B)
Mobile
Data
($275B)
Regulated
Services
($1.5T)
Un-
regulated
S...
Make Telecoms an Essential Spice for every Business Recipe
Do more VAS!
No. We tried a
similar service in our
market and it failed,
and we’re never ever
going to try again
What do you think of t...
No. It will not work in
our market. Because
I’m a 50 year old guy
who understands all
my customers better
than they know
t...
No. A feature of your
service overlaps with
an existing.
What do you think of this service idea?
No. We have a
similar service
launched, and are not
going to experiment
to make it better or
address other
customer segmen...
No. Our network can
not support such as
service, even though
such services are
going over the top
today.
What do you think...
No. It looks a bit like
Joyn, we’re not sure
about it, but because
it looks a bit like
something we may do
in the future w...
No. It must work
across all devices,
even though most
devices will never use
it.
What do you think of this service idea?
No. We need
additional (random)
features included
before we could
consider it.
What do you think of this service idea?
No. It must work on
IMS (even though it
doesn’t need to).
What do you think of this service idea?
No. It must work
across all our
customers from day
one, even though
most will never use it.
What do you think of this serv...
No. It must conform
to our process and
design norms. But
we’re not going to tell
you what they are.
What do you think of t...
No. It must integrate
with all our existing
platforms, even
though it can work
fine in the current
configuration.
What do ...
No. It must be
delivered through our
preferred SI or NEP,
who will copy / kill
the service
immediately.
What do you think ...
No. You must work
through our app store
/ portal, which we’re
in the process of
closing.
What do you think of this service...
No. We can only focus on
4 service launches per
year. We only back major
successes like Video
Telephony, Mobile TV,
Push T...
No. We just don’t
have the bandwidth,
to do our job.
What do you think of this service idea?
No. We have a
network lock-down as
we launch LTE so
cannot do anything
for the next 6-9
month.
What do you think of this s...
No. Bob has left the
business and we’re
waiting on his
replacement, who
never comes.
What do you think of this service ide...
No. We’re waiting on
annual budgets to be
confirmed, sometime
in the next 6-12
months.
What do you think of this service i...
No. We’re re-
organizing again this
year.
What do you think of this service idea?
No. Someone in the
organization doesn’t
like such services.
What do you think of this service idea?
No. That cannot be
implemented without
changing our IN /
product catalog /
CRM / billing /
network.
What do you think of t...
No. We cannot bill /
sell services under $5
per month.
What do you think of this service idea?
No. We have a
backlog of 24 months
on billing updates,
even though the
service doesn’t need
to be in that pipeline.
What d...
No. You must work
through our
innovation group who
we all hate and ignore
as they’re parasites on
our business.
What do yo...
No. You must talk with
Bob who will then pass
you to Bill, who will then
pass you to Mary, who
will then pass you to
Paul,...
Telecom Application Developer EcosystemRevenue
Product
Internal Telco Developers
Partner Developers
Telecom App Developers...
www.tadsummit.com
Independent Review of Telecom APIs
Independent Review of Telecom APIs
Independent Review of Telecom APIs
Independent Review of Telecom APIs
Independent Review of Telecom APIs
Independent Review of Telecom APIs
Upcoming SlideShare
Loading in …5
×

Independent Review of Telecom APIs

12,227 views

Published on

Post-conference workshop, An Independent Review of Telecom APIs given at the SDP Global Summit

Published in: Technology, Business

Independent Review of Telecom APIs

  1. 1. Independent Review of Telecom APIs Sept 20th 2013
  2. 2. Structure: Alan’s Bit • The Painful Facts! • Why do telcos need APIs? • Why all the big numbers? • Beware the Bait and Switch! • Where are the Telco API successes? • Dos and Don’ts of Telco API success • Mapping the API landscape! • Where are Telecom API going? • What needs to change? 2 © 2010 Alan Quayle Business and Service Development
  3. 3. Structure: Jean’s Bit • TeleStax introduction • What is RestComm? • HealthSense Case Study: using Telecom APIs to help baby boomers age safely • RestComm demo 3 © 2010 Alan Quayle Business and Service Development
  4. 4. Structure: Juan’s Bit • Case Study: Bank using joyn API for self-service • Case Study: Telco using joyn API for self-service • Case Study: Leading IVR/contact vendors adding a new channel using the telco API. o http://blogs.voxeo.com/voxeotalks/2013/09/04/joyn-voxeo-cxp-a-new- way-to-deliver-customer-care/ 4 © 2010 Alan Quayle Business and Service Development
  5. 5. Structure: Dan’s bit • The Tropo story • Tropo's products in a nutshell • Some deployed case studies • Use cases and other cool stuff 5 © 2010 Alan Quayle Business and Service Development
  6. 6. Structure: Luis’s bit • APIDAZE: facts & figures • Presentation of the APIDAZE REST API • Customer case: How a leading European affiliate network increased its revenue by 15% using APIDAZE • APIDAZE & WebRTC • WebRTC integration using APIDAZE 6 © 2010 Alan Quayle Business and Service Development
  7. 7. No developed market telco has successfully engaged mobile application developers with Telecom APIs
  8. 8. BUT Telecom API successes have come from using APIs internally
  9. 9. AND Telecom API successes have come from using APIs with existing partners
  10. 10. APIs reduce business friction. This means the value is not ‘in the API’ it’s in the service or data delivered through the API.
  11. 11. Mobile Application Developers ONLY care about direct access to a large engaged customer base that is prepared to pay. Apple and Android fulfill this need, Telcos are IRRELEVANT
  12. 12. This is the Most Important Slide in the PackRevenue Product Internal Telco Developers Partner Developers Telecom App Developers Mobile App Developers Long Tail Developers
  13. 13. Why? graphic
  14. 14. Why do Telcos need APIs? Without APIs Telecoms will become irrelevant as Service Providers because customers will expect communications to be embedded in their experiences. — Alan Quayle, Independent Telecom Thinker  APIs will become critical to maintaining Telecom’s customer relevance The money is not ‘in the API,’ it’s in the service delivered by the API. APIs are simply delivering services more efficiently, which opens up new business opportunities. — Jose Valles, VP Partner Products at Telefónica Digital  APIs are just a technology, its all about the services An API strategy is becoming a must…in terms of speed to market with new products, maximizing business development, and product development opportunities. — Steve Kurtz, VP Business Development, USA TODAY  APIs are a global IT trend across all industries
  15. 15. What is an API? • http://www.telco.com/api.php?action=remove_friction APIs reduce business friction by making it easy for software systems to work together using existing well understood web technology that any IT person can understand
  16. 16. Why do Telcos need APIs? 1995 2000 2005 2010 Why do we need a Web site? Of course we have a Web site Why do we need an API? Of course we have an API InnovationUpsell New business Operational efficiency Increase footprintAccelerate internal projects Extend products / services Make churn harder Partner opportunities New distribution Device and mobile support Telecoms is the ‘vital spice’ of any successful business ecosystem Process automation
  17. 17. Easy and Economical 90% Global comms clouds Laggards 10% Telco becomes the “path of last resort” as apps use “easy and economical” APIs for 90% of comms Applications Customers Telco What if a Telco does nothing?
  18. 18. Offers services direct Offers services direct Consumers Business Commoditizes pricing Easy and Economical 90% Global comms clouds Laggards 10% Telco gets commoditized and detached from customers for comms services Telco Wholesale that’s a good model!
  19. 19. Reality graphic
  20. 20. Market Requirements: Why are operators spending money on API? • M2M to support provisioning and management • Wishful thinking in building a developer community like Android and Apple • Support open innovation and work more easily with partners on new business models and market opportunities • Support internal innovation, in some cases focused on specific market segments like enterprise • Support open innovation with specific partners targeting specific market segments • Experimenting in what APIs could means to their business • Build specific business opportunities like direct carrier billing (mobile payments) • Laziness
  21. 21. Dos and don’t of telco API success? • Focus on internal and partner innovation with APIs o DO NOT chase long tail developers, telcos are now irrelevant • Focus initially on doing 1 or 2 services well, e.g. payments and communications • Focus on building a business o DO NOT publish an API and hope hackathons are enough o You will need sales, marketing, business development and critically support • Focus on the proposition to the top-target API consumers o DO NOT waste time on platform or ecosystem game theory o Build a business first, then focus on the platform and ecosystem
  22. 22. Mapping graphic
  23. 23. Mapping Telcos across the API Implementation Landscape Internal APIs External APIsBoth Experiment Broad Focused BusinessUseofAPIs Organizational Focus of APIs Likely Evolution Path Telecom Italia does not have everything right, for example, they lack the focus on building API-enabled businesses, but its closer than most.
  24. 24. Mapping vendors across the API landscape Cloud / BOSS Assets IT / Service Assets Network Assets IMS Assets Transactional APIs e.g. call control Informational APIs (e.g. customer profile) Developer Community Developer Portal API Management API Services Network Gateway API Publishers Voxeo Labs, Twilio API Management (including API Security) Intel Software (Mashery), CA (Layer 7), Apigee
  25. 25. Where are External Telco APIs going? • External Telecom API Roadmap o Payments: whether to expand beyond digital downloads o Communications: across all VAS not just calls – RCS, messaging, number provision, WebRTC, etc. • Focus on building a businesses around the APIs rather than publish and wishful thinking o Sales, marketing, business development and critically support o Traditional transition from tech-focus to business-focus
  26. 26. Brown-Nosed Middle Manager!
  27. 27. Market Chatter is Monopolized
  28. 28. Mobile Everything, WebRTC
  29. 29. Customers Services
  30. 30. Fixed Voice ($325B) Mobile Voice ($615B) Fixed Data ($275B) Mobile Data ($275B) Regulated Services ($1.5T) Un- regulated Services ($650B)-5 to -7% 5.5 to 9% 3 to 4% 0 to 2% 0-2% Total Telecoms Services ($2.15T) 3-6% + = Over the Top Messaging hits SMS growth Mobile substitution of fixed broadband with LTE OTT substitution, saturation, competition Mobile and OTT substitution Sources: operator averages across developed and developing markets, supplier estimates, Alan Quayle 1-3.3% Threats to Revenue There’s just 2 things we need to focus on
  31. 31. Make Telecoms an Essential Spice for every Business Recipe
  32. 32. Do more VAS!
  33. 33. No. We tried a similar service in our market and it failed, and we’re never ever going to try again What do you think of this service idea?
  34. 34. No. It will not work in our market. Because I’m a 50 year old guy who understands all my customers better than they know themselves. What do you think of this service idea?
  35. 35. No. A feature of your service overlaps with an existing. What do you think of this service idea?
  36. 36. No. We have a similar service launched, and are not going to experiment to make it better or address other customer segments. What do you think of this service idea?
  37. 37. No. Our network can not support such as service, even though such services are going over the top today. What do you think of this service idea?
  38. 38. No. It looks a bit like Joyn, we’re not sure about it, but because it looks a bit like something we may do in the future we’re not going to do it. What do you think of this service idea?
  39. 39. No. It must work across all devices, even though most devices will never use it. What do you think of this service idea?
  40. 40. No. We need additional (random) features included before we could consider it. What do you think of this service idea?
  41. 41. No. It must work on IMS (even though it doesn’t need to). What do you think of this service idea?
  42. 42. No. It must work across all our customers from day one, even though most will never use it. What do you think of this service idea?
  43. 43. No. It must conform to our process and design norms. But we’re not going to tell you what they are. What do you think of this service idea?
  44. 44. No. It must integrate with all our existing platforms, even though it can work fine in the current configuration. What do you think of this service idea?
  45. 45. No. It must be delivered through our preferred SI or NEP, who will copy / kill the service immediately. What do you think of this service idea?
  46. 46. No. You must work through our app store / portal, which we’re in the process of closing. What do you think of this service idea?
  47. 47. No. We can only focus on 4 service launches per year. We only back major successes like Video Telephony, Mobile TV, Push To Talk, See What I See… What do you think of this service idea?
  48. 48. No. We just don’t have the bandwidth, to do our job. What do you think of this service idea?
  49. 49. No. We have a network lock-down as we launch LTE so cannot do anything for the next 6-9 month. What do you think of this service idea?
  50. 50. No. Bob has left the business and we’re waiting on his replacement, who never comes. What do you think of this service idea?
  51. 51. No. We’re waiting on annual budgets to be confirmed, sometime in the next 6-12 months. What do you think of this service idea?
  52. 52. No. We’re re- organizing again this year. What do you think of this service idea?
  53. 53. No. Someone in the organization doesn’t like such services. What do you think of this service idea?
  54. 54. No. That cannot be implemented without changing our IN / product catalog / CRM / billing / network. What do you think of this service idea?
  55. 55. No. We cannot bill / sell services under $5 per month. What do you think of this service idea?
  56. 56. No. We have a backlog of 24 months on billing updates, even though the service doesn’t need to be in that pipeline. What do you think of this service idea?
  57. 57. No. You must work through our innovation group who we all hate and ignore as they’re parasites on our business. What do you think of this service idea?
  58. 58. No. You must talk with Bob who will then pass you to Bill, who will then pass you to Mary, who will then pass you to Paul, who will then pass you back to Bob. What do you think of this service idea?
  59. 59. Telecom Application Developer EcosystemRevenue Product Internal Telco Developers Partner Developers Telecom App Developers Mobile App Developers Long Tail Developers
  60. 60. www.tadsummit.com

×