Duncan Rein, CEO of Silas Partners, posts here regarding how CRM (Constituent Relationship Management) should be and inevitably will be fully integrated with the church’s website. This is further fuel for our previous discussion with Tony Dye and others about Church Management Systems (ChMS) and Content Management Systems (CoMS).
To put it in concrete terms, at Resurrection we’re using TYPO3 for content management and Shelby for church management/CRM. I’m in agreement that ultimately we need to: A) integrate the two; or B) replace both with something else already integrated; or C) develop an open source church management/CRM that we can natively integrate with TYPO3. Right now we’re working on option A, but somewhat reluctantly since this is inelegant and it’s difficult to see how well it will work over the long term. Option B isn’t a great one for us because we’re fully committed to TYPO3 and Web Empowered Church. That leaves option C, for which my heart yearns, but we can’t pursue because we have no funding or interest among executive management here.
Hmmm … Maybe we take Tony’s suggestion and sneak this in the back door by gradually building a CRM/ChMS in the form of TYPO3 extensions?