From the start, the premise was simple: to deliver hosted applications over the network to customers. Application service providers (ASP) jumped into the market in droves to cash in on what was expected to be a gold mine. During the ASP frenzy of 1999, Dataquest Inc. predicted that industry revenue would top $22 billion by 2003. But hitting it big as an ASP wasn't so easy.
"Everybody expected this to be instantly adopted, that customers would just stop dead in their tracks and say, 'Wow! This is what I've been missing all my life!' -- like a revolutionary kind of thing," says Laurie McCabe, vice president and service director at Summit Strategies Inc. in Boston. "But very few things are revolutionary. Most things are evolutionary. And what we're seeing is the evolution of the industry."
Evolution means change, and in the ASP market, change means consolidation. Dozens of ASPs are struggling or going out of business. Those failures -- including the Intel Corp/SAP AG venture Pandesic LLC and, more recently, ASP pioneers Breakaway Solutions Inc. and FutureLink Corp. -- are making an already skittish customer base even more wary.
At the same time, though, hundreds of companies are happily using hosted applications. And while the ASP market hasn't come close to reaching the lofty initial projections, it's still strong. According to Stamford, Conn.-based Gartner Inc., ASPs pulled in $2.1 billion in 2000, and worldwide ASP revenue should hit $7.4 billion by 2003.
 | Gone but not forgotten Many ASPs lacked the business plans or financial backing to survive in the market. Here are some of the best-known failures: Agillion Inc.: Customer relationship management (CRM). Launched 1998; closed March 2001. Breakaway Solutions: E-business applications, creative professional services, Web integration. Launched 1992; filed for Chapter 11 in September 2001. FutureLink: Enterprise resource planning and CRM. Launched 1995; filed for Chapter 11 in August 2001. HotOffice.com: Calendaring, collaboration, office services. Launched 1995; closed December 2000; assets acquired by Thruport Technologies in September 2001. Pandesic: E-commerce. Launched 1997; closed July 2000 and finally stopped serving customers in February 2001. Red Gorilla: Time- and expense-tracking, calendaring. Launched 1999; closed October 2000. | | |
| |||
The ASP industry is experiencing growing pains common to any emerging technology, as IT executives slowly warm to the idea of changing the way they do business. The difference is that instead of providing a tangible product, ASPs are delivering a service that is somewhat difficult to define. Add to that the inherent complexities of remotely delivering applications designed for a client/server environment and the troubles quickly mount. Nevertheless, the notion of software as a service is here to stay. The question is which vendors will figure out the winning way to deliver that service.
Growing pains
ASPs emerged during the dot-com boom when capital was easy to get and business plans consisted of little more than a build-it-and-they-will-come philosophy. But demand didn't take off quickly enough, and many ASPs were stung by their lack of focus.
"Most ASPs tried to be everything to everybody," says Lew Hollerbach, managing director of service providers at Aberdeen Group Inc. in Boston. "You cannot go into business these days and have the sort of throw-anything-against-the-wall-and-see-if-it-sticks approach. It just doesn't work. You have to have focus."
For example, Pandesic was highly touted because of its founders, but when it couldn't make the transition from delivering e-commerce applications to dot-coms to servicing larger companies, the venture folded, he says.
Such failures have scared many firms away from considering ASPs. But IT executives who have successfully used ASPs advise their peers against ruling them out.
For example, National Semiconductor Corp. calls its ASP rollout a definite success, says Ulrich Seif, CIO at the Santa Clara, Calif.-based manufacturer. Last year, National Semiconductor decided to shift its IT operations and thought ASPs could save money by offering scalability and reducing staffing needs.
"We wanted to explore if the ASP model was viable. To really test the model, we had to find out if we could put a key application like our finances on an ASP," Seif says. That worked OK, and Qwest Cyber.Solutions LLC (QCS) now hosts National's 10,000-seat SAP human resources package and a SAP financial package that's accessed by about 500 users.
Another ASP convert recommends doing due diligence in order to pick an ASP that's likely to stay afloat.
"Go into it with your eyes open. Evaluate the worst-case scenario. Come up with contingency plans and always monitor your applications," says Rodric O'Connor, vice president of technology at Putnam Lovell Securities Inc. in San Francisco.
O'Connor carefully checked the financials of the ASPs he considered, ensured that critical data he needed was synchronized daily into an internal database in case the vendor went out of business, set up redundant network connections among his four offices to offset any infrastructure problems, and used virtual private networks (VPN) and Secure Sockets Layer-encrypted Internet connections to access his applications. He uses AppShop Inc. for Oracle Financials, Salesforce.com Inc. for customer relationship management, BlueMatrix Inc. for research management, Jamcracker Inc. for human resources software from Employease Inc., access control from iPass Inc., and online collaboration tools from WebEx Communications Inc.
"The core financial arguments [for using ASPs] outweigh the fear," O'Connor says.
Technical difficulties
You can't blame potential ASP users for being cautious. In addition to some shaky business models, ASPs were facing difficult technical hurdles. "There were last-mile concerns, concerns about security over the Internet, transaction volumes over the Internet, things like middleware to write and maintain interfaces," says Rob Unger, CEO of Agilera Inc. in Englewood, Colo. "It's not as easy as people might have thought it was going to be. But that's actually where the value to clients comes in, because in effect they'd have to manage all of that internally if they were going to do it themselves."
So while early ASPs targeted dot-coms and small businesses that required little integration and customization and accessed their applications largely via the Internet, maturing vendors struggled with how to provide the same service to more demanding large corporations.
Corporations were worried about security, connectivity and integration, observers say. One thing that troubled them was delivery over the public network, says Mark Hoffman, application systems architect at Tufts Associated Health Plans Inc. in Waltham, Mass., and a member of the ASP Industry Consortium's End User Council.
"There's the question of latency involved with the Internet cloud, because it's really kind of a black hole when it comes down to it. Even with a VPN, you can have a disruption of service; your service provider's router could fail," Hoffman says.
Even today, most large corporations connect to their ASPs, at least for data transfer, via private lines. For example, National Semiconductor is located close enough to a QCS data center that it accesses its SAP application via a T3, "which is a 45M bit connection that puts them right on the LAN," says Klaus Preussner, director of infrastructure at the chip maker.
The proliferation of less-expensive bandwidth helped launch the ASP market because vendors could offer the pipes needed to deliver bandwidth-heavy enterprise applications, such as PeopleSoft and SAP, with high levels of performance. The proliferation of metropolitan-area Ethernet will only increase the quality of application delivery.
But bandwidth at a lower cost does nothing to help ASPs deal with the complexity of delivering applications designed for a client/server environment, another technical obstacle ASPs encountered.
"They were forcing a square peg in a round hole," says Summit Strategies' McCabe. "If you have applications that were designed to be put on a server by a company, used by one company, used with a Windows interface, let's say, the things you have to do to make that work as a Web-delivered service to many customers is pretty mind-boggling."
What's more, big companies didn't want the "vanilla" applications ASPs were set to offer, preferring customized software that could be integrated with their internal systems. While ASPs offer some degree of customization -- QCS, for example, has prepackaged, industry-specific software suites -- few are willing to spend the time and money it takes to offer high levels of customization. One exception is San Carlos, Calif.-based Corio Inc., which now hosts Brisbane, Calif.-based Hitachi America Inc.'s highly customized SAP R/3 software.
Another approach to customization is to choose an ASP that focuses on a vertical market. Larry Hancock, CEO of Altius Health Plans Inc., a health maintenance organization in South Jordan, Utah, was faced with upgrading his online claims and benefits software from Phoenix-based Quality Care Solutions Inc. He also had to meet stringent security guidelines set by the Health Insurance Portability and Accountability Act -- all with an IT staff of 12.
By turning to health care industry-focused ASP The Trizetto Group Inc., Hancock says, he can continue to run applications customized to his needs and provide high-quality service to his 115,000 members without worrying about internal IT.
"Somebody like us, we just can't keep up on it," he says. "When you have somebody like Trizetto that has the resources and is big enough to keep up on it, then there is a lot more value there than just some somebody hosting the application for you."
Delivering the data
Assembling the infrastructure necessary to deliver hosted applications isn't inexpensive. Most ASPs have found it difficult to establish the customer base and recurring revenue they need to offset debt.
Market research firm IDC in Framingham, Mass., released a return-on-investment study earlier this month showing that ASP usage provides a more than 400% ROI over five years. Analyst Amy Mizoras says, "One of the things we're investigating is, Are the customers getting ROI at the expense of the ASP's own ROI?"
Take USinternetworking Inc. (USI), for example. One of the first ASPs when it launched in 1998, Annapolis, Md.-based USI decided it needed to build its own data centers to offer the complete service it figured larger companies would demand. USI invested millions of dollars in its buildout, but customers were slow in coming.
USI instituted layoffs and decided not to build out any more data centers. Earlier this month, Bain Capital Inc. promised the ASP a $100 million equity investment that should carry USI to profitability. Still, USI executives say, their decision to build their own data centers was the right one.
"Some people have suggested that you can provision an NT or Windows 2000 box, or a Unix box, with an Oracle database or a SQL database. Stick a router in front of it with a firewall behind it, build some bricks and some concrete and stick a cage in there, and you have all you really need to be an ASP in terms of the application stack," says Matt Howard, USI's vice president of business development. "That's not true at all."
What's needed is tight integration between the application and all layers of the infrastructure -- from servers to network operating systems to databases to networks, he says. "It all starts with service. And to be in the service business, you need to understand the total stack," says Howard.
Infrastructure is something network executives need to take into account when considering ASPs. If your internal network isn't suitable for handling ASP-delivered applications, you may face big headaches such as systems integration and the need to install client software on each desktop.
"You need to make [the ASP] a strategic initiative," says National Semiconductor's Seif. "You've also got to have the right infrastructure behind it."
National uses a portal to deliver all of the applications accessed by its employees, customers and partners, eliminating the need to install clients on individual computers. That made moving to QCS easy. "When we moved to the ASP, we only had to change one IP address," Seif says.
Software as a service
Vendors such as Microsoft Corp., Sun Microsystems Inc. and IBM are developing Web services that will let applications communicate with one another using XML-based languages. And PeopleSoft 8 and Siebel 7, for example, are designed to be delivered online.
What does this mean for pure-play ASPs? They will have to find the niche where they can not only deliver applications but also add value, observers say. Those that don't are ripe for acquisition by telecommunications companies or large consultancies with the deep pockets to fund the top-heavy business model.
"When we look, say, five years from now, the early ASPs will probably look as different from the software as service providers as Cro-Magnon did from humans," says Summit's McCabe. "It's got to change and adapt before it reaches its ideal state."