What makes a nonprofit CRM implementation different from a commercial one, and how does that change your approach?

Two structural differences drive almost every design decision, and I raise both in the first discovery session.

1. The same person plays several roles at once. A constituent can be a donor, a volunteer, a programme participant and a board member simultaneously, and those roles are not mutually exclusive the way a lead and a customer are. That is why Nonprofit Cloud invests in relationship objects rather than assuming one person equals one record type.
2. Money arrives with strings attached. Restricted gifts, grant conditions and reporting obligations mean the system has to answer “how much of this may we spend on that”, not just “how much came in”. The gift designation model exists for this reason, and getting it wrong is an audit problem, not a reporting inconvenience.
3. Practically, that changes sequencing: I settle the constituent and designation models before configuring anything user-facing, because fundraising, programmes and outcome measurement all hang off them.
4. It also changes stakeholder work. Finance has a real veto on the designation design, and programme staff — not just fundraising — need to be in the room, because their data feeds the impact reporting the funders will read.