How to write a grant proposal that gets funded (2026): step-by-step guide

The difference between a funded grant proposal and a rejected one is almost never the quality of the underlying idea. It is almost always the quality of the writing — specifically, whether the proposal addresses the funder's stated criteria, sets measurable objectives, presents a credible budget, and includes every required document. Grant reviewers evaluate hundreds of proposals per cycle. The ones that win are not the most innovative or the most deserving — they're the ones that made the reviewer's job easiest: clearly structured, well-evidenced, and precisely aligned with what the funder said they wanted to fund. This guide walks you through every section of a winning grant proposal with a reusable template, real strong and weak examples, and the eight most common rejection reasons to eliminate before you submit. For a list of programs to apply to, see our best small business grants in 2026 roundup. For women-specific programs, see our grants for women-owned businesses guide.

Before you write anything: the preparation that determines everything

The most important grant-writing work happens before you open a blank document. Applicants who skip preparation write technically competent proposals that still fail because they're solving the wrong problem, targeting the wrong program, or missing the funder's implicit priorities. This section covers the preparation steps that separate funded proposals from rejected ones.

Step 1: Read the entire solicitation document — twice

Every grant program publishes a solicitation (called an RFP, RFA, NOFO, or funding opportunity announcement). It specifies what they're funding, who's eligible, how proposals will be evaluated, what format to use, and the deadline. Read the entire document the first time without stopping. Then read it again with a highlighter and mark every evaluation criterion, formatting requirement, and eligibility condition.

This sounds basic. It isn't. A 2024 analysis of 1,200 rejected SBIR proposals found that 31% were eliminated for administrative noncompliance — wrong file format, exceeded page limits, missing sections, or expired SAM.gov registration. Not for bad ideas. For not reading the instructions. The solicitation is also where you find the evaluation criteria — the exact rubric reviewers use to score your proposal. Every section of your proposal should be written to maximize your score on those criteria, in that order.

Step 2: Identify the funder's core mission and vocabulary

Every grant-making organization has a mission, and they fund projects that serve that mission. NSF funds projects that advance scientific knowledge. The SBA funds projects that strengthen small businesses. The Eileen Fisher Foundation funds women-owned businesses that advance environmental sustainability. The Amber Grant funds women entrepreneurs with compelling personal stories and clear plans for the money.

Your proposal must speak the funder's language. If the solicitation uses the phrase "community resilience," your proposal should use that phrase. If the evaluation criteria mention "commercialization potential," every section should address it. Reviewers are looking for alignment — proposals that feel like they were written for this funder, not repurposed from a different application.

Before writing, answer this question in one sentence: "Why would this specific funder, given their specific mission, want to fund this specific project?" If you can't answer it clearly, you either have the wrong program or the wrong framing. Fix the framing before you write.

Step 3: Contact the program officer (for federal grants)

Federal grant solicitations list a program officer or point of contact. Before writing, email them a 2–3 paragraph summary of your idea and ask: "Does this align with the topics you're looking to fund in this cycle?" This takes five minutes and can save you six weeks of work on a proposal that doesn't fit.

Program officers are not adversaries. They want to fund good projects and are permitted to give pre-application guidance. Common responses: "Your idea fits Topic 3 better than Topic 1" (saves you from targeting the wrong section), "We are specifically looking for X this cycle" (gives you insider framing), or "This is slightly outside scope — consider the [different solicitation] instead" (saves you from a futile application). Applicants who contact program officers before submitting win at meaningfully higher rates.

Step 4: Research previous winners

Most grant programs publish lists of past winners. For SBIR, the award database at sbir.gov contains every award ever made — search by agency, year, and keyword to find projects similar to yours. Note the language they use, the specificity of their objectives, and the types of organizations that win. For private foundations, search for press releases about past winners and read any available project abstracts. This intelligence is worth more than any generic grant-writing guide.

The complete grant proposal template: section by section

The following template covers the standard sections found in most grant proposals. Federal grants (SBIR, NIH, NSF) have strict section requirements — follow their exact guidelines, not this generic structure. Private and corporate grants may use different formats and shorter lengths. Adapt this template to match the specific requirements of your target program. The content within each section, however, is applicable everywhere.

Section 1: Cover page and executive summary

What it is: A one-page (typically 200–300 words) overview of your entire proposal. This is the first thing reviewers read, and research on reviewer behavior shows that initial impressions formed in the first two minutes strongly predict final scores. Write the executive summary last, after you've written every other section and know exactly what you're proposing.

What to include: The problem you're solving (one sentence, specific), your proposed solution (one sentence, specific), why your approach is better than alternatives (one sentence), the expected outcomes (measurable), the funding amount requested, and why this funder should care (alignment with their mission).

The difference: the strong example tells the reviewer exactly what the product does, exactly how much it costs to build, exactly how you'll test it, and exactly why it matters. The weak example tells the reviewer nothing except that the applicant likes adjectives. Every sentence should carry specific information.

Section 2: Problem statement (statement of need)

What it is: A data-supported description of the problem your project addresses. This section answers: "Why does this project need to exist?" It is not about your company. It is entirely about the problem and the gap in existing solutions.

What to include: The scope and severity of the problem (quantified), who is affected (specific population), current solutions and their limitations (named alternatives), the gap your project fills, and citations to credible sources (peer-reviewed literature, government statistics, industry reports). Every data claim needs a citation. Uncited statistics will be flagged by reviewers as unreliable.

Common mistake: Making the problem statement too broad. "Healthcare is expensive and inefficient" is true but useless. Narrow it down to the specific, quantifiable gap your project addresses. One well-documented narrow problem beats a vague description of a large industry.

Section 3: Project description and technical approach

What it is: The core of your proposal. This describes exactly what you'll do, how you'll do it, why your approach is better than alternatives, and why you believe it will work. For federal proposals, this is typically 10–20 pages. For private grants, it may be 1–3 pages.

Structure it clearly with subsections: Background and Innovation → Technical Approach → Specific Tasks → Expected Results → Risk Mitigation. Use descriptive headers that match the evaluation criteria language wherever possible. Use bullet points, numbered lists, and tables to make your approach scannable. A diagram or flowchart of your technical approach is often worth 500 words of prose.

Include competitive differentiation: Reviewers need to understand not just what you're building but why existing solutions don't solve the problem. A 4-column comparison table (Your Solution | Alternative A | Alternative B | Alternative C) with rows for key performance metrics is the most efficient way to show competitive advantage. Build it — reviewers notice when it's missing.

Common mistake: Describing what you'll build without explaining how. "We will develop an AI-powered platform" tells a reviewer nothing. "We will develop a CNN-based image classification model trained on 40,000 labeled agricultural images, achieving targeted 95% accuracy on a held-out validation set of 5,000 images by Month 6" tells them you know what you're doing.

Section 4: Objectives, milestones, and timeline

What it is: A structured breakdown of what you'll accomplish, when, and how you'll measure success. This section is where good ideas become credible proposals. A compelling narrative in Section 3 without a disciplined plan in Section 4 reads as wishful thinking.

Use the SMART framework: Specific, Measurable, Achievable, Relevant, Time-bound. If a reviewer cannot objectively determine whether you achieved the objective at the project's end, the objective is not specific enough.

Include a Gantt chart or timeline table showing all tasks and milestones across the project period. For a 12-month Phase I project, a simple table with months across the top and tasks down the side (with shaded cells indicating duration) takes 30 minutes to make and significantly increases reviewer confidence in your planning.

Section 5: Evaluation plan

What it is: A description of how you'll know whether the project worked. Many proposals omit this section entirely, which reviewers interpret as the applicant not having thought through what success looks like.

What to include: Success metrics for each objective (what will you measure, how, using what instrument or method), data collection procedures (frequency, sample size, statistical approach), and what threshold defines success versus failure for each metric. Include a contingency plan: if Milestone X produces poor results, what is Plan B?

Section 6: Budget and budget justification

What it is: A line-item financial plan showing exactly how you'll spend the grant funds, with a narrative justifying why each expense is necessary and reasonable for the proposed scope. The budget must tell the same story as the technical narrative — if you describe three major tasks in Section 3 but your budget only funds one engineer at 10% time, reviewers will question whether you can execute what you promised.

Standard budget categories and how to document them:

Personnel: List each person by name and role, their annual salary or hourly rate (use market-rate data for justification if needed), the percentage of time dedicated to the project, and the resulting dollar amount. Add fringe benefits at your actual rate or estimate 25–35% of base salary (include: health insurance, retirement contributions, payroll taxes — FICA, FUTA, SUTA). Example: "Dr. Jane Smith, Principal Investigator, $120,000 annual salary × 50% effort × 12 months = $60,000. Fringe at 28% = $16,800."

Equipment: Items over $5,000 per unit require individual justification including make/model, unit cost, quantity, and explanation of why this specific equipment is necessary and why purchasing (versus renting or using shared facilities) is appropriate. Example: "Bruker Tensor 27 FTIR Spectrometer: $42,500. Required for precise contaminant identification at sub-ppm concentrations. Rental is unavailable in our region; nearest shared facility is 4 hours away, incompatible with daily testing schedule."

Materials and supplies: Be specific, not vague. "Lab consumables: $5,000" invites questions. "Reagents and chemical standards for 300 water tests (EPA Method 200.8 standards, $12/test): $3,600. Disposable sample vessels and filters (bulk order): $800. Circuit components for 3 prototype units: $600." Total: $5,000 — same amount, much more credible.

Travel: Each trip needs destination, purpose, number of people traveling, and estimated costs. "3 field validation visits to Montana, Idaho, and Oregon farm sites; 1 person, 3-day trips; estimated airfare $450 × 3, lodging $150/night × 9 nights, per diem $65/day × 9 days = $1,350 airfare + $1,350 lodging + $585 per diem = $3,285."

Indirect costs (overhead): Use your negotiated indirect cost rate if you have one. If not, use the de minimis rate of 10% of Modified Total Direct Costs (MTDC) — allowed for any recipient without a negotiated rate under 2 CFR 200.

Budget justification red flags reviewers look for: Salary rates above market without justification; equipment purchases for items already owned; travel to conferences not directly related to the project; indirect cost rates above the de minimis without documentation; budget that doesn't reflect the personnel needed to execute the proposed scope of work.

Understanding how grant income is treated differently from loan proceeds for tax purposes affects your budget planning. CeoCult's business tax deduction guide covers grant income reporting, business expense deductibility, and how to structure your finances before and after receiving a grant award.

Section 7: Organizational background and key personnel

What it is: Proof that your team can execute the project. This section answers "Why should we trust this team to deliver?" not "Tell us about your company."

What to include: A brief organizational background focused on capabilities directly relevant to this project (not a general company brochure), biographical sketches of key personnel that highlight experience directly relevant to the proposed work (not a full CV), description of relevant facilities and equipment you already have, and any previous grant awards or relevant project completions.

Common mistake: Generic bios that list every position someone has ever held. A reviewer evaluating a water quality sensor proposal does not need to know that your CEO started their career in retail banking. They need to know that your lead engineer spent 8 years at a sensor company and holds 3 patents in electrochemical detection. Cut ruthlessly. Every sentence of a biographical sketch should answer: "Why is this person qualified to do this specific project?"

Section 8: Commercialization or sustainability plan

What it is: For SBIR and business grants, a description of how you'll turn grant-funded work into a sustainable business. Funders increasingly require this — they want to invest in projects with lasting impact, not ones that end when the grant runs out.

What to include: Target market definition (specific industry, geography, customer segment), market size with source citations (cite IBISWorld, Statista, or government data — never just state a number), competitive landscape analysis, pricing strategy, go-to-market plan with specific channels, realistic 3-year revenue projections, intellectual property strategy, and any existing letters of intent or customer interest.

Common mistake: Citing a TAM of "$50 billion" without explaining how you'll capture even a fraction of it. A credible commercialization plan targets a specific initial beachhead market: "We will target the 12,000 organic farms in California and Oregon in Year 1, selling direct through the CCOF and NOFA member networks where we have existing relationships. Target customer acquisition cost: $85. Target Year 1 sales: 200 units × $299 = $59,800." That's more compelling than any hockey-stick chart.

The 8 most common grant rejection reasons

These patterns account for the vast majority of rejections across federal, private, and corporate grant programs. Fix these before you submit.

1. Not addressing the solicitation criteria. The single most common rejection reason. Reviewers score your proposal against the published evaluation criteria. If your proposal doesn't address each criterion with specific evidence, it will score poorly even if the idea is excellent. Before submitting, print the criteria list and verify that your proposal addresses each one explicitly — preferably with section headers that mirror the criteria language.

2. Vague or unmeasurable objectives. "We will improve outcomes" is not an objective. "We will reduce average patient wait time from 4.2 hours to under 2 hours as measured by electronic health record timestamps across 150 patient encounters by Month 8" is an objective. If a reviewer cannot determine whether you achieved the goal at the project's end, it's not specific enough.

3. Generic narrative that could describe any company. "We are an innovative team with deep expertise developing cutting-edge solutions" — reviewers see this language in 40% of applications. Replace every generic claim with a specific fact. Not "deep expertise" but "combined 34 years of electrochemical sensor development and 7 issued patents in the relevant technology area."

4. Budget doesn't match the scope of work. If your technical approach describes building a complex multi-component system but your budget funds one part-time engineer and $2,000 in supplies, reviewers will either reject the proposal as infeasible or reduce the award to match what the budget can actually produce. Align your budget to your technical approach before finalizing either.

5. Missing required documents. Expired SAM.gov registration (automatic disqualification for federal grants), missing letters of support that the solicitation required, wrong file format (PDF when they wanted Word, or vice versa), missing signed cover page, or incorrect naming convention for uploaded files. Use a submission checklist — create one from the solicitation's requirements list and check off every item before submitting.

6. Submitted close to the deadline. Grants.gov, FastLane, and other federal submission portals routinely experience traffic spikes and technical issues in the 24 hours before a major deadline. Proposals submitted within 12 hours of the deadline miss mandatory system checks, have last-minute errors not caught under time pressure, and in some cases fail to process entirely. Submit at least 48–72 hours early. There is no advantage to waiting.

7. No preliminary data or proof of concept. For research and innovation grants (SBIR, NIH, NSF), proposals without any preliminary evidence — a simple experiment, a simulation result, a literature analysis showing feasibility — score significantly lower than those with supporting data. If you haven't built anything yet, at minimum reference published research or technical analysis that establishes feasibility. "Our approach is technically feasible because X, Y, Z [citations]" is better than "we believe this will work."

8. Weak letters of support. A letter that says "We support this project and hope it succeeds" adds zero value. A strong letter says: "Our hospital system will provide [Company] with access to our patient population for the proposed clinical validation in Phase I, provide a $25,000 cash contribution to co-fund Phase II if Phase I results meet the stated benchmarks, and has signed a letter of intent to purchase 12 units at commercialization." That's a commitment — and it demonstrates that the customer validation piece of your commercialization plan is already underway.

After you submit: the review process, and what to do with rejection

Federal grants (SBIR, NIH, NSF): Your proposal enters a peer review process. A panel of 3–5 experts scores your proposal against the published criteria. The entire process takes 3–6 months. You receive reviewer comments regardless of outcome — read them carefully. They are specific, professional, and directly actionable.

Private foundation grants: Review processes vary widely. Some use panels similar to federal review. Others have small internal selection committees. Timelines range from 4 weeks (Amber Grant) to 6 months (Cartier Women's Initiative). Private funders often do not provide feedback on rejections — if you receive it, treat it as a gift.

If you're rejected: Do not skip this step. Read the reviewer comments (if provided), identify the 2–3 most critical criticisms, and fix them before the next cycle. Most funded proposals were rejected once or twice before winning. NSF SBIR data shows that resubmitted Phase I proposals win at nearly double the rate of first-time submissions in the same topic area. Rejection is data, not verdict.

If you're funded: Celebrate briefly, then set up proper financial tracking immediately. Federal grants require quarterly progress reports and financial reports compliant with 2 CFR 200 (the Uniform Guidance). Never commingle grant funds with general business revenue — open a dedicated account. Reporting non-compliance can result in clawbacks and disqualification from future programs.

For managing the business operations funded by your grant, tracking expenses and generating the financial reports required by funders, BagEngine reviews accounting and business management tools rated for small business grant recipients specifically. Clean records throughout the grant period make your final report straightforward and position you well for renewal or Phase II applications.

Grant writing by program type: what changes and what stays the same

The principles above apply universally. Here's how the emphasis shifts by program type:

Federal grants (SBIR, USDA, NSF): Technical depth is paramount. Reviewers have domain expertise. Show your work: methodology, data, citations, risk analysis. Budget justification must be meticulous. Commercialization plan is required and weighted heavily. Read previous funded abstracts. Contact the program officer. Allow 6–8 weeks.

Private foundation grants (Amber Grant, Cartier, Eileen Fisher, Tory Burch): Founder narrative carries significant weight — sometimes more than the financials. Specificity and authenticity beat polish. "I started this business after watching my mother lose her farm to a water contamination event that cost $40,000 to remediate — which is why I'm building affordable testing equipment for rural farmers" is more compelling than a generic executive summary. Your story must be true, specific, and directly connected to the mission alignment.

Corporate grants (FedEx, Comcast RISE, Hello Alice): Applications are short — optimize every sentence. The online form constrains you to a few hundred words per question. Lead with your strongest metric. No padding. Use specific numbers wherever possible. Public voting components favor businesses with an existing customer base or social media presence that can mobilize votes.

State grants: Match your project to the state's economic development priorities. If you're in a rural state, emphasize rural job creation. If applying in a tech hub, emphasize innovation and scalability. State reviewers are often less technically expert than federal panels — write for clarity over technical depth. Our grants vs. loans comparison covers when state grants make more sense than SBA loan programs.

Free resources to improve your grant writing

Your local SBA Small Business Development Center (SBDC): Free grant-writing consulting, proposal review, and connections to state and federal programs. Find your nearest center at americassbdc.org.

Your local SBA Women's Business Center (for women entrepreneurs): Specialized support for women-owned businesses, including grant identification and proposal review. See our women's grants guide for WBC locations and programs.

Grants.gov email alerts: Set up keyword alerts at Grants.gov to receive notifications when new federal opportunities match your criteria. For a complete walkthrough of using the platform, see our Grants.gov guide.

Content creator-specific grants: If you're a content creator, influencer, or media professional applying for creative or business development grants, our grants for content creators guide covers platforms and programs specific to your field — many of which have simpler applications than traditional business grants.

Bottom line

A winning grant proposal is not the most creative one submitted. It's the one that made the reviewer's job easiest: clear structure aligned with the stated criteria, specific measurable objectives, a budget that matches the scope, and not a single missing document. Start 6–8 weeks before the federal deadline (or 2–3 days before a simple corporate grant). Read the solicitation twice. Contact the program officer. Research previous winners. Build a compliance checklist and complete it 48 hours before submitting.

If you're rejected, read the feedback, fix the three most critical issues, and resubmit next cycle. The resubmission rate among eventually-funded SBIR applicants is over 60% — meaning the majority of successful proposals were rejected at least once. Persistence, combined with specific improvements, wins the grants game. For programs to target with your improved proposal, see our complete small business grants guide.