All posts
November 5, 2026
Figures checked November 2026

How to Write a Grant Proposal That Wins — How-To #017

A grant proposal is a written case that a funder's money will buy a specific, measurable outcome. It has six sections — the question, the need, the objectives, the methods, the budget, and what happens after the money ends — and every page must answer what the money buys.

An open proposal binder with a fountain pen across the pages, a magnifier over a signature line, and checked boxes.
Six sections. One audition. Make every page earn its keep.

Difficulty: Intermediate · Time: 20–40 hours for a strong first proposal · Cost: $0 — the price is your time.

Disclosure: some links on this page are affiliate links. As an Amazon Associate, Changenaire earns from qualifying purchases made through links on this page, at no extra cost to you.

Key takeaways

  • Every funder asks one question on every page: what outcome will my money buy, and how will I know it happened?
  • The needs statement needs a number with a source, not adjectives — reviewers are immune to "critical" and "urgent."
  • Objectives must survive one test: how would we know, at the end, whether this happened? Use SMART.
  • Narrate every budget line — what it buys and why the amount is reasonable — then check the math twice.
  • Never skip the sustainability section: name how the work survives after the money ends.

Go deeper (affiliate link — we may earn a commission): Storytelling for Grantseekers by Cheryl A. Clarke — the craft book for the needs statement — how to tell your story so the funder feels the problem, not just reads the numbers.

A program officer is not reading your proposal the way you wrote it. She is scoring it.

That is the single most useful thing a first-timer can understand about grant writing. The reviewer has a rubric, a stack, and a deadline. She reads for evidence, not inspiration. She is asking one question on every page: does this answer what my organization is trying to buy? A proposal that answers it clearly wins. A proposal that performs passion and hopes she notices does not.

This morning's installment — How to Find and Win Small Business Grants (How-To #016) — found the money. This one wins it. Six sections, the order reviewers expect them, and how to write each one so it scores.

Answer the question the funder is actually asking

Strip away the guidelines, the forms, the appendices, and every funder is asking exactly one thing:

What outcome will my money buy, and how will I know it happened?

Not your story. Not your struggle. Not your vision, your passion, or your five-year dream. The outcome — stated early, stated plainly. "With $75,000, we will train 120 returning citizens as certified home-health aides over 18 months, with a target placement rate of 70%." One sentence. A reviewer can score that. She cannot score "we are deeply committed to workforce empowerment."

Write the outcome sentence first, before anything else. Tape it above your desk. Every section of the proposal exists to make that sentence believable.

Write the needs statement with data, not adjectives

The needs statement proves the problem is real and worth the funder's money. First-timers write it with adjectives — "critical," "urgent," "devastating." Reviewers are immune to adjectives. They were vaccinated in graduate school.

What moves a reviewer is a number with a source. How many people face this problem, in what geography, at what rate — and how is it getting worse or being ignored? A county unemployment figure from the Bureau of Labor Statistics beats three paragraphs of “urgent.” A local waitlist count beats "devastating."

Then tie the need to the funder's mission in one explicit sentence. Funders don't fund problems; they fund their problems. Show them the overlap and you've done half the persuading before the methods section even starts.

Go deeper (affiliate link — we may earn a commission): Storytelling for Grantseekers by Cheryl A. Clarke teaches the other half of the needs statement — how to tell your story so the funder feels the problem, not just reads the numbers. Optional reading; the steps above stand on their own.

Make your objectives measurable — the SMART treatment

Every objective in the proposal should survive one interrogation: how would we know, at the end of the grant, whether this happened? If you can't answer, the objective is decoration.

The classic treatment still works because reviewers still use it: Specific (who, what), Measurable (how many, what rate), Achievable (with this budget, this staff), Relevant (to the need and the funder's mission), Time-bound (by when). "Train 120 aides in 18 months with 70% placement" survives the interrogation. "Empower the community through training" does not.

Here's the discipline that separates winners: every objective gets a matching line in the evaluation plan. Objective without measurement is a wish. Measurement without an objective is busywork. The rubric scores the pair.

Describe your methods as a calendar, not a wish list

The methods section is where proposals go to die — usually as a paragraph of good intentions: "we will conduct outreach, deliver training, and provide support services." A reviewer reads that and thinks: when? who? in what order? producing what?

Answer with a timeline. Month by month (or quarter by quarter for longer grants): what happens, who does it, what it produces. "Months 1–2: recruit 40 participants through partner referrals (program coordinator). Months 3–8: two training cohorts of 20 (lead instructor). Months 9–18: placement support and 90-day retention tracking."

A calendar is a promise with a schedule. A wish list is a promise with adjectives. Reviewers fund the first one.

Build the budget like an audit is watching

Nothing sinks a proposal faster than a budget that doesn't add up — literally. Reviewers check the math. So check it first, then check it again, then have someone else check it.

Three budget rules that win:

Narrate every line. Each line item gets one sentence: what it buys, and why the amount is reasonable. "$72,000 — lead instructor, 0.75 FTE at $64,000 annual salary, 18 months." That sentence tells the reviewer you've actually priced the work instead of inventing a number.

Respect the caps. Many funders cap indirect/overhead rates or forbid certain costs outright (no equipment over a threshold, no lobbying, no alcohol at events — yes, someone had to be told). Violating a stated cap is an instant disqualification, not a negotiation.

Make the totals match everywhere. The budget table, the narrative, the cover form, the summary — one number, everywhere. A mismatch says "we don't track our own money," which is a strange thing to say to someone you're asking for money.

Show how the work survives after the money ends

This is the section first-timers skip and reviewers never do. The funder is asking: are we buying a year of activity, or are we buying something that lasts?

A real sustainability plan names the mechanism: earned revenue that continues after the grant (fee-for-service, product sales), other funders already in conversation, cost structures that shrink once the program is built, or partners absorbing pieces of the work. "We hope to find more funding" is not a mechanism. It's a hope, wearing a suit.

End the proposal the way you started it — on the outcome. The reviewer closes the document remembering what her money buys and why it outlives her check. That's the audition. Make it a standing ovation.

At a glance

At a glance: How to Write a Grant Proposal That Wins
SectionWhat it must do
The funder's questionState the outcome the money buys, early and plainly
Needs statementProve the problem with a sourced number
ObjectivesSMART — measurable, with a date
MethodsA calendar, not a wish list
BudgetEvery line narrated, math checked twice
SustainabilityHow the work survives after the money ends

Common mistakes

Mistake: Writing the needs statement with adjectives instead of data.

Fix: Lead with a number and its source — how many people, in what place, at what rate.

Mistake: Objectives nobody can measure.

Fix: Make each one Specific, Measurable, Achievable, Relevant, and Time-bound, and ask "how would we know it happened?"

Mistake: Methods as a paragraph of good intentions.

Fix: Write the methods as a calendar — month by month, what happens, who does it, what it produces.

Mistake: A budget that does not add up, or lines with no explanation.

Fix: Narrate every line in one sentence and have someone else check the math before you submit.

Mistake: Skipping the sustainability section.

Fix: Name the mechanism — earned revenue, other funders in conversation, shrinking costs, or partners absorbing pieces.

Questions people ask

How long should a grant proposal be?

Exactly as long as the guidelines say — no longer, no shorter. If the funder gives page limits, they are testing whether you can follow instructions. If there is no limit, 8–15 pages for most foundation and state grants is our honest working range — a rule of thumb, not a funder's rule.

Can I reuse one proposal for multiple funders?

The skeleton, yes — your needs data, your timeline, your budget math are yours. The submission, no. Every funder's mission, rubric, and limits differ, and reviewers can tell a mail-merge from the first paragraph. Tailor it or do not bother.

Do I need a professional grant writer?

No. A careful first-timer who follows the funder's guidelines beats a hired writer who does not. What helps enormously is one brutally honest reviewer — someone who will circle every vague sentence.

What sinks most proposals?

Vague outcomes nobody can measure, no evaluation plan, budgets that do not add up, and ignoring the funder's mission to talk about your own. Every one of those is fixable before you submit, and almost none are fixable after.

What comes next

The funding stretch of the series closes here — #016 found the money, #017 taught you to win it. But grants are one lane, and most builders fund the work the old-fashioned way: customers. Next, the series turns to the question every #003, #007, and #013 reader hits the moment they have something to sell: How to Price Your Product or Service — How-To #018. Find the money, win the money — then price what you sell.

Go deeper (affiliate link — we may earn a commission): Grant Writing For Dummies by Beverly A. Browning is the plain-English companion for the whole proposal, from finding the grant to submitting it. Optional reading; the steps above stand on their own.

Sources

The steps, timelines, and targets in this guide are our own method, stated as our experience or as a rule of thumb where noted. Where a figure comes from an outside source, it is linked in the text and listed below.

Figures in this guide are as of November 2026.

The Changenaire Newsletter

Subscribe for more free step-by-step how-to guides to help you get more things done to grow your business or project everyday.

Email required. Unsubscribe anytime.

Read our Privacy Policy.