Individual Giving Program Design for Nonprofits
Small and mid-sized nonprofits funded mostly by grants and government contracts get told the same thing: build a major gifts program, the board will introduce you to people. It rarely works. Major donors are not introduced, they are developed — they come up through an organization's own individual giving program over a period of years, and if that program does not exist there is nothing for an introduction to land in.
This engagement designs the program around what you are already doing. Most organizations have far more individual connection than they count: a direct mail list that has been running for decades, event registrations, program alumni, volunteers, social media followers, a newsletter nobody thinks of as fundraising. The connection can be five different ways at once. The work is to catalog all of them, define the stages between a first gift and sustained support, and build the ramp that carries someone from one stage to the next instead of leaving them where they landed.
Then the engagement ends where a ramp either runs or quietly stops: the technology. You leave with a specific recommendation for what to operate this on — the systems you already have, each given a clear job, knitted together at the seams, usually with a small custom piece or two rather than a new platform. That last part is more affordable than most boards assume, and worth understanding before the next migration gets proposed.
Signs this is the work
- Most of your funding is grants or government contracts, and everyone on staff knows how fragile that is.
- The board has been asked to introduce you to major donors, and it has produced a few meetings at best.
- Thousands of names sit across mailing lists, event registrations, and program records with no way to move any of them anywhere.
- One development person does everything, and individual giving loses to the grant deadline every time.
- Gifts arrive, get thanked, and stay one-time.
How the engagement runs
- 01
Connection inventory
We catalog every touchpoint a person already has with you and can be reached back through — the mail list, event registrations, program alumni, volunteers, the newsletter, the social accounts, the donation page — and note how many people each one holds, what it currently asks of them, and whether anyone follows up.
- 02
Ramp definition
We define the stages between first contact and sustained support in CARE terms, so moving someone from here, to here, to here becomes a written path rather than an instinct held by whoever has been at the organization longest. Each stage gets a definition somebody can apply to a real record.
- 03
Advancement moves
The specific follow-ups, invitations, and asks that move a person from one stage to the next. This is donor cultivation and moves management, sized to the team you have rather than to the development department you do not.
- 04
Tooling and rhythm
Which of your existing systems tracks which part of the ramp, where the signals that trigger a move actually live, and what has to be built to connect them — usually a small custom piece rather than a new platform, since purpose-built software has become cheap enough for a nonprofit to commission. Then the weekly rhythm on top of it: what a one-person development shop looks at, and what to do when a signal fires.
What you get
- A catalog of every existing connection surface, with its size and its current ask
- A written stage model of the giving ramp, from first gift through recurring giving to major support
- An advancement playbook of the moves between stages, and the weekly rhythm for running them
- A technology recommendation: what runs the ramp across your current systems, which custom connectors are worth building, and roughly what they cost
The engagement is mostly Advance: giving the organization a way to think about moving a supporter from here, to here, to here. Connect supplies the surfaces people arrive on, Relationships is what keeps them present between gifts, and Exchange is where sustained support finally shows up. Even well-staffed development shops tend to have all four pieces and no framework for the movement between them — and no system that can show where a given person currently sits.
See the CARE frameworkQuestions we get asked
- Shouldn't our board be introducing us to major donors?
- Board introductions are a bonus, not a program. When they do work, it is usually because the person being introduced already had some connection to the organization or the cause. Major donors overwhelmingly come up through an organization's own individual donor program — a first gift, a second, a recurring commitment, a conversation — over years. A major donor pipeline that depends entirely on board members knowing wealthy strangers is not a pipeline. Build the individual giving program first and the introductions have somewhere to land.
- We only have one development person. Is this realistic?
- Capacity is the design constraint, not an objection to the work. This used to be person and relationship based, and it took a team: a major gifts officer carrying a portfolio, someone on annual giving, someone on events. Most organizations no longer have that and are not going to get it. The framework substitutes structure for the missing role — a written ramp and a small number of defined moves — so advancement does not depend on a specialist you cannot hire. Anything the current team could not run in a normal week does not go in the plan.
- Is this just moves management?
- It is the same instinct, yes. But moves management assumes a development department, a portfolio per officer, and a CRM already configured to track it. This starts from what you actually have — the mail list, the event, the program roster — and designs the engagement ladder around those surfaces and one person's real capacity. Put another way: a major gifts consultant starts at the top of the ladder and works the donors already near it. This builds the ladder.
- Do we need a new CRM or fundraising platform for this?
- Usually not, and the recommendation is usually to keep what you have. A migration costs real money, eats most of a year, and tends to move the same problems into a nicer interface. What has changed is the economics underneath the question. Building a small, purpose-built piece of software — a connector that keeps your mail platform, your event tool, your CRM, and the spreadsheet somebody actually maintains in agreement about who a supporter is and where they sit on the ramp — used to require an enterprise budget. It does not anymore. Work at that scale is now genuinely in reach for a small nonprofit, it typically costs less than a migration, it disrupts nothing your staff already know how to use, and it gets built around your ramp instead of around a vendor's assumptions about how fundraising works.
Often paired with
- Mission Growth Map
Nonprofit Donor Journey and Engagement Strategy
A map of the journey across participants, staff, volunteers, donors, partners, and funders — and where it breaks.
- Mission Surface Review
Nonprofit Website and Digital Experience Audit
A structured review of the website, forms, donor journey, program touchpoints, and technology behind them.
Not sure this is the right starting point?
Most organizations sit across two or three of these at once. A short conversation usually surfaces which one to start with — and it is fine to arrive with the problem rather than the engagement.