Christine Gomez
Senior Consultant
Robin Balfanz
Consultant
You’ve completed your system selection, negotiated the contract, and signed on the dotted line. What comes next is harder.
A system implementation is a fundamentally different kind of project than a system selection. Where a selection is about deciding, an implementation is about doing. It requires different people, different rhythms, and different kinds of accountability. Organizations that carry over the same team structure from selection to implementation, without revisiting who needs to be involved and why, often find themselves underprepared for what the work demands.
Here is what to know about building the right core team for a successful implementation.
Start with Your Goals, Not Your Org Chart
Before you can determine who should serve on your implementation core team, you need to be clear about what a successful implementation looks like for your organization.
Some organizations define success as data accuracy: all historical gift records, donor relationships, and fund designations are migrated correctly and are accessible from day one. Others prioritize functional readiness: specific modules—membership, ticketing, major gifts—are fully configured and usable at launch. Still others focus on adoption: staff are trained, confident, and using the new platform within the first weeks.
Most implementations involve all these goals to some degree. The question is which ones carry the most organizational urgency, because the answer determines who needs to be on the core team. If data accuracy is paramount, you need strong representation from whomever owns those data sets. If a specific functional area must be live and operational on day one, the person who oversees that area needs to be actively involved throughout configuration and testing.
This is not a hypothetical exercise. Naming your success criteria before core team formation helps you build a team that is equipped to deliver.
Who Should Be on the Implementation Core Team
The Project Lead
The project lead from your system selection should, in most cases, continue in that role through implementation. This person brings institutional knowledge of why certain decisions were made, has the organizational authority to hold people accountable, and serves as the primary internal advocate for the project. Continuity here matters.
Data Integrity Lead
Your data integrity lead, whoever is responsible for keeping your constituent database clean and consistent, is among the most important members of an implementation core team. This person understands what the data means, how it was entered, where the inconsistencies live, and how it needs to map to the new platform. They often serve as a translator between the technical requirements of the vendor and the practical realities of the organization’s data.
Functional Area Owner
Functional area owners are where implementation core teams often differ most from selection teams. Rather than generalists who can speak to broad organizational priorities, implementation core teams need people who can go deep into their specific area—who understand the data, the workflows, the exceptions, and the use cases. This might include the gift processing manager, prospect management lead, membership coordinator, or event registration team, depending on what systems you are implementing and what must work correctly at launch.
Reporting and Analytics Keeper
Someone with strong reporting and analytics knowledge should also be represented. Data migration is only valuable if the new platform can surface data in ways that inform fundraising strategy and organizational decision-making. Involving someone who understands your reporting needs early (rather than an afterthought after configuration is complete) dramatically improves the quality of what you get at launch.
Project Manager
A project manager on the client side is worth considering carefully. Your vendor will drive the implementation timeline and manage their own deliverables. But someone needs to own the client-side logistics: tracking action items, ensuring materials are reviewed on schedule, coordinating stakeholder availability, and flagging when deadlines are at risk. If your team does not have bandwidth for this role, a consulting partner like Benefactor Group can provide this capacity—and bring the added perspective of managing not just the primary CRM timeline but also any adjacent integrations (payment processors, email platforms, event tools) that need to be ready at launch.
The Right Size: Four to Six People
We recommend four to six people for an implementation core team. Beyond that, scheduling becomes a recurring obstacle, decision-making slows, and it becomes harder to maintain the focused accountability that implementation requires.
If your organization’s structure means that more than six people genuinely need to be involved in implementation decisions, consider creating a two-tier model: a core team that manages day-to-day project work and a steering committee that includes broader functional representation, meets less frequently (typically monthly), and focuses on progress reporting, issue escalation, and organizational readiness. The steering committee members are often the people who will lead training and adoption within their departments, making them valuable channels between the core team and the rest of the organization.
Accountability Is Not Optional
Implementation projects fail or go significantly over budget and timeline most often not because of technology problems, but because of accountability problems. Deliverables slip. Reviews don’t happen on time. Testing gets deprioritized when other demands arise.
Weekly check-ins for the core team are strongly recommended, particularly during active phases of configuration, data migration, and testing. The weekly cadence is not busywork but a forcing function. When team members know they will be reporting on progress each week, action items stay front of mind. When check-ins become bi-weekly or monthly, things fall through.
The project lead needs to have the organizational standing to hold people accountable. If a separate project manager is used, they must be empowered to report delays or issues directly to the project lead, who then uses their standing to resolve them. In addition, the executive director or CEO needs to visibly reinforce that implementation participation is a real organizational priority, not something team members can deprioritize when other demands arise.
Make Time Before You Run Out of It
One of the most consistent challenges in implementation projects is that the people who need to be most engaged are also the people whose schedules are least flexible.
The solution is not to replace these people on the core team. It is to protect their time deliberately. Implementation participation, whether that means attending weekly check-ins, reviewing configuration documentation, completing user acceptance testing, or attending training sessions, should be treated as an organizational priority and reflected in workload planning, not layered on top of an already full schedule.
Where internal capacity is genuinely constrained, outside partners can absorb meaningful portions of the work: building training curricula and end-user documentation, facilitating user acceptance testing sessions, managing integration timelines, and handling the project management overhead that otherwise falls to already-stretched staff.
Your Investment Deserves the Right Team
A system implementation represents not just a significant organizational investment of money and resources, but also of the overall strategic direction. Organizations that realize the full value of this investment are almost always the ones that are intentional about who is on the core team, clear about what success looks like, and disciplined about protecting the time and accountability the work requires.
If you’re preparing to move into implementation or want to assess how your current team and timeline are set up for success, we’d welcome the opportunity to connect. Benefactor Group has supported nonprofit organizations through system selections and implementations of all sizes, and we’re glad to share what we’ve learned.