Nonprofit annual appeal planner

What goes in and out

You give it

• Donor counts for each group (new, renewing, lapsing, mid-level, prospects).
• Each donor's last gift and highest gift.
• Past appeal response rates and average gifts (optional).
• Your campaign goal and the channel, mail or email.
• Your send dates and key deadlines.
• Verified cost data for what a gift pays for.
• Document (optional)
• Spreadsheet (optional)

You get

• A plan that splits your donors into groups, each with its own message.
• Suggested gift amounts for each group, based on past giving.
• An appeal letter or email with a P.S. and matching reply wording.
• A dated send calendar that spaces out your asks.
• A scorecard to track response rate, average gift and cost to raise a dollar.

How the task works

• Group donors by history. Separate new, returning, lapsing, and larger donors so each group receives a fitting ask.
• Write a clear appeal. Use a specific story, verified gift impact, suggested amounts, deadline, and one next step.
• Plan dates and review. Match reply amounts across channels, space appeals sensibly, and define response and cost measures for review.

Full instructions

• Open Claude, ChatGPT or Gemini and paste in the skill instructions. No code or paid tool is needed.
• Paste your donor group counts, gift history, goal, channel and send dates. Send no names, emails, addresses or other identifiers. Use group counts and donor ID numbers only. Check your data-protection policy and your AI tool's terms before you paste any donor records.
• Give real cost data for what a gift pays for. If you have none, your AI will leave a bracketed blank to fill in.
• Check the gift amounts, the impact lines and the story before anything goes out.
• Have a person review the full appeal, because it goes to your whole donor list at once.
• After the appeal closes, paste in the results and ask for the scorecard.

Full instruction file

Annual Fund Appeals

Before you start

Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait.

What you need (use your own material or the linked skill):

• Your question (yours): the decision or problem, and what a good outcome looks like.

Makes it better (optional):

• A document (yours): a finished document, such as a Word file, a PDF or a page of notes.
• A spreadsheet (yours): a spreadsheet with its data, formulas and charts.

How to start:

1. Look first. Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name.
2. Check what's missing. Look for your question, a document, a spreadsheet. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps.
3. Do the job. Follow the skill below with the facts and tools you have. Mark each gap with MISSING: where it belongs and never invent a fact to fill it.

Tools that do this best:

• A chat AI that can read your files: The skill works from records and drafts you provide. Research tasks also need current, checked public sources.

When to Use This Skill

Use this skill for the strategy and copy of a mass-channel fundraising ask (mail or email) sent to the broad annual-fund donor file — not for configuring the CRM/segmentation software itself (nonprofit-donor-crm), not for team/peer fundraising campaigns like walks or runs (nonprofit-peer-to-peer-fundraising), and not for non-ask newsletter content (nonprofit-email-newsletter). Typical triggers:

• "Plan our year-end appeal calendar"
• "Segment our donor file for the fall mail appeal"
• "Write the appeal letter and reply card for giving season"
• "Build an ask-string ladder for this segment"
• "What should our response rate benchmark be, and why did this appeal underperform?"
• "Plan a #GivingTuesday email sequence"

Core Concepts

• Annual fund — the recurring, unrestricted (or lightly restricted) mass-donor giving program, distinct from major/planned/capital gifts; typically the base of the donor pyramid by count, not by dollar total.
• Ask string — the set of suggested gift amounts presented to a donor (e.g., "$50 / $100 / $250 / $500 / Other"). Anchor ask strings to the donor's own giving history, not a generic ladder: a common formula is to center the ask string around 1.1x-1.5x the donor's last or highest gift, with the top option meaningfully higher to invite an upgrade.
• Segmentation — splitting the donor file into groups that receive different messaging/ask levels: new donors (first-year), renewing donors, lapsed donors (see boundary note below), mid-level donors, and non-donor prospects/lapsed inquirers. Segmentation logic can live in the CRM (nonprofit-donor-crm sets up the tooling); this skill uses those segments to drive messaging and ask amounts. Lapsed-donor win-back campaign design belongs to nonprofit-donor-retention; this skill covers what to send an active/recently-lapsed segment as part of the regular appeal calendar.
• Appeal calendar — the annual sequence of mass appeals, typically: spring/mid-year appeal, summer sustainer push, fall/pre-year-end appeal, December year-end appeal (often a large share of annual-fund dollars; the share varies, so check your own giving data), and a January thank-you/tax-receipt touch.

Standard Deliverables

1. Segmentation plan — list of segments with distinct messaging angle and ask-string logic per segment.
2. Appeal letter — direct-mail or email copy following direct-response structure: a compelling opening (specific person/moment, not a mission-statement restate), the problem, the specific ask amount(s), what the gift accomplishes in concrete terms ("$75 provides X"), a deadline or urgency device, a clear single call to action, and a P.S. (direct-mail P.S. lines are read almost as often as the opening and should restate the ask/urgency).
3. Reply device / donation page — matches the letter's ask string exactly; for the online donation page's conversion-copy mechanics specifically, defer to nonprofit-donation-page-copy, but ensure the appeal's messaging and ask amounts are consistent across mail, email, and the landing page.
4. Appeal calendar — dated plan across the fiscal year with channel, segment, and theme per drop, spaced to avoid fatigue (avoid stacking two full-file asks within 2-3 weeks of each other).
5. Performance scorecard — per appeal: response rate (gifts / pieces sent), average gift, cost-to-raise-a-dollar, and year-over-year comparison by segment.

Concrete Steps

1. Pull and segment the donor file: new, renewing, lapsing (1-2 years since last gift; test messaging here vs. handing fully lapsed 2+ year donors to a dedicated win-back track), mid-level, and prospects.
2. Set ask strings per segment anchored to giving history (1.1x-1.5x last/highest gift, escalating top anchor) rather than one flat ask string for the whole file.
3. Draft the letter using direct-response structure; lead with a specific story or moment, state the ask early and again in the P.S., and quantify gift impact in concrete terms.
4. Build the reply device/donation page to mirror the letter's exact ask amounts and any matching gift or challenge grant mentioned.
5. Slot the appeal into the calendar with adequate spacing from other mass appeals and from any peer-to-peer or event solicitation touching the same file.
6. Send a testable variant where feasible (subject line, ask amount, or opening story) if volume supports statistically meaningful comparison.
7. After the appeal closes, calculate response rate and average gift by segment; compare to prior year and to sector benchmarks (annual fund response rates commonly run low-single-digit percentages for cold mail and higher for warm/renewal segments — treat any specific external benchmark figure as a rough reference, not a guarantee, and prioritize the org's own year-over-year trend).
8. Feed underperforming segments back into the segmentation plan for the next cycle rather than repeating the same ask unchanged.

Common Failure Modes

• One ask string for everyone: ignoring giving history produces both under-asks (frustrating loyal donors) and over-asks (alienating new/small donors).
• Mission-statement opening: burying the ask and the human story under organizational boilerplate in the first paragraph, where response-rate impact is highest.
• Mismatched channels: letter and online donation page showing different suggested amounts or different campaign framing, confusing the donor and depressing conversion.
• Appeal stacking: sending a full-file mail appeal and a full-file email appeal with the same ask within days of each other, spiking unsubscribes/opt-outs.
• No P.S. or weak P.S.: skipping the highest-read line of a direct-mail letter.
• Ignoring cost-to-raise-a-dollar: chasing response rate alone without factoring mail/print costs against a lower-cost email-only push for marginal segments.

For Advisors

When reviewing a client's annual fund program, request the last 2-3 years of appeal-level response rate and average-gift data segmented by donor type before recommending new creative — a declining-response problem is often a segmentation or list-hygiene issue (routed partly to nonprofit-donor-crm), not a copywriting one. Push clients toward a documented appeal calendar with explicit spacing rules; ad hoc appeal scheduling driven by whoever has bandwidth that month is the most common root cause of donor fatigue and inconsistent year-over-year comparisons. Frame the December appeal's outsized share of annual results to the board explicitly so cash-flow and staffing decisions account for that concentration.

After this

When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:

• The SMS send checker. It takes the draft and plan.
• The Email draft reviewer. It takes the draft.
• The Email draft readiness checker. It takes the draft. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.