Sumac « Young Associates

Sumac Research. February, 2012.
Co-author: Ye Adam Tian

“After people, data is your most important asset.” This is the first of 10 Nonprofit Technology Commandments outlined by John Kenyon, noted non-profit technology educator and strategist. And it’s true, isn’t it? Data is the key to a non-profits’ success, so you’ve got to take good care of it! But where do you house it? How do you choose the right software? Well this is a good place to start! Here are seven things to consider, along with some fundraising software reviews and resources to help you find the right match for your organization.

7 Things to Consider

Features. Before you even start looking for software, decide what you need the software to do and make a list. What data do you want it to hold? What features do you absolutely need? One of the mistakes in Robert Weiner’s 10 Common Mistakes in Selecting Donor Databases is buying more than you need. Robert Weiner is a popular non-profit technology consultant who has written for every major non-profit technology publication. Some of the other mistakes listed: randomly looking at demos, falling in love with cool features, and prioritizing price above everything else.

Customization. Another thing you may want to consider is how easy the software is to customize. Let’s face it, no two non-profits are alike. You have different programs and different terminology, and you don’t want to build your own database from scratch if you can avoid it, as Robert Weiner explains in Why Building Your Own Database Should Be Your Last Resort. So look for software with easy customization that allows you to tailor the database to your needs.

Usability. Also important to consider is usability. Because this fundraising software is going to be an integral part of your non-profit, you want it to be intuitive and easy to use. To determine just how user-friendly it is, have a look at some demo videos, get a personal demo and ask current users what they think of it.

Cost. Does the software fit into your budget, both now and in the future? In order to determine this, you have to take into account all of the costs associated with owning the software (the “total cost of ownership” or TCO). Direct costs include the software license itself, data conversion, installation, training, and support. Indirect costs include IT staff required to maintain the system, consultants needed, and upgrades to computers needed to run the software.

Security. Since you’re dealing with donor information, security must be a consideration. There are many question that you’ll want to ask. For example: Where is the data stored? Who has direct access and authority? How is the data shared between different people and departments? How is that process managed? Is there any risk of exposure of your data to the online community?

Ability to Get Data In & Out. This one is often overlooked, but it’s so important. You’ll often want to get data into your database – a list of names and addresses for instance. You’ll also want to get data out – for email marketing, accounting or event purposes. So, being able to easily import and export data is very important!

Technical Support. Finally, does the fundraising software come with quality customer support? Really what you want to know is whether you’ll be able to contact someone by phone or email when you really need help, and how quickly they will be able to assist you. You may also be interested in seeing what other kinds of support they offer: frequently asked questions on their website, documentation, training videos, etc.

Reviews

Don’t know where to start looking for fundraising software? Start here:

Low-Cost Fundraising Software Comparison:

Check out NTEN and Idealware’s Consumers Guide to Low Cost Donor Management Systems for an overview of 29 systems — what they do, recommendations for systems based on particular needs, and comparison charts.

Fundraising Software Listing & Reviews:

Donations

On a tight budget? TechSoup offers donations of fundraising software to registered non-profit organizations all around the world. Here’s a link to available donations in Canada and the United States.

This tip sheet was created by Sumac Research. Sumac is a complete nonprofit software solution that is free for small organizations and includes data conversion and installation for larger organizations. For more information, visit the Sumac website.

Open this tip sheet in its own tab to comment

Your database could use a glossary! Each field should have its own definition, specifying what type of info belongs there, and what format should be used. This resource should be at the side of everyone allowed to enter data.

Identify all the ways in which your organization gathers patron and donor data – pledge cards, membership renewals, subscription orders, event registrations, email communications, etc. Set up a grid to compare the data elements you collect, to ensure consistency.

Be alert to how donors and patrons interact with your various systems. Many have multiple phone numbers and email addresses – and they may give different versions of their name and address on subscription renewals, pledge cards, draw tickets, etc. It’s your job to identify and prevent duplications.

Who’s in charge of your organization’s database? In some organizations, various staff and volunteers from multiple departments may have a hand in the process. It’s important to clarify responsibility, and make sure that one person, or perhaps a committee, clearly takes the lead.

Think about how many people in your organization have a hand in processing data. They all need to understand their important role in keeping your data “clean” – and to follow the same policies and procedures for handling this crucial resource.

Sort your donor list by postal code to see if you can identify clusters. Recognizing patterns like this can allow you to target mailings, and plan programs and activities to suit identifiable groups.

How many times – and in how many systems – does your organization capture contact information? It’s worth the effort to eliminate duplication amongst database software, email, social networking contacts, random Excel files and others. Ideally, you will have one unified source for all contacts.

Establish uniform procedures for entering tricky database information such as addresses. Is it 500 Main Street, Suite 211… or 211-500 Main St… or Apt 211, 500 Main St… or something else? Set standards to keep data consistent and reduce errors and duplications.

What is a database? A database is a means for organizing, storing, managing, and retrieving information. Your fundraising, box office, sales and accounting software are all considered to be types of database software.

Bookkeeping packages (e.g. QuickBooks, Simply Accounting) spreadsheets (e.g. Microsoft Excel) and database software (e.g. Sumac) are electronic tools for delivering a narrative on your operations and programs. It is essential that you pay attention to the stories they tell; it is equally important that these different sources communicate effectively with each other in order to deliver a meaningful tale.

Who’s doing the talking? It is important to be consistent when communicating financial information. Decide which system will do the talking and which will do the listening. Having information flow in one direction will reduce errors, confusion, or missed transactions. Multiple databases in a single organization should be used simultaneously and reconciled to each other on a regular basis. Integrating your databases into your daily routine will help to support sound management.
Speaking the same language. When communicating financial information from one system to another it is important that the allocation is the same in both systems. For example, if you are tracking donations that are associated with a certain project or event in your database software, make sure you make the same allocation in your accounting software. This will help in the future when pulling reports from either system or doing reconciliations.
Doing a little bit at a time. Errors more often happen when you try to condense information. While it might be more efficient to do weekly reports, errors may occur if financial information provided by the database software doesn’t match what is in the bank. For example, if you are doing daily credit card batches, than weekly reports may not catch the information you need. Batch totals and generated reports need to have the same time parameters. Keep things simple and work on a consistent basis. While it might take a little longer initially, it will make it easier to identify errors, saving time in the long run.
Take time for the details. It might be easier to group contact information together when going from one system to another, but it can contribute to errors. Make sure whatever information you are tracking in one system is communicated to the other system. For example, record individual names and donation amounts rather than a batch total.
Keep an eye on things. Try doing regular reconciliations and comparisons between your database software and financial software. Tracking as you go will make doing a year-end reconciliation go smoothly, and will help you know where you are in regards to budget vs. actual.
Remember what you did. You are only as good as your information. (Garbage In/Garbage Out). If your database software gives you the option to record communications, such as emails, memos, or notes, try using the function with regards to financial transactions. If you have special notes relating to a transaction, record it in the communication notes for that contact for easy reference. Storing important information pertaining to donors or other contacts will contribute to organizational history and make staff transitions easier.
Don’t leave it to the last minute. We are often leaving grant reports and year-end audits until the last minute, when it can be a headache to go back through months of activity to get the information needed for the report. Track as you go in both the database software and financial software. Doing it in both will act as a double check to make sure the numbers are correct, as well as take some of the stress of that last minute report.
It’s okay to anticipate. It is common to anticipate transactions, especially those reflecting revenues (eg. Held tickets, pledges, and confirmed grants). Make sure that if you are entering an anticipated transaction into your database software as a receivable, that you communicate that information to the financial software. Not doing so could result in double counting the revenue when the money does actually arrive. Be sure to compare receivables list from all databases on a regular basis.
Break it down. Most database software packages will allow you to break out details on transactions. Breaking out gross amounts, taxes, and any service fees applicable will help eliminate errors or the need for further calculation when entering data into the financial software. Make sure you have taken full advantage of all the setup features to automate standard charges (eg. service charges and sales taxes).
Where it all belongs. Similar to your financial income statement where revenues are tracked on a yearly basis, it is important to do the same in your database. Most database software doesn’t have the concept of deferred revenue, so you may have to indicate what year funds are allocated to. For example, allocating things like donations, grants, and ticket sales to your 2009-2010 season will make reconciling and reporting easier. It will also help in the budgeting process when you are able to pull up reports with precise data pertaining to certain years.

This tip sheet was created by Samantha Zimmerman of Young Associates. Founded in 1993, Young Associates provides bookkeeping and financial management services in the charitable sector, focused on arts and culture. Young Associates also provides consulting services in the areas of data management, business planning and strategic planning. Heather Young published Finance for the Arts in Canada (2005), a textbook and self-study guide on accounting and financial management for not-for-profit arts organizations.

Disclaimer

Open this this tip sheet in its own tab to comment