Free for fundraising and development teams

AI Prompt Guide for Fundraising Professionals

Copy a prompt. Fill in the brackets. Read the draft before you send it.

The working set Operation Impact uses when we train fundraising and development teams. Research, meetings, phone, LinkedIn, email, year-end, DAFs, matching gifts, the ask, stewardship, grants, partners, and the file — written for every title that raises money, not one job description. Version 1.2 · September 2026. The PDF is free — name, title, organization, and email first.

Version 1.2 · September 2026 · Copy, fill in the brackets, then read before you send

Free download

Get the PDF

Name, title, organization, and email. The file downloads as soon as you submit. We use the list to know who has the guide — not to sell it.

We use this only to send the guide and follow up about fundraising systems work. We do not sell the list. See Privacy & terms.

Start here

This is the whole method.

Most free prompt lists are generic ChatGPT tips with the word nonprofit added. This is the set Operation Impact uses when we train teams. Titles differ — account executive, partnerships director, annual fund, grants, major gifts. The motion does not.

  • Open the tool you already have

    ChatGPT, Claude, Copilot, or Agentforce. This guide does not require a new platform.

  • Copy one prompt

    Match it to the work in front of you — a call, a meeting, an email, an ask. One job at a time.

  • Replace the words in [brackets]

    Your organization, the program, the facts you already know. Leave blanks empty rather than guessing.

  • Paste notes only where it says to

    No children’s names, medical detail, wealth scores, or account numbers. If you would not put it in a vendor’s log, do not put it here.

  • You send it. The tool does not.

    Read the draft out loud. If it does not sound like you, rewrite the first and last sentence before it leaves.

AI drafts. You decide.

Use it to get words on the page. You still choose the facts, the timing, the ask, and whether this person should be asked at all. A donor, a foundation, a company, a church, a civic club — they are not a lead to process.

What it is good for

A short brief from public notes. A first draft of a call opener or an email. Turning messy visit notes into a file log. A meeting plan from facts you already trust. A year-end sequence that does not repeat the same paragraph three times.

What it is not for

Inventing statistics, quotes, or results. Setting the ask amount. Sending the message. Pretending a conversation happened. Tax advice on DAFs, estates, or matching gifts.

What to put in a prompt

Say who you are, what you know, and what you want back.

Vague questions get vague letters. The prompts below already include these parts. You only fill in the brackets.

  • Who you are

    One line, in your words. Example: “I raise money for [Organization]. I am preparing a first meeting.” Titles vary. The work does not.

  • What you know

    Only real facts: the organization, the program, where the relationship stands, and notes you are allowed to share.

  • What you want

    One job. “Write a 120-word follow-up with one next step” works. “Help me with this donor” does not.

  • Limits

    Say what not to invent. Ask it to mark guesses as [TO VERIFY]. Ban the phrases your organization never uses.

  • How it should look

    Ask for a subject line, a word count, or short bullets. If you do not say the shape, you will spend the afternoon fixing the shape.

  • A last check

    Ask it to list anything it assumed. Then you still read the draft. If it could have been sent by any nonprofit in America, it is not done.

What never to paste

Do not put a donor’s private life in a chat window.

  • Social Security numbers, passwords, bank or account numbers, or ID numbers from your CRM.
  • Wealth-screening scores, estimated net worth, or screening files.
  • A child’s full name, medical detail, or anything a reasonable person would not want in a chat log.
  • A full contact list. Use “Person A, last gave two years ago, to after-school” instead.
  • Private board notes, lawyer letters, or personnel files.

A short daily habit

Fifteen minutes. Look, prep, write, check.

  • LookOpen three accounts you should work today. If you cannot name the next step on each, that is the work.
  • PrepUse Research or Meeting plan on the one conversation that matters most this week. Strip private detail first.
  • WriteDraft the call, the email, or the follow-up. One ask or one next step — not both buried in warmth.
  • CheckRun Before you send. Log the activity. Put the next step on a date.

Managers: look at next steps, not hours. “I used AI” is not a measure of progress.

Prompt library

Copy a prompt. Fill in the brackets. Read it before you send.

Get the PDF

40 prompts

Getting started

Starter prompt you can reuse

Use this when

Save this once. Use it whenever you are not sure how to begin.

Fill in the brackets

Your organization, your role in your own words, who this is for, and the one thing you want back.

I raise money and build relationships for [Organization name]. My role here, in my own words: [e.g. I manage a portfolio / I run annual giving / I work corporate partnerships / I write grants / I support the team]. A person will read your draft before anything is sent or said. Here is what I know: - Our mission, in one sentence: [ ] - This is for: [an individual / a family / a foundation / a company / a congregation / a civic group] - Where we are with them: [first contact / staying in touch / asking / thanking / they said not now] - Facts I have already checked: [paste only notes you are allowed to share] - What I need from you, in one sentence: [ ] Please: - Do the one job I named. Do not add extra sections. - Do not invent statistics, quotes, gift amounts, or results. - Mark anything you are unsure about as [TO VERIFY]. - Write at a grade 8–10 reading level. - Sound like a specific person at a specific organization. No slogans. No "journey." No "impactful." No "I hope this finds you well." - Keep it to [word count or length]. When you finish, list anything you assumed that was not in my notes.

Getting started

Make notes safe to paste

Use this when

Before visit notes, a spreadsheet row, or a screening snippet go into a general AI tool.

Fill in the brackets

Your raw notes under My notes.

Rewrite the notes below so they are safe to paste into a general AI tool. Remove: - names of children - medical detail - account numbers, home addresses, CRM IDs - exact wealth-screening figures Replace people with roles if a name is too identifying. Keep the fundraising facts. Give me the cleaned notes, then a short list of what you removed and why. My notes: [paste]

Getting started

How we sound

Use this when

Once, from emails or web copy your organization already likes. Paste the result above later prompts.

Fill in the brackets

400–800 words of approved emails or site copy.

These samples are how our organization already sounds when we are at our best. Write a one-page voice guide we can paste above future prompts: - Who we sound like, in one sentence - Words we use - Words we never use - How we talk about the people who give (never as saviors, never as ATMs) - How we talk about the people we serve (dignity; no trauma as a marketing hook) - Typical sentence length - Three rewritten sentences that match the voice If the samples are stiff, say so. Do not flatten us into "nonprofit voice." Samples: [paste]

Getting started

Check a draft before you send it

Use this when

After any AI draft. You still read it yourself.

Fill in the brackets

Paste the draft under Draft.

You are a careful editor for a fundraising team. Read the draft below. For each item, write Pass or Fail and one short reason: - True - Respectful - Specific to this organization - One next step - Sounds like a person - Honest (no fake deadline, no made-up match, no tax advice) - Private enough - Ready to send Kill these if they appear: "I hope this finds you well," "just circling back," "I know you are busy," "your generosity," "journey," "impactful." Then give me a revised draft that fixes every Fail. Do not add new facts. Draft: [paste]

Research

One-page person brief

Use this when

Before a first meeting. Public information only. This is not a wealth screen.

Fill in the brackets

Organization name, the person’s public name, and public notes only.

I work in development at [Organization name]. A colleague will check every claim before we use this. Using only the public notes I paste, write a one-page brief on [Person’s public name]. Do not add facts I did not give you. If you search, name the source. Headings: - Snapshot (who they are, four lines) - Connection to our mission (only if the notes support it) - Public giving or civic pattern - Likely interests - Questions I still need answered before a meeting - Sources - [TO VERIFY] list Do not estimate net worth. Do not suggest an ask amount. Public notes: [paste]

Meetings

Plan for a meeting

Use this when

The day before a first visit, a cultivation visit, or an ask — with an individual, a family, a foundation, or a company.

Fill in the brackets

Meeting type, length, goal, who will be there, what you know, and what not to raise.

I am preparing a [first / follow-up / ask] meeting for [Organization name]. Length: [30 / 45 / 60] minutes. Who they are to us: [individual / family / foundation staff / company / congregation]. Goal, in one sentence: [ ] Who will be there: [roles] What we know (checked facts): [ ] What we must not raise: [ ] Write a meeting plan: - Opening 60 seconds (no monologue) - Six questions, in order, and why each one matters - Two stories we are allowed to tell, tied to their interests - If this is an ask: the ask sentence, then a note to pause - How to close, plus a written next step - What success looks like if they do not give today Do not invent prior conversations. Keep the language simple.

Meetings

Questions for a first conversation

Use this when

You need better questions than “tell me about your philanthropy.” Works for individuals, foundations, and companies.

Fill in the brackets

Who you are meeting and which program you might discuss.

I am preparing to meet a [individual / family / foundation / company community lead / congregation] about [program]. Write ten questions grouped by: - why they give or partner - timing - who else decides - what is appropriate to ask about capacity - permission for a next step For each question: why I am asking, and what a useful answer sounds like. Flag any question that would feel like a wealth interrogation or a pitch.

Meetings

Notes after a visit (for the file)

Use this when

Same day. This is for the CRM, not for them.

Fill in the brackets

Cleaned visit notes. Strip private detail first.

Turn the visit notes below into a file memo. This is not for the other party. Include: - What they care about, in their words if I captured them - Ready / not yet / unlikely — and why - A suggested ask range only if the notes support it. If not, write "range not yet earned." - Next step, who owns it, and a date - Risks (someone important was not in the room, competing campaign, cooling interest) No "great meeting." No adjectives that do not change the work. Visit notes: [paste]

Meetings

Invite them to see the work

Use this when

A site visit, program tour, or ride-along would move the relationship more than another coffee.

Fill in the brackets

What they would see, how long, and why this person — from notes you have.

Write a short invite to see our work in person. What they would see: [ ] Length: [ ] Why this person (from my notes): [ ] Logistics I can offer: [dates / parking / who greets them] 120 words or less. One next step: a date, not a brochure. Do not turn the visit into an ask.

Phone & LinkedIn

Phone opener and voicemail

Use this when

You are about to dial. You need fifteen seconds that do not sound like a script.

Fill in the brackets

Why you are calling, how you know them, and the one thing you want (a time, not a gift).

I am about to call someone on behalf of [Organization name]. How we know them: [introduction / event / prior gift / they asked to be called] Why I am calling, in one sentence: [ ] What I want from this call: [a 20-minute meeting / an answer to one question] — not a gift on the phone. Write: - A 15-second opener I can say out loud (permission to continue, then the reason) - A 20-second voicemail if they do not pick up - One backup line if they say "now is not a good time" Do not write "just circling back." Do not ask for money on this call. If a line would embarrass me in a grocery store, rewrite it.

Phone & LinkedIn

LinkedIn connection and first note

Use this when

They are a real person, not a lead in a sequence. Keep it short enough to read on a phone.

Fill in the brackets

Why them, any shared context, and what you want after they accept (usually a time).

I work in development at [Organization name]. I am writing a LinkedIn note, not a pitch. Why this person: [ ] Shared context, if any: [event / introducer / public post] What I want after they accept: [a short call / nothing yet, just the connection] Write: - A connection note under 300 characters. Why them. No case statement. No link. - A first message after they accept, under 80 words, with one next step or no ask at all if I said the connection is enough. Do not use "I'd love to pick your brain." Do not attach a deck.

Phone & LinkedIn

Text the same day

Use this when

You already have permission to text, or they texted you first. Confirm a time. Do not fundraise by SMS.

Fill in the brackets

What you agreed in the room or on the call.

We already spoke. I have permission to text, or they texted me first. What we agreed: [ ] Write a text under 40 words that confirms the next step and the time. No mission paragraph. No emoji unless I use them in the notes. Do not ask for a gift by text.

Emails

First email after an introduction

Use this when

Someone already introduced you. Do not ask for money in this email.

Fill in the brackets

Who introduced you (by role), why a short meeting might help them, and two time windows.

The introduction already happened. Draft an email under 140 words that: - thanks the introducer by role (do not leak their private note) - says in one sentence why 25 minutes might be worth their time - asks for 25 minutes - offers two time windows Do not ask for money. Do not attach a brochure. Do not write "I know you are busy." Give me three subject lines, preview text, the email, and a shorter text-message version.

Emails

Follow-up the same day as a visit

Use this when

Write it before you leave the office. Do not re-pitch the whole case.

Fill in the brackets

One thing they said, the next step you offered, and one useful thing you can send.

I am writing the same day as a visit. Write a 120–160 word email that: - names one thing they said (only from my notes) - confirms the next step I proposed in the room - offers one useful thing (a visit, a short brief, or an introduction) — not five attachments - does not re-pitch the case Give me a subject line and the email. Notes: [paste]

Emails

After an event

Use this when

Within two days. Thank a specific moment, not “great event.”

Fill in the brackets

Event name and what they attended or said.

Event: [name] What they attended or said: [notes] Write a 90-word email that thanks them for a specific moment. Propose one next step that matches what they signaled (a tour, coffee, or an introduction). If they signaled no interest in a gift this year, do not force an ask.

Emails

After they said not now

Use this when

They declined a meeting, a gift, or a timeline. Stay in the relationship. Do not punish them with a brochure.

Fill in the brackets

What they said, and the next honest touch you can offer.

They said not now. What they actually said: [ ] A later touch that would still be useful: [an update in six months / a site visit with no ask / nothing unless they write] Write an email under 110 words. Thank them for the clarity. Do not sneak in an ask. Do not write "I'll keep you in the loop" unless I named the loop. Subject line and body.

Year-end

Three-email year-end sequence

Use this when

One segment. One story. Three letters that do not clone each other. No fake midnight deadline unless you have a real one.

Fill in the brackets

Segment, one true story, one true number, suggested amount, whether a real deadline exists, and how they usually give.

Write a three-email year-end sequence for [Organization name]. Segment: [first-time / loyal annual / monthly / major / partners / lapsed] One story I may use (already checked): [ ] One number I may use (already checked): [ ] Suggested amount, if any: [ ] Real deadline, if any: [date or none] How they usually give: [check / card / DAF / company / unknown] Email A — early December (or late November). Work from this year. Little or no ask. Remind them they already belong here. Email B — mid-December. The story. The number. A clear ask. A second option (monthly, a visit, or a DAF grant) only if I provided it. Email C — last days of the year. Short. Specific. No drama. If I gave no real deadline, do not invent one. Each email needs a subject line, preview text, and body. Change the opening each time. Do not recycle the same paragraph. Do not invent a matching gift. Do not use "time is running out" unless I gave a real deadline. Donor, partner, or grantmaker as the subject. Program as the object.

How they give

When they give through a donor-advised fund

Use this when

They mentioned a DAF, a Fidelity/Schwab/community foundation fund, or “I’ll recommend a grant.” The fund is the vehicle. The person is still the relationship.

Fill in the brackets

What they said about the fund, what you are asking, and timing if you know it.

They give, or may give, through a donor-advised fund. What they said: [ ] What we are asking them to consider: [ ] Timing I know: [ ] Write: - How to talk about the DAF without treating the sponsor as the donor - A short email they could forward to their fund (or to a spouse) that makes recommending a grant easy - One question about timing, because grants are not cash in the door this week - What not to say (no tax advice, no "your DAF has to give this year," no pretending we received a gift until the grant arrives) Keep the person as the decision-maker. The DAF is paperwork, not a personality.

How they give

Company matching gifts

Use this when

You want to mention a match without turning the ask into a coupon.

Fill in the brackets

Whether you know their employer matches, and the link or instructions you can actually provide.

I may mention a company matching gift. What I know about their employer: [unknown / I think they match / they have matched us before] Instructions or link I can actually send: [ ] or none Write: - One sentence I can add to an ask or a thank-you that mentions matching as a courtesy, not a closer - A version if I do not know whether their employer matches - A version if they have matched us before - What not to do: do not assume, do not invent a match rate, do not make the gift about "doubling their impact" unless I gave you a real match Two or three sentences max in each version.

How they give

Invite a monthly or recurring gift

Use this when

A loyal annual donor, or someone who said they want to be easier to count on. Not a first meeting.

Fill in the brackets

What they give now, a monthly amount that is honest, and why monthly helps the work (one true reason).

They already give, or they asked how to make giving simpler. Current pattern: [ ] A monthly amount I am allowed to suggest: [ ] One true reason monthly helps the work: [ ] Write a 140-word note that invites a recurring gift. Do not frame monthly as "more money from you." Frame it as steadier for the work, if my reason supports that. Include a way to stay annual if they prefer. No fake urgency.

The ask

Three ways to say the ask

Use this when

Prepare the sentence. You still say it. Then stop talking.

Fill in the brackets

Amount, purpose, and why this person or organization — from notes you have checked.

I am preparing an ask for [Organization name]. Amount: [ ] Purpose: [ ] Why this person or organization (checked notes): [ ] Write three versions of the ask: - Direct: one sentence with amount, purpose, and a question - Story: four sentences, still one question at the end - Numbers-first: for someone who wants figures before narrative Then write two likely concerns and a calm response to each. Do not use pressure language. Do not invent a deadline or scarcity. Do not promise naming or recognition unless I said we can. Do not give tax advice.

The ask

When they push back

Use this when

You heard “not now,” “I need to talk to someone,” “we already gave,” or “send me something.” Stay calm. Do not argue.

Fill in the brackets

The objection in their words, and what you can honestly offer next.

They pushed back. What they said, as close to their words as I have: [ ] What I can honestly offer next: [ ] Write: - A spoken reply under 40 words (then a pause) - What not to say - A follow-up email only if a written next step is still appropriate Do not debate. Do not stack more case. Do not manufacture urgency.

The ask

After they decline

Use this when

The answer was no. The relationship is not over unless they said it is.

Fill in the brackets

What they declined, and whether they left a door open.

They declined [the gift / the amount / the timing / a partnership]. What they said: [ ] Door they left open, if any: [ ] Write a 90-word note that thanks them, does not relitigate the ask, and names one later touch only if they invited it. If they closed the door, write the shorter version that simply thanks them and stops.

The ask

Prepare a planned-giving conversation

Use this when

A will, beneficiary designation, or “I want to do something later.” Honor family first.

Fill in the brackets

What you know about them. No wealth score.

I am preparing a conversation about a bequest or a beneficiary designation. What I know (no wealth score): [ ] Give me: - how to open without sounding like an estate sale - five questions that honor family first - language for "I am not ready" - the one page we should leave behind Do not draft legal documents. Do not estimate estate value. Do not give tax advice.

The ask

Cue card for a peer who will ask a peer

Use this when

A board member, volunteer, ambassador, or colleague is willing to ask someone they know. They need something they can actually say.

Fill in the brackets

Who is asking, who they will ask, and the amount and purpose if you have them.

I am coaching someone who will ask a peer on behalf of [Organization name]. Who is asking (role, not a lecture): [board / volunteer / alumnus / parent / congregant / colleague] Who they will ask: [ ] Amount and purpose, if known: [ ] Write a one-page cue card they can actually use: - why they are the right person to ask - a 45-second case - the ask sentence - what to do if the answer is not now No script they would be embarrassed to read aloud. No jargon they do not use.

After the gift

Thank-you that can actually be sent

Use this when

After a gift, grant, or sponsorship. They are the subject. The program is the object.

Fill in the brackets

Purpose, relationship (first / loyal / major / company / foundation), and one impact fact you may cite.

Write a thank-you for this gift, grant, or sponsorship. Purpose: [ ] Relationship: [first / loyal annual / major / company / foundation / congregation] Impact I am allowed to cite: [ ] 180–220 words. They are the subject. The program is the object. Do not write "your generosity." Show what happens next and when they will hear from us. Give me an email version and a 90-word handwritten card version.

After the gift

Tribute or memorial thank-you

Use this when

The gift honors or remembers someone. Be careful with names and with grief.

Fill in the brackets

Who is honored or remembered, who gave, and what you are allowed to say.

This gift is in honor or in memory of someone. Who is honored or remembered: [ ] Who gave: [ ] What I am allowed to say: [ ] Whether we notify a family: [yes / no / I do not know] Write a thank-you that is specific and quiet. Do not use the dead or the honored person as a fundraising hook. If I do not know family-notification rules, add a [TO VERIFY] instead of inventing a process. 90–140 words.

After the gift

A year of stewardship for one relationship

Use this when

You need a calendar, not an ask every quarter. Works for a person, a family, a company, or a foundation.

Fill in the brackets

What they like, and whether your team is thin or fully staffed.

Write a 12-month stewardship calendar for one relationship. Include: an impact report, an invitation, informal contact, a board or site moment, and the next ask window. Mark each touch as email, call, or visit. Do not schedule an ask every quarter. That is not stewardship. Known preferences: [ ] Staffing: [thin / normal]

After the gift

Note to someone who stopped giving

Use this when

Report progress. Offer a way back. No guilt.

Fill in the brackets

Year of last gift and purpose if you know it. One true piece of progress.

Last gift: [year], purpose if known: [ ] Write a 110-word email that: - reports one piece of progress I can stand behind - offers a simple way back (a gift, a visit, or a reply about what they want to hear) - does not accuse them - does not use "we miss you" as a hook Give me five subject lines that do not say "We haven't heard from you."

Grants & partners

Need statement from facts you already have

Use this when

A grant narrative. Every number must come from your notes.

Fill in the brackets

The funder’s priorities (from their guidelines) and your checked need facts.

I am writing a grant Need section. Funder priorities, from their guidelines: [paste] Our checked need facts (do not add statistics): [paste] Write 280–320 words. Use their language without copying it. Every number must come from my notes or be marked [TO VERIFY]. Give me the Need section and a short table of each claim and where it came from in my notes.

Grants & partners

Short inquiry to a foundation

Use this when

You are asking if you may apply — not sending a full proposal.

Fill in the brackets

Why you fit, the project in one paragraph, and what you want (a call or the right process).

Write a 140-word inquiry email to a foundation. One paragraph on why we fit. One paragraph on the project. One ask: a conversation, or confirmation of the right process. Do not attach a full proposal unless they asked.

Grants & partners

One-page letter of inquiry

Use this when

They asked for an LOI or a one-pager, not the full proposal yet.

Fill in the brackets

Funder name, project, amount if allowed, and checked facts only.

Write a one-page letter of inquiry. Funder: [ ] Project: [ ] Amount, if I am allowed to name it: [ ] Checked facts I may use: [ ] Include: who we are, the need, what we will do, what it costs, how we will know it worked, and the ask. Every number from my notes or [TO VERIFY]. No slogans. No appendix.

Grants & partners

Brief before a company meeting

Use this when

Treat a partner like an account. Find budget and calendar, not just “they should care.”

Fill in the brackets

Company public name, what you know, and what you are offering (sponsorship, volunteers, cause campaign, or in-kind).

I am preparing a first meeting with a company. Company (public name): [ ] What we know: [ ] What we are offering: [sponsorship / volunteers / cause campaign / in-kind] Write a one-page brief with: - their business interest (not only "they should care") - who inside the company is likely to decide - what we can offer - risks (greenwash, staff time, exclusivity) - a first-meeting agenda - questions that qualify budget and calendar

Grants & partners

Sponsorship one-pager

Use this when

An event or program sponsorship. Benefits they can actually deliver, not a fantasy menu.

Fill in the brackets

Event or program, levels you really have, and what you can actually provide.

Write a one-page sponsorship sheet. Event or program: [ ] Levels we actually offer: [ ] Benefits we can actually deliver: [ ] Audience, if I have a real number: [ ] Plain language. No "exciting opportunity." If a benefit would embarrass us if we failed to deliver it, leave it off. End with who to talk to and by when, if I gave a date.

Pipeline

Monday look at your list

Use this when

Accounts with no next step are the agenda. Works for any book of relationships.

Fill in the brackets

An anonymized list: code, stage, last step date, next step, dollar if appropriate.

I am reviewing a list of [number] accounts. The list is anonymized: code, stage, last-step date, next step, dollar amount if appropriate. Please: - flag accounts with no next step, or a next step older than 21 days - suggest the single best action this week for the eight most urgent - name two accounts that should be recoded or dropped, with a reason Do not invent contact history. List: [paste]

Pipeline

CRM note after a contact

Use this when

The write-up you log. Short. No “great meeting.”

Fill in the brackets

Raw notes from the contact.

Turn my raw notes into a CRM activity under 120 words. Include in the text: date, type, who was there, what we learned, next step, who owns it, date of next step. No adjectives. No "great meeting." Raw notes: [paste]

Pipeline

Forecast in language leadership can read

Use this when

Packet week. Do not hide a miss. Do not write a victory lap.

Fill in the brackets

An anonymized snapshot of stage totals only.

I will paste an anonymized pipeline snapshot (stage totals only). Write 250 words a board, CEO, or finance lead can read without a translator. Cover: what is committed, what is in play this period, what slipped and why, and what would change the number. No victory language. Do not hide a miss. If you are inferring, say so. Snapshot: [paste]

Pipeline

Coaching agenda for a 1:1

Use this when

Ten minutes with someone on the team. Look at next steps, not hours logged.

Fill in the brackets

An anonymized weekly report from one person.

From this anonymized weekly report, write a 10-minute coaching agenda. Look at next steps, not hours. Name one skill to practice (discovery, the ask, closing, or follow-up). Do not write a performance review. Report: [paste]

Pipeline

Handoff when you leave an account

Use this when

Someone else is taking the relationship. Write what they need, not a novel.

Fill in the brackets

Cleaned notes: who they are, last contact, next step, sensitivities, how they give.

Write a one-page handoff for a colleague taking this relationship. Include: - who they are to us, in four lines - last meaningful contact - next step already promised - how they give (if known): check, card, DAF, company, foundation - sensitivities (do not call on X day; spouse not in the room; they dislike events) - what not to do in the first 30 days Notes: [paste]

Pipeline

First 90 days on a new book

Use this when

You inherited a portfolio, a region, a partner list, or an annual-fund segment. Do not restart every relationship from zero.

Fill in the brackets

What you inherited, how thin the file is, and how much time you have each week.

I just inherited a book of relationships at [Organization name]. What I inherited: [portfolio / region / partners / annual-fund segment] How thin the files are: [ ] Hours I have for this each week: [ ] Write a 90-day plan: - who to call in the first two weeks (criteria, not a fake list of names) - what to clean in the file - what not to ask yet - how I will know week 12 was a good start No transformation language. Practical.

Before you send

If one fails, fix it.

  • Is it true?

    Every number, quote, and result is in your notes — or marked [TO VERIFY].

  • Is it respectful?

    No trauma as a marketing hook. No savior tone. No child named unless your protocol allows it.

  • Is it specific?

    If any nonprofit in America could send this, add one true detail or delete it.

  • Is there one next step?

    A meeting, a time, or one question. Not a menu.

  • Does it sound like a person?

    Read it out loud. Kill “I hope this finds you well,” “just circling back,” and “I know you are busy.”

  • Is the ask honest?

    No fake deadline, no made-up match, no pressure dressed as urgency. No tax advice.

  • Is it private enough?

    No extra personal detail they did not put in public or give you permission to use.

  • Would you hit send?

    The subject line is human. The preview text does not advertise that a computer wrote it.

Training

A saved file nobody uses does not raise a dollar.

This is the public version of how Operation Impact trains fundraising and development teams — every title that holds a relationship, on ChatGPT, Claude, Copilot, or Agentforce. The guide is free. The habit is the work.

Book time to meet with us

The first meeting ends with one realization: whether you have a scientific pipeline — and a CRM that generates trustworthy leading KPIs.

Book time to meet with us