The Gift Is in the Group Text
There is a group text, on four different iPhones in three different time zones, where your next major gift is being decided this month.
You are not in it.
The four people in it are Maeve, who is sixty-six, recently retired from running marketing at a regional bank in Saint Paul, and the donor on the file you keep refreshing. Her daughter Cora, forty-one, in Brooklyn, who runs a small family foundation for a tech founder and has become, by family consensus, the philanthropy committee of one. Maeve's brother Dan, sixty-three, an estate lawyer in Phoenix, who structures every dollar the family moves before it moves. And Joyce, the family's financial advisor since 2008, whom Maeve will not commit a six-figure gift without asking first.
The thread was started in March, when Maeve's mother died and the family foundation became real instead of theoretical. It now has several hundred messages, three voice notes, one PDF of a 990, and a screenshot of your About page from a Tuesday in May.
You have met exactly one of these four people. You think the gift is yours to lose. It hasn't been for months.
The room you have been talking to is a hallway
Major gifts are still taught as a one-to-one conversation. One person on the donor's side. One person on the org's side. A careful line between them.
That curriculum has been stale for a decade and is now actively wrong in the entire above-six-figure tier of American giving. The donor on the file is no longer the decider. She is the last person in the conversation, signing off on a choice four other people helped her make.
She is not less generous. She is more careful. She is sixty-six. She has watched two friends mishandle inherited money and one cousin sued by his own children. She is not putting a quarter-million dollars anywhere her brother, her daughter, and her financial advisor have not all three quietly nodded at.
The decision is committee work. The committee is on a group text. The named donor is the chairwoman, not the board.
Who is actually in the thread
Cora, the adult daughter. She will Google you on a Sunday night. She will read your 990 with the bored thoroughness of someone who reads 990s for a living. She will text the thread, at 9:17 on a Tuesday, Mom, their ED's last org had a 990-PF restatement in 2021 — want me to dig in. She is younger than your development officer, more technical, and significantly more skeptical. She decides whether you survive the diligence pass.
Dan, the brother. He will write the actual check, set up the actual DAF, and structure the actual planned-giving arrangement. He will never visit your office. He will form a complete opinion of you from the documents Cora forwards him and one call with your CFO in September. He says almost nothing in the thread. When he does, the gift either happens or it doesn't.
Joyce, the financial advisor. She has been doing this longer than your executive director has been alive. She is not opposed to you. She is professionally obligated to ask Maeve, softly, whether the gift fits inside the long arc of the family's plan, and whether the timing is right for tax purposes, which is the polite phrase for no, not this year. If Joyce says not yet, the gift slips to spring. You will hear about it in October, from Maeve, as we're going to take another look at this in Q2. That sentence is Joyce.
Maeve, the donor. She is on your mailing list. She came to the gala in April. She had coffee with your executive director in May. She has, in her own way, already decided to give you something. The size and the timing of that gift are not, in any meaningful sense, hers anymore. They belong to the thread.
What your CRM thinks is happening
Your CRM has one record for Maeve. The notes column says coffee with ED 5/14, asked about literacy, family foundation in formation, follow up in July. That is the whole map of the relationship as far as your software is concerned. One donor. One officer. One linear cultivation arc.
The CRM has no field for Cora. No field for Dan. No field for Joyce. There is, somewhere in a custom field nobody fills out, a place to list related parties, and the last person to update it resigned in 2019.
This is not a software problem. It is an attention problem the software encoded. We built the CRM around the donor because we believed the donor was the decision-maker. She isn't. The CRM is a beautifully maintained portrait of one person, in the corner of a room with three other people the development officer has never seen.
The most common reason the gift slips a year
It is rarely that the donor changed her mind.
It is almost always that someone else in the thread had a question, on a Thursday evening, that nobody in your office was equipped to answer. The brother in Phoenix wanted to use a DAF and your team had never been asked, by name, for your EIN at 4:32 on a Thursday afternoon. The daughter read a Reddit thread about a sector controversy your team would have happily addressed in two paragraphs — if anyone had told you Cora existed. The advisor wanted to know how a stock gift would be received, and the answer took your CFO eleven days to produce.
You were running a major-gift conversation in 2009. The thread was running one in 2026. The two were not the same shape.
You were talking to Maeve. The thread was talking around you.
What you can actually do, from outside the room
You will not be invited into the thread. You should not want to be. It is a family group chat full of grocery requests and small unflattering jokes about your executive director's blazer. Stay out.
What you can do is make the thread's work easier.
Send Maeve, in early September, the small careful packet a thread would want. Two pages of Form 990 highlights in plain English. A one-page memo from your CFO on how DAF gifts and stock gifts are received. A one-paragraph statement on the 2021 controversy Cora is about to ask about, before she asks. Your EIN, your last clean audit, your planned-giving language. No glossy magazine. No mission narrative. No four-color object.
Include a short cover note: I imagine the people helping you think this through may want some of this in one place — here it is.
You have just done the most respectful thing a 2026 development officer can do. You have acknowledged that the gift is not a private decision. You have treated the donor's family as competent. You have saved Cora a Sunday evening. The thread will read your packet. The thread will, in some small but real way, begin to like you. Dan will message the others: they sent the audit and the planned-giving sheet up front. That's unusual.
You did not enter the thread. You shaped what the thread is talking about.
A useful thing for a tool to do here
Maeve has a daughter, a brother, a financial advisor, and twenty other ties — a college, two boards, a foundation she started in 2018 for her late husband, a maiden-name string of family giving going back to a steel town in Ohio in 1962.
A development officer cannot, by hand, on a Wednesday morning before the eleven o'clock meeting, assemble a portrait of all of that. So the portrait does not get assembled, and the officer walks in holding a record of one person to meet, across the table, the chairwoman of a four-person committee.
Point Rōmy at the name and the portrait that comes back is the room, not the chair. Maeve and the daughter who runs the foundation in Brooklyn. The brother in Phoenix and the kinds of causes his clients tend to fund. The advisor's firm and what it has historically counseled around DAFs. Every relationship pulled from the public record — board minutes, foundation filings, alumni magazines, news — and linked back to where it came from.
You walk in with the cast list. You ask, kindly, the right question about Cora by name. Maeve, for the first time in this courtship, feels you have noticed that her life is shared.
That is the bare minimum of what it has always meant to know a donor — that you also know the people she trusts.
The name on the gift line is the last signature
The check will say Maeve. The recognition wall in 2031 will say Maeve. The thank-you note will be addressed, properly, to Maeve.
That is not the room.
The room is four people on a thread. Three of them you have not met. One of them you will never meet. And the gift, when it comes, will be a decision they made together — on a Thursday in late September, after a voice note from Joyce, a thumbs-up from Dan, and a fine, do it from Cora at 10:42 p.m. — to which Maeve will reply, an hour later, with a single word.
That word is what your CRM will record as the gift.
The eight months of group-text work that produced it will not be anywhere in your file. But it is the whole story of how the gift happened.
And the next gift in your file is, right now, being decided the same way — on a different thread, by four different people, in a room you have not yet learned to see.
So: who else is at the table.