Dear ldunham,
Welcome to TechSoup!
I am skeptical of most RFPs for donor databases. I've seen many examples of RFPs that did not repay the amount of time and effort that went into them. Vaguely worded RFPs yield vague responses. You need to phrase your questions so that they mean the same thing to all readers and yield unambiguous answers (which is hard to do). And you need think about how you will evaluate each answer. What does it mean when a vendor says their system supports matching gifts? Is that specific enough? Are any questions deal-breakers that will disqualify a vendor? Are some questions worth more points than others?
Start by describing your organization and the problems you are trying to solve. Then focus on mandatory and high-priority requirements that will allow you to compare vendors. Don't ask general questions like "can your system process gifts?" Ask specific questions, like "can gifts be split between funds in a single transaction?", or "can soft credit be split between several parties?", or "can fundraising credit be split between several fundraisers?" (these are meant as examples -- they may not apply to you). Try to think of questions that will distinguish one vendor from another.
And remember, if your RFP is 30 pages, the responses will be at least as long, and you’ll have to read and rate every one.
As far as how to write an RFP, it should come out of a list of your requirements. NPower has a great how-to guide called
Four Steps to Selecting Donor Management Software. It includes a worksheet that has examples of how to rate features
(here) and an example of functional requirements
(here). Once you know what you're looking for, you can ask a pool of vendors whether they can provide those features, and at what cost.
You can also ask the vendors you're considering whether they can provide a sample RFP. Many of them will. Get several, since each vendor will provide one that's tuned to their system.
Robert