Dana is the only person at her youth services nonprofit who writes grants, and she spent most of a month on a full proposal to a foundation that declined it in a single sentence: the project fell outside their geographic priorities. That information had been available before she started. The Letter of Inquiry exists precisely to prevent that month from being wasted, both for her and for the funder, and learning to write one well is the highest-leverage grant skill a small development office can build. An LOI is short, it is fast, and it is the gate that most foundation money now passes through.

What an LOI Is and Why Funders Use Them

A Letter of Inquiry is a brief preliminary application, typically 1 to 2 pages, that many foundations use to screen proposals before inviting full applications. Think of it as a pre-proposal. The funder reads a short document, decides whether the fit is plausible, and invites the promising applicants to submit everything else. Nothing about that process is adversarial, and understanding why funders adopted it is the fastest way to write LOIs that get invited rather than filed.

From the funder's side, the LOI is a workload and quality instrument. It reduces the reading burden enormously, because they review 50 LOIs instead of 50 full proposals. It filters out poor-fit applicants early, before either party has invested serious time. It helps program officers identify the promising opportunities they want to pursue. And it speeds up decision-making across the whole cycle, which matters when a foundation is trying to move money on a fixed calendar. A funder who receives a poorly targeted full proposal has lost hours; a funder who receives a poorly targeted LOI has lost minutes.

From your side, the arithmetic is even better. You only write a full proposal if you are invited, which saves the time Dana lost. If your LOI is rejected you can request feedback and improve, which is a far cheaper lesson than a declined proposal. And the effort ratio is not close: an LOI takes 2 to 3 hours, while a full proposal takes 20 to 40 hours. That ratio is the entire strategic argument for treating LOIs seriously rather than dashing them off. A handful of well-researched LOIs costs you roughly what a single full proposal costs, and it tests that many hypotheses about fit instead of one.

LOI Structure and Components

The standard LOI runs 1 to 2 pages single-spaced, which is roughly 250 to 500 words. That constraint is unforgiving and it is the reason most LOIs fail: writers try to compress a full proposal instead of writing a different document. Check the funder's own guidelines first, because they override anything here, but where a funder is silent the following components are what reviewers expect to find, in this order, with these proportions.

Read that grid as a budget rather than a checklist. Within a document of a few hundred words, a paragraph is a substantial allocation, and the bullet points for outcomes are doing as much persuasive work as everything above them. If your draft has four paragraphs of need and one sentence about your solution, you have not written a short proposal; you have written the wrong document.

LOI Template

The following template gives you the skeleton. Replace the bracketed placeholders with your own specifics, and resist the temptation to add sections that the funder did not ask for.

[YOUR ORGANIZATION LETTERHEAD]

[DATE]

[FUNDER NAME]
[PROGRAM OFFICER NAME]
[ADDRESS]

RE: Letter of Inquiry - [PROJECT NAME]

Dear [PROGRAM OFFICER NAME]:

Executive Summary
We are seeking $[AMOUNT] from [FOUNDATION NAME] to [SPECIFIC ACTION] that will [SPECIFIC OUTCOME]. This project is critical because [BRIEF JUSTIFICATION]. We have served [POPULATION] since [YEAR], and this grant will allow us to [SCALE/IMPROVE] our impact.

The Problem
[SPECIFIC DATA] shows that [PROBLEM] affects [POPULATION] in [GEOGRAPHY]. For example, [SPECIFIC STATISTIC]. This creates [CONSEQUENCE]. Existing solutions are insufficient because [GAP IN CURRENT APPROACHES].

Our Solution
[YOUR ORGANIZATION] will [SPECIFIC ACTIVITIES]. Our approach is evidence-based because [RESEARCH/DATA]. We will serve [NUMBER] individuals over [TIMEFRAME]. Our past work demonstrates our capacity: [SPECIFIC PAST RESULT].

Expected Outcomes

• By [DATE], [NUMBER] individuals will [SPECIFIC OUTCOME]
• By [DATE], [METRIC] will improve by [PERCENTAGE]
• [ADDITIONAL OUTCOME]

Funding Request
We are requesting $[AMOUNT] to support [NUMBER]-month implementation. This investment will [SPECIFIC RESULT]. Our total project budget is $[TOTAL], with [X%] coming from [OTHER SOURCES].

Closing
We believe this project aligns perfectly with [FOUNDATION NAME]'s commitment to [THEIR PRIORITY]. We would welcome the opportunity to discuss this further. Thank you for considering this proposal.

Sincerely,
[YOUR NAME]
[TITLE]
[ORGANIZATION]
[PHONE]
[EMAIL]

How to Write Each Section

Executive Summary, the hook. This first paragraph determines whether they read the rest, so make it compelling rather than administrative. It needs to carry your organization's name, what you are asking for, why it matters, and what impact it will have, all in the space of a few sentences. A working example: "The Martin Luther King Community Center seeks to expand our afterschool mentoring program, reaching 200 additional youth in East Sacramento. Last year, our participants showed 40% improvement in school attendance." Notice that the second sentence is doing the persuading. It is not a claim about intention; it is a result that already happened, which is the only kind of evidence that makes a stranger believe your forecast.

Statement of Need, the evidence. Use data, research, and local statistics to prove the problem is real and urgent in your specific place. Do not just say "children need mentorship." Say: "In Sacramento County, 35% of high school students are chronically absent, compared to 21% statewide. Students with mentors show 64% higher attendance rates." Cite your sources. Use specific numbers rather than vague claims. The comparison to the statewide figure is what makes the local number mean something, because a reviewer with no knowledge of your county cannot tell whether a rate is alarming until you give them something to measure it against.

Project Description, the action. Describe what you will actually do, concretely enough that a reader could picture a week of it. Not: "We will provide mentoring." Instead: "Each student will be paired with a trained mentor for 1-on-1 meetings twice weekly. Mentors will focus on academic support, confidence-building, and college planning. Mentees will set quarterly goals and track progress using our custom tracking system." The specificity is not decoration. It is the evidence that a real program exists behind the proposal, because vague descriptions are what organizations write when the design has not been done yet, and program officers know that.

Expected Outcomes, the proof points. Use bullet points here, and start each one with "By [DATE]" so that every outcome carries a deadline and a metric. Examples: "By June 2027, 80% of program participants will report improved school attendance" or "By December 2026, graduating seniors will have submitted 25 college applications." An outcome without a date is an aspiration, and an outcome without a number cannot be reported on later. Since your eventual grant report will be judged against exactly these lines, write outcomes you would be willing to be measured by.

Funder-Specific Customization

Never send the same LOI to two different funders. The core of your document stays the same, but four things should change for every recipient, and reviewers can tell instantly when they have not. Reference their specific priorities in their own words: "Your foundation's focus on youth leadership aligns perfectly with our mentoring approach." Match their grant size, requesting an amount in the band they typically give rather than one far above or below it. Match geography, emphasizing the impact that falls inside the area they fund. And reference their past grants: "We see you funded [similar organization] in 2024 for youth programs" tells a program officer you did the homework before writing.

The reason this works has nothing to do with flattery. A foundation's priorities are the criteria their board approved, and a program officer advancing your LOI has to explain internally why it fits those criteria. Every sentence in which you have already made that connection is a sentence they can lift straight into their own summary. You are not persuading a reader; you are equipping an advocate.

From LOI to Full Proposal

If you are invited to submit a full proposal, your LOI becomes its foundation rather than a discarded draft. Each section expands roughly in proportion to its importance in the longer document. The executive summary becomes the 1 to 2 page proposal introduction. The statement of need expands to 2 to 3 pages with more research and local data. The project description expands to 3 to 4 pages with a detailed timeline, staffing, and activities. The outcomes develop into a full evaluation plan with data collection methods attached to each measure.

You are not starting over. You are adding detail and evidence to what was already written, which is another reason to write the LOI carefully in the first place: a sloppy LOI that somehow gets invited leaves you rebuilding the argument under deadline pressure, while a well-structured one leaves you filling in what you already know. Keep the LOI in the same folder as the proposal draft and track any changes, because a full proposal that contradicts the LOI it grew from is a credibility problem that reviewers do notice.

Submission Best Practices

• Submit 5 to 7 days before the deadline rather than on the day itself, so that a portal failure or a formatting problem is recoverable.
• Proofread 3 times for typos, spelling, and grammar. In a document of a few hundred words, one error is a visible proportion of the whole.
• Use the funder's specified format exactly, whether that is PDF, Word, email, or an online form.
• Include all required attachments: organizational summary, 501(c)(3) letter, and board list.
• Send from an official organization email address rather than a personal one.
• Save the document with clear naming, such as "[ORG NAME]_LOI_[FUNDER]_[DATE]", so you can find it again when the next cycle comes around.
• Keep a copy for your records and your grant tracking, since the LOI is the starting point for both the proposal and the next cycle's application.

LOI Success Rates and What They Mean

It helps to know the shape of the funnel you are entering. A typical funder receives 50 to 100 LOIs and invites 15 to 25 of them to submit full proposals, which is a 15 to 25% LOI success rate. Of those invited, 50 to 70% receive full funding, giving a 7 to 18% full funding rate overall. Those figures are worth sharing with a board that expects grant writing to feel more certain than it is, because they establish that a decline is the normal outcome of a single application rather than a verdict on the organization.

What you do with a rejection matters more than the rejection itself. Request feedback and ask a specific question: "What would strengthen our LOI for next year?" Feedback improves future applications in a way that guessing cannot, and program officers frequently answer when asked politely and briefly. If you are invited to submit a full proposal, you have passed the first major hurdle; now the task is writing an excellent full proposal on the foundation the LOI already laid.

Anti-Patterns

• Too vague. "Our program helps youth succeed" says nothing a reviewer can evaluate. "Our mentoring program increases school attendance by an average of 22 percentage points for at-risk high school students" gives them something to weigh.
• No data. Every claim should have evidence behind it. "This problem affects thousands of families" is weak; "In our service area, 1,247 families live below the poverty line according to 2024 Census data" is strong because it is checkable.
• Asking for the wrong amount. Requesting far more than a funder typically gives makes an invitation unlikely, and requesting far less than you need means you will be underfunded even if you win. Both errors come from skipping the research on their grant range.
• Focusing on need instead of solution. Spend 30% of the LOI on the need and 70% on your solution. Funders already know the problem exists; what they do not know is whether you can solve it.
• Ignoring funder priorities. Every LOI should include 1 to 2 sentences showing you understand what they care about. "Your foundation's commitment to environmental justice resonates deeply with our work" demonstrates homework, and its absence demonstrates the opposite.
• Compressing a full proposal. Cutting a full-length narrative down to two pages produces dense, unreadable text. The LOI is a different document with a different job, and it should be written from scratch to that job.

Practice Prompts

• Draft one LOI against the word budget. Write a complete LOI for a real prospect and hold it to 1 to 2 pages. Then count the words in each section and compare against the component table.
• Rewrite your weakest sentence. Find the vaguest claim in an existing proposal and rewrite it with a specific, checkable number and a source.
• Build a funder profile before you write. For one target funder, record their priorities, typical grant size, geography, and one recent grant to a similar organization. Then write the two customization sentences that reference all four.
• Test the need-to-solution ratio. Take a draft and mark which paragraphs describe the problem and which describe your response. If the balance is not close to 30% need and 70% solution, rebalance it.
• Write three outcomes with dates. Draft outcome bullets that each begin with a date and end with a metric you could actually report on when the grant period closes.
• Make the fit-check call. Script the short call to a program officer asking whether your work is a plausible fit, and make it before your next submission.
• Set up your submission file naming. Adopt a naming convention and a tracking sheet, then retroactively rename last year's LOIs so the archive is usable.

Reflection

Look back at the last grant application your organization lost and ask at what point the mismatch became knowable. In most cases the answer is early, and often before any writing started at all. The LOI is valuable less because it is short than because it forces the fit question to the front, where it costs hours instead of weeks to answer. Then ask a harder question: when a funder declined, did anyone request feedback? Organizations that treat a decline as information accumulate an understanding of their funder landscape over a few cycles. Organizations that treat it as a verdict simply apply again with the same document and receive the same answer.

Glossary

• Letter of Inquiry (LOI): a brief preliminary application, typically 1 to 2 pages, used by foundations to screen prospective applicants before inviting full proposals.
• Pre-proposal: another name for the LOI stage, emphasizing that it precedes and feeds the full application.
• Executive summary: the opening paragraph stating the ask, the reason, and the expected impact.
• Statement of need: the evidence section establishing that the problem is real, local, and urgent.
• Project description: the concrete account of activities, showing what will happen and why it should work.
• Outcomes: dated, measurable statements of what will change, which later become the basis of your grant report.
• Program officer: the foundation staff member who reviews inquiries and advocates internally for the ones they want funded.
• Funder priorities: the issue, population, and geographic criteria a foundation's board has approved, against which every application is judged.
• Full funding rate: the proportion of all submitted LOIs that eventually result in a funded grant, after both the invitation and the proposal stages.

Related Lessons

• The Grant Lifecycle: From Discovery to Closeout
• Funder Research for Small Nonprofits: Free and Low-Cost Methods
• Budget Narratives for Grant Proposals: What Funders Want to See
• Outcome-Focused Grant Writing: What Funders Want in 2026
• Grant Reporting Best Practices: Building Trust Through Transparency

Closing

The LOI rewards precision over effort, which is an uncomfortable adjustment for people who have been taught that grant writing is about thoroughness. Two pages, a specific problem with local evidence, a solution described concretely enough to picture, outcomes with dates attached, and a request sized to what this particular funder actually gives. That is the whole document. Dana's wasted month was not caused by bad writing; it was caused by writing before checking fit, and the LOI is the instrument that puts the fit question first. Write it as its own document rather than a compressed proposal, customize it for every recipient, submit early, and ask for feedback when the answer is no.

Key Takeaways

• An LOI is a screening document of 1 to 2 pages, roughly 250 to 500 words, not a shortened full proposal.
• The effort ratio is decisive: 2 to 3 hours for an LOI against 20 to 40 hours for a full proposal.
• Follow the component proportions, giving outcomes real space and keeping the need section disciplined.
• Spend 30% of the document on the problem and 70% on your solution.
• Every claim needs a specific, checkable number and a source; vagueness is the most common failure.
• Customize priorities, grant size, geography, and past-grant references for every funder.
• Submit 5 to 7 days early, proofread 3 times, and follow the funder's format exactly.
• A decline is the normal outcome of any single application. Request feedback, improve, and reapply on the next cycle.

Frequently Asked Questions

Should we contact the funder before submitting an LOI? Yes, if they accept inquiries. Call or email the program officer with something short: "Hi, I am wondering if our program is a good fit for your foundation. We work on [issue] in [geography]. Would you be open to an LOI?" That 2-minute conversation prevents you from submitting to a poor-fit funder, and it means your document arrives with a name attached to it rather than as one anonymous file among many. Check their guidelines first, since some foundations explicitly decline pre-submission contact.

How many LOIs should we submit per year? Aim for 8 to 12 per year, roughly 1 to 2 per month. Quality beats quantity by a wide margin here: a single excellent LOI to a good-fit funder outperforms 20 mediocre LOIs to poor-fit funders, because fit is the variable that determines most outcomes and no amount of polish compensates for its absence. Spend the time you would have spent on volume on research and funder alignment instead.

What if we are rejected after submitting an LOI? Request feedback and try again next year, since most foundations accept annual applications. Improve based on what you learn: stronger data, better outcomes, a different ask amount, or a clearer connection to their priorities. A second application with real improvements often succeeds even when the first was rejected, because the program officer sees an organization that listened. Resubmitting the same document unchanged produces the same result.

Can we reuse the same LOI for different funders? Use the same structure and core content, but customize for each funder. Your problem statement and your solution do not change, because they are facts about your work. What changes is the framing: funder priorities, the grant amount, the geographic emphasis, and the opening and closing paragraphs that reference their specific focus. That is a small share of the total words, and it is the share that determines whether the rest gets read.