Nonprofits are not short of software. They have a donation page, a payment gateway, an email tool, a spreadsheet for volunteers and another for the appeal, and every one of those was a sensible decision on the day it was made. What none of them do is hold the relationship, because a relationship is exactly the thing that falls between tools.
The general-purpose CRMs that could hold it are built around a sales pipeline, where a contact moves forward until they either buy or are disqualified. A donor does not behave like that. A donor gives, then volunteers, then goes quiet for a season because their circumstances changed, then comes back further in than before if somebody noticed. Ask a sales pipeline to model that and you get a stage list nobody in the organisation is willing to update.
So the structure came first. One record for a person, holding both the money and the time they give. Then the scoring, built on behaviour instead of the calendar, because the calendar is what made the eleven-year donor invisible. Then the suggested action, because a flag without an instruction is just a new source of guilt for a team that is already stretched. Then the reporting, because the report is what would have prevented the whole thing.
The visual language of the product came out of the same argument. A donor base is not a funnel and it is not a deal board. It behaves like a planted bed: things grow when they are attended to, they wilt quietly when they are not, and the wilting is visible long before the plant is gone if anyone is looking at the bed rather than at the total.