How to Write a Grant Proposal: The Complete Step-by-Step Guide

A grant proposal is a structured, persuasive request that convinces a funder your project deserves their money. It is not an essay and not a sales pitch — it is an argument backed by evidence, scored against criteria the funder has usually published in advance. Get the structure and the fit right and average writing will win. Get them wrong and beautiful writing still loses.

1. How funders actually decide (read this first)

Before you write, understand the room you're writing for. Most competitive grants are scored by reviewers against a rubric — a points sheet tied to each required section. Reviewers often read many proposals in one sitting and skim before they score. Three consequences follow:

• Fit beats eloquence. A proposal that maps cleanly to every scoring criterion and the funder's stated priorities outscores a more elegant one that wanders.
• Front-loading wins. Put the answer first — in the proposal overall, and in every section and paragraph. A skimming reviewer should grasp your need, solution, and ask within the first page.
• Make scoring easy. Use the funder's own section headings and terminology so a reviewer can find — and award — each point without hunting.

2. Before you write a word

Research the funder

Funders fund problems they already care about. Read the funder's mission, the projects they funded in the last 1–3 years, and their typical award size. You are looking for a genuine overlap between what they want to change and what you do. If their past grants are $10,000 community projects, a $2 million request signals you didn't do your homework.

Check eligibility and make a go/no-go decision

Read the eligibility rules line by line: legal status, geography, sector, required registrations, matching-fund requirements, and deadlines. If you don't clearly qualify, stop — a strong proposal to the wrong funder is wasted effort. Treat eligibility as a hard gate, not a hurdle to argue around.

Gather your evidence and your story

Before drafting, collect: data on the problem (from credible sources), your organization's track record and numbers, the specific people you serve, and one or two real stories that put a human face on the need. You'll draw on these in every section.

Mirror the funder's language

This is the single highest-leverage editing pass you can make. If the funder talks about "economic resilience," use that phrase — not your internal jargon. You're not changing your project; you're describing it in the words the reader already values.

3. The anatomy of a grant proposal — section by section

Below are the eight core sections, in the order funders read them. For each: what it is, what reviewers look for, and how to make it strong. We'll follow one running example — a fictional youth digital-skills nonprofit in Lagos applying for a 12-month training grant — to show the difference between weak and strong.

3.1 Cover letter / Letter of Inquiry (LOI)

A one-page introduction to your organization and your request. Many foundations ask for an LOI first and invite a full proposal only if interested — so the LOI is often your real first impression. State who you are, the problem, your proposed solution, the amount requested, and why this funder specifically. Keep it warm, specific, and short.

3.2 Executive summary (or abstract)

A tight overview of the entire proposal: the need, your solution, the amount requested, expected impact, and your organization in brief. Reviewers frequently read this and nothing else before forming an opinion — so write it last, and make it stand alone.

3.3 Statement of need (the most important section)

This is where most proposals are won or lost. The statement of need proves the problem is real, urgent, and worth solving — before you talk about yourself. Structure it like this:

• Lead with the problem and data. Open with specific, cited statistics from credible sources (government data, reputable studies, your own program data).
• Show the gap. Contrast current conditions with the desired outcome — the distance between them is the need.
• Make it human. Pair the statistics with one short, real story so the reader feels the problem, not just reads it.
• Establish urgency. Explain why this matters now, not someday.
• Connect to the funder. Tie the need directly to the funder's stated priorities.

3.4 Goals and objectives

A goal is the big-picture change you want to create; it's usually not directly measurable ("equip Lagos youth to enter the digital economy"). Objectives are the specific, measurable results that add up to the goal. Aim for one or two goals, each supported by several objectives. Make every objective SMART — Specific, Measurable, Achievable, Relevant, Time-bound.

It helps to write three kinds of objectives:

• Process objectives — what you'll do ("deliver 12 cohorts of training to 400 youth by month 12").
• Outcome objectives — the change in the people you serve ("70% of graduates demonstrate job-ready skills on assessment").
• Impact objectives — the longer-term result ("55% of graduates placed in paid work within six months").

3.5 Methods / approach (the implementation plan)

This is how you'll turn objectives into outcomes: the concrete activities, the timeline, who does what, and why your approach will work. Reviewers want a credible, realistic plan — not just intentions. Include a timeline (by month or quarter), key milestones, and staffing. If your field uses them, a simple logic model (inputs → activities → outputs → outcomes) is a powerful one-page way to show the whole chain of cause and effect.

Crucially, the methods section must reconcile with everything else: every objective needs an activity that achieves it, and every activity needs a line in the budget.

3.6 Evaluation plan

Evaluation proves you'll know whether the project worked — and funders increasingly require it. Distinguish two layers:

• Process evaluation — did you do what you said (numbers trained, sessions delivered)?
• Outcome evaluation — did it create the change you promised (skills gained, jobs secured)?

For each objective, name the indicator (what you'll measure), the baseline (the starting point), the target, the data source, and who collects it. Decide whether evaluation is in-house or via a third-party evaluator (third-party adds credibility for larger grants). A measurable objective makes this section almost write itself — another reason to get objectives right.

3.7 Budget and budget justification

A budget is a financial argument, not a spreadsheet afterthought. It has two parts: the line-item budget and a narrative justification explaining why each cost is necessary and how it was calculated. Standard categories include:

Know the difference between direct costs (tied to the project) and indirect costs (overhead that keeps your organization running). Many funders cap indirect costs at a fixed percentage — check before you build. If the funder requires matching funds, you can usually count both cash match (hard money from other sources) and in-kind match (donated time, space, or goods, fairly valued).

3.8 Organizational background & capacity

Here you prove you can deliver. Cover your mission, track record (with numbers), relevant past projects, key staff, and your governance and financial systems. Funders are trusting you with money; show you've succeeded before and can manage it. New organizations can borrow credibility through strong partners, a fiscal sponsor, or the documented experience of their team.

3.9 Sustainability (when asked)

Many funders want to know what happens after their money runs out. Show how the work will continue — earned revenue, other funders, institutional adoption, or community ownership. Even a brief, credible plan reassures funders their investment won't simply stop.

4. Writing techniques that win points

• Answer first, everywhere. Lead each section and paragraph with the conclusion, then support it. Skimming reviewers reward it.
• Be specific. "400 youth in 12 months" beats "many young people." Numbers signal competence.
• Pair evidence with emotion. Data earns the reviewer's head; one real story earns their heart. Use both, briefly.
• Write in plain, active voice. "We will train 400 youth," not "400 youth will be trained." Clarity reads as competence.
• Use the funder's words. Mirror their priorities and terminology so points are easy to award.
• Cut jargon and filler. Every sentence should earn its place against the page limit.

5. Finding funders and writing proposals across Africa

For nonprofits and businesses in Nigeria, Kenya, Ghana and across the continent, the fundamentals above hold — but a few realities deserve attention:

• Look local and global. Beyond international funders (Mastercard Foundation, USADF, and others), pursue local foundations, development-finance institutions, government schemes, accelerators, and corporate CSR programmes. Many are under-applied to.
• Get your registration in order. Most funders require legal registration (for example, CAC registration in Nigeria) and may ask for a constitution, board list, or tax status. Sort this before deadlines, not during.
• Budget in the right currency. Follow the funder's currency rules; if you budget in local currency for a foreign funder, state your exchange-rate assumption and date. Build in a sensible buffer for FX movement where allowed.
• Show financial credibility. Audited accounts, a separate project bank account, and clear fiscal controls reassure funders wary of mismanagement.
• Businesses can win grants too. Founders and SMEs are eligible for many fellowships, challenge funds, and accelerator grants — for-profit grant funding is more abundant than most assume.
• Partner to build credibility. A respected local partner or fiscal sponsor can make a young organization fundable.

6. Why most proposals get rejected

With roughly 97% of applications turned down, it pays to avoid the predictable failures. The most common are:

• Poor fit with the funder's priorities.
• Ignored eligibility rules or missed deadlines.
• Exceeding the page or word limit (often an automatic disqualification).
• A weak statement of need — claims without data.
• Vague objectives that can't be measured.
• A budget that doesn't match the narrative.
• Generic, recycled text that ignores the specific funder.

7. Pre-submission checklist

• You meet every eligibility rule, and the deadline is confirmed.
• Every required section and attachment is present, in the requested order.
• You're within the page/word limit and formatting rules.
• The statement of need leads with cited data and one human story.
• Every objective is SMART and has a matching activity and evaluation indicator.
• The budget reconciles line-by-line with the narrative; indirect-cost cap respected.
• You used the funder's language and priorities throughout.
• A second person has proofread it against the funder's rubric.

8. After you submit

Confirm receipt, then track the decision timeline. If you win, read the award terms carefully, set up reporting from day one, and deliver what you promised — strong reporting is the foundation of renewals. If you're declined, request the reviewer feedback or scores; funders often share them, and they are gold for your next attempt. Most successful grant-seekers reuse and refine a strong proposal across several funders rather than starting from scratch each time.

Frequently asked questions

Keep going: Grant writing glossary · How Grant Wizard works · Grant Wizard vs ChatGPT