How to Manage Donors, Volunteers, and Fundraising for Nonprofits

Nonprofit development is four jobs duct-taped together, and most of the people doing them learned on the job. The annual fund runs on a calendar — year-end appeal, spring renewal, summer dormancy. Major gifts run on relationships — a discovery meeting in March that turns into a $250K ask in November if you don't drop the thread. Recurring monthly giving runs on payment processors and cancellation-save flows. Planned giving runs on a 15-year horizon and a will. Each of those programs has a different cadence, a different reporting metric, and a different donor psychology, and the dev director is supposed to keep all four humming while the board treasurer asks why fundraising costs went up.

Then there are volunteers. The ones who show up every Tuesday for fourteen years and the ones who flake the morning of the gala. Skill-matched volunteer placement is the difference between a retired CFO doing real pro bono work and a retired CFO stuffing envelopes for three hours and never coming back. Recognition cadence — a thank-you note, a holiday card, a name in the annual report — is the difference between a 30% retention rate and an 80% one.

And then it's gala season. Four hundred guests, fifty auction items, table-sponsor logos that have to be rendered correctly on the program, a silent-auction app that crashes at 8:47 p.m., and a board chair who wants the post-event acknowledgment letter in donors' mailboxes within 72 hours. The dev director who knows their top 50 donors by name plus last conversation plus likely next ask is the dev director who hits annual goal. The software is just the memory aid — but a dev director without that memory aid is a dev director who forgets that the Hendersons gave $50K last December and asks them for $1,000 in May.

This is a five-step playbook for managing the four programs, the volunteers, the gala, and the board pack with one nonprofit management software platform instead of seven. It assumes you are running lean — one or two development staff, a board that wants real reporting, and donors who can tell when you're using a generic CRM that doesn't understand soft credit, in-kind gifts, or memorial donations.

The first segmentation every dev director needs is LYBUNT and SYBUNT — donors who gave Last Year But Unfortunately Not This year, and Some Year But Unfortunately Not This year. The first list is your renewal program. The second is your reactivation program. They are not the same email and they are not the same ask. A LYBUNT got a tax receipt in February and is statistically likely to renew if asked twice between September and December. A SYBUNT lapsed two to five years ago and needs a re-introduction — what the org did with their last gift, what changed, why now.

The second segmentation is by giving level and capacity. A $50 donor who gives every month is a sustainer and goes into the recurring program. A $5,000 donor who gives once is a major-gift prospect and goes into moves management — the discipline of moving a prospect from identification to cultivation to solicitation to stewardship through a tracked sequence of meetings, letters, tours, and small asks. Every major gift in your pipeline should have a current move assigned, a next move scheduled, and a probability and dollar amount attached. If you have 80 prospects and no scheduled next move on 40 of them, your pipeline is dead — you just don't know it yet.

Planned giving is its own track and runs on a 10-to-25-year horizon. The donor is usually 60+, has been giving for a decade, and has mentioned the org in a will or beneficiary designation. Planned-giving touchpoints are softer than major-gift asks — a legacy society newsletter, an estate-planning seminar, a handwritten note on the donor's birthday. The CRM has to track bequest intent without confusing it for a current pledge, because a confirmed bequest is not revenue this year, it is revenue someday, and the board will be confused if you mix them.

In Deelo CRM, each contact carries giving history, soft credits (the donor's spouse gave but the gift goes to both), capacity rating, current major-gift stage, next-move task, and a notes field that survives staff turnover. When the next development director joins, they inherit the relationship history, not a stack of binders.

If you only run one program well, run the sustainer program. A $25/month donor gives $300 a year and stays for an average of 4 to 6 years if onboarded properly — that is $1,200 to $1,800 in lifetime value from a single conversion, with no annual renewal ask required. A 100-donor sustainer base is $30,000 a year of unrestricted, predictable revenue. A 1,000-donor sustainer base funds a program officer.

The mechanics matter. Autopay setup has to be one click on mobile, because donors abandon at every form field. The default ask amount on a recurring page should be higher than the one-time average — donors who choose monthly are choosing a smaller individual amount but a larger annual one, and the ask should reflect that. Cancellation save is its own flow: when a sustainer cancels, the system should offer to pause for 60 days, downgrade the amount, or switch the designation before processing the cancel. Most sustainers cancel because of a temporary cash crunch, and a 60-day pause retains 30 to 50% of would-be cancels.

Failed-payment recovery is the second piece. Card declines and expirations account for 20 to 30% of sustainer churn. The recurring program needs an automated retry sequence (typically 3, 7, and 14 days after the failure) and an email sequence asking the donor to update their card before the system stops trying. Without that, you lose donors to expired cards who would have happily renewed if asked.

The Deelo Automation app handles the cancellation-save flow, the failed-payment retry sequence, and the new-sustainer onboarding series — first-month thank-you, second-month impact story, sixth-month survey, twelve-month anniversary card.

Volunteers are not free labor. Volunteer hours that are well-coordinated, skill-matched, and recognized produce real program output and create future major donors — board members and six-figure donors disproportionately come from the active-volunteer pool. Volunteer hours that are mismanaged produce a churned volunteer who tells five friends not to volunteer with you.

Skill matching is the first lever. A retired CFO doing pro bono finance work for your audit committee is delivering $300/hour of value. The same retired CFO stuffing envelopes is delivering $20/hour and quietly resenting the assignment. Volunteer profiles need a skills tag, an availability window, and a preferred-shift type — short-term project, weekly recurring, event-based, or board-track. The match between role and volunteer is the retention lever.

Shift signup needs to be self-serve and mobile-friendly. A volunteer who has to email the coordinator to sign up for a Tuesday shift is a volunteer who signs up half as often. A public calendar with one-click signup, automated reminders 48 hours and 24 hours before the shift, and a one-click cancel that immediately notifies the coordinator is the operational baseline.

Recognition cadence is what creates retention. The minimum is a thank-you the same week of the shift, a personal note at the 25-hour and 100-hour marks, a name in the annual report, and an invitation to the volunteer appreciation event. High-value volunteers — the ones with 200+ annual hours or specialized skills — get a personal call from the executive director once a year, a holiday card, and an invitation to a small donor-and-volunteer mixer. That cadence is what produces the board-track pipeline.

The gala is the single biggest operations event most nonprofits run, and the place most events go wrong is the data plumbing — table sales, auction items, sponsor recognition, and post-event acknowledgment all live in different spreadsheets if you let them. Pull them into one platform.

Table sales need to track the buyer (usually a corporate sponsor or board member), the table host, and the assigned guests by seat number, with dietary restrictions and accessibility needs flagged. Sponsor recognition has to render correctly across the program, the website, the lobby signage, and the post-event report — different orgs need their logo at different sizes, with brand guidelines, and the wrong rendering on a $25K sponsor logo is the kind of mistake that loses the sponsor next year. Auction items need a procurement record (donor, fair-market value, in-kind acknowledgment letter), a bidding record (winner, winning bid, paid status), and a post-event reconciliation that closes out unsold items.

Peer-to-peer fundraising — a 5K run, a giving day, a birthday-fundraiser month — is the second event lever. P2P works because each fundraiser is asking their own network, which converts at 5 to 10x the rate of a cold appeal from the org. The platform needs personal fundraising pages with team rollups, leaderboard mechanics that drive social pressure, and automated cheer-on emails when a donor gives to a fundraiser. The org's job is to recruit team captains, equip them with email templates and social copy, and stay out of the way.

Post-event acknowledgment is where most events fail. Tax receipts to all attendees within 72 hours. Personal thank-you calls from board members to the top 20 donors within seven days. A post-event impact story (what the gross funded, what the net impact was) within 30 days. The events that get this rhythm right convert one-time gala attendees into recurring annual donors at 40 to 60% rates. The events that don't, get attendees who came for the open bar and never give again.

The board pack is where dev directors prove the program is working. It is also where most dev directors lose the room by reporting fundraising in a way that doesn't connect to mission. A board chair does not care that the email open rate was 28%. A board chair cares whether the org served more clients, kept more clients, and produced an outcome that matches what the org promised in the case for support.

The metrics that move boards are donor retention rate (overall, sustainer, major-gift), average gift size by segment, lifetime value by acquisition channel, cost per dollar raised, and the LYBUNT recovery rate. Each of those connects back to a fundraising lever the board can decide to invest in. Donor count alone is a vanity metric — a 2% gain in retention is worth more than a 20% gain in new acquisition for almost every nonprofit at scale.

Impact metrics belong in the board pack alongside fundraising metrics. Beneficiaries served, services delivered, outcomes measured. The board pack should tell a single story: the fundraising program produced X dollars, of which Y went to programs, which served Z beneficiaries, who experienced this outcome. When the dev report and the program report match that story, board confidence is high and major asks land. When they don't, the board starts asking why fundraising costs went up.

Form 990 is the public version of that same story and gets read by foundation program officers, journalists, and watchdog sites. The 990 needs to reflect well — fundraising-cost ratios, executive compensation, and the program-service-accomplishments narrative are scrutinized line items. The dev director should review the draft 990 every year and make sure the narrative on Schedule O matches the case for support, because a sloppy 990 narrative is a free reason for a foundation to decline a grant.