The structure to follow, a worked example, and the mistakes worth avoiding.
Writing a grant proposal is often the first hurdle between a good idea and the funding that can turn it into reality. Most applicants stumble on the same three things: unclear objectives, a weak narrative that doesn’t speak the funder’s language, and a budget that looks either unrealistic or unfinished. Follow it step by step, and you will produce a proposal that reads as finished before you hit “submit.”
Step by Step
- Read the solicitation front‑to‑back
- Highlight every eligibility criterion, deadline, and formatting rule.
- Note the funder’s stated priorities (e.g., “community resilience” or “early‑stage technology”).
- Create a checklist in a spreadsheet; mark each item as you satisfy it.
- Define the problem in one sentence
- Ask yourself: What gap does my project fill, and why does it matter now?
- Draft a 15‑word “problem statement” and test it on a colleague who isn’t in your field. If they can’t paraphrase it, tighten the language.
- Set SMART objectives
- Specific, Measurable, Achievable, Relevant, Time‑bound.
- Example: “Increase the number of low‑income households with access to broadband from 42 % to 68 % in County X by June 2025.”
- List 2–4 objectives; each will become a subsection in the “Project Description.”
- Develop a logic model
- Sketch inputs → activities → outputs → outcomes.
- This visual helps you see where evidence is needed and keeps the narrative focused on results, not just tasks.
- Write the narrative in the funder’s voice
- Use the exact keywords from the solicitation (e.g., “capacity building,” “sustainability”).
- Structure each paragraph: Context → Gap → Your Approach → Expected Impact.
- Keep sentences under 25 words; use active verbs (“train,” “deploy,” “evaluate”).
- Build a realistic budget
- Start with the logic model: every activity needs a line‑item cost.
- Include direct costs (personnel, equipment, travel) and indirect costs only if the funder permits them.
- Add a brief justification (e.g., “$12,000 for a 3‑month part‑time data analyst to clean and code survey responses”).
- Polish and proofread
- Run a spell‑check, then read the proposal aloud.
- Verify that every requirement on your checklist is ticked.
- Send the draft to two reviewers who are familiar with the funder’s portfolio; incorporate their feedback before the final submission.
A Simple Structure to Follow
| Section | What to Include | Approx. Length |
|---|
| Cover Sheet | Project title, PI name, institution, grant number (if applicable) | 1 page |
| Executive Summary | One paragraph summarizing the problem, solution, and requested amount | 150–200 words |
| Problem Statement | Data‑driven description of the need; cite 2–3 recent sources | ½ page |
| Project Objectives | List of SMART objectives; each with a measurable indicator | ½ page |
| Methodology / Project Description | • Overview of approach <br>• Work plan (timeline or Gantt) <br>• Roles & responsibilities <br>• Evaluation plan | 2–3 pages |
| Budget Narrative | Itemized costs with justification; total amount requested | 1 page |
| Organizational Capacity | Brief CVs of key staff, past relevant grants, facilities | ½ page |
| Sustainability / Dissemination | How results will be maintained or shared after funding ends | ½ page |
| Appendices | Letters of support, IRB approval, data collection instruments | As needed |
Copy this outline into a new document, replace the placeholders, and you’ll have a skeleton that satisfies most federal, foundation, and corporate grant templates.
Common Mistakes to Avoid
- Over‑promising outcomes – reviewers flag proposals that claim “nationwide impact” without a clear scaling plan.
- Ignoring the funder’s evaluation criteria – if the solicitation scores “innovation” and “feasibility,” you must address both explicitly.
- Submitting a budget that doesn’t add up – mismatched totals raise red flags and often lead to outright rejection.
- Using jargon without definition – acronyms like “CBPR” or “IoT” must be spelled out the first time they appear.
- Leaving blank pages or sections – even optional fields should contain a brief statement (“Not applicable”) rather than an empty space.
A Short Example
> Executive Summary
> The Rural Health Initiative (RHI) will close the 30 % telemedicine gap affecting adults over 65 in County Y. By deploying two mobile broadband units and training five community health workers, RHI will increase telehealth visits from 12 to 48 per month within 12 months. The project requests $150,000 to cover equipment, personnel, and evaluation costs, and will be sustained through a partnership with the County Health Department after the grant ends.
Notice how the summary packs the problem, solution, measurable target, and budget request into three concise sentences. The same clarity should permeate the rest of the document.
Pro Tips
- Align every paragraph with a reviewer rubric – before you write, list the rubric items (e.g., “Significance,” “Approach,” “Budget”) and tag each paragraph with the relevant item. This ensures nothing slips through the cracks.
- Use a “one‑pager” logic model as a checklist – each box (inputs, activities, outputs, outcomes) becomes a line‑item in the budget and a paragraph in the narrative.
- Quote recent, peer‑reviewed data – a 2023 CDC report on broadband access carries more weight than a 2015 newspaper article. Include the DOI or URL in the reference list.
- Build a “risk mitigation” sub‑section – briefly acknowledge the biggest obstacle (e.g., “weather delays”) and state the contingency plan. Reviewers appreciate realistic foresight.
- Submit a PDF that matches the funder’s formatting guidelines exactly – page size, margins, and font (often Times New Roman 12 pt) are not optional; a non‑compliant file can be rejected before anyone reads the content.
With a clear problem statement, a logic‑driven work plan, and a budget that tells a coherent story, your grant proposal will stand out for the right reasons. Follow the steps, respect the funder’s language, and you’ll move from idea to funded project with confidence.
What does “written to the solicitation” actually mean?
It means the document is built from your funder’s notice of funding opportunity rather than from a template. Paste the NOFO — or its URL, or the PDF — into the last box on the form. We read it and pull out the sections it requires you to write, the order it lists them in, the length limits it sets, the deadline, the eligibility and cost-share rules, and the review criteria, with their point weights where the solicitation states them. The draft then comes back in those sections, under those headings, with each review criterion addressed explicitly and the heavily weighted ones developed at more length than the light ones. That is the part a professional does and a chat window does not: reviewers score against the criteria as the solicitation words them, so matching that structure and that vocabulary is most of the work.
What if my solicitation does not publish point weights?
Plenty do not, and you should know which case you are in before you pay rather than after. Federal notices usually print the criteria with the points beside them. A great many foundation and state guidelines print the criteria with no scores at all, and some describe a panel that reads and deliberates without scoring anything. Where the weights are published, the heavier criteria are developed at more length and the compliance table shows what each one is worth. Where they are not, nothing is invented to fill the gap: every criterion is still addressed explicitly under your funder’s own headings, and the table still shows where each one is answered, without a fabricated score. The free solicitation check linked at the top of this page tells you which of the two your notice is, in about a minute, before you spend anything.
How do I know you actually read my NOFO, and did not just make the table up?
Because every value we take from your solicitation is checked back against its own text before it is used, word for word, and anything that does not match is thrown away rather than guessed. The Reviewer Compliance Check at the end of your document is then assembled by code from what survived that check and from measurements of the draft itself — no language model writes any part of it. If our automated read proposed something we could not find in your document, it is listed at the bottom under “What the automated read could not confirm”, so you can see what was discarded. And if we cannot verify enough of the structure to stand behind it, we do not quietly fall back to a template and let you assume otherwise — the document says so at the top, in bold, on the first page.
Is it funder-ready?
Not the moment it arrives, and we are not going to tell you otherwise. What arrives is a complete structured first draft in your funder’s section order, addressing their review criteria, in an editable Word file. What it deliberately will not do is fill in facts only you hold. Your UEI and SAM.gov registration, your board and staffing figures, letters of support, local cost data, your real baselines — anywhere one of those belongs you get a labelled bracket rather than a plausible-looking guess. There are dozens of them: the one order we have run end to end under this exact process came back with 74 of them across about 26,000 characters, which is roughly one every few paragraphs. That is a single document rather than a promise — a solicitation asking for fewer figures produces fewer — but it is the right order of magnitude to plan around, and working through them is the job the draft leaves you. That is the design, not a shortcoming: a wrong UEI or an invented statistic is an administrative rejection that never reaches a reviewer, and it is the applicant who carries it. The compliance table also tells you where your sections stand against the stated limits — but page counts depend on your own template’s font and margins, so confirm those in your document. Read the free sample first.
How long does it take, and what if it stalls?
It is written one section at a time, so it is not instant. A clean run is roughly two to three minutes and you watch each section land on the page; reading and checking your solicitation adds a step before that. It can also stall part-way: the last full run we timed stopped after four of that solicitation’s sections, restarted itself, and finished twenty-two minutes after the order went in. That is the honest range — a few minutes normally, longer if it has to restart. What protects you either way is how delivery works. The page you land on after paying refreshes itself, and if writing stopped it resumes from the sections already written rather than starting over. Your link is permanent, so you can close the tab and come back to it, and if you leave your email we send you that link the moment you pay. If it is still unfinished after half an hour, email us with the link and we finish it by hand or refund you.
Why $399 when a grant writer charges thousands?
Because you are buying the document, not the hours. A professional grant writer sells you their time — discovery calls, drafts, revisions, and their judgement about your programme — and prices accordingly. Here no person writes it and no person reviews it before you see it: a language model, prompted with the requirements read out of your own solicitation, drafts every section from what you type in, and you edit from there. If what you need is someone to sit with your board and shape the strategy, hire the writer. If you already know your programme and what you need is your funder’s sections drafted, criterion by criterion, and in front of you today, this is that.
Who is this actually for?
Organisations that already know their programme and have written or paid for a proposal before. You recognise a statement of need, you have your figures, and what is costing you is the blank page and the hours it takes to write to someone else’s required structure. It will not find you a funder. There is no grants database here and no matching engine — this writes against a solicitation you already have in hand, and some subscription tools do bundle funder search where we do not. If finding the opportunity is still the part you need, Grants.gov lists every federal notice at no cost and most states run their own portal; come back once you have picked one. It will not decide your evaluation design either. It gives you the funder’s structure, argued against the funder’s criteria, so your editing time goes into the parts only you can write.
I already pay for ChatGPT. Why is this $399?
The honest answer is that you can check our work before you pay, and you cannot check your own prompting before you do it. The sample linked on this page is two complete sections of a real run of this exact service against HRSA-27-099, a real published federal solicitation. The applicant in it is invented; the funding opportunity is not. Read it. If it is not better than what you would get out of an afternoon in a chat window, do not buy this. What the $399 buys that a chat subscription does not is the part that is not the model: your solicitation is read and its required sections, limits and scored criteria are pulled out and verified word-for-word against the document before anything is written from them; the draft is structured to that, not to a template; where your solicitation publishes point weights each criterion gets development in proportion to its points, and where it does not, every criterion is still addressed explicitly rather than handed an invented score; and an automated pass removes any number, percentage or dollar figure you did not supply and leaves a labelled bracket in its place. Then you get a compliance table, built by code rather than by the model, showing where each criterion is addressed and how your lengths sit against the limits. Pasting a sixty-page NOFO into a chat window and asking it to do all of that is possible — it is just the part most people skip, and skipping it is what produces a proposal that reads well and scores badly.