Your Salesforce implementation will shape how your team works for years. A good consultant sets you up for long-term success. A bad one leaves you with a system nobody understands, nobody uses and nobody can fix without paying for more consulting hours.
Choosing the right partner is one of the biggest technology decisions your nonprofit will make. Here's how to do it well.
Why it matters more than you think
A failed Salesforce implementation wastes money, and it also wastes time, wears down your team's trust and leaves you with a system that works against your mission. I've seen nonprofits spend six figures on implementations they had to tear down and rebuild because the original consultant didn't understand their workflows, their data or their capacity.
The rebuild always costs more than doing it right the first time.
Red flags to watch for
Not every consultant who lists "nonprofit experience" on their website actually has it. Here's what should give you pause.
They don't ask about your mission or how you work. If the first conversation is about features and licenses instead of how your team actually works, that's a problem. Your CRM should serve your mission.
They push a template solution. "We'll set you up with our standard nonprofit package" sounds efficient. But every organization is different. Your donor management, program tracking and reporting needs are specific to you. Cookie-cutter setups create cookie-cutter problems.
They can't explain things in plain language. If your consultant talks only in Salesforce jargon and can't translate it into language your program staff understand, they're going to build something your team can't use.
They build things only they can maintain. This is the biggest one. If your consultant creates complex automations, custom code or intricate configurations that need their ongoing involvement to keep running, they've built themselves a recurring revenue stream.
Green flags that signal a good fit
They start with discovery. A solid consultant spends real time understanding your organization before proposing anything. They want to see your current processes, talk to the people who'll use the system and understand what success looks like for you.
They give you clear scope and pricing. You should know what you're getting, what it costs and what happens if things change. Vague proposals with open-ended timelines lead to budget overruns.
They train your team. Implementation without training is just installing software. Your team needs to understand how to use the system and why it's set up the way it is.
They have real nonprofit experience. Working with NPSP, Nonprofit Cloud, Program Management Module, grants tracking and donor management is very different from setting up Sales Cloud for a tech company. Make sure your consultant has done this work before and can prove it.
Questions to ask before you sign
Keep this list handy while you compare consultants:
- What's your experience with NPSP, Nonprofit Cloud and nonprofit organizations specifically? Look for concrete examples.
- Will I work with the same person throughout the project? At larger firms, the person who sells the work often isn't the person who does it. Handoffs mean lost context.
- How do you handle scope changes? Projects evolve. You want a consultant who's open about what's in scope, what's not and what changes will cost.
- What does handoff look like? When the project ends, what do you walk away with? Documentation? Training? A system your team can actually manage?
- Can I talk to past nonprofit clients? References matter. Ask about communication, timeline accuracy and support after the project.
Build to hand off
This is the principle I care about most: your consultant should build something your team can run without them.
That means using standard Salesforce features wherever possible: Flows instead of Apex code, configuration over custom development, clear documentation and thorough training. Your team should be able to manage, change and grow the system after the engagement ends.
Finding the right fit
At Datawake, these principles guide every engagement. You work directly with me from discovery to handover, with no junior staff learning on your project. Every build is designed for your team to own, and every scope spells out what's needed and what it costs.
If you're comparing consultants and want a straightforward conversation about your Salesforce needs, reach out. I'll give you a straight answer about how I can help.