As cap10morgan noted in a recent blog, non-profits and open source solutions are a natural partnership. CiviCRM has been a fabulous gift to the organization that I lead, Trinity Episcopal Church. It allowed us to move from a FileMaker database accessible only to our office staff to a robust solution accessible to most of our membership. (We constantly remind ourselves that not everyone's online!) We are still using a FileMaker/CiviCRM hybrid solution however and CiviPledge is our roadblock.
Pledge accounting is central to our contribution accounting - 92% of our income is from pledges. Is your organization's income weighted toward pledges? Do you use CiviPledge? If not, what's missing for you? Join the discussion on our forums or edit the specification on our wiki page.
For us there are two deal breaker features missing:
CiviCRM's target users are non-profit organizations. I have to believe that there isn't an organization in our user base that wouldn't simply say "thank you" to a pledge payment that was "short" of the expected amount. I have even more confidence that a payment exceeding the expected amount would be just as acceptable! Our current model in CiviPledge only accepts a payment amount of
Pledge/n for Pledges with "n" payments.
We are working around this issue by recording Pledges in CiviCRM, but then posting pledge payments to CiviContribute using a defined contribution type of Pledge. We then export Contributions and Pledge data to FileMaker, which links the two data sets, calculates pledge balances, and prints reports. This means that our online users can see their contributions on their CiviCRM dashboard, but not their pledge balance.
I'm beginning to think that what CiviPledge needs is a development roadmap, adding a couple critical features each release. Now you know what I would add next... what's important for you? Join in the process today and help us build a better solution!!