David, you've nailed it. I guess the problem is that ChMSs are notoriously bad with interoperability in my experience and want to keep the data within their bl

David, you've nailed it. I guess the problem is that ChMSs are notoriously bad with interoperability in my experience and want to keep the data within their black box. A separate engagement tool would be fairly impotent if it was separate and had no way of accessing the membership database. Viable solutions for churches tend to be afterthought bolt-on modules for their existing ChMS, which is a shame. My dream would be for ChMS vendors to agree on a standard API for exchanging member information. But I'm afraid hell might freeze over before I see something like that. Out of necessity, a good church engagement tool may have to be also a ChMS as well.