MemberVerify update

In March, I posted "I Fixed the Association Database Problem." It's been a few months, so here's an update.

Back then, MemberVerify already worked, and I knew it could help nonprofits clean their databases and increase revenue. Since then, my goal has been to improve the program, cut costs, and strengthen security.

Here's an update on each.

Program and Costs

These turned out to be the same job. My number one goal is to make this affordable for nonprofits on a tight budget, without giving up quality.

In March, MemberVerify leaned on third-party databases, with AI doing the heavy lifting on everything else. It worked, but it was slow and expensive. So I dumped the databases and built a multi-model agentic engine that researches each contact in real time, running simple models for the easy calls and heavier ones when it gets hard.

AI only does research. Decisions are made by fixed rules, hard-coded into the program, built on a few hard-won principles:

The result is a stronger system at a fraction of the cost. It only spends real horsepower on hard cases, so it runs for far less than before, and that goes into lowering your price.

Security

Data is sacred, and I know that as well as anyone. In 23 years, I never sold my contact data, gave registration lists to sponsors, or bought data for my own use. I hold yours even more closely. Here's how.

None of this is a box I check. For membership organizations, trust is the entire asset, and I protect your data like it's my own. For 23 years it was.

If your organization is fighting this, I'd love to help. Reach out anytime.

Back to all posts