Copyright Society For Nonprofit Organizations May/Jun 2004| [Headnote] |
| Which ASP offers the tools your organization needs? Here's how to decide. |
Many of today's nonprofit executives have begun to realize the importance of specialization when it comes to communication technologies. With growing frequency, organizations are outsourcing large technology initiatives, leaving the installation and maintenance of online tools to the professionals while staff members focus on using these tools to communicate with their constituencies.
In recent years, there has been a proliferation of Application Service Providers (ASPs) catering to the technology needs of nonprofits. This generally has been a boon to the nonprofit sector, enabling organizations of all shapes, sizes, and budgets to take advantage of new technologies to improve their Web sites, track their constituencies, accept online donations, and send targeted e-mails.
But selecting an ASP involves more than simply picking a vendor selling commoditized products and services. Nonprofits assessing ASPs should look beyond a simple line-item comparison of features and evaluate each vendor's fitness as a potential partner. Unlike a traditional software purchase, which can be as straightforward as acquiring a product, using an ASP involves a long-term association.
Asking a few critical questions up front will help ensure a long, stable, and productive relationship:
How will your data be stored, managed, and backed up? Who will have access to it?
Your ASP will be responsible for planning, building, and executing a technical strategy to guarantee that data will survive a physical, electronic, or financial disaster. At a minimum, every service provider should take a daily snapshot of the latest constituent information for storage on a separate system from the primary database in case of a computer failure. There should be a plan in place to ensure that such a system is immediately available to reduce the risk of any loss of service.
Ask your potential ASP about the Internet data center it will use to manage its computing facilities. Third-party vendors should have a proven customer success record with resources to meet demanding business conditions. Someone at every ASP you are considering should be available to answer your questions about network up-time or availability and physical security.
Additionally, inquire about the restrictions your ASP has set up regarding internal access to your data. How many people have direct access to the database? How many employees have the administrative passwords and how often are these changed? Clearly, the provider you select should treat this access the same way you do, limiting it to those who need to interact directly with your account. Although virtually all ASPs collect aggregate data across their customer base for trend analysis, they should not be discussing highly sensitive marketing data beyond the terms of your agreement.
How do you get the data in and out of your donor database?
You probably are working with an ASP to further your overall marketing efforts. So you will have to integrate data collected online with your traditional "offline" donor database system. Almost every service provider will claim the ability to export data in some format for this purpose. Be aware, though, that the mechanism and flexibility for this process varies widely among ASPs.
The process of mapping specific data in the online world to your donor database is not a trivial undertaking. An ASP should be able to take individual fields and transform, replicate, and assign them within your existing system as needed. The actual process for executing this data synchronization should require minimal intervention, but also should allow some manual controls to ensure the quality of the data exported, including the ability to remove duplicate profiles of constituents.
Most important, no matter how much confidence you have in a potential vendor, ask them to refer you to customers for whom they've done similar integration. Ideally, each potential vendor will be able to put you in touch with customers similar to your organization in terms of size, donor database, and functional applications.
How do you handle credit card numbers?
An ASP offering online donations will have to get credit card numbers from constituents. Be diligent about understanding exactly what happens to these numbers during and after the donation. In most cases, ASPs contract with a thirdparty transaction vendor to handle the processing and interaction with financial institutions. This not only ensures accurate and timely execution, but also entrusts the storage of sensitive information to organizations that specialize in the requisite security.
More specifically, confirm with your potential ASP partner that it erases all credit card information immediately after passing it along. No matter how confident you are in the security of the transaction vendor, it is a moot point if an inherently less secure ASP keeps a copy in its systems. Although this is less of an issue for single transactions, ASPs may decide to store card information themselves for sites offering sustainer giving or recurring payment programs. If you will be using this functionality, ask exactly where the card information is stored between scheduled transactions.
What software operating system and database is your system based on?
You may want to broach the subject of software operating systems with a service provider. A variety of tools are capable of providing the reliable performance needed for these applications, but if an ASP is using enterprise products from
Microsoft, you may want details of measures they've taken to combat their potential weaknesses. There have been a number of high-profile attacks on ASPs that have not conscientiously applied
Microsoft patches to protect against software virus attacks.
Generally, if a provider is using a UNIX-based operating system, such as Sun Solaris, BSD Unix, or Linux, you can be assured that these time-tested systems will be much more resistant to such attacks and won't require expensive investment in your ASP's technical resources to keep operating smoothly.
How are fixes and improvements managed?
The features and functionalities provided by an ASP boil down to a set of software tools that require constant fixes and improvements. A true ASP will have written most of these applications from scratch to meet the specific needs of customers. It will be able to correct mistakes quickly and respond to new feature requests with minimal effect on system usability. When speaking with prospective vendors, try to find out about their historical responsiveness. Ask about their recent release schedule or examples of new features or problems that they have quickly resolved. Progressive ASPs should have a system in place to document and manage requests for new features and be able to discuss specific plans for upcoming development of new tools.
Educated, proactive consumers will be prepared to ask probing questions to determine which technology providers truly offer the tools their organization needs in the most dependable way. Although specific responses will vary widely, you should be able to create an "apples-to-apples" profile of each potential vendor and its investment in the facilities, talent, and methodologies to provide you the best quality service.
| [Sidebar] |
| Ask exactly where the credit card information is stored. |
| [Sidebar] |
| Evaluate each vendor's fitness as a potential partner. |
| [Reference] |
| Resources |
| Bhagat, Vinay, "Online Advocacy: Mobilize Supporters to Take Action," Nonprofit World, Vol. 21, No. 6. |
| Elges, Mary, "Driving Traffic to Your Web Site," Nonprofit World, Vol. 20, No. 6. |
| Frenza, J.P., "How to Stake Out Your Claim in Cyberspace," Nonprofit World, Vol. 15, No. 4. |
| Frenza, J.P. & Leslie Huffman, "Top Ten Web-Site Tips," Nonprofit World, Vol. 16, No. 1. |
| Paley, Scott, "Cyberactivism: How a Web Site Can Make or Break Your Organization," Nonprofit World, Vol. 21, No. 5. |
| These resources are available from the Society's Resource Center, www.snpo.org. |
| [Author Affiliation] |
| Vinay Bhagat is the founder and CEO of Convio (106 East 6th Street, Suite 800, Austin, Texas 78701, www.convio.com), the leading online Constituent Relationship Management (eCRM) company serving the nonprofit sector. |