Chair: Next up, we have Alan Quayle, an independent consultant.
Alan: Good afternoon, change of pace I'm afraid. We've had some excellent presentations. I guess you could say on the geeky side of the equation, now some really boring stuff around operators and what they're thinking, processes, and a few simple numbers as that tends to be how they think about it, in terms of business cases.
What I'm going to represent here is I work with a number of operators, supplies application developers in the industry, generally in terms of new services. I am trying to give you some perspective in terms of the thinking that is going through operators' minds at the moment, around why they're opening the network.
What I would like to do, first of all, is to provide a little bit of framing around how operators typically do their business case. The first of course, is this is a strategic business case, which is "The boss told me." It could be basically, "Well, I'm not sure exactly how we're going to make money about this, but with this sort of fuzzy idea of what we're going to do, it looks like we're going to make a lot of cash."
What I'm actually focusing on in this presentation is on the really boring operation of business case, that is here is what we anticipate our revenues to be, here is what we think about customers are going to be - oh look, we can actually make money out of this. That's where I'm going to be focusing this presentation.
Then, of course, there is a third typical business case, unless of course there is copying. You look across at what other operators are doing, for example PushToTalk, or Fento, and you go, "Hey, let's do that as well. I'm not sure of the business case, but because they're doing it, let's copy them."
That's the typical cases; I'm going to be focusing on the operational piece of that. One of the things I want to provide, in terms of the little bit of background, is what has changed. What is driving operators to look at this concept of opening their network?
First of all, operators are getting a clear understanding of the fact that their new product development process is broken. I show here a simple example of the process that takes place; opportunities are identified, they do some market research. Once you can see that, "Maybe customers are going to be interested in this," you then have the fight for the budget. Of course, it's a big corporation so if you are lucky you get your timing right so you can get it into the annual budget cycle, or basically you have to beg, borrow, and steal from other projects.
Then, once you get all that, you have the new product development process, which of course is all focused on delivering a scalable product that works across millions of customers and integrates with all the billing, CRM, etc, all the other processes that an operator deploys.
Once you get through that new development process, you then are at the point whereby you can launch. The time it has taken you to get from that initial market research, getting the budget together, and getting through the new product development process, what you launch with tends to be, unfortunately, a little bit different from what you were talking to your customers about initially, in your market research.
You basically have to go through and re-launch the product, to actually get to where you wanted to get to in the first place. The typical time lines you are looking at for an operator's new product development process, to get to launch - twelve to eighteen months. Then for re-launch, it's anywhere between eighteen to thirty months.
Operators do realize that this process is broken. What's driving that realization is actually their customers. I think this is the real driving force. We can talk about regulations, we can talk about competitive environment; it's the customers that are driving operators. Customers' expectations around how they experience services is changing and changing quitedramatically. They're now engaged in service relationships with a whole range of brands out there.
Just to quantify what I mean, in terms of that change in expectation; I show on the top here, a typical operator process that I just showed before. I am just picking on Shai Berger and his company Fonolo, as an example of a cool Voice 2.0 application.
The numbers I want to highlight here - first of all, from concept to launch, as I indicated with the operator process, is between eighteen to thirty months. I'm not saying Fonolo has done it in four months, but typically, with a lot of the cool apps, you are looking at something that is a far shorter time frame from concept to launch.
Of course, they don't have the scalability issues. They don't have to integrate with billing, with CRM, and all those other pieces, so as you would expect; it's quicker to get out the door for the initial launch. The more important figure I want us to focus upon is between launches.
An operator has their cycle, and it will be between six to twelve months in terms of when they're updating those applications. With a lot of the apps that customers are experiencing and using today, they are now engaged in a dialog with those applications.
As a result, they're seeing that app changing on a weekly basis. A customer uses Fonolo and says, "You know what; could you add in Bell Canada's IVR into this app?" Within a week, you can imagine you could get the scenario where now, the capability is added in there.
There are these expectations from customers in how they're experiencing those services. Also, the dialog that they're engaged in is really starting to worry operators.
Another aspect is really the emergence of a whole range of inadvertent commerce, open service platforms that are appearing at the edge of the network. We've had some great presentations in terms of the mobile devices that are out there, but it's not just the mobile side of the equation. It's also the broadband side of the equation, as well.
There is a whole range of platforms that are being put out there with PlayStation and the Sony Store where you can basically rent or buy HTDV movies or TV content. You also have the WEtv. In one of the WEtv channels, you have a browser and actually, content providers, for example BBC, have realized that "I don't need a set top box. I don't need to go through all this hassle. There is a service platform that sits on the network where customers can access a WE channel and be able to access my content." There is a whole range of over-the-top platforms coming out that really are starting to bypass operators.
Of course, at Mobile World Congress, we saw a lot of announcements in terms of app stores , and a lot of operators making their launches, and it's to the point whereby, for a lot of developers, it really is noise in the system.
Apple, of course I show there, is one that a lot of developers have focused on. In fact, I know I can give quite a few examples of application developers that have given up on the mobile industry, and have decided to focus on Apple. Why? Because it provides a clear channel to market so those twenty million plus customers that are using not just the iPhone but the iPod Touch, and once you get Apple approval - if you get Apple approval for your application - you're there. There is a clear model and you have a market of twenty million people buying your application. That is the key; it's a direct channel to market that the developers care about.
What I've just provided are some of the issues and concerns that are going through operators' minds in terms of how do we react to the fact that customers are changing in terms of their expectations? We now have a set of open service platforms at the edge of our network that are enabled for delivery over the top services, and what have emerged are a range of development communities that really are driving service innovation and resonating with customers.
On to the boring bit, now, in terms of what operators are doing around the business case. I'm just giving you a flavor of the typical operationally focused business case that I've seen for a number of operators as they're looking at how can we make money out of opening our network.
I'm giving a simple scenario, just so you have some quantification around some numbers. This is a converged operator so it's a mobile and a broadband operator. They're in a mature Internet-centric market. There are about ten million customers, 20/80 split between pre-pay and post-pay, just so you understand the type of operator I'm looking at in this scenario.
Looking at this over a three year period, you want silo consolidation across messaging location, billing, of course with a lot of operators in mature markets. They have a lot of people in a lot of silos. This is actually an important piece of the business case.
I really focused around getting the processes sorted out, in terms of service exposure. Year one is actually set up. It's year two, year three, where they actually focus on service capabilities.
The service capabilities I show here are just for example purposes. Every operator is different, depending on what capabilities they have in their network, depending on the competitive environment that they're in, depending on the services they already have in their product mix. There is not a defined recipe, in terms of what you should and shouldn't expose. All I'm showing here are some examples.
Because of the audience, I'm going to skip over the year one. Basically, I just draw an analogy to BT that implemented a service-delivery platform across those silos. You can see here, it was able to achieve a 60% reduction in work force. That is the boring stuff; we'll skip over that. All it's saying is there is fat within those operators and by putting a service-delivery platform in, you can remove some of the fat.
Let's have a look at the services that you can enable through opening capabilities in the network. I show here just a few. I show here service categories, rather than going down and giving specific use cases. We have, of course, communication-enabled business processes. As we have Tom Howe here, if you want to ask about that, just talk to Tom Howe.
Enterprise, voice mashups there, a whole range of cool apps there; you can see there for example, eHealth, Dial2Do, really cool app in this space. I have here content 2.0. What I mean by that is rather than using the inefficient and expensive messaging platform for delivering content, just deliver it over IP.
Also, for a lot of operators, they're finally waking up to the fact that social communications present a market where they can get their brand out in that market. There are one hundred seventy-five million Facebook customers, which actually presents quite an interesting opportunity for them. They're starting to get their heads around some of the opportunities there.
Presence and location is actually pretty boring stuff. It's asset management machine-to-machine, more enterprise focused than it is on the consumer side. Then, I throw in that set top box services because there are a whole range of opportunities emerging, particularly from the cable space, with true two-way, with EBIF, where you now have on that set top box a whole range of cool widgets that are enabled. You saw that with the Adobe presentation, very much that they're looking also to that set top box as a platform for a whole range of services.
With these services that are enabled, one thing I didn't point out earlier on and I should have stated; the underlying assumption here is you're not charging for these capabilities that the operators are exposing. You're exposing these capabilities to make the services easier to use, to make the services cooler for customers.
What you are doing is sharing in the revenue that is generated through those services. This isn't nickel and diming in terms of location. You offer location and then because that app uses location, it is easier to use.
Also, the model that you use, in terms of what the customer pays - I always say customers pay on three dimensions: in cash, in time, or in privacy. Here, I basically showed that the user chooses the model, whether it's usage subscription or ad supported.
Typically what I'm seeing is around $40 to $75 million rev in year three. These aren't like, "Oh my God, it's going to fundamentally change our business," but you can make the case for opening the network and actually taking a very pragmatic approach.
The key here is focusing on the few key services that the executives within the operator can believe, "Yes, I can see how we can make $10 million there. I can see how we can make $15 million on that service." Everything else is really just jam that sits on top of the business case.
In opening the network, there are a few critical issues. I think first of all copy smart; don't copy dumb. An operator's business is very different from Apple. Apple doesn't really care about making money in the App Store. It cares about making the iPhone and the iPod Touch cool so the App Store is about driving value there and making money on those devices. For an operator, they need to make money on the App Store.
Another of course, is operators are boring and stodgy. There is no point in trying to be a forty-year old dressed as a twenty-year old in this game. As an operator, just focus on what you are.
In opening the network, it really does impact all lines of a business. Operators have got distracted in a way, by focusing on the consumer side, when actually for them, there is a lot more money to be made on the enterprise side, and to be honest; the innovation cycles - there is a lot more over-the-top services that are going to be far more adept at making money there than operators.
As you saw, this isn't a groundbreaking business case, but at least it's enough to justify action. Hopefully, just giving you a perspective on some of the thinking, on some of the numbers that are going around in terms of operators, and to bring it back to the point I made at the start; we've been talking about an operator turning into a utility for over a decade, now.
I think where we are is really starting to reach a crossroads, not because of regulation or competitive environment, but it's actually the customer making that decision. With that, I'm finished and I apologize that I've used up my full fifteen minutes, but you can catch me at coffee break. Thank you.


