Six Tips For ASP Success

 
 
By John Pallatto  |  Posted 2003-11-21
 
 
 

Six Tips For ASP Success


The success of a few key Application Service Providers is nothing less than the crack of doom for the long-established model of selling enterprise software packages.

In a few years the purchase of enterprise scale software packages could become as obsolete a business practice as employing squads of bookkeepers with eyeshades and paper ledgers to maintain corporate accounts.

Thats because the benefits of dealing with an ASP will, in the long run, far outweigh the cost benefit of buying packaged software. Two exceptions: fundamental corporate applications, such as desktop productivity software and some database programs.

Every major application that an organization installs in-house requires a costly hardware infrastructure to run it and people to maintain it. With the ASP model all the application features are available through a web browser and the service provider takes on the expense of providing the software and hardware infrastructure to deliver the service.

ASPs today are much more scalable than they were when the services came online nearly five years ago. Many of these services installed existing client/server programs on their sites and simply enabled customers to access those applications through a Web browser.

Some used licensed third party software that required the ASP to install a separate copy for every customer. That meant the ASP had to replicate the entire application hardware and software stack for each customer, a model that was neither economical nor scalable. Performance and sometimes even security were weak. Thats why they failed.

Todays providers are offering applications designed from the ground up to run as a service. RightNow Technologies Inc., a customer relationship management ASP, estimates that its services can save customers at least 50 percent of the cost of an internally hosted application by eliminating the hardware and software infrastructure to run it.

RightNow, based in Bozeman, MT., is one of a rising number of ASPs that are winning the confidence of a growing roster of customers. Others in this category include Salesforce.com, and Salesnet Inc. of Boston.

But perhaps the most compelling advantage of working with an ASP is that the customer has a far greater level of control over the business relationship. Buying a major enterprise application can feel like being joined at the hip with the vendor. The customer is buying into the vendors application architecture and business strategy.

If that architecture is flawed or if it cannot adapt to changing business needs or technological advances, its very difficult to switch without considerable cost and business disruption.

With an ASP the customer has a much great control of the relationship because they get fixed-term service contracts. If the customer is not happy, switching doesnt involve scrapping a huge investment in software and hardware.

Working with an ASP also means you only use the applications and features that are most relevant for your operation. The customer isnt tied to creeping application complexity that inevitably results as vendors add features in pursuit of supposed competitive advantage. These features add to the cost regardless of whether they are critical to the customers business.

Next page: Six Tips For Successful ASP Selection.

Six Tips For Successful


ASP Selection">

Selecting an ASP: There are a number of factors you need to consider when selecting an ASP.

  • Service Level: Some ASPS offer 24/7 availability of 99.5 percent or higher. If an ASP cant promise availability at this level, then you should consider another provider who can.

  • Application performance: This is the other side of the coin. Productivity will suffer and users will get frustrated if it consistently takes 10 seconds or more to execute page loads. Customers should be able to demand and get consistent page loads of about 2 seconds.

  • Real-Time Monitoring: An ASP should provide you the ability to readily monitor in real time the performance of your organizations access to all the applications. This allows you to keep performance constant during peak periods or as you add additional users.

  • Integration: You also need to ensure that an ASP can readily integrate their services with your existing internal applications. This is typically done through the use of Web services and XML. Integration wont be easy or economical if the service provider has to write lots of custom APIs to ensure your critical business applications can share data with the ASP.

  • Phased Upgrades: Another touted advantage of working with an ASP is that application upgrades are automatically deployed to all customers at the same time. But ASPs should also give customers the option of phasing in upgrades to make sure that they dont disrupt business and provide adequate time to train employees to use new features.

  • Defined Exit Policy: If the time comes when you decide that you and ASP must part ways there has to be a rational exit process in place that ensures that all of your data securely departs with you.

    But even splitting up with an ASP should be a lot less painful than tossing out an in-house application that you may have spent years and perhaps several million dollars to install and maintain.

    eWEEK.com Enterprise Applications Center Editor John Pallatto is a veteran journalist in the field of enterprise software and Internet technology.

  • Rocket Fuel