We call it keeping overhead low.
The overhead ratio - the percentage of organizational spending that goes to administration and operations rather than direct program delivery - has become the primary metric by which donors, foundations, and watchdog sites like Charity Navigator judge nonprofit quality. A low overhead ratio signals efficiency. A high one signals waste. The logic sounds reasonable until you follow it to its operational conclusion.
A $5M nonprofit and a $5M business unit are solving nearly identical operational problems. Both are tracking their constituents. Both are measuring outcomes. Both are reporting to stakeholders and managing a distributed workforce. One of them has a BI platform, a configured CRM, automated reporting pipelines, and a dedicated IT function. The other has Google Sheets, a donor database installed by a volunteer in 2012, and one part-time administrator holding it all together.
The difference is not leadership. It's not ambition. It's not even skill - the nonprofit's program director often has credentials and sector experience that her corporate counterpart can't match. The difference is that when the business unit budgets for operational infrastructure, it calls that investment "operations." When the nonprofit does it, the sector calls it overhead and penalizes accordingly.
The result is an infrastructure deficit that compounds year over year, and a sector-wide assumption that this is simply the cost of doing mission-driven work. It isn't. It's a structural choice that we've been making collectively for decades - and it's time to call it by its right name.
The gap isn't abstract. It shows up in specifics that anyone who has worked inside a nonprofit organization will immediately recognize.
Grant reporting is one of the clearest examples. Most nonprofits manage grant compliance reporting entirely in spreadsheets - one spreadsheet per funder, formatted differently for each, manually updated after every service delivery event by program staff who were hired to deliver programs, not manage data. When a foundation asks for a mid-year report on client outcomes, a nonprofit leader without proper data infrastructure doesn't pull a report. She reconstructs one from multiple sources, spending time that could have gone to mission delivery on data archaeology.
Donor management is another. The average nonprofit CRM is either underconfigured enterprise software (Salesforce NPSP set up by a volunteer who has since moved on, with half the records incomplete and no documentation of the original data model) or a legacy system purchased in a prior decade that no longer integrates with anything else the organization uses. When donor records are duplicated, incomplete, or disconnected from program data, major gift cultivation becomes guesswork.
The absence of integrated data infrastructure means most nonprofits cannot answer the question that every funder now asks: what is your cost per outcome? Not because they don't care about efficiency, but because they don't have the data plumbing to calculate it. Program data lives in one system. Financial data lives in another. There is no integration, no ETL process, no unified view. The answer to "what does it cost to move one person from housing insecurity to stable housing?" requires a manual calculation that a data analyst at a foundation takes for granted and a nonprofit program director has never had the tools to produce.
NTEN has documented the technology gap in the nonprofit sector for years. TechSoup has built an entire organization around providing access to discounted software for nonprofits. Both organizations are doing important work, and both represent an acknowledgment by the sector that the problem is real.
But discounted software solves approximately 20% of the problem. The other 80% is implementation, configuration, training, and ongoing support - and none of that has a funding mechanism that scales.
A nonprofit can obtain a Salesforce NPSP license at a dramatically reduced rate through TechSoup. Obtaining the license does not configure the system, clean the existing donor data, build the custom reports that match the organization's funding compliance requirements, or train the staff who will use it every day. Implementation of a nonprofit CRM typically costs between $15,000 and $50,000 in consulting fees, even before staff time is factored in. That cost does not appear in the TechSoup discount. It appears in the overhead budget - which the organization has been told to minimize.
The funding structure creates a direct incentive against infrastructure investment. Foundations award program grants for direct service delivery. Capacity-building grants - which would cover technology infrastructure, staff training, and systems development - are rarer, smaller, and often require the organization to demonstrate it already has the capacity to absorb the investment. Multiyear operating grants that give organizations the flexibility to invest in infrastructure without justifying every dollar against direct program outcomes exist in only a handful of forward-thinking foundations.
Most nonprofits are operating on annual grants for program delivery, with overhead caps that make any significant technology investment look like mismanagement. The infrastructure doesn't get built not because nonprofit leaders don't understand its value, but because the funding model makes building it financially punitive.
When I was managing an $89M fleet operation at Enterprise Mobility, I built Power BI dashboards and API-driven reporting pipelines that eliminated manual Excel workflows for two to three staff members. I integrated Dayforce and Workday into unified data views that let leadership make staffing decisions in real time instead of from week-old reports. The investment in infrastructure paid back in staff time within weeks.
The same analysis - the SQL-based root-cause work that identified the scheduling inefficiencies driving overtime costs - ultimately saved approximately $221,000 annually and reduced overtime by 23%. That analysis was possible because I had clean, integrated, trustworthy data. It was not possible before the infrastructure existed to support it.
Nonprofits need exactly this kind of infrastructure, and the operational problems they're solving are no less complex. Impact measurement across multiple program lines for multiple funders with different reporting requirements is at least as analytically demanding as fleet utilization optimization. Donor stewardship at scale - understanding which relationships are warming, which are at risk, what communication cadence is working - requires the same kind of CRM intelligence that a corporate sales organization applies to pipeline management. Workforce management for a distributed staff of program workers, case managers, and volunteers is a scheduling and capacity problem that would be recognizable in any operations context.
The tools exist. The problems are real. The gap is the funding model that treats the infrastructure as waste.
The good news is that this is a solvable structural problem. It requires funders to change some assumptions, but the path is clear.
Multiyear general operating support is the single highest-leverage investment a foundation can make in a nonprofit's operational capacity. When organizations have predictable, flexible funding, they can make infrastructure investments that pay back over multiple years - the same logic any CFO would apply to a capital expenditure budget. Operating within annual grant cycles makes it nearly impossible to make investments that pay back on a three-year timeline.
Explicit capacity-building grant programs - with realistic budget amounts, reasonable overhead allowances, and recognition that implementation costs money - allow organizations to make technology investments that wouldn't survive a standard program grant budget. Funders like the Packard Foundation and MacArthur Foundation have infrastructure grant programs that exist precisely for this reason. They are the exception, not the rule, and they are oversubscribed.
Removing overhead penalty from grant evaluation criteria would, alone, meaningfully change what organizations feel safe investing in. The overhead ratio tells you almost nothing about organizational effectiveness and almost everything about how an organization categorizes its spending. Funders who have moved away from overhead ratio as an evaluation criterion and toward outcome efficiency metrics consistently find that their grantees make better long-term decisions.
The communities nonprofits serve are often the same communities that are underserved by the private sector, underinvested in by government, and most dependent on the operational effectiveness of the organizations trying to help them. Those communities deserve organizations with real capacity to measure impact, manage resources, and adapt to changing conditions.
Operational capacity requires infrastructure. Infrastructure requires investment. Investment shows up in overhead budgets. We have built a funding model that penalizes the investment that makes the mission possible.
That's not an inevitability. It's a choice - made at the foundation level, reinforced by watchdog rating agencies, and accepted by a sector that has learned to work around it instead of naming it clearly.
Overhead isn't a dirty word. It's what makes organizations work. The question the sector needs to ask is not how to minimize it, but how to invest it wisely - and whether the funding structures we've built make wise investment possible.
For the organizations doing the most important work in the country, the answer right now is mostly no.