A Case for Support Is Not a Strategic Plan

I work with a lot of organizations to refine or create their case for support. Recently, in two instances, the team came to the table wanting to turn their strategic plan into a fundraising document.

It doesn't work that way.

A case for support is an external communication tool. Its job is to articulate, in plain language, what problem your organization exists to solve, why you are the best suited solution to that problem, why it matters now, and what partnership with you makes possible. It's designed to move someone from interest to investment. It's not a brochure, a grant proposal, or an annual report. It's the foundational argument for why someone should fund your work.

A strategic plan is an internal operational document. It tells your team where you're going and how you'll get there. It's full of KPIs, timelines, and organizational priorities that matter deeply to staff and board but mean almost nothing to a prospective donor reading your materials for the first time.

When Five Leaders Tell Five Stories

One organization I'm working with has a beautiful and ambitious strategic plan centered on expanding programming from one city to a national footprint. When I sat with their leadership team and asked each person to articulate their five-year vision, I got five different answers. Not contradictory, exactly, but each leader emphasized something different based on their role: the program director talked about reaching more youth, the finance director talked about revenue sustainability, the marketing director talked about becoming a household name, the ED talked about replicating a culture of care.

That moment is always clarifying. You can feel the energy shift in the room when a team realizes that their internal alignment is much looser than they assumed. And that's not a failure. It's exactly why you do this work before you put a document in front of a donor.

That diversity of perspective is healthy inside an organization. But if it shows up in your external messaging, it creates confusion for supporters. The case for support is where you take all of those internal threads and weave them into a single, compelling narrative that anyone can understand and feel motivated by.

The framework I use is straightforward. Start with the "why": the vision for the world that's bigger than your organization. Then name the "need": the specific barriers preventing that vision from being realized. Then show how your organization uniquely addresses that need, with proof. Then make the invitation to partnership concrete.

If you're struggling to articulate your case, the problem isn't usually that you don't have a compelling story. It's that you're trying to tell every story at once. The best cases for support are ruthlessly focused. They say one thing clearly, not five things vaguely.

Need help building or refining your case for support? Let's start with a conversation. (opens in new tab)