When grant revenue is not keeping pace with an organization’s ambitions, the obvious response is often to increase proposal volume.
There are more opportunities to pursue. The development team is already busy. Program leaders need funding. Someone on the board has identified a promising foundation. Before long, the conclusion seems self-evident: we need another grant writer.
Sometimes that is exactly right.
But writing capacity is only one part of institutional fundraising, and in many organizations it is not the part holding things back.
A nonprofit can submit more proposals without materially improving its funding position. It can add prospects faster than it can qualify them, pursue grants that are only loosely connected to organizational priorities, or spend substantial time winning restricted revenue that creates as many operating problems as it solves.
The issue in those cases is not the quality or quantity of the writing.
It is that grant writing and institutional development are being treated as the same thing.
They are not.
Grant writing is a production function. Institutional development is a management function.
The distinction becomes important as an organization grows.
The proposal comes later than we tend to think
A strong proposal matters. It needs to make the case clearly, answer the funder’s questions, present a credible budget and survive all of the small technical requirements that can undermine an otherwise good request.
But much of the work that determines whether a proposal is worth writing happens before a sentence is drafted.
Someone has to decide which opportunities deserve attention.
Eligibility is a very low bar. A foundation can technically fund an organization and still be a poor prospect. The more useful questions are whether there is genuine alignment, whether the likely award warrants the effort, whether the organization can meet the requirements comfortably, whether the relationship has room to develop, and whether pursuing the opportunity makes sense relative to everything else competing for the team’s attention.
There is a second decision that matters just as much: what are we actually asking this funder to support?
Organizations rarely have a single funding need. There may be established programs, new initiatives, capital requirements, operating pressure, workforce needs and strategic priorities unfolding at the same time.
Those needs should not simply be translated into a series of interchangeable proposals.
One funder may be exceptionally well aligned with a particular program. Another may be capable of providing flexible support. A long-standing institutional partner may warrant a larger renewal request. A new prospect may be interesting but not yet important enough to absorb significant staff time.
These are portfolio decisions.
The proposal is what comes after them.
A grant calendar can keep a team organized. It cannot decide where the organization should be going.
Most established development operations have some version of a grants calendar. They should. Deadlines, reports, renewals and submissions need to be controlled.
But a calendar and a funding strategy solve different problems.
A calendar tells the organization what is due.
A funding strategy should tell leadership what institutional revenue it is trying to build.
That requires a broader view.
Where is grant revenue concentrated? Which relationships are growing? Which programs are chronically difficult to fund? How dependent is the organization on restricted support? Where are the strongest renewal opportunities? Which funders have the potential to become meaningful long-term partners? What revenue will the organization need two or three years from now that it is not cultivating today?
Once those questions are on the table, the value of an individual application looks different.
A $25,000 grant may be highly valuable if it opens an institutional relationship with significant long-term potential.
A larger award may be less attractive if it requires the organization to create activities it would not otherwise prioritize or introduces a reporting burden that is disproportionate to the funding.
A new prospect may deserve less attention than a current funder whose relationship has never been developed beyond a routine annual renewal.
And sometimes the right decision is simply not to apply.
That discipline is one of the clearest signs of a mature development function.
The existence of an opportunity is not, by itself, a reason to pursue it.
Development has to understand the organization, not simply the funder
Institutional fundraising sits at the intersection of programs, finance, executive leadership and the outside funding environment.
It is difficult to do well from the edges of an organization.
Development needs to understand what programs actually cost, not merely what can be placed into a grant budget. It needs to know where demand is changing, where capacity exists, what outcomes can credibly be promised and what an award will require from the rest of the organization after it is made.
Finance needs to understand what development is trying to build and where restricted revenue may create pressure elsewhere.
Program leaders need to be able to articulate what additional resources would actually make possible.
And executive leadership needs visibility into how all of this fits the institution’s broader direction.
When those functions are disconnected, the grant writer often ends up compensating for decisions that have not been made elsewhere.
A proposal is drafted before the program is fully defined.
A budget is assembled to fit a request rather than to reflect the real economics of the work.
A compelling new opportunity appears and the organization reshapes the program around it.
Or development learns too late that the operational requirements attached to an award are much more significant than anyone anticipated.
These are not writing problems.
They are management problems that happen to become visible during the writing process.
This becomes especially important during periods of growth
Some of the most difficult funding decisions arise when an organization is doing well.
Consider a nonprofit that has made a major capital investment and is entering a new phase of growth.
The building may be complete or nearly complete. Programs are expanding. The organization has more physical capacity, greater visibility and a stronger story to tell.
At the same time, the capital campaign may not be fully closed, and the larger operation now carries a larger annual funding requirement.
It would be easy to treat those as two separate fundraising assignments: finish the capital campaign and find more program grants.
In practice, the development challenge is more nuanced.
The new infrastructure may strengthen the case for program investment because it allows the organization to serve more people, deliver services differently or expand into new areas. Some funders may still be appropriate capital prospects. Others may be much better suited to workforce, food access, education, healthcare or another programmatic priority. A long-standing partner may be ready for an expanded institutional relationship rather than another narrowly framed request.
The job is to understand how those opportunities fit together without allowing one funding need to obscure another.
That requires someone to manage the funding architecture of the organization.
More applications alone will not do it.
Winning the grant is not the end of the work
Another common imbalance is that organizations devote extraordinary energy to acquiring new funders while treating existing awards primarily as reporting obligations.
That leaves a great deal of value on the table.
A grant means an institution has already reviewed the organization and decided that its work merits investment. That is not merely revenue. It is the beginning—or continuation—of a relationship.
What happens between one application and the next matters.
Development should know how the funded work is performing, what has changed inside the organization, which results are likely to matter to the funder and whether there are natural opportunities to deepen the relationship.
A funder should not have to wait for the next proposal to learn something meaningful about the organization it supports.
Good stewardship also improves judgment. Over time, development learns which institutions are genuinely engaged, which relationships have room to grow, which programs resonate, where flexibility exists and where an organization may be relying too heavily on funding that is unlikely to expand.
That knowledge should influence the next funding decision.
If every cycle begins again with a prospect list and a deadline, much of that institutional intelligence is lost.
More prospects are not necessarily more opportunity
This is becoming increasingly relevant as prospect research becomes easier.
A competent researcher can already produce hundreds of possible foundations. AI will make it possible to produce thousands.
That does not mean a development team suddenly has thousands of useful opportunities.
The value increasingly lies in judgment.
Which prospects are actually credible?
Which are merely adjacent?
Which requests are worth the organizational effort they will require?
Which programs should be protected from being stretched to fit whatever funding happens to be available?
Which funders should be cultivated now even if no immediate application is open?
And which opportunities should be declined because they pull attention away from more important relationships?
The best development operations are not indiscriminate.
They are selective for a reason.
Staff time is finite. Executive attention is finite. Program leaders cannot continuously contribute to applications without cost. Finance cannot rebuild budgets indefinitely. Every proposal carries some organizational expense whether or not that expense appears on a development budget.
A strong funding strategy accounts for that.
There are times when another grant writer is exactly the right answer
None of this diminishes the value of excellent grant writers.
There are organizations with a clear institutional funding strategy, disciplined prospect qualification, well-developed programs, strong stewardship and more good opportunities than the existing team can reasonably handle.
In those organizations, additional writing capacity can be extremely productive.
The difference is that leadership already knows what the writer is being asked to accelerate.
That is the question worth answering before adding capacity.
Does the organization know which institutional revenue it wants to grow?
Does it know which funders matter most and why?
Are program and financial assumptions reasonably clear before proposals begin?
Are existing funders being developed as relationships rather than managed as deadlines?
Can leadership see where institutional revenue is concentrated and where it is vulnerable?
Are reporting and stewardship informing future strategy?
If those fundamentals are in place and the limiting factor is simply the number of strong proposals the team can produce, hire another grant writer.
If they are not, another writer may make the organization busier without making the development function stronger.
Institutional development is bigger than proposal production
At its best, institutional development gives an organization a coherent way to connect its mission, programs, finances and external funding relationships.
It helps leadership decide what is worth pursuing.
It makes program needs more intelligible to funders.
It protects the organization from chasing money that does not fit.
It builds continuity across relationships rather than treating each award as a separate event.
And it gives leadership a clearer view of where institutional revenue is coming from and where it needs to come from next.
Writing is an essential part of that work.
But it is not the whole function.
So when an organization feels that it needs more grants, the first question should not automatically be how many more proposals it can submit.
The better question is whether the organization has the development capacity to decide which proposals should be written at all.