A foundation asks for a two-page letter of inquiry first. A founder is thrilled: just two pages, I'll write it tonight, it's not even a full application. He takes his usual pitch about the organization, trims it down to two pages, and sends it off.
A month later, a polite "this isn't a fit for us right now" arrives. He didn't know an LOI isn't a shortened application, it's a separate genre with exactly one job: making the reader want to ask you for the full application. A condensed version of everything doesn't do that job.
A letter of inquiry is a short, one-to-two-page letter that opens or closes the door to a full application. It isn't written about the whole organization, it's written about one specific project matched to a specific foundation's interests, and its goal isn't to tell everything, it's to make the reader want to know more.
The first paragraph is the hook: the problem and who you are, with no long wind-up. In a few lines, the reader needs to understand what this is about and why you're the one to trust with it. Next comes what you're proposing to do and for whom: a specific project, not the organization's entire range of activities.
Then why you specifically: proof, not adjectives. Not "we're an experienced, dedicated team," but "we've run this program three times, and here's what happened." Then how much money is needed and for what, an order of magnitude with no detailed budget. And finally what the result will be. All of it fits on one or two pages, and it fits not because you were lazy, but because the genre demands brevity.
The most common mistake is writing an LOI about the whole organization at once, instead of one project matched to a specific foundation's interests. The author assumes that the more they say about their wonderful organization, the better. In reality, the reader drowns in generalities and never sees a specific proposal to respond to.
An LOI gets written after the research from researching foundations, not before it. The foundation's reader needs to feel that you know exactly who you're writing to: that your project matches what this foundation has actually funded in the past. A letter that could obviously be sent to any foundation unchanged reveals that no research happened, and it shows from the first lines.
An LOI is many times cheaper than a full application: two hours versus two weeks. That's exactly why a well-built grant pipeline, covered in your grant pipeline, is built on inquiry letters, not full applications. Many precise short attempts almost always outperform three agonizing full applications written blind.
A rejection at the LOI stage costs you two hours, not two weeks, which makes the genre a perfect tool for reconnaissance. You quickly test many foundations and put real effort into a full application only where the LOI already sparked interest. This saves months of work over a year.
Below is a builder that assembles an LOI draft step by step, drawing on data about the foundation from your short list.
An LOI draft for a real foundation from your short list. This is the module's first working document, not a practice exercise, a letter that, after polishing, can actually be sent. Keep it next to your short list, so you have a version for each foundation.
How is an LOI different from a full application?
An LOI is many times shorter and solves one problem: spark interest and get an invitation to submit a full application. It's a gate, not the application itself.
Does every foundation ask for an LOI?
No, foundations have different processes: some want a full application right away, others start with an LOI. What's needed is always written in the foundation's guidelines.
Can I send the same LOI to several foundations?
Technically yes, but it almost always backfires. A strong LOI is noticeably tailored to a specific foundation, and a generic letter reads as an absence of research.
What do I do after a rejection at the LOI stage?
Don't get too upset: the cost of a rejection here is just two hours. Note the reason if one's given, and move to the next foundation on your list, you can continue the relationship with this one later (program officers).
An LOI promises a result in a few words, but a real application requires showing exactly how your actions turn into change. Many organizations stumble right here: confusing what they do with what changes because of it. The next lesson is about the logic model, the tool that brings order to that chain.