donor-lifecycle-requirements
Requirements mapping for the full donor lifecycle in NPSP or Nonprofit Cloud: acquisition stage design, moves management for cultivation and solicitation, upgrade path design, lapsed donor re-engagement strategy, and segmentation for portfolio management. NOT for marketing automation execution, email campaign configuration, or recurring donation implementation.
Best use case
donor-lifecycle-requirements is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Requirements mapping for the full donor lifecycle in NPSP or Nonprofit Cloud: acquisition stage design, moves management for cultivation and solicitation, upgrade path design, lapsed donor re-engagement strategy, and segmentation for portfolio management. NOT for marketing automation execution, email campaign configuration, or recurring donation implementation.
Teams using donor-lifecycle-requirements should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/donor-lifecycle-requirements/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How donor-lifecycle-requirements Compares
| Feature / Agent | donor-lifecycle-requirements | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Requirements mapping for the full donor lifecycle in NPSP or Nonprofit Cloud: acquisition stage design, moves management for cultivation and solicitation, upgrade path design, lapsed donor re-engagement strategy, and segmentation for portfolio management. NOT for marketing automation execution, email campaign configuration, or recurring donation implementation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# Donor Lifecycle Requirements This skill activates when you need to map the full donor lifecycle in NPSP or Nonprofit Cloud — from prospect acquisition through cultivation, upgrade, and lapsed re-engagement. It produces lifecycle stage maps, Moves Management configuration requirements, segmentation designs, and upgrade path workflows grounded in NPSP/NPC platform capabilities. --- ## Before Starting Gather this context before working on anything in this domain: - **NPSP vs NPC:** As of December 2025, NPSP is no longer offered in new production orgs. New nonprofits use Nonprofit Cloud (NPC). Legacy orgs remain on NPSP. The donor lifecycle features differ — confirm which platform before designing workflows. - **Moves Management is NPSP-specific in its classic form:** NPSP Moves Management uses Opportunity Stages mapped to cultivation stages on a Contact or Opportunity. NPC uses a portfolio management approach. These are different design paradigms. - **LYBUNT/SYBUNT are NPSP report concepts:** LYBUNT (Last Year But Unfortunately Not This Year) and SYBUNT (Some Year But Unfortunately Not This Year) are standard NPSP report labels for lapsed donors. These reports are built on Opportunity data in NPSP. NPC has Actionable Segmentation for donor classification. - **Segmentation ≠ Marketing Automation:** Donor segmentation in this context means portfolio classification for relationship management — who goes in the Annual Fund, Mid-Level, or Major Gift portfolio. This is NOT campaign management or email marketing execution. --- ## Core Concepts ### NPSP Moves Management NPSP Moves Management maps the donor cultivation lifecycle through **Opportunity Stage picklist values** and a Contact-level field tracking the donor's current cultivation stage. The lifecycle is: Prospect → Identified → Cultivating → Solicited → Closed Won (or Lost) Configuration components: - Opportunity Stage picklist values aligned to cultivation stages - Opportunity Sales Process restricting stages per Opportunity Record Type - Path component on Opportunity layout showing stage progression - Custom reports on Opportunity Stage changes for portfolio review The "moves" in moves management are tracked as Opportunity Stage progressions, with associated Activity records documenting each cultivation touch (meeting, call, event attendance). ### NPC Donor Segmentation (Actionable Segmentation) Nonprofit Cloud uses **Actionable Segmentation** to classify donors into portfolio tiers. This is NOT marketing automation segmentation — it is a CRM classification tool that: - Assigns donors to portfolios (Annual Fund, Mid-Level, Major Gifts) - Tracks portfolio assignments and assignment history - Enables fundraiser-specific views filtered by portfolio Actionable Segmentation creates Contact-level classification records that route donors to the appropriate fundraising strategy and portfolio manager. ### Lapsed Donor Re-engagement NPSP provides three lapsed donor report types: - **LYBUNT** — gave last year but not this year; highest priority for re-engagement - **SYBUNT** — gave in a prior year but not in the most recent year - **Multi-year lapsed** — no gift in 2+ years; lower priority, higher acquisition cost These reports are built on Opportunity records (filtered by `npsp__LastOppDate__c` and `npsp__TotalGifts__c` rollup fields on Contact). The Enhanced Recurring Donation (ERD) `Status__c` field transitions to **Lapsed** automatically when a recurring donor misses a scheduled payment, providing an additional re-engagement trigger. --- ## Common Patterns ### Moves Management Stage Progression in NPSP **When to use:** Designing the cultivation-to-solicitation lifecycle for major and mid-level donors in NPSP. **How it works:** 1. Define Opportunity Stage values: Prospect Identified, In Cultivation, Proposal Pending, Solicitation Made, Closed Won, Closed Lost. 2. Create an Opportunity Record Type for Major Gift Solicitations with a restricted stage progression. 3. Add Opportunity Path component to the record detail view. 4. Create Engagement Plans for each cultivation stage to auto-generate tasks (thank-you call, site visit invite, proposal draft). 5. Build a Pipeline Report on Opportunity Stage grouped by fundraiser to enable weekly portfolio reviews. **Why not only Contact activities:** Opportunities provide the financial projection (Amount field), close date, and stage progression that Activities alone cannot. Portfolio reviews need to see cultivation stage AND dollar value in a single pipeline view. ### LYBUNT Re-engagement Workflow **When to use:** Annual lapsed donor re-engagement campaigns in NPSP. **How it works:** 1. Run the NPSP LYBUNT report filtered to the re-engagement donor threshold (e.g., gave $500+ last year, no gift this year). 2. Export or mass-action to create Campaign Members on a re-engagement Campaign. 3. Configure an Engagement Plan on the Campaign to assign tasks: personalized outreach call → handwritten note → event invitation sequence. 4. Track re-engagement gifts via Opportunity linked to the Campaign. 5. Measure re-engagement rate: Campaign ROI report comparing re-engagement gift total to prior year giving. **Why Engagement Plans over Flow:** NPSP Engagement Plans create task sequences without complex automation configuration and allow fundraisers to mark tasks complete at their pace. Flow can automate the entire process but removes fundraiser discretion in cultivation approaches. --- ## Decision Guidance | Situation | Recommended Approach | Reason | |---|---|---| | Major gift cultivation tracking | NPSP Moves Management + Opportunity Stages | Stage progression tracks relationship investment over time | | Annual fund lapsed re-engagement | LYBUNT report + Campaign + Engagement Plan | Built-in NPSP tooling for lapsed donor identification | | Portfolio tier assignment | Actionable Segmentation (NPC) or custom Contact field (NPSP) | NPC has native segmentation; NPSP requires custom field | | Recurring donor lapsed trigger | ERD Status = Lapsed + triggered task/alert | ERD auto-transitions to Lapsed on missed payment | | Donor upgrade identification | Giving history analysis: consecutive giving + amount trend | NPSP rollup fields (TotalGifts, NumberOfGifts, LastOppAmount) | | Marketing email execution | NOT this skill — use Marketing Cloud MCAE | Donor lifecycle ≠ marketing automation execution | --- ## Recommended Workflow 1. **Platform confirmation** — Confirm NPSP or NPC. The feature set for moves management and segmentation differs significantly between platforms. 2. **Lifecycle stage definition** — With fundraising staff, define the donor lifecycle stages from prospect through upgrade and retention. Map each stage to Salesforce features (Opportunity Stage, Contact lifecycle field, ERD Status). 3. **Segmentation design** — Define portfolio tiers (annual, mid-level, major) and the criteria for each (giving history thresholds, capacity indicators, relationship stage). 4. **Lapsed donor definition** — Confirm organizational definitions of LYBUNT, SYBUNT, and multi-year lapsed. Confirm NPSP rollup fields (`npsp__LastOppDate__c`) are calculating correctly. 5. **Engagement Plan design** — For each lifecycle stage, design the task sequence for cultivation touches and re-engagement outreach. 6. **Report design** — Design portfolio review reports, lapsed donor dashboards, and upgrade candidate reports before configuring automation. 7. **Review** — Confirm segmentation design is NOT conflated with marketing automation. Verify lapsed reports use correct NPSP date rollup fields. Confirm NPSP is legacy platform if org was created after December 2025. --- ## Review Checklist - [ ] NPSP vs NPC platform confirmed - [ ] Donor lifecycle stages mapped to Salesforce features (Opportunity Stage, ERD Status, etc.) - [ ] Portfolio tier definitions and criteria documented - [ ] Lapsed donor definitions (LYBUNT, SYBUNT) confirmed with fundraising team - [ ] NPSP rollup fields (`npsp__LastOppDate__c`, `npsp__TotalGifts__c`) confirmed accurate - [ ] Engagement Plans designed for cultivation stage task sequences - [ ] NPC Actionable Segmentation NOT conflated with marketing automation --- ## Salesforce-Specific Gotchas 1. **NPSP is no longer offered in new production orgs** — As of December 2025, new nonprofits use Nonprofit Cloud (NPC). Designs referencing NPSP Engagement Plans, LYBUNT reports, or NPSP rollup fields need to confirm the org is a legacy NPSP org. New orgs will not have the NPSP package. 2. **NPC Actionable Segmentation is not marketing automation** — NPC Actionable Segmentation classifies donors for portfolio management. It does NOT send emails, manage campaign audiences, or connect to Marketing Cloud. Conflating segmentation with campaign execution leads to scope creep into marketing automation territory. 3. **ERD Status transitions to Lapsed automatically** — Enhanced Recurring Donation status transitions from Active to Lapsed automatically when a scheduled payment is missed. This is a platform behavior that fundraising teams often discover unexpectedly when donors call about their lapsed status. --- ## Output Artifacts | Artifact | Description | |---|---| | Donor lifecycle stage map | Visual map of lifecycle stages from prospect to major donor, with Salesforce feature alignment | | Segmentation design | Portfolio tier definitions, criteria, and assignment workflow | | Lapsed donor re-engagement design | Identification criteria, workflow, and Engagement Plan task sequences | --- ## Related Skills - `npsp-engagement-plans` — For implementation of Engagement Plans supporting the cultivation task sequences designed in this skill - `recurring-donations-setup` — For ERD configuration relevant to recurring donor lifecycle and lapsed re-engagement - `program-outcome-tracking-design` — For the program delivery side of nonprofit CRM alongside donor lifecycle
Related Skills
lifecycle-hooks
Use when building or reviewing Lightning Web Components — specifically lifecycle management, wire service, memory leak prevention, navigation, and Lightning Locker Service constraints. Triggers: 'LWC', 'connectedCallback', 'renderedCallback', 'memory leak', 'NavigationMixin', 'wire'. NOT for Aura components.
revenue-lifecycle-management
Use this skill when implementing or troubleshooting Salesforce Revenue Lifecycle Management (RLM) — the native Revenue Cloud product covering order-to-cash lifecycle, Dynamic Revenue Orchestrator (DRO) fulfillment plan design, asset amendments, billing schedule creation via Connect API, and invoice management. Triggers on: Dynamic Revenue Orchestrator, RLM order decomposition, DRO fulfillment swimlanes, native Revenue Cloud billing schedule, asset lifecycle management Salesforce. NOT for CPQ quoting or pricing rules (use cpq-* skills), not for the legacy Salesforce Billing managed package with blng__* objects (different product entirely), not for standard Order objects without Revenue Cloud features.
volunteer-management-requirements
Use when designing or implementing volunteer management in Salesforce for nonprofits using NPSP or Nonprofit Cloud — covers V4S managed package objects vs. NPC-native volunteer objects, hours tracking, scheduling, and recognition workflows. NOT for HR systems, commercial employee volunteering programs, or Field Service Lightning crew management.
agent-console-requirements
Use when gathering and documenting requirements for a Lightning Service Console deployment: agent workspace layout, page template selection, utility bar composition, macro requirements, case handling workflows, split-view navigation design, and licensing requirements. Triggers: service console requirements, agent workspace design, console page layout, utility bar planning, console licensing. NOT for console configuration steps or click-by-click setup (use admin/case-management), NOT for Omni-Channel routing model design (use architect/service-cloud-architecture), NOT for CTI telephony integration details.
wealth-management-requirements
Use this skill when gathering, structuring, and documenting requirements for a Financial Services Cloud (FSC) wealth management implementation — including financial planning workflow discovery, portfolio review process mapping, client lifecycle requirements, advisor tooling needs, and FSC architecture determination (managed package vs. FSC Core). Trigger keywords: wealth management requirements, FSC requirements gathering, financial planning workflow, portfolio review process, advisor tools setup, FSC data model scoping, wealth management process mapping. NOT for implementation, configuration, or code — use financial-account-setup, fsc-action-plans, or apex/fsc-financial-calculations for those. NOT for FSC architecture decisions — use architect/wealth-management-architecture. NOT for Health Cloud or NPSP requirements.
territory-design-requirements
Use this skill when gathering or evaluating requirements for a Salesforce Enterprise Territory Management (ETM) territory design: alignment criteria, coverage model selection, assignment rule logic, geographic considerations, hierarchy depth and breadth, and user-to-territory ratios. Trigger keywords: territory design, territory alignment, territory model requirements, sales coverage model, territory criteria, geographic territory, named account territory, overlay territory. NOT for ETM configuration or setup steps — use enterprise-territory-management for that. NOT for role hierarchy design — use sharing-and-visibility.
subscription-lifecycle-requirements
Use when documenting, reviewing, or gathering requirements for Salesforce CPQ subscription lifecycle behavior: how amendments, renewals, upgrades, downgrades, and cancellations must work for a specific business. Trigger keywords: subscription requirements, amendment requirements, renewal requirements, proration requirements, co-termination, subscription ledger, upgrade downgrade policy. NOT for CPQ setup or configuration, not for Apex amendment API implementation, and not for Revenue Cloud advanced order management.
revenue-recognition-requirements
Use this skill to configure and troubleshoot Salesforce Billing revenue recognition rules, schedules, and GL transaction generation in compliance with ASC 606. Triggers: 'revenue schedule not generated after order activation', 'blng__RevenueSchedule__c records missing', 'how to configure blng__RevenueRecognitionRule__c on a product', 'Finance Periods not set up before revenue schedule generation', 'revenue schedule did not update after contract amendment', 'performance obligation allocation for bundled products', 'distribution method for revenue spread', 'ASC 606 implementation in Salesforce Billing'. NOT for billing schedule setup (see billing-schedule-setup skill), NOT for standard Salesforce CPQ quoting, NOT for OpportunityLineItem native Revenue Schedules (standard platform feature unrelated to Salesforce Billing), NOT for Salesforce Revenue Cloud (Revenue Lifecycle Management).
requirements-traceability-matrix
Use this skill when building or maintaining a Requirements Traceability Matrix (RTM) on a Salesforce project: one row per requirement, columns for source, user-story id(s), test-case id(s), defect id(s), sprint, release, and status. Covers forward traceability (req → story → code → test) and backward traceability (test → req). Trigger keywords: RTM, requirements traceability matrix, audit trail for salesforce delivery, traceability for steerco, deferred requirement tracking, regulatory traceability. NOT for requirements elicitation (use requirements-gathering-for-sf). NOT for user-story authoring (use user-story-writing-for-salesforce). NOT for UAT test design (use uat-test-case-design). NOT for Apex test design (use agents/test-generator/AGENT.md). NOT for backlog prioritization (use moscow-prioritization-for-sf-backlog).
requirements-gathering-for-sf
Use this skill when eliciting, documenting, and structuring requirements for a Salesforce implementation or enhancement: writing Salesforce-specific user stories with acceptance criteria, mapping As-Is and To-Be business processes, conducting stakeholder discovery interviews, and performing gap analysis against standard Salesforce capabilities. Trigger keywords: requirements gathering, user story, As-Is To-Be, gap analysis, stakeholder interview, process mapping, business requirements, fit gap. NOT for technical design decisions (use solution-design-patterns). NOT for automation implementation (use flow/* or apex/* skills). NOT for data model design (use data-model-design-patterns or object-creation-and-design).
quote-to-cash-requirements
Use when gathering, designing, or validating the end-to-end quote-to-cash process on standard Salesforce: Opportunity to Quote (with line items) to Synced Quote to Approval Process to Quote PDF to Order creation. Trigger keywords: quote approval, discount policy, quote PDF limits, order from quote, quote sync, quote template. NOT for CPQ/Revenue Cloud pricing rules, discount schedules, or guided selling — use CPQ skills for those.
portal-requirements-gathering
Use when gathering requirements for a customer portal, partner community, or self-service Experience Cloud site. Triggers: 'gathering requirements for customer portal', 'planning Experience Cloud site', 'what license for community portal', 'portal user journey mapping', 'self-service requirements'. NOT for Experience Cloud implementation or configuration. NOT for post-launch portal optimization or redesign.