Most weeks I get a call from a nonprofit that wants to upgrade its donorb tracking capabilities. The organization has outgrown using spreadsheets to track gifts, donors, and contacts. They want a sophisticated database that will help them identify, cultivate, and communicate with their best donors. Unfortunately, all too often the organization wants to meet these goals by building its own donor database.
There are certainly instances when a custom database is the best or only solution. But those are few and far between. Usually, the nonprofits I talk to aren’t building a database because they have unique requirements. They just have a copy of FileMaker or Access, and maybe a volunteer who knows how to use it. I respond by telling them why they shouldn’t build their own database:
- Risk: Building a database is a risky proposition. I’ve seen countless custom database projects that failed to meet the organization’s needs. There have been a variety of causes: requirements weren’t clearly understood or articulated by the organization or were constantly changing; the programmer got distracted by other projects, or left the organization; bugs were never fixed; reports and documentation never got written. Whatever the reason, these projects turned out to be frustrating, costly, time-consuming examples of good intentions yielding bad results. Yes, I’ve seen successful custom donor databases – many of today’s commercial databases started that way. But I’ve seen many more failures than successes.
- Focus: Building a donor database will require significant input from the people who will use it. They’ll need to describe, in detail, the minutiae of daily operations as well as your management reporting needs. Is turning fundraisers into database designers really the best use of their time?
- Support and Maintenance: Who will you call when your homegrown system has problems? What if the person who wrote it isn’t available? What if you need new functionality that’s beyond the technical skills of the original programmer? Building a database is an iterative process – you’re going to want to make changes over time. Without ongoing support and maintenance, bugs won’t be fixed, questions won’t be answered, and changing needs won’t be addressed.
- Training: Who will train staff to use the system? Software training is an art, and not everyone is good at it. But let’s say the person who built the system provides great training. Will she be available for years to come as you get new staff? And, just as important will you have training and reference manuals? How will you keep database training from being like a game of “telephone,” where the tenth person trained hears something totally different than the first person (and the garbage in your database reflects it)?
- User Community: With commercial database applications, a host of programmers and clients are providing input to help improve the software. There are user groups (both physical and virtual) where you can learn how other organizations are using the software. There are other clients of whom you can ask questions when problems arise. If you build your own database, there’s seldom anyone else you can turn to for advice or help.
- Documentation: I distinguish between three types of database documentation. The first is technical: it tells other programmers why the database was designed the way it was. The second helps train staff members on how to use the database (click this button to go to that screen). The third describes your organization’s procedures, so the right data goes in the right place. When it comes to homegrown databases, all three types of documentation are as rare as Yeti sightings.
- Cost: Price is the bottom line. You can get bids for a commercial system. How do you get a firm price and feature list for a custom system? You also need to consider the cost in staff time of designing and testing the system. Keep in mind that every change to the database will cost money: will you be able to pay for upgrades to fix problems and keep up with evolving technologies? While a custom database may seem like a bargain up front, in the long run it may cost a lot more than a commercial database.
-----------------
More resources:
Blank Bill Of Sale
This information or section may also include the condition of the property and necessary repair details. Lastly, one of the most important information in a bill of sale is the signature of both the seller and the buyer with the complete name underneath it. The date of the signing should also be included. The complete name and signature of at least one credible witness need to be included also. Remember, there should... Source..
Letter writing template
These ideas should be observed especially among the individual who frequently write business letters, for instance. In every type of letter, there is a corresponding action to take such as making a... Continue reading..
Coupon Template
In terms of marketing, one can regard a coupon as a piece of paper that’s just about the size of a train ticket having the power to be interchanged for a rebate when you want to purchase a certain product or... Click here to continue..
Pivot tables
For a better understanding and for additional information especially individuals unfamiliar with cyber languages it is best to understand first what software or program means? The term program in cyber world is also otherwise known as software. Both terms are interchangeable as the two are similar in meaning which is defined as a series of computer commands scripted to carry out a specific order as computers needs programs or software via its center... Continue reading..
