Good major-donor meeting preparation turns verified relationship context into a short agenda, useful questions, and clear boundaries. Good follow-up turns only confirmed decisions and commitments into a reviewed message and owned tasks. Neither step should predict a gift, infer private motivation, or convert an ambiguous conversation into a promise.
The meeting loop in one view
| Moment | Evidence to assemble | Human-reviewed output | Safe stop |
|---|---|---|---|
| Before | Meeting purpose, approved donor record, stated interests, prior interactions, open commitments, program facts, preferences | One-page brief, agenda, questions, unknowns | Identity, purpose, consent, or source is unclear |
| During | The donor’s own words, questions, objections, decisions, and agreed next steps | Accurate notes with uncertainty preserved | Do not fill gaps from memory or inference |
| After | Approved notes, exact commitments, communication preference, responsible owners, dates | Unsent follow-up draft, tasks, record-update proposals | Material fact, recipient, amount, restriction, or date is ambiguous |
| Review | Source records and organizational policy | Approved message and accepted system updates | Required reviewer or authoritative system is unavailable |
This is a relationship-continuity workflow. It helps the organization remember what it learned and what it owes. It is not a scoring system for who will give.
Use the BRIEF preparation method
B: Bound the meeting
State the purpose, participants, desired decision, time available, and topics that should not be raised. A stewardship conversation, qualification meeting, program briefing, and solicitation meeting are different jobs.
R: Reopen the authoritative record
Check identity, household rules, giving history, restrictions, communication preferences, and official proposal state in the donor CRM. Do not rely on a copied amount or an AI summary for a material fundraising fact.
I: Inspect relationship evidence
Review approved prior notes, recent messages, meetings, program interactions, and the accountable relationship owner. If a board member or colleague may know the donor, treat that as a possible path until the person confirms both the relationship and willingness to help.
E: Expose unknowns
List what the team does not know, what appears stale, and where sources conflict. Convert assumptions into questions for the fundraiser, not statements about donor intent.
F: Frame the next conversation
Prepare a concise agenda, three to five questions, relevant program evidence, open stewardship items, and an explicit review boundary. The fundraiser decides the tone and strategy.
What an agentic assistant can do safely
Aurora can work across available Finta context and supported connections to check relevant CRM, inbox, calendar, and document sources, synthesize a meeting brief, prepare a draft, propose supported record changes, and complete only supported actions within available permissions. Its product flow makes source, tool, and confirmation boundaries visible.
That makes Aurora agentic in a bounded sense: it can take multiple supported steps toward a defined output instead of returning only a generic answer. It still cannot know private context that was not recorded, and it waits for review before an external message is sent.
Finta CRM can keep the working relationship stage, owner, research, mutual connections, permitted inbox context, and next move together. The donor CRM remains authoritative for gifts, pledges, receipts, restrictions, consent, and official fundraising reporting.
Worked example: from a program visit to a precise follow-up
A donor is visiting a workforce-training program six months after making a restricted gift.
Before the meeting, the gift officer verifies the designation and recognition preference in the donor CRM. In Finta, the team reviews the last approved meeting note, the program leader’s outstanding promise to share completion data, and the calendar invitation. Aurora prepares a brief with three sections: confirmed history, the unresolved reporting commitment, and questions for the visit.
During the visit, the donor asks for an updated outcome report and offers to introduce the program leader to an employer. The notes say exactly that. They do not say the donor intends to renew the gift or guarantee the introduction.
Afterward, Aurora prepares:
- An unsent thank-you email referencing the visit and the requested report.
- A proposed task for the program leader to deliver the report by the date the team confirms.
- A proposed task for the gift officer to ask whether and how the donor would like to handle the employer introduction.
- A record-update proposal containing only the confirmed interaction and next steps.
The gift officer reviews the message, verifies the recipient and commitments, and routes official donor-record changes to the donor CRM.
A note template that resists accidental invention
Use four headings after every substantive donor meeting:
- Confirmed: facts, decisions, and interests the participant explicitly stated.
- Requested: documents, introductions, answers, or actions requested by either side.
- Open: unclear points, unresolved questions, and items that require verification.
- Owned: each accepted next step, responsible person, and reviewed date.
Avoid fields such as “likely gift,” “ready to ask,” or “high affinity” unless the organization has a governed, documented methodology and a legitimate basis to use it. Even then, model output should not be treated as donor intent.
Ethical and privacy checks
The Association of Fundraising Professionals Code of Ethical Standards calls for accurate communication, donor privacy, protection of confidential information, and respect for donor intent. Before using AI-assisted preparation or follow-up, confirm:
- The information is authorized for this team and this purpose.
- Sensitive or irrelevant personal data is excluded.
- Donor preferences and restrictions come from the authoritative record.
- A person can reopen every material source and correct the result.
- The relationship owner reviews the donor-facing message.
Blackbaud’s current donor-engagement prompt documentation also illustrates how meeting preparation and post-meeting drafting can use constituent context. The broader lesson is not that every system owns the same data. It is that useful assistance depends on the right record context and an accountable reviewer.
Limits and disclosure
Finta is not donor accounting, gift processing, tax receipting, wealth screening, or a donor-likelihood model. It does not decide ask amounts, gift timing, capacity, affinity, or intent. Available evidence can be incomplete or stale. Development professionals remain responsible for privacy, strategy, stewardship, record accuracy, and every donor-facing action.
Prepare the conversation and close the loop
Use Finta to bring permitted relationship evidence into a concise brief, then turn confirmed outcomes into reviewed follow-through. Explore the donor meeting follow-up workflow.