The nonprofit's guide to issuing a Salesforce RFP

A Request for Proposal, sometimes called an RFQ, is a structured document describing your project, your needs, your timeline, and your budget, which formally invites qualified firms to respond. For a nonprofit choosing a Salesforce partner it does two useful things: it creates a consistent basis for comparing firms, and it gives your leadership a documented, defensible selection process.

Not every Salesforce project needs one. Organizations typically issue an RFP when a board or funder requires competitive bidding, when the budget is large enough that structured comparison is worth the overhead, when they are undertaking a major platform migration, or when they are entering a multi-year managed services relationship. For a small scoped project, an exploratory conversation, or an organization that already has a partner it trusts, an RFP can add process without adding clarity.

The thing to settle before you write one: the goal is not to find the cheapest option. It is to find the partner with the right expertise. A firm that has spent years implementing Salesforce for nonprofits will ask different questions, flag different risks, and design a different solution than a generalist adapting commercial patterns to your mission. Your RFP process should be built to surface that difference rather than to average it away.

1. Organizational background. Who you are, your mission, your team size, and the systems you run today. A partner who understands your context writes a better proposal, and the ones who skip this section in their response are telling you something.
2. Project goals and success criteria. What does a successful engagement look like twelve months from now? Your definition of done is the single most useful paragraph in an RFP, and the one most often left out.
3. Scope of work. Implementation, data migration, custom development, integrations, training, managed services. Be specific. A vague scope produces proposals you cannot compare.
4. Current Salesforce state. Starting fresh or migrating? Which products are in play: NPSP, Agentforce Nonprofit, Education Cloud, Grantmaking? An honest description of a messy org gets you better answers than a tidy one.
5. Data overview. Roughly how many records, which systems need to integrate, and your candid read on data quality. Nobody is grading you on this.
6. Timeline and key dates. Proposal deadline, decision date, desired start, and any hard dates: fiscal year end, board meetings, grant reporting, a contract that expires.
7. Budget range. Include one. A range makes your RFP more likely to attract serious, calibrated responses. Omitting it reliably produces proposals that miss, and a round of rescoping that costs everyone a month.
8. Evaluation criteria. How you will score and select. Tell firms what matters most: sector experience, approach, team, cost, references. Partners who know the criteria write to them, which makes your comparison easier.
9. Submission instructions. Format, length limit, required attachments, point of contact, and how to send it.
10. Questions and clarifications. A deadline and a route for vendors to ask before submitting. The questions you get are a free review of your own RFP.

• Your RFP states your mission and the problem you are solving.
• You have described your current Salesforce environment, or said plainly that you do not have one.
• Your scope is specific enough that two different firms would propose similar work.
• You have included a realistic budget range.
• You have named your stakeholders and your decision-makers.
• You have set a deadline for questions and a separate deadline for submissions.
• You have stated your evaluation criteria.
• You have identified two to four qualified nonprofit Salesforce partners to invite.
• Your IT lead, your program lead, and your executive sponsor have all read it.
• You know what a winning response looks like before you send it.

If you would like a second read before it goes out, send us the draft. We review RFPs whether or not we end up bidding, and we will tell you what a partner is likely to find unclear.

What to look for in a nonprofit Salesforce partner

Look for active Salesforce Consulting Partner status, not simply an organization that uses or resells the platform. Ask whether the certifications belong to the people who will actually work on your project, rather than to the firm in aggregate.

Beyond credentials, look for demonstrated experience with the products that carry nonprofit work: Agentforce Nonprofit, formerly Nonprofit Cloud, along with NPSP, Salesforce Grantmaking, and Education Cloud. A firm that has implemented these several times moves faster and makes fewer expensive mistakes than one learning on your project.

Then ask how they have handled the parts of nonprofit work that do not fit commercial CRM patterns: program delivery, case management, constituent relationships, grant reporting, board governance. Ask for references from organizations that resemble yours in size, mission area, and complexity. And think past go-live, because Salesforce is a platform you will live in for years: the question is whether this is a firm you can grow with.

Where to find qualified firms

The Salesforce ecosystem is large. These are the places we would look, and we are listed in the first two ourselves, which is rather the point of naming them.

• Watt's List, an independent directory of Salesforce consultants and firms focused specifically on nonprofits, maintained by Watt Hamlett Consulting rather than by any of the firms listed on it.
• The Salesforce AppExchange partner finder, filtered on Nonprofit under industry competencies. You can narrow further by rating and by diverse-owned status.
• NTEN, for community referrals from people who have run the same project you are scoping.
• Peer recommendations from organizations working in your mission area. Still the best signal there is.

And whether to send it to us

Buzzbold has built Salesforce for mission-driven organizations since 2011 and has been a Salesforce Partner since 2014. We work almost exclusively with nonprofits and education organizations, across grantmaking, fundraising, program management, case management, and migrations. If your project touches any of that, we would like to receive your RFP.

Salesforce is the most configurable CRM there is, and that cuts both ways. A partner without nonprofit experience will configure it the way they know how, which is not necessarily the way your organization needs it. The result is usually recognisable: over-engineered where it did not need to be, under-configured where it did, and quietly unused.

Data models are where this shows up first. In a nonprofit CRM one contact is often simultaneously a donor, a volunteer, a program participant, and a board member. Modelling that so you can report on each relationship without creating duplicates or losing history is something experienced nonprofit practitioners do by reflex. For everyone else it is a lesson that arrives late and costs money.

The same applies to the rhythms a generalist cannot see: fiscal year transitions, grant reporting cycles, fundraising seasonality, board calendars. A managed services team that does not know those dates is always reacting. One that does gets ahead of them.

It applies to AI too, which is why we treat AI as a layer you earn rather than the headline. Agents built without an understanding of constituent relationships and community trust can undermine the very thing they were meant to help. Get the fundamentals right first; the AI work is far better on a foundation that is already trustworthy.

Do I need an RFP to work with Buzzbold?

No. Many of our engagements begin with a discovery conversation rather than a formal RFP. If you are still scoping, reach out and we will help you work out whether an RFP is the right instrument at all.

How many firms should I invite to respond to my RFP?

Most nonprofit Salesforce RFPs benefit from three to five qualified responses. Too few limits comparison. Too many creates evaluation work that nobody has time for. Favour quality: invite firms with demonstrated nonprofit Salesforce experience rather than filling a quota.

Should my Salesforce RFP include a budget?

Yes, wherever you can. A realistic range lets qualified partners scope work that is actually actionable. Without one you will receive proposals that vary wildly in scope and price, which tells you nothing about which firm is better.

What is the difference between an implementation RFP and a managed services RFP?

An implementation RFP scopes a defined project: a migration, a new product, a specific build. A managed services RFP scopes an ongoing relationship: administration, monitoring, support, and stewardship of the platform over time. Some organizations issue both at once; others sequence them.

How long should my Salesforce RFP be?

Long enough to be specific and short enough to be read. Five to ten pages suits most nonprofit Salesforce RFPs. Put detailed data or technical specifications in appendices rather than the main document.

What Salesforce products does Buzzbold work in for nonprofits?

Agentforce Nonprofit (formerly Nonprofit Cloud), NPSP, Salesforce Grantmaking, Education Cloud, managed services, and Agentforce. Our work is concentrated in grantmaking, fundraising, and program management.

How do I evaluate proposals once I receive them?

Score against the criteria you published. Common dimensions are relevant nonprofit experience, the credentials of the people actually assigned, methodology, references, total cost, and long-term fit. Run structured reference checks, and ask for a working session rather than a presentation before you decide.

Is Buzzbold a Salesforce Partner?

Yes. Buzzbold has been a Salesforce Partner since 2014, earned over roughly three years of work rather than by clicking a button, and has built Salesforce for mission-driven organizations since 2011.

We respond to RFPs for Salesforce implementations, managed services, data migration, CRM strategy, grantmaking, and Agentforce work, for nonprofits and education organizations.

Start here and tell us the shape of the project. We will confirm receipt and reply within one to three business days with a route for sending the document itself. If the scope is not right for our team we will say so, and where we can we will point you toward firms that fit better.

Every RFP we receive is reviewed confidentially and is never shared.

• Managed services, for what an ongoing relationship actually covers.
• Nonprofit Salesforce consulting, for how we implement.
• Salesforce migration, if you are moving from NPSP or an older org.