Thoughts on the utility of CRM
Customer relationship management, or CRM, is often thought of as solely a technology system. But it’s more than that. It’s a philosophy. It’s a policy and strategy of connecting different staff within an organization so as to coordinate their efforts in creating an overall valuable relationship for the constituent. It’s about breaking down silos of work and information, and creating a holistic picture of each constituent so that s/he might be better served.
In mission-based work, the “value” of that relationship is not measured in dollars, but rather in total impact that constituent has on the mission. Funds donated are a part of the equation, but there are so many other activities a constituent can undertake that add to the mission impact bottom line.
High constituent impact is best elicited by targeting that constituent with information and opportunities for action which directly suit his/her interests. Asking a millionaire for $35 is not the best way to maximize her impact on the mission, just as asking someone who is dedicated to marine mammals to lobby the government on behalf of urban farmers isn’t either.
CRM allows an organization, over time, to aggregate all the interests and traits of a constituent, and activities she has undertaken. This information is really just the artifact of a relationship that has developed over time. CRM then allows the organization, which may have staff come and go, to interact with the constituent with all the benefit of the history of that relationship. This more authentic relationship allows for more appropriate interactions, leading to two things: a constituent who feels valued by the organization, and more actions being taken.
Having a good history of a broad relationship allows an organization to work in new ways. It may be that an event coordinator has always wanted to send invites to all constituents in Oregon who have come to events in the past and have also expressed an interest in the issue of climate change. It is likely that the answer to that question has been, “we can’t get that info.” By implementing CRM across the organization, staff members can have richer data, and be much more creative in how they use it.
In a complex organization with multiple outreach channels it is nearly impossible to provide this kind of service without CRM. Add to the fact that large, complex organizations almost always have thousands of constituents, and the necessity for CRM becomes even more apparent.
Most organizations would describe their relationship with data as less than satisfying. Often it is a struggle to put data into a system, and the results never really pay off. Successful implementation of CRM requires a change in the way an organization relates to its data. By spending time up-front determining what data is important to capture, how it will be captured, and most importantly, how it will be used to add value to the mission, and organization can place CRM at its center and be ready to reap the benefits.
In addition to helping get daily work done, data on constituents and their actions can be aggregated for periodic analysis. Key metrics can be generated that tell various stories about the organization, the constituents and the outreach work being done. This big-picture information can help managers make decisions about organizational resources and efforts.
CRM at scale is very difficult to implement without a technology system behind it. If an organization has a good CRM system, it can serve as the core repository of constituent information. It is then possible to integrate a CRM system with other technology systems that address specific needs like: mass emailing, event registration, and web content publishing.
It is even possible for a CRM to integrate with a system for planning and tracking organizational goals. Activities and outreach efforts recorded in the CRM system can roll up to the strategic goals they relate to. By doing this, a constituent-centered organization can deeply embed CRM into everything it does. And if done well, it can have a significant positive impact on how rapidly the organization moves to fulfill its mission promise.

June 5th, 2008 at 11:08 am
Steve, I couldn’t agree with this more. It’s about making things that are normally invisible, visible to an organization.
June 5th, 2008 at 12:25 pm
Right on Eugene. It’s a massive topic, so I’m glad my attempt to summarize rang true for you.
June 5th, 2008 at 4:05 pm
Excellent post as usual Steve. One (of likely hundreds) of other challenges the CRM can overcome with the right technology is the concern of appropriate staff permissions (a.k.a. fiefdom). Many npo’s purposefully build or contract for a “database” that isolates their constituent focus from others within the organization (ahem, major donors) for fear of losing control. However, a good CRM implementation can support permission-based access and outreach business rules while still allowing the org to build a complete, 360d profile of every constituent.
June 5th, 2008 at 4:09 pm
Thanks Tompkins. I love turf battles! They are so much fun for everyone!
June 6th, 2008 at 9:37 am
Why are reasons that users don’t implement or fully implement a CRM system in a nonprofit? I can think of few off the top of my head….
June 6th, 2008 at 9:54 am
Ah adoption. That is a whole conversation. I’d love to hear your thoughts. We’ve been thinking a lot about that lately, and surely haven’t cracked that nut with any kind of confidence. There are so many factors at play. I’ll try to get some thoughts up about it in the next couple weeks. Or you could blog about it…you have a blog, right?
June 7th, 2008 at 11:02 am
Thanks again for this thinking brother. You know I love riffing with you on this stuff. And… Hello Eugune! Here’s some quick thoughts on why users don’t implement…
Effective CRM implementation requires culture change. Given that…
- Motivation: The design and implementation should be tied to vision and key organizational goals. Organizational leadership should understand this relationship and help staff see how the CRM will help them to better accomplish their organizational tasks leading to the overall success of the vision. Individual staffers should be able to understand how their work helps forward the whole. Connect their individual contribution to the success of the whole. MAKE IT FUN!
- Behavior: Your process mapping is key here Steve… How will the way staff do their work change? This is all about working smarter. Outreach, event planing, campaign strategy, evaluation… how will having a CRM aid these processes. Break it down and help people understand how their day to day tasks/processes will change. Create some projects that demonstrate this… support staff to be successful. Build momentum. Communicate successes to the organization. Take more on each time in a step wise manner. Don’t overwhelm.
- Systems: What organizational processes and systems should change/tweak as a result? Are there barriers to implementation? Don’t take too much on at once… take things on in manageable chunks with adequate resources… prioritize and approach step wise. Organizational planning, campaign planning, event coordination, development campaigns… look into the nooks and crannies of the organization and ensure that the required systems and structures are in place to ensure the adoption is successful. Reward people for successes. Support them to change.
Let the force be with you!
xo, j
June 7th, 2008 at 12:52 pm
Thanks Jodie! I love getting to tap your deep expertise about organizational change. Change really is an Art, isn’t it?