The Situation

This is a national membership organization with a complex constituent base. They have members who pay dues. They have members who purchase benefits (some paid, some included). They have donors who give money. They have chapters, national and international, each with their own membership structures. They have a community platform facilitating engagement.

On the surface, they had technology to handle all of this: a CRM for members, a separate donor management system, a portal where members purchased and accessed benefits, spreadsheets for chapter management, a community platform, a public website that tied it all together. Over 30,000 active recurring subscriptions flowed through the portal every month.

The problem: none of it talked to each other.

Nobody knew if John Smith in the donor database was the same John Smith in the member CRM. Nobody knew which members actually used which benefits, over what time period, or how their usage changed year to year. Nobody knew which members were also donors. Nobody could see chapter membership and activity in one place.

Leadership couldn't answer basic questions: Which benefits drive engagement? Which members are at risk of not renewing? Which constituents should we communicate with differently, based on their relationship with us?

The organization was flying blind with data.

Why It Mattered

You can't make smart funding decisions about which services to expand or retire without knowing if anyone's using them. You can't justify program investments to funders when you can't show adoption rates or engagement trends.

More immediately, communication was broken. A long-time, high-dollar donor who was also a member was getting the same "welcome to our community" email as a brand-new member paying their first dues. The organization was manually pulling donor lists and member lists, cleaning them, and sending separate campaigns every month - work that was error-prone and unsustainable.

There was also an operational constraint: the website and portal were well built and stable, supporting those 30,000 recurring subscriptions. They couldn't be disrupted or replaced.

The organization needed to see their constituents clearly. They needed to make decisions based on data. And they needed to do it without touching systems that were working.

The Challenge

This wasn't a "pick a new CRM and migrate" situation. The problem wasn't any single system. The problem was that multiple systems existed in isolation.

A monolithic, all-in-one platform wouldn't have worked. It would have required replacing the portal that thousands of transactions ran through every month. The solution had to work within the constraints of systems that couldn't change.

What We Did

Instead of consolidating everything into one platform, we built a stack.

Wicket became the system of record for membership and donor data. Not because it does everything, but because it's designed to integrate with best-in-class tools instead of trying to be best-in-class at everything.

The billing and accounting layer was separated from the membership data. Years of custom work had tacked it onto the old CRM, and it needed to be decoupled.

The portal connected directly to Wicket, pushing day-to-day membership and benefit data into a single source of truth. When a member accessed a benefit, that interaction now flowed back into the core system.

Metabase connected to Wicket as the reporting layer. Questions that previously required weeks of manual work, or were simply impossible to answer, now took minutes.

A dedicated data project unified 40+ years of member history, cleaning and deduplicating records so that the organization could see relationships clearly.

Throughout, we focused on one thing: making sure staff could do their jobs better, not worse. Training, clear communication, and proper support during the transition were as important as the technology itself.

What Became Possible

Leadership could now ask questions that previously required weeks of manual work or simply weren't answerable:

• Which benefits drive the highest engagement? Which members renew after using them?
• How has member usage of services changed over the past three years?
• Which communication strategies actually move people to action?
• What are the demographics and regional preferences of our members, across benefits and engagement?
• Does high engagement in our community platform translate into higher usage of services?

Funding conversations changed. When the organization went to funders to ask for investment in a benefit or program, they had data showing adoption rates, engagement trends, and impact on member retention.

Operations changed. Communications became targeted and relevant instead of generic and frequent. Staff could make decisions about program priorities based on actual usage patterns instead of guesses.

Email campaigns can now segment by member and benefit data. Full segmentation by donor type and chapter leadership is coming in the next phase - the infrastructure is ready, but there's more data work to do.

Most importantly, the organization can start to see their constituents clearly. They can understand who these people are, what they care about, and what services matter to them - and they can make decisions, about funding, about programs, about communication, based on that clarity.

The Lesson

This organization didn't need a full technology overhaul. They needed strategic thinking about which systems should talk to which other systems, and why. They needed infrastructure that could grow and change without breaking the parts that were already working.

The answer wasn't "pick one platform to rule them all." The answer was "think clearly about what data needs to flow where, then connect systems that are good at their specific jobs."

That kind of clarity - about data, about architecture, about what questions you actually need answered - is what makes the difference between organizations that are held hostage by their systems and organizations that use their systems to lead.