How to Write a Grant Proposal That Gets Funded (Step-by-Step)
Most grant proposals fail not because the project is bad, but because the application doesn't speak the funder's language. Here's how to fix that.
Skip the research. Find your grants now.
GrantCrafter delivers a personalized grant report in 2 minutes.
Understand the Funder Before You Write a Word
Before you type a single sentence, read everything the funder has published. Their website, past grantees, annual reports, and stated priorities are a roadmap to what they want to fund. The most common reason proposals get rejected is misalignment — the applicant wrote about what they want to do, not what the funder wants to support.
What to research before writing: - The funder's mission statement and strategic priorities - List of recent grantees and what they funded - Average award size and project duration - Whether they fund your type of organization (nonprofit, for-profit, individual) - Geographic restrictions (local, regional, national, international)
Once you understand the funder, your job is to connect your project to their goals — not the other way around. If you can't make that connection clearly and honestly, this grant may not be the right fit. Applying anyway wastes your time and theirs.
Writing a Compelling Needs Statement
The needs statement answers one question: why does this matter? It establishes the problem your project addresses and makes the case that the problem is real, significant, and urgent.
What a strong needs statement includes: - Data: Current statistics that quantify the problem. Use local data when possible — funders care more about their community than national averages. - Human impact: Who is affected and how? Numbers tell the scale; stories create urgency. - Gap analysis: What's being done now, and why isn't it enough? This positions your project as filling a real gap. - Connection to funder priorities: Explicitly connect the need to what the funder cares about.
Common mistakes: - Using vague language ('many people suffer from...') instead of specific numbers - Writing about your organization's needs rather than the community's needs - Presenting a problem so large no grant could address it - Failing to connect local data to the broader issue
Aim for 1-2 pages. Every sentence should either establish the problem's scale, its human impact, or explain why current solutions aren't enough.
Creating a Realistic Budget
Funders review budgets carefully — an unrealistic budget is an immediate red flag. Your budget should be detailed, justified, and clearly connected to project activities.
Budget fundamentals: - Personnel: List each position, salary, and the percentage of time devoted to this project. If you're requesting 50% of a coordinator's salary, explain what they'll spend 50% of their time doing. - Direct costs: Equipment, supplies, travel, contractor fees. Each line item should have a clear justification. - Indirect/overhead: Many funders cap indirect costs at 10-15% of direct costs. Know the funder's policy before you submit. - Matching funds: If you have matching funds from other sources, include them. It demonstrates organizational strength and commitment.
Budget narrative: Most grants require a budget narrative explaining each line item. Don't just repeat the numbers — explain why each expense is necessary to achieve project goals.
Get quotes for any major purchases or contracts before submitting. 'Approximately $5,000 for equipment' is less persuasive than '$4,850 for one Dell Inspiron laptop and one Epson scanner, per attached vendor quotes.'
Writing Strong Program Objectives
Objectives are specific, measurable outcomes your project will achieve. They're not activities (what you'll do) — they're results (what will change because you did it).
The SMART framework: - Specific: What exactly will change, for whom, by how much? - Measurable: How will you know if you achieved it? - Achievable: Is this realistic given your resources and timeline? - Relevant: Does this connect directly to the problem in your needs statement? - Time-bound: By when will this outcome be achieved?
Weak objective: 'Provide job training to unemployed adults in our community.' Strong objective: 'By December 31, 2025, provide 40-hour job training certification to 30 unemployed adults in [City], with 75% obtaining employment within 90 days of completion.'
Funders want to know what success looks like. Make it concrete, make it countable, and make it honest. Don't promise outcomes you can't realistically achieve — you'll have to report on these later.
The Cover Letter
Your cover letter is often the first thing a program officer reads. It should be concise (one page maximum), professional, and compelling.
Cover letter structure: 1. Opening sentence: Who you are and what you're requesting (amount and purpose) 2. One paragraph: The problem and your organization's unique position to address it 3. One paragraph: What you're requesting and what it will accomplish 4. Closing: Gratitude and next steps
Personalize every cover letter. Address it to the specific program officer if you know their name. Reference the specific grant program. Avoid generic phrases like 'we are pleased to submit' — they tell the reader nothing.
If you've had previous contact with the funder (attended an informational webinar, had a call with a program officer), mention it briefly. It signals you've done your homework and taken the time to understand their priorities.
Common Mistakes That Get Proposals Rejected
Submitting without reading the guidelines: Every funder has specific requirements for format, length, attachments, and submission method. Ignoring them signals carelessness.
Exceeding page limits: If the guidelines say 5 pages, submit 5 pages. Reviewers may stop reading at the limit.
Generic applications: Copy-pasted language from other applications is obvious. Reviewers read hundreds of proposals and recognize boilerplate.
Missing attachments: A missing IRS determination letter, audit, or required certification can disqualify an otherwise strong proposal.
Submitting at the deadline: Systems crash, attachments fail to upload, and last-minute errors get missed. Submit at least 24-48 hours early.
Not following up: After submission, send a brief note confirming receipt. After a decision (positive or negative), ask for reviewer feedback. Most funders appreciate the professionalism, and feedback from a rejection can dramatically improve your next application.
Frequently Asked Questions
How long should a grant proposal be?
Follow the funder's guidelines exactly. Most letters of inquiry are 2-3 pages; full proposals range from 5-20 pages. When no length is specified, aim for the minimum needed to make a compelling case.
Should I call the funder before applying?
Yes, when possible. A brief call to confirm eligibility and ask clarifying questions demonstrates seriousness and often surfaces insights that strengthen your application. Many funders appreciate pre-application contact.
How do I write a grant proposal if I've never written one before?
Start by reading successful proposals from similar organizations (many are public records). Follow the funder's guidelines precisely, use clear non-jargon language, and have someone unfamiliar with your work review the draft for clarity.
What should I do if my proposal is rejected?
Request feedback from the funder — many provide brief reviewer notes. Review your proposal critically against the feedback. Most successful grant writers submit to 15-20 funders and expect a 10-20% success rate.
Ready to find your grants?
GrantCrafter delivers a personalized grant report for your business in 2 minutes. $24.99 — no subscription.
Get My Grant Report — $24.99 →