This section of the RFP template defines what functionalities and phases are included in the project scope. The goal is to select a platform that can act as a core enabler for digital fundraising, improve the donor experience, streamline processes, and support future growth. It also emphasizes the need to upgrade existing capabilities and potentially consolidate fragmented systems.
This involves developing new donation forms that are intuitive, user-friendly, and mobile-first in design. They should be embeddable on various pages or accessible via branded landing pages, and fully branded to match the organization’s identity. Forms must support various giving types, including:
Additional requirements include:
Example:
“We currently have static donation forms that cannot easily be edited or branded. Our goal is to replace these with flexible, mobile-optimized forms that support giving via Apple Pay, allow toggling between one-time and monthly gifts, and dynamically display ask amounts based on UTM parameters.”
Design and implement a secure, integrated portal where donors can:
Example:
“We want donors to be able to update expired credit cards or change recurring donation dates without calling our donor services team. Our ideal donor portal would offer full self-service capabilities and sync with our Salesforce instance.”
Implement a marketing automation suite that supports both broadcast and triggered messaging. Required capabilities include:
Example:
“We aim to automate our acknowledgment and recurring renewal reminders and send them via both email and SMS, segmented by campaign engagement history. Today, these workflows are entirely manual.”
Provide tools or integrations for peer-to-peer (P2P) fundraising campaigns, including:
Example:
“We plan to launch peer-based fundraising around a national day of giving, allowing teams and individuals to fundraise under a shared campaign umbrella.”
Deliver either native functionality or integrate robustly with third-party event registration platforms. Events should support:
Example:
“We run 10–15 donor engagement events per year and need an easy-to-use registration tool that connects to our donor records in Salesforce.”
Support the creation of flexible forms to:
Example:
“We need to build simple forms that route advocacy campaigns to legislators and also create lead records in our CRM with specific interest tags.”
Provide secure payment processing with:
Example:
“We prefer to keep Stripe as our payment processor but are open to using the platform’s native solution if it improves transaction success and reporting.”
Offer robust capabilities for:
Example:
“We need to report on campaign ROI by source channel (email, SMS, organic) and reconcile donations to our finance system monthly.”
Support staff with the ability to record and manage:
Example:
“Currently, offline donations sit in a separate database. We need the ability to log these in the same system so donor history and tax summaries are complete.”
The vendor should outline and support the following phases:
Example:
“We expect the vendor to provide a detailed implementation timeline, including how long it will take to migrate recurring gift tokens and test CRM sync workflows.”
This section should clearly define what resources are expected from both the vendor and the nonprofit throughout the project phases, such as:
Example:
“We have one full-time CRM admin and one marketing lead who will be involved in implementation. The vendor should provide project management and technical integration resources.”