Your Beneficiary Isn't Always Your Customer: The Buyer vs. Beneficiary Problem
A workforce program in your city hits every number in its state contract. Enrollment target: met. Job placements within 90 days: met. Cost per participant: under budget. The state renews the contract. The press release goes out.
Ask the case managers who ran it, though, and you'll hear a different story. The participants who were hardest to place — people with recent incarceration, unstable housing, no reliable transportation — got quietly triaged to the back of the line, or referred out, or left off the roster entirely. Not because staff didn't care. Because the contract paid per placement, and placing someone who was already close to job-ready cost less time and hit the number faster than placing someone who needed six months of support to get there.
The state got what it paid for. The people who needed the program most did not get what they needed.
This isn't a story about a bad nonprofit or a lazy caseworker. It's a story about who the program was actually designed to satisfy — and it is the single most common structural problem in mission-driven work: the person paying for a service and the person receiving it are not the same person, and most programs are quietly built for the one who pays.
When success on paper doesn't mean success for the people who needed it most
The Accepted Story
When a funded program underperforms for the people it's supposed to serve, the usual explanations sound like this: the nonprofit needs better outreach. The community is "hard to reach" or "disengaged." The staff needs more training. The org needs to demonstrate more impact to justify its next grant.
Every one of those explanations puts the burden back on the organization or the community. None of them asks a more basic question: who was this program actually designed to please?
The Reclaimers Reframe
This is not a program-quality problem. It is a customer-definition problem.
In a normal market, the person who pays for a product is the person who uses it, and their satisfaction (or their choice to walk away) is the feedback loop that keeps the product honest. In most nonprofit and public-good work, that loop is broken. A government agency, foundation, insurer, or institutional partner pays. A resident, patient, student, or client receives. The buyer defines what "success" means in the contract. The beneficiary lives with whatever that definition leaves out.
Product designers who build enterprise software have a name for a version of this same problem. It's sometimes called Grudin's Law, after researcher Jonathan Grudin's observation about workplace technology: when the people who benefit from a system are not the people who do the work of using it, the system tends to fail or get quietly subverted [9]. The social sector version is a mirror image — when the people who benefit from a program are not the people who define what "working" means, the program tends to optimize for the wrong thing, even while hitting every number in the contract.
Your beneficiary isn't always your customer. Until an organization names that split honestly, it will keep building things that satisfy funders and quietly fail the people those funders claim to be helping.
The Machinery Underneath
This gap isn't accidental. It's the predictable output of how money moves through the sector.
Government contracts are written around what's auditable, not what's effective. In 2023, two-thirds of U.S. nonprofits held at least one government grant or contract, generating roughly a quarter of average revenue [1]. Those contracts routinely underfund the real cost of the work: 76% of nonprofits with a capped indirect cost rate could recover less than 10% of overhead, and a quarter recovered nothing [1]. Mid-contract, 44% reported governments changing eligibility rules or adding reporting burdens with no added funding [1]. None of that optimizes for the beneficiary's experience. It optimizes for what a government auditor can defend in a budget hearing.
Performance-based contracts reward the easiest version of the work. When payment is tied to metrics like job placements, providers respond rationally: serve whoever hits the metric fastest, and defer the people who'd take longer. Researchers studying performance-contracted job placement services documented exactly this — providers under high-powered performance contracts shifted toward clients easiest to place, a pattern known as cream-skimming [2]. The contract wasn't broken. It worked exactly as designed, for the buyer's metric, not the hardest-to-serve beneficiary.
Funders often don't price what the work actually costs. The "nonprofit starvation cycle," named by researchers Ann Goggins Gregory and Don Howard in 2009, describes how funders' unrealistic expectations about overhead push nonprofits to underspend on the infrastructure that makes programs work — which reinforces funders' belief that lean is good [3]. The beneficiary experiences the resulting thin version of the program. The funder sees a low overhead ratio and calls it efficient.
Pay-for-success models can formalize the split instead of closing it. Social impact bonds route government payment through private investors repaid only if outcome targets are hit — which can push providers toward whichever beneficiaries are easiest to help, since missing targets means investors don't get paid [4]. The structure protects the payer's return, not a guarantee that the beneficiary got what they needed.
Different sectors, same architecture: whoever controls the money defines the terms, and whoever the terms are for has no seat at the table.
Who Absorbs the Cost
The people closest to this gap pay for it in specific ways.
Case managers absorb it as moral injury — quietly deciding who gets served this quarter because the contract rewards speed over need, then carrying that decision home. Beneficiaries absorb it as service that technically exists but doesn't fit: a job program that ignores their transportation, a housing intervention measured by exits rather than whether anyone stayed housed. Organizations absorb it as chronic instability, chasing whatever metric keeps the contract alive instead of what the community actually needs. And trust erodes on all sides — funders conclude the sector is inefficient, beneficiaries conclude the program was never really for them, staff conclude the work is unsustainable.
None of that is evidence that people don't care. It's evidence of a model that never asked the beneficiary what success should mean.
What a Better Model Requires
Closing the buyer-beneficiary gap doesn't mean refusing government contracts, walking away from foundation funding, or pretending institutional buyers are the enemy. It means building deliberate mechanisms that give beneficiaries real influence over what "success" means and real recourse when a program isn't working for them — even when they aren't the ones signing the check.
Four components matter most:
Shared metric design. Write outcome definitions with beneficiaries in the room before a contract is signed, not report them after. If a workforce contract only counts 90-day placements, add what a beneficiary would define as success: job quality, commute time, retention at six months.
Governance seats, not advisory panels. The difference between consultation and power is whether a beneficiary can change a decision, not just comment on it. Federally Qualified Health Centers are legally required to seat a governing board where at least 51% of members are patients [5]. That's not a suggestion box — it's a binding vote over budget, staffing, and strategy, the same leverage a customer has when they can take their business elsewhere.
Ownership tied to the beneficiary, not just the payer. In Cleveland, anchor institutions including the Cleveland Clinic, Case Western Reserve University, and University Hospitals agreed to direct a share of their combined billions in annual purchasing toward Evergreen Cooperatives, worker-owned businesses built in low-income neighborhoods [6]. The institutions are still the buyer, but the workers are owners: over several years, each worker-owner has accumulated real equity in the business [6]. The buyer relationship got restructured so beneficiaries hold a permanent stake in the value it creates.
A feedback loop that costs the organization something when ignored. In participatory grantmaking, the people affected by a funding decision help make it. The Trans Justice Funding Project seats a rotating panel of trans and non-binary community fellows who score every application and decide award sizes [7]. The Omaha Community Foundation runs grant committees made up of residents who identify with the population served [8]. In both cases, the funder gave up sole authority over what "worth funding" means — the only way a feedback loop becomes real instead of decorative.
None of this requires abandoning institutional money. It requires building structures where institutional money doesn't get the only vote.
The Buyer-Beneficiary Alignment Audit
Use these five questions on any funded program, contract, or partnership your organization runs:
Map the split. Who signs the check, and who receives the service? Write both down. If they're the same person, this framework doesn't apply to you. If they're not, keep going.
Who defined success? Did the beneficiary have any input into the outcome metrics in your contract or grant agreement — or were they set entirely by the payer, based on what's easy to report?
Does the beneficiary have real recourse? If a beneficiary is unhappy with your program, can they change it, escalate it, or leave without losing access to something they need? Or are they functionally captive to whatever you built?
Does a beneficiary sit where decisions get made? Not a satisfaction survey. Not a listening session. A seat with a vote on budget, staffing, or strategy.
If the payer's priorities and the beneficiary's needs diverged tomorrow, which one would you follow? Be honest about what your funding structure forces you to do, not what your mission statement says you'd do.
If most of your answers point toward the payer, you don't have a beneficiary-centered model yet. You have a funder-satisfaction model that happens to serve people as a byproduct — and that model breaks exactly when a beneficiary's needs and a funder's priorities stop lining up.
What to Measure Instead
Contracts and board reports tend to track what's easy to count: people served, dollars raised, services delivered. None of those numbers tell you whether the buyer-beneficiary gap is closing. Track these instead:
Beneficiary retention and return rate — do people come back voluntarily, or only when mandated?
Beneficiary representation in governance — what share of your board or advisory structure is made up of people who use your services, with an actual vote?
Share of contracts with beneficiary-defined metrics — how many of your funding agreements include an outcome the beneficiary helped set, not just the payer?
Complaint-to-change ratio — when a beneficiary raises a concern, how often does something in the program actually change?
Revenue concentration — what share of your budget comes from a single buyer whose priorities you can't afford to challenge?
These are harder to report in a grant deck than "number served." They're also the numbers that tell you whether your beneficiary has any power at all.
The Choice Underneath
Every funded program makes this choice, whether or not anyone names it out loud: build for the one who pays, or build power for the one it's for. Most programs default to the first option, not out of bad intent, but because that's who wrote the contract and who renews it.
Naming the gap doesn't fix it by itself. But it's the precondition for fixing it — you cannot redesign a system you've been describing as a program quality problem. The organizations that close this gap don't do it by refusing institutional money. They do it by building governance, metrics, and ownership structures that hand real power to the people closest to the problem, so the beneficiary's voice carries weight the funding relationship alone would never give it.
You don't need another strategy document that names this tension and then goes quiet on what to do about it. If you're trying to redesign the funding, governance, or measurement system underneath your work so it answers to the people it's for — not just the people who fund it — The Reclaimers can help you build the version that lasts.
Run the Buyer-Beneficiary Alignment Audit on your own program this week. Then book a Fit Call with The Reclaimers, and let's pressure-test the model together.
Sources
Urban Institute, "Nonprofit Trends and Impacts 2021–2023: National Findings on Government Grants and Contracts from 2019 to 2023" (2024, data year 2023) — Nonprofit Trends and Impacts 2021–2023: National Findings on Government Grants and Contracts from 2019 to 2023
Pierre Koning & Carolyn Heinrich, "Cream-Skimming, Parking and Other Intended and Unintended Effects of High-Powered, Performance-Based Contracts," Journal of Policy Analysis and Management (2013) — Cream‐Skimming, Parking and Other Intended and Unintended Effects of High‐Powered, Performance‐Based Contracts
Ann Goggins Gregory & Don Howard, "The Nonprofit Starvation Cycle," Stanford Social Innovation Review (2009) — The Nonprofit Starvation Cycle (SSIR)
Social impact bond / pay-for-success criticism, secondary analysis — Social impact bond and Paying for success: An appraisal of social impact bonds
HRSA Bureau of Primary Health Care, Health Center Program Compliance Manual, Chapter 20: Board Composition (current, updated Oct. 2025) — Chapter 20: Board Composition | Bureau of Primary Health Care
Fifty by Fifty / Community-Wealth.org: Wealth-Building Strategies for America's Communities reporting on Evergreen Cooperatives, Cleveland — https://www.fiftybyfifty.org/2021/03/evergreen-cooperatives-adapt-and-grow/ and Evergreen Cooperatives take the spotlight in Cleveland, OH during GOP Convention
Trans Justice Funding Project, participatory grantmaking model — Fund 101: What Is Participatory Grantmaking?
Omaha Community Foundation, participatory grantmaking model — Participatory grantmaking: What happens when communities help decide? -
9. Jonathan Grudin's concept ("Grudin's Law"), summarized via Donald Norman, Things That Make Us Smart, and secondary explainer — https://experiencecurve.com/grudins-law/ (used as a cross-sector analogy, not sector-specific data)
