I work for a Christian not-for-profit called the City Bible Forum. We create opportunities for city workers to learn about Jesus: who is he, and what are his claims. For many, this is their first opportunity to do so.
We are not a church, but are more like an advocacy group.
CiviCRM is a good fit for us ...
- A complete solution - the beauty of CiviCRM is that it brings together all our contact information into one place
- A growing solution - the CiviCRM team have an uncanny knack of knowing our pain-points and adding features for which we have an emerging need.
Features we use ...
- Relationships - for us relationships with individuals are key.
- Custom data - we use flags on relationships to measure how that relationship aligns with our strategies
- Events - we organise events for ourselves and run them on behalf of other organisations.
- Mailings - these are essential for communicating with our stakeholders.
- Groups - internally we refer to these as 'lists'. We used the 'word replacement' facility to change our UI. (Internally, we use the word 'group' to mean a bunch of people who regularly meet, and the standard term 'group' was causing confusion.)
- Contact types - it's really handy to be able to create contact types that represent structures in our organisation (eg, a team)
- Contributions - being able to process donations and event fees online is a fantastic time-saver
Features we are "growing into" ...
- Campaigns - we are starting to use these for fund-raising and for getting people involved in our programs. Looking forward to 3.4 and subsequent improvements in this feature.
- Cases - some people, after looking at the evidence, are convinced that they should follow Jesus, and we feel we have a special obligation to help them in that. We feel that Cases offer the possibility of improving the quality of our service in this regard, so we're currently looking at this.
As we are a small outfit, we can't contribute significantly to the financing of CiviCRM's development, so I try to 'give back' by being active in the forums and in testing.
Ken West