A national wildlife conservation nonprofit had invested in Microsoft Dynamics 365 CRM seven years ago. Their development team never adopted it. Multiple consultants had tried to launch CRM-based workflows. Each attempt failed. The system had 498,000+ accounts, 42,000+ confirmed duplicates, and over-customized forms from a prior consultant that didn’t match how the team actually worked.
We started with the people, not the technology. We spent time understanding how the development officers actually track relationships and proposals. We mapped their real workflow into six process stages and validated it with the team before we touched the system. Then we stripped away the over-customization. We used out-of-box Dynamics features: Business Process Flows, filtered views, dashboards. We identified two pilot users who would champion the system instead of forcing adoption across the entire team. We created “firewall” views so the development team sees only their 50-100 organizational funders, not the full 498K accounts.
The CRM now matches how the team actually works. Adoption is driven by the users who need it most, not mandated from the top. The prior consultant built impressive customizations nobody used. We built simple configurations people actually use. This is what “People first, then process, then technology” looks like in practice.