|
Wednesday, April 20, 2005
Bus. Std: ASPs Failed - but are now making a Comeback
My latest column in Business Standard: About 5-6 years ago, Application Service Providers (ASPs) were one of the hottest categories in software. They would transform the way software would be delivered, and create a win-win situation for customers and software vendors. That dream did not pan out. ASPs were lumped in the basket of Internet failures – along with online pet food stores and b2b exchanges. Unlike the others, though, ASPs are now making a comeback – and for good reasons. I believe that the ASP business is where Search was in 1999 when Google strode on the scene – ripe for new entrants to come in and change the rules of the game. But first, let us take a walk down memory lane to understand the promise of ASPs and then analyse what went wrong in the first wave. ASPs offer applications over the Internet using their own servers to customers, who pay a regular fee for the use. For companies, there is no need to own either the application or the underlying infrastructure. For service providers, it helps them aggregate a large number of customers providing economies of scale. Using the Internet as the distribution medium, ASPs can reach out to customer globally. Wikipedia outlines the advantages: software integration issues are eliminated from the client site; software costs for the application are spread over a number of clients; and, vendors can build more application experience than the in-house staff. It also mentions the disadvantages: the client must generally accept the application as provided since ASPs can only afford a customised solution for the largest clients; the client may rely on the provider to provide a critical business function, thus limiting their ability to handle that function to that of the provider; continuing consolidation of ASP providers may cause changes in the type or level of service available. ASPs promised a world where software would be delivered over the Internet, customers would have to pay a monthly service charge rather than a large upfront payment, and vendors would have great scale in offering the services to business globally – much like Yahoo, Google and MSN have done for consumers in every country of the world. On paper, the ASP idea looked like a great win-win for everyone. So, what went wrong? An October 2002 article in Baseline summarised what went wrong with the business model of Application Service Providers (ASPs): “The idea was that the customers, then primarily dot-coms, would be freed of purchasing and maintaining software and could use their dollars elsewhere, perhaps to bolster their marketing budgets and build their brands. And the rent would provide ASPs with a steady source of income…But two things went wrong. First, there were few companies that thought renting was a good idea. Most wanted to own an asset as important as software, and they were not about to turn over anything that controls their critical business processes to an outsider. Second, the Internet stock-market crash wiped out most of the customers.” John Hagel’s book “Out of the Box” (published in 2002) has an extensive discussion on ASPs, what the early companies did wrong, and how it can be done right. He writes: “ASPs in many respects presented a false start in the efforts to break out of the enterprise straitjacket. In particular, few of them adopted Web services architectures as their technology platform. Instead, they attempted to build businesses on the Internet using traditional technology architectures. This proved a significant flaw in the early ASP model.” Hagel then discusses the reality of the first wave of ASPs: Hagel’s key point: “The Internet is not simply a new distribution channel. It often requires a fundamentally new set of products and technologies if a business is to exploit its full potential…Web services architectures are the key to unlocking the full business potential of the Internet.” That is the starting point for rethinking ASPs. But there’s a lot more to ASPs than web services. We also need to rethink the markets they address. As I will explain in the next column, the big opportunity for ASPs is the long tail of enterprises in the world’s developing countries – what I call the SMEEMs (small- and medium-sized enterprises in emerging markets). They have been largely unaffected by the Internet – other than email usage and in some cases, a minor web presence. The software they use for their business remains almost identical to what they used five or more years ago. [In India, this is limited to mostly pirated copies of Microsoft’s Windows and Office, and Tally for accounting.] They are the weak links in the information value chain and the next big opportunity for software vendors.
Broadband for Development
Tom Friedman writes:
Also read Thomas Bleha's article in Foreign Affairs.
IBM's Challenges
The New York Times assesses the future after IBM's disappointing results:
Aggregation as the New Scale
Jeff Jarvis writes:
Fred Wilson adds: "You cannot collect all the pieces of a marketplace in a centralized way and control all of it. The technology won't allow that to happen. You can't 'get to scale' that way. You must be open to others owning pieces of the equation. You must let the users get the value of scale however the choose to create that scale. You must facilitate the creation of virtual scale."
Adobe's Plans
The Economist profiles Bruce Chizen, the boss of Adobe Systems. Some of these ideas become even more important in the context of Adobe's decision to acquire Macromedia. Last week, he was in Brussels to demonstrate how. Belgium will be the first country in the European Union to give its citizens electronic ID cards. And by plugging these cards into the USB ports of computers that have Reader, Belgians will soon be able to “sign”—ie, digitally authenticate and seal—PDF documents such as tax forms, mortgage applications, patent approvals and anything else that today requires a signature in ink.
TECH TALK: When Things Go Wrong: The Present Situation
The second failure that I had discussed last week was the one that I am presently going through. I thought quite a bit before writing about it. It is never easy to discuss unpleasant realities in public! As Sachin put it: “After reading this article from you, what came to my mind was that it takes a lot of courage to write about one’s own failure.” Indeed, it does! But then I have been quite open on the blog and in my writings, so I decided to go ahead. It is never easy talking about the present. Analysing a decade-old experience can be easy because the ending is now known. But thinking through the immediate past and the coming future is not easy. But if as entrepreneurs we can be more open, I think it will definitely help all of us do things better. No book on entrepreneurship can lay out the roadmap to success, but learning from experiences of others can definitely lay out the path to avoid failure! As I look at our business in Netcore, there are two parts to it. One is the Linux-based messaging and security business, which has a customer base of over 350 small- and medium-sized enterprises garnered over the past 7-odd years. This business is growing, but not fast enough to support the rising costs of doing this business and fund our other activities. Which brings me to second part of our business. The vision here has been to provide computing as a service and create a platform for the next billion people. (Talk of ambition!) Here, we have tried a few ideas around server-centric computing and thin clients, but somehow the solutions have just not been good enough. So, there are twin challenges that I face: how can we grow the messaging and security business and take steps towards realising our vision of computing as a service. While I did wonder whether we should drop one in favour of the other and focus, I think that the two businesses are complementary. Doing the first helps us build a customer base which allows us to bootstrap the second business. By narrowing what we do in each of the two areas will help us achieve the twin objectives of building a near-term profits engine and a longer-term growth platform. So, in the messaging and security business, we need to (a) focus on a few standardised offerings that we sell without getting into too much of customisation (b) build a distribution channel so we can amplify our market reach (c) invest in building a brand that separates us from other players. Here, the products are ready. What we need to do better is on the marketing and sales side. Our current customer base gives us the foundation to build further on this business and I am confident that in the next few months, we can not only turn the corner here but also build an engine for growth going ahead. The second business is harder because we are now going into unchartered territory. I understand now that the mistake we made was that we started from the “devices” (thin clients) side instead of focusing first on the “services” (applications and content). It is the services which will make computing desirable and compelling for the small- and medium-sized enterprises (SMEs) to get more computers – which is where the thin clients will come in. So, in the business, the first focus is on creating a suite of useful services which address customer key points and deliver them via the Internet. This is the ASP (application service provider) model – starting with SaaS (software-as-a-service) and then going on to CaaS (computing-as-a-service). When I look back, one of the missing elements was focus. Sunil Goyal put it very nicely: “I think for any business dreaming to be big there's always a stark difference between short term reality and vision of tomorrow. The strong mental models might make one believe this is achievable but reality still plays its part. Even though I don't have much experience, but I am experiencing this phase myself. My own realization of the current startup time phase is, to have the right FOCUS.” This is what we will need to bring to the tasks ahead. Tomorrow: The New Business Related Entries: [All]TECH TALK: When Things Go Wrong: Looking Ahead [April 22, 2005] TECH TALK: When Things Go Wrong: The New Business [April 21, 2005] TECH TALK: When Things Go Wrong: Dealing with Failure (Part 2) [April 19, 2005] TECH TALK: When Things Go Wrong: Dealing with Failure [April 18, 2005] TECH TALK: When Things Go Wrong: Why Failure Happens (Part 2) [April 15, 2005]
Tech Talk
| PermaLink
| Comments (1)
Considering that 'Applistructure' (aka combination of application and infrastructure) market segment is still in a defination stage, you sure need to decide on being a infrastructure or a application/service company. Trying to do this for the bottom of the pyramid, is sure a real challenge. As a regular reader of this blog its been good to learn from your experiences and better understand the ground realities. Its nice watching 'swadesh' movie but success sure is a longer endevour. Good luck |
See my analysis of software as a service in general (ASP is one form of this concept) on http://www.strategicboard.com/weblog/pivot/entry.php?id=121
Thanks,
Posted by Dudu MimranDudu
Propecia
Posted by MattMeridia
Propecia
Ambien
Levitra
Order Viagra
Generic Viagra
Cialis
Generic Meridia
Generic Propecia
Cialis Online
Posted by LillyAmbien
Order Viagra
Buy Meridia Online
Viagra
Cheap Viagra