Feature area
Sapling keeps households, individuals, organizations, DAFs, sponsors, advisors, tags, tasks, notes, recurring giving, and relationship history connected to one donor record.
Why it matters
A fundraiser should not have to decide whether the truth lives on a person, household, company, foundation, payment record, task board, tag list, or spreadsheet. Sapling is designed around the donor record as the operating home for relationship work: who they are, who they are connected to, what they have done, what the team knows, and what should happen next.
Contact record preview
Sapling is built so households, organizations, DAFs, tasks, gifts, tags, and communication history live close enough together that a fundraiser can understand the relationship without opening five tools.
Jennifer Lee Household
Major donor · DAF prospect · assigned to Aisha Bennett
Lifetime giving
$184,250
Household members
3
Open tasks
4
Active tags
12
Major gift received
$25,000 · Arts Access Fund
Recurring commitment active
$500 monthly · next expected Oct 1
Receipt and thank-you delivered
Tax receipt PDF emailed and stored
AI-managed tag updated
High capacity · event follow-up · DAF prospect
Individuals
Sapling donor records are meant to answer the fundraiser’s first question quickly: who is this, what is the full relationship, what happened, and what should we do next? The record can carry giving, people, organizations, notes, tasks, files, events, receipts, communication history, and report context without forcing staff to stitch together the story later.
Fundraising relationships often run through spouses, family members, assistants, trustees, advisors, and multiple people inside the same household. Sapling keeps individual context visible while preserving the household-level donor picture.
A gift may come through a DAF sponsor, corporate provider, foundation, business, social fundraiser, or sponsor while the real relationship belongs somewhere else. Sapling is built to separate transaction routing from donor understanding.
The contact page should be where cultivation becomes action. Staff can add tasks, assign ownership, review tags, track recurring giving, open gift history, and keep the next move visible next to the donor context.
Orchid is most useful when it can reason from the actual CRM record: giving history, notes, events, imports, communication, tasks, and relationship context. The goal is not a disconnected chat answer; it is better donor work with the source still nearby.
Sophisticated nonprofits need private records, permission-aware actions, auditability, data health, and exports without turning every workflow into an admin project. Sapling keeps operational controls close to the record instead of hidden in a separate system.
Sophisticated teams need to see who owns a relationship, where cultivation stands, and what next action belongs in the portfolio.
Keep exploring