Most people think grant writing is about writing. You find the RFP, you read the questions, you sit down and answer them as beautifully as you can, and you hit submit. If the answer comes back no, the conclusion is usually that the narrative needed work, or the budget justification was thin, or someone else just wrote a better story.

Sometimes that's true. But more often, the application was decided long before anyone opened the portal. By the time you're filling out the form, you're not making your case. You're showing the receipts for a case you either already built or didn't.

The foundation is the application

Look at what a funder actually asks for. Your financial statements. Your board roster. Your conflict of interest policy. How you track outcomes. Who handles the money and who checks their work. What happens if your executive director gets hit by a bus. None of that is writing. All of it is infrastructure.

A grant application is really a series of questions about whether your organization can be trusted with someone else's money and someone else's mission. The narrative sections get the attention, but the attachments and the checkboxes are where a lot of applications quietly fall apart. You can't write your way into having a fiscal policy. You either have one or you're drafting it at 11pm the night before the deadline, and reviewers can usually tell which.

When the nonprofit I founded applied for its first major government grant, we were about eight months out from our very first program. What carried that application wasn't clever prose. It was the work we'd already done: the governance, the documentation, the data collection we'd built into our programming from day one. The application just gave us somewhere to point to it.

So if you're a small or new organization and you want to be "grant ready," the most valuable hours you spend probably won't be on any application at all. They'll be on the boring stuff. Board policies. A real budget with real controls. A way to measure what you do. The application is the last step, not the first.

The relationship nobody tells you to build

The other thing people miss is that grants are relationships too.

We all know that major gifts are about relationships. Nobody expects a wealthy individual to write a big check after one cold email. You cultivate. You meet for coffee. You learn what they care about and you show them how your work connects to it. Family foundations, same thing.

But somehow, when it comes to institutional grants, a lot of organizations treat the process like a vending machine. Put in the application, wait to see if money comes out. Meanwhile, there's a program officer on the other side who is a person, who has a portfolio, and who very much prefers funding organizations they already know.

If the first time a program officer hears your name is when your application lands in their queue, you're starting from behind. The organizations that get funded have usually been in conversation for months: an introductory call, a site visit, an update when something worked, a question about whether a new program fits their priorities before submitting anything.

A program officer isn't a donor

Here's where it gets different, though. The relationship with a program officer is built on a different foundation than the relationship with an individual donor.

With an individual donor, the whole game is connecting your work to what that person cares about. Their values, their history, the cause that moved them. They're giving their own money, and they get to give it for their own reasons.

A program officer isn't giving their own money. They're stewarding an institution's mission, and they have to defend every recommendation to a committee, a board, or a set of strategic priorities they didn't personally write. They might love you. That doesn't matter much if they can't make the case for you internally.

So your job isn't to appeal to what the program officer cares about. Your job is to show them that funding you fulfills their mission, and then give them the evidence they need to prove it to the people above them. Shared mission is the entry point. Proof is what actually closes it.

Proof is readiness

This is where the two halves of this conversation meet. Proof doesn't come from a well-written outcomes section. It comes from having the mechanisms to measure your impact in the first place.

If you can't tell a program officer what changed for the people you serve, how you know, and how you'll keep knowing, you're asking them to take your word for it. And taking your word for it is not something they can put in a funding recommendation.

At my nonprofit, we started collecting mood data from participants early, before anyone asked us to, because we knew that eventually someone would want to know whether this works. That habit is now one of the most useful things we bring to a funder conversation. Not because the numbers are perfect, but because they exist, they're consistent, and they let a program officer say "here's what this organization does" with something more than a feeling.

And our measurement is built to grow with the program. Alongside our drop-in classes, we're expanding to offer closed cohorts, where the same group of people moves through a curriculum together. With that expansion, we're adding longitudinal tracking using established, peer-reviewed tools that measure things like resilience and social support. That means following how people change over the full arc of a program, not just how they feel at the end of one class. That plan isn't something we'll figure out once the money comes in. It's part of the expansion itself, because a funder shouldn't have to wonder how we'll know whether it worked.

That's the lesson for any organization: when you ask a funder to help you grow, your plan for proving the growth works belongs in the same ask.

That's the whole point. Organizational readiness isn't paperwork for its own sake. It's what makes you fundable, and it's what turns a relationship with a program officer from a friendly conversation into a partnership they can actually justify.

Build the house first

If there's one takeaway, it's this: stop treating the grant application as the work. The work is building an organization sturdy enough that the application almost writes itself, and building relationships with the people who will read it long before you ask them for anything.

Get your policies in place. Set up your financial controls. Start measuring now, even if it's simple. And go talk to program officers when you don't need anything yet, with a clear sense of how your work advances what they're trying to do.

By the time the RFP drops, you shouldn't be starting. You should be finishing.