Choosing A Database? Mistakes To Avoid

April 13, 2009      Admin

Consultant Robert Weiner recently presented a webinar for Fundraising Success, called "Understanding and Maximizing Your Donor Database for Fundraising Success."

As reported here, Weiner included a discussion of  "ten mistakes nonprofits commonly make" when choosing a database.

Having sat on both sides of the table during this ugly and painful process, I thought his list was spot on! Here it is …

  1. Letting techies make the decision.
  2. Wishful budgeting.
  3. Prioritizing price above everything.
  4. Randomly looking at demos.
  5. Falling in love with cool features.
  6. Falling in love with the salesperson.
  7. Buying more than you need.
  8. Confusing highly functional software with highly trained staff.
  9. Hoping the database will install itself.
  10. Leaving the database to fend for itself.

For me, item #8 is the biggie. Your software is only as good as the people who are going to milk it. If you have a robust donor file, a well-trained data analyst is worth his or her weight in gold … or even something more precious!

You can still register to listen to this webinar here for another 90 days or so, for $65.

Tom

P.S. Speaking of online edification, don’t forget to check out IFC Online, the world’s first global, virtual fundraising conference. Taking place May 12-14 completely over the internet, the event will deliver live, interactive, workshops and plenaries to a world-wide audience of fundraising professionals. The e-Conference will feature raising funds online and building constituency through email, SMS and Web 2.0. If you register by next Monday (April 20th), you get a $25 discount. Info here.

 

2 responses to “Choosing A Database? Mistakes To Avoid”

  1. Choosing A Database? Mistakes To Avoid | The Agitator – Fundraising, Direct Marketing and Advocacy Strategies for Nonprofits…

    A great list of 10 important things to think about when selecting a fundraising database….

  2. Grant says:

    Good article! I find the key for a solid dbase is to test it to assess it’s validity.