Case file · [Non-profit]

Found the bottleneck they couldn't name. Fixed it in two weeks.

11 décembre 2025 · Community non-profit · ~25 staff · Anonymised, the judgment is exactly as it ran
① What they came with

A vague pain, “donations are slipping and we don't know why”, and no vendor pitch on the table.

A regional community-services non-profit, around twenty-five staff, long donor history, board mostly volunteer. The executive director called with a problem she could not name. Donations were down about fourteen percent year-on-year. New-donor acquisition was actually up. Major-gift renewals were steady. The slip was somewhere in the middle of the funnel, and three quarters of strategic-planning conversations with the board had failed to surface where. There was no consultant in the funnel, no vendor proposal, no plan to react against. The development director was tired; the executive director suspected something was wrong but had no language for it. Their request was unusually honest: “Come in, look at how the work actually happens, and tell us what you see.” We took the hour at the standard rate. It was the rare engagement that started with a buyer asking the question instead of asking for confirmation.

② The answer, first

The bottleneck is the post-donation experience, not strategy. A 2014 receipt template has been quietly losing the donors you've already won.

We opened the second hour with the diagnosis, not a discovery deck. The slip wasn't in fundraising strategy; it was in customer service. We had watched a real donation flow through the system that morning. The receipt that fired was a generic template last edited in 2014. It thanked “Friend” for the gift, named no campaign, acknowledged no prior history, mentioned no person at the organisation, and offered no follow-up. Every donor, first-time, twentieth-year, lapsed, board member, got the same email. We then pulled the cohort data the development director had not had the time to assemble. First-time donor retention was twelve percent (the sector baseline for an org their size is thirty to forty). Lapsed-donor reactivation was zero, because no reactivation campaign existed. The donations weren't slipping. They were walking away, quietly, through a surface nobody had touched in a decade.

③ The working, shown

So they could see the leverage and run the work themselves.

We spent the rest of the morning building the case in front of the development director. We pulled six months of donation receipts at random and read them out loud. We segmented the donor list by tenure, gift size, and last-gift date. We mapped the segments to the kinds of messages that would have been honest to send each one, a thank-you variant for a first-time donor that named the specific programme they gave to; a re-engagement note for donors who had given annually for years and had missed last year; a stewardship update for major givers that wasn't a request. We wrote the rough copy for each on a whiteboard. We then sized the actual implementation: the email platform they already paid for had templates, segments, and automation. The whole programme could be built and tested in two weeks of the development director's focused time, with no consultant in the room. We sketched the success metrics: target a lift in first-time retention from twelve to twenty percent within two quarters, target a non-zero lapsed reactivation campaign by end of next quarter, and bring the board pack a single chart showing retention by cohort over time. The dev director, asked whether she could write the copy herself, looked at us like the question was insulting. She had been wanting to write that copy for years.

④ The cut

We billed for the diagnosis, declined the implementation, and walked the staff through the success criteria so the board would know the work had landed.

We sent a four-page recommendation to the executive director, with the cohort data on page one and the email-programme spec on pages two and three. The fourth page named our bill: three thousand for the diagnosis, the spec, and a half-day of working through the segments with the dev director. We declined the implementation work explicitly. We declined the offer of a quarterly “fundraising advisory” retainer that the executive director floated at the end of the meeting; the dev director did not need a retainer, she needed two weeks of board-protected time. We named the two pieces of help we would be willing to offer in future at the same standard rate (a six-month review of whether the metrics had moved, and a single hour of help when the next vendor walked in with a “donor management platform” proposal, because someone would). We sent the spec. The implementation took the dev director ten working days over the next month. Lapsed reactivation, two quarters out, was at eight percent. First-time retention was at twenty-two percent. Donations stopped slipping. Nothing had been bought.

⑤ Signed

A named person walked the diagnosis to the board, with the dev director in the room and the cohort chart on the screen. Not a faceless “we”, not a recommendation that arrived with a vendor selection bundled in, not an engagement that needed a consultant on the next call to keep going. The board chair, asked at the half-year mark whether the small bill had been the right call, sent a forward of the lapsed-reactivation chart with a single sentence attached. The dev director keeps the original whiteboard photo on her wall. We have never returned to this client. We don't need to.

← The full record
Sector and figures are generalised to protect the client; the diagnosis and the work we declined are unchanged. Sometimes the bottleneck is a thing nobody has been allowed to name. Naming it is the engagement.