Need, Plan, Benefit: The Case for Support in Three Parts
Your case for support is about you. It shouldn’t be.
Somewhere on your shared drive there is a document called something like “Case for Support — FINAL v6.” Fourteen pages. It opens with the year you were founded. There’s a section on your theory of change, a paragraph on your executive director’s last three jobs, a pie chart of your budget, a page on your strategic plan, and a closing appeal for partnership.
Every word of it is true. The credentials are real, the theory of change is defensible, and the pie chart is accurate to the dollar. It took four months and eleven people, and by the end, everyone was sick of it and glad to be done.
It is also, start to finish, about your organization. And no one gives to an organization. They give to what it does, and how it does it — the need it meets, the change it makes, the family it serves. A donor can find your organization admirable and keep their checkbook closed, because admiration was never what opened it.
That is the failure, and it isn’t a failure of care. The document mistakenly identifies the organization as the subject. It reads like a credentialing packet because that is what it is — an answer to a question no donor asked. Are you legitimate? The donor arrived with a different question, and the fourteen pages never reached it.
Just make it about the donor
The sector has a correction ready for exactly this, and it’s the obvious one: if the case is about the organization, make it about the donor instead. Put “you” in every paragraph. Cast the donor as the one who saves the day. Lead with what their generosity makes possible.
That answer has real evidence behind it, and I won’t pretend otherwise. Donors give more when you make the ask about them — their identity, their capacity, their power to change something. One field experiment with more than 12,000 affluent households found that framing a gift around what the donor could personally accomplish, rather than what a group could do together, raised total dollars by roughly 80%. That is not a rounding error. That is the donor-centric playbook doing exactly what it promises.
So give the playbook its due: for a single ask, measured in dollars alone, making it about the donor wins.
One thing the playbook skips, though. Those are studies of appeals — the letter, the email, the ask across a table. The case for support sits upstream of all of them. It’s the source every appeal is drawn from. Which is precisely why it’s the wrong place to pour the flattery in. What goes into the case runs downhill into everything you write after it.
The research isn’t wrong. It’s answering a smaller question than a case has to. It measures the first gift. It says nothing about the second, the tenth, or whether the donor will still be there in five years. Flattery lands that first gift. I’ve also watched it land the first gift and build nothing behind it: no second gift, no relationship, no one who stays.
Worse, it trains the donor. Tell someone often enough that they’re the hero and they start to believe it — and a donor who believes it starts to run the show, because the organization has taught itself to need his approval more than he needs the mission. That isn’t a relationship. It’s a dependency the organization built for itself, and now has to keep feeding.
Laying out a change
A case written from the organization’s point of view swells, because everyone in the building has a claim on it — the program director’s program, the trustee’s accreditation, finance’s pie chart, the board chair’s founding story. Review only adds. And leadership won’t cut it back, because a case about the organization is also a portrait of the people who run it, and vanity never asks for its own portrait to be trimmed. It isn’t the writer’s fault. The lean draft gets written; it thickens in a room where no one owns the word no.
Strip all of that away, and what remains is simple. Simple is the hard part, though — most nonprofit writing errs the other way, mistaking complication for rigor. A case for support isn’t meant to be clever. It lays out a change, in three moves: name a need, offer a plausible plan to meet it, show what changes when the plan works. Need, plan, benefit. Three questions, answered in order, in about two pages.
It’s easy to follow because it’s how anyone decides whether a problem is worth their money. Is this real? Will this work? And — the question every donor is actually asking — where do I fit? Answer those three and the donor can see the change clearly enough to find their place in it. Not as the hero of it. As part of it.
Each of the three is simple to name and easy to get wrong. Take them in order.
The need is the community’s, not yours. This is the slot where the organization-centered case fails, and it fails while feeling honest, which is why nobody catches it. “We need to raise two million dollars” is not a need. It’s your budget gap. “Four hundred families in this county are on a nine-month waiting list for services that already exist” is a need — true whether or not your organization exists, still true if you closed tomorrow. Take your organization out of the sentence. If the need falls down, you wrote about yourself again.
The plan is specific and plausible. Specific, so the donor knows exactly what their money buys. Plausible, so they believe it can be done — a real step toward the solution, not a promise to end the problem outright. Nobody believes one organization can erase the waiting list to zero, and the claim that it will isn’t visionary; it’s back to being about itself. Name the ground you can actually take: moving the list from nine months to six is a plan; ending need in your county is a mission statement in a plan’s clothes. This is also where the donor finds the answer to the question, ‘Where do I fit?’ A plan sized honestly has a place in it a donor can take — a part of the solution with their name on it, not the whole of it resting on their shoulders.
The benefit is what changes in the world. Not what the donor gets. The moment benefit turns into recognition levels, naming rights, and the donor wall, the document has quietly become a price list. The benefit is that the list drops from nine months to six — a result, in the world, for the people whose need you named at the top.
That’s the whole document. Everything else on your drive is supporting material.
Where the donor actually stands
Look at where that leaves the donor — in neither of the usual places. Not left out, and not crowned. The donor is told the truth about a real problem, a real plan, and a real outcome, and shown the exact part of it that can be theirs. A role, not a compliment.
That distinction is the one the research keeps proving, and everyone keeps misreading. Go back to that field experiment—the appeals that raised giving by 80%. They didn’t tell wealthy donors they were wonderful; they told them they could get something done. The money followed the deed, not the flattery. Telling a donor what they can do is both true and effective, at once.
Flattery is neither.
What a real case does that flattery can’t
Fundraising is a human act, not an audit; warmth is how you earn a donor’s attention. The only question is what you do with it once you have it. A real case does two things flattery never can.
The first: it says something. Your generosity makes all of this possible fits every donor to every nonprofit in the country — paste it into the case for a food bank, a symphony, a hospice, or a land trust, and not a word changes. It opens a door onto an empty room. The van now runs the Tuesday route, and the families who used to miss the food bank because they couldn’t get there don’t anymore opens onto the work, and it makes a donor feel more, not less, because the warmth is fastened to something only this organization could say. A fact also hands a donor something to do: a number to move, a claim to press you on. A compliment hands them nothing to hold.
The second is where the money actually is. Donor retention has sat near 43 percent for years, first-time retention below 20; four of every five new donors are gone within the year. The sector lands the first gift and loses the rest. What earns the next one isn’t a mystery — donors stay when they trust an organization and can see that their last gift did something, when the change they paid for shows up in the world, and someone shows them. That’s a relationship, and it grows from exactly what the case is made of: the truth about the need, and the evidence of change. It’s the real joy of giving, too — not being told you’re wonderful, but watching something you funded actually happen.
Flattery grows none of it. It hands a donor a feeling, and a feeling doesn’t renew: there’s no need they’re tracking, no plan they’re watching, no benefit they’re waiting to see land. So the warm words have to run warmer every year, and warmer costs more — and it was never yours anyway, because anyone can flatter a donor, and the organizations with money do it better than you can. What no one can copy is the donor who stayed because the list really did drop from nine months to six, and got to watch it happen.
This is good news if you run a small shop. The expensive kind of donor experience — the staff, the production, the recognition apparatus — you can’t match, and here’s the part worth hearing: you don’t need to. A case built on the truth of the need is something a two-person shop can write as well as anyone, better even, because being small puts you closer to the work than the foundation across town will ever be. Your case can say what that closeness lets you see, in specifics, a larger, more distant organization can’t match. That isn’t the lesser hand. Written honestly, it’s the stronger one.
Take your name out
So: tell the truth about the need. Say what you’ll do about it. Say what changes if you do. Give the donor a real part in the work — not the lead, a real part — and let that be enough. It is.
You already know which document you’re holding. Take your organization’s name out of the first paragraph and read it again. If the need is still standing there without you — urgent, specific, true — you have a case for support. If it falls over the moment you step out of the sentence, the organization was the subject all along, and no edit will save it, because the problem was never the writing.
That’s the whole difference between a case for support and a brochure with a budget in it. One is about the work. The other is about you.
Write the one about the work.