How to write a research proposal that gets funded

A funded proposal is not a longer proposal — it is a better-staged one. The reviewer reads the first paragraph carefully, skims the next page, then decides whether to invest the remaining ten minutes. That sequence shapes everything about how a competitive proposal is built. This guide walks through the four-section structure we teach in Research Goal's methodology cohort.

The twelve-minute rule#

Reviewers on most panels read 8 to 15 proposals per round. The average attention spent on a single proposal — first pass — is twelve minutes. Anything that doesn't earn the next minute, doesn't get one. Your proposal is competing for minutes before it competes on merit.

The four-section structure#

Strong proposals across disciplines share the same load-bearing skeleton — even when the funder's template tries to disguise it. Naming the four sections makes the staging visible.

1. Significance — why this matters now#

The first 250 words must convince the reviewer that not funding the work is the costlier choice. State the problem in plain language, name the population or system at stake, and quantify the gap. Save the literature deep-dive for later — the opening is for consequence, not citations.

2. Approach — what makes your method fit#

Reviewers want to see fit, not novelty. Name the method, then explain — in one paragraph — why this specific design answers the question better than the obvious alternatives. The strongest signal a reviewer can read is that you considered three approaches and picked one for a real reason.

3. Feasibility — proof you can land this#

Pilot data, a letter of access, a preprint, a software demo — anything that shows the work is partially done before the money lands. Proposals that ask reviewers to take feasibility on faith lose to proposals that show one figure of preliminary work.

4. Impact — who acts on this and how#

Most proposals end with vague claims about contribution. Name the specific group that changes behaviour because of your findings — a clinical guideline body, a policy office, a successor research program. "This will inform future work" is the weakest possible close.

The lead paragraph earns the rest#

If the reviewer puts the proposal down after the first paragraph, they should already know: what you're doing, why it matters, what you'll deliver, and why you. That's four sentences. Strong proposals re-write this paragraph eight to ten times. Weak proposals re-write it twice.

Budget mistakes that derail strong science#

Reviewers read the budget before the methods. A mismatched budget undoes a strong narrative in thirty seconds. Three patterns we see in nearly every rejected first-time proposal:

• Round numbers — "$50,000 for personnel" reads as guessed; "$48,720 across 0.4 FTE at the post-doc step" reads as planned
• No mention of overhead — the indirect cost line is the easiest red flag to spot; show you know it exists
• Travel without a destination — "Conference travel: $4,000" loses to "AGU Fall Meeting + one collaborator visit, capped at $3,800"
• A line item the methods don't mention — every dollar in the budget must trace back to a sentence in the approach

Wrapping up#

Treat the proposal as a staged conversation with a tired reviewer. Earn the first minute with significance, the next three with approach, the next four with feasibility, and close with impact specific enough that the reviewer can name who acts on it. Do that and the budget — which they read first — already lines up with the story.