The best Salesforce nonprofit consultant is the one who understands your programs first, scopes the work in writing, and leaves your team able to run the system without them. Technical skill matters, but it is rarely what separates a good project from a regretted one. Clear scoping, relevant experience, honest references and a real handover do.
We are a Salesforce consultancy, so we have an obvious interest here. This guide is written the way we would want a board member or executive director to evaluate any firm, including us. Use the questions with every candidate and compare the answers.
Start with your own homework
A consultant can only be as good as the brief you give. Before you talk to anyone, write down:
- The problem. "Our case managers re-enter data in three places" is a better brief than "we need Salesforce."
- The users. How many people, in which roles, with what technical comfort.
- The data. Where it lives today and how clean it is.
- The constraints. Budget range, deadlines such as a grant start or fiscal year, and compliance needs such as health information.
- The decision-maker. Who signs off, and who will own the system afterward.
If you cannot answer these yet, a short discovery engagement can help. Be wary of anyone who promises a firm plan before asking any of them.
Questions about scoping
Scoping is where most projects are won or lost.
How do you define the scope, and what is written down? Look for a document that lists deliverables, assumptions, what is out of scope, who does what, and how changes are handled. If scope lives only in a sales call, expect surprises.
What do you need from us, and how much staff time should we plan? Projects stall when the nonprofit's side is underestimated. A good consultant will tell you plainly how many hours your team will spend on decisions, testing and data cleanup.
How do you handle change requests? Every project changes. The question is whether changes are priced and agreed before work happens.
Who will actually do the work? Ask whether the person you meet is the person who builds. Subcontractors are not a problem in themselves, but you should know who they are.
Questions about NPSP and Agentforce Nonprofit experience
The Salesforce nonprofit landscape has two main tracks, and a consultant should be able to discuss both with you.
The Nonprofit Success Pack (NPSP) is the long-standing managed package that many nonprofits use. It is still supported, but it no longer receives new features and Salesforce has announced no end date. Agentforce Nonprofit (formerly Nonprofit Cloud) is the newer product where Salesforce is investing. You may also hear the term "Nonprofit Cloud consultant," and it is worth asking whether a consultant has delivered projects on the product itself or only studied it. We compare the two in Nonprofit Cloud vs NPSP and answer the common worry in Is NPSP going away?.
Questions to ask:
- Have you implemented on both NPSP and Agentforce Nonprofit? Experience on one does not transfer fully to the other, because the data models differ.
- What would you recommend for us, and why? A good answer depends on your situation. Be cautious of a firm that recommends the same thing for everyone, whether that is staying on NPSP or moving.
- What are the tradeoffs? An honest consultant will name downsides of their own recommendation.
- Have you handled data migration at our scale? Ask about duplicates, history and what typically gets left behind.
If you are also weighing other systems, an even-handed starting point is nonprofit CRM software compared. A consultant who only ever recommends Salesforce deserves a follow-up question about when it would not be the right fit.
Questions about your specific work
Salesforce is a platform, and nonprofit needs vary widely. Match the consultant to your use case:
- Fundraising and donations. Ask how they model gifts, recurring donors and soft credits. See Salesforce donation management for what good answers sound like.
- Grants. Ask about tracking applications, awards, deliverables and reporting. We cover the topic in grant tracking in Salesforce.
- Case management and health programs. Ask about client records, referrals and consent.
- Sensitive data. If you hold health information, ask how they handle access, encryption and Salesforce's Business Associate Addendum. A good consultant will not call Salesforce simply "HIPAA compliant"; they will explain that coverage depends on the services in your agreement and your configuration. Our overview is in Salesforce HIPAA BAA.
Questions about references and proof
Can we speak with two or three past clients similar to us? Ask for organizations of similar size and complexity, and then actually call them. Ask what went wrong, how it was handled, and whether they would hire the firm again.
Can we see examples of your documentation? Process maps, data dictionaries and training materials show how a firm works better than a slide deck does.
What credentials do you hold? Certifications held by individual consultants can be verified through Salesforce's credential system. Be careful with vague phrases about relationships with Salesforce, and ask exactly what a claim means and how you can check it.
What happens when a project goes badly? Everyone has had one. The answer tells you about honesty and process.
Questions about handover and training
A system is only valuable if your staff use it and someone can maintain it.
- What training do you provide, and for whom? Look for role-based training, not a single recorded demo.
- What documentation will we own? You should receive configuration notes, a data dictionary and admin guidance.
- Who administers Salesforce after launch? Some nonprofits hire an admin, some train a staff member, and some keep a consultant on a support arrangement. All are valid. Choose deliberately.
- Will you work in our org the way we can maintain it? Prefer standard configuration over unnecessary custom code, and ask the consultant to explain any custom work.
- Do we keep full ownership of our Salesforce org and data? The answer should be an unqualified yes.
Fixed price, hourly, retainer: how pricing models compare
We will not quote prices here, but it helps to understand the common models.
- Fixed scope. You agree on deliverables up front. This gives budget certainty but depends on a clear scope. Poorly defined scope leads to disputes or change orders.
- Time and materials (hourly). You pay for hours worked. It is flexible when requirements are unclear, but you need a way to track progress and cap spending.
- Retainer or managed support. A recurring arrangement for ongoing changes and admin help. It works well after launch, if you agree what is included and how requests are prioritized.
- Phased. A discovery phase first, then a build with a clearer scope. Many nonprofits find this lowers risk.
No model is automatically best. What matters is that the model fits how well your requirements are understood, and that the contract says what happens when estimates change. Also ask what Salesforce itself costs for your licenses and add-ons, and get that answer from Salesforce, since eligibility and terms vary. We discuss that in Is Salesforce free for nonprofits?.
Red flags
- A fixed plan before any discovery. Nobody can responsibly scope a project they do not understand.
- Pressure to sign quickly, or a deal that only exists this week.
- Vague scope and no written assumptions.
- Reluctance to share references, or references that are all unrelated to your work.
- Overpromising. Phrases like "no problem, Salesforce can do anything" skip the tradeoffs.
- No mention of your staff's time, training or adoption.
- One answer for everyone, including a push toward custom builds when standard features would work.
- Unclear ownership. Anything that suggests you will not control your own org, data or documentation.
- Dismissing security questions. Access control and data protection should come up early, not as an afterthought. If you want a sense of what to expect, see how to find over-permissioned users in Salesforce.
A simple way to compare candidates
Ask each firm the same ten questions, take notes, and score them on a one to five scale for scoping clarity, relevant experience, references, handover plan and fit with your team. Include "would our staff enjoy working with them?" It matters more than people expect.
Frequently asked questions
How do I find a Salesforce nonprofit consultant?
Start with referrals from peer organizations, then check consultant listings and Salesforce community groups. Interview at least two or three firms using the same questions.
What is the difference between a Salesforce consultant and an admin?
An admin maintains your org day to day. A consultant designs and builds larger changes, such as an implementation or migration. Many nonprofits use both, in-house or outsourced.
Do I need a Nonprofit Cloud consultant or an NPSP consultant?
It depends on which product you use or plan to use. Ask any candidate about both, and about how they would help you decide between them.
Should I choose a big firm or a small one?
Neither is automatically better. Larger firms may offer more breadth, and smaller ones often offer more direct access to senior people. Judge by relevant experience and references.
How long does a Salesforce nonprofit project take?
It varies widely with scope, data quality and how fast your team can make decisions. A good consultant will give a range and explain what could change it.
Should we hire a consultant or learn Salesforce ourselves?
For small, simple setups, a capable staff member with training can go far. For migrations, sensitive data or complex programs, outside help usually reduces risk. Many organizations do both.
Talk it through with us
If you are choosing between consultants, or want a neutral view of your current setup first, we are happy to look at your org and share what we see, with no obligation. Book a free Salesforce health check.