Four service models, matched to four gaps
“Grant writer” is a label that covers at least four distinct services, and most bad engagements start by purchasing the wrong one. Name your gap first, then buy the service that fills it.
| Service model | What you receive | The gap it actually fills | Typical fee logic |
|---|---|---|---|
| Funder research | A screened prospect list with evidence per funder | You can write but do not know who to ask | Flat project fee |
| Proposal development | Drafted narratives, budgets, and assembled applications | You know the funders but cannot produce the documents | Project fee per application, or retainer |
| Review and editing | Margin-level critique and revision of your draft | You can produce but want a stronger, cleaner submission | Hourly |
| Systems and training | Templates, a tracker, a core narrative, and a trained staff member | You will apply many times and want the capacity in-house | Project fee or short retainer |
The most expensive mismatch is buying full proposal development when the organization is not ready for it. A writer cannot invent your program design, your outcomes, or your budget; if those do not exist, a drafting engagement stalls into billed discovery meetings. Candid’s overview of what a grant proposal contains is a fast readiness test: if you cannot supply the raw facts behind each component, buy program design help or systems help first, not writing.
Anchoring the cost conversation helps too. The Bureau of Labor Statistics profiles fundraisers as an occupation, including wage data; a consultant’s rate should make sense next to the fully loaded cost of an employee doing the same work, given that consultants carry their own overhead, taxes, and unbilled time.
Fee structures and the commission problem
Three fee structures are legitimate, each fitted to a different level of uncertainty. Hourly fits open-ended or poorly defined work such as editing and discovery; ask for a cap. Flat project fees fit well-defined deliverables such as one application to one named funder; they only work when the scope is written down, which is what the checklist below is for. Retainers fit ongoing multi-application relationships; insist on a monthly deliverables list so the retainer buys output, not availability.
The fourth structure is the one to refuse.
Red flags that end the conversation
Some signals are worth a follow-up question. These are not those. Each row here is a reason to stop evaluating and move on.
| Red flag | Why it disqualifies |
|---|---|
| Guarantees funding, or heavily implies it | No provider controls a funder’s decision; a seller who claims otherwise is misrepresenting the product |
| Quotes a success rate with no denominator | “90 percent funded” is meaningless without knowing how many submissions, which funders, and who counted |
| Commission or percentage-of-award pricing | See the position above; it also signals distance from professional norms |
| Will not produce a written scope | Every dispute you will ever have is settled, or not, by this document |
| Reuses one boilerplate proposal across clients | Funders read many proposals; recycled narrative is recognized and it reads as disrespect |
| Asks for your portal passwords | Access should run through client-owned accounts with the provider as an authorized user, never shared credentials |
| Cannot list what they need from you | A provider who promises results without your program facts, numbers, and approvals is not planning to write anything specific to you |
| Pressure to sign before a deadline “closes” | Manufactured urgency is a sales tactic, and deadlines you learned about yesterday are rarely deadlines you should chase |
The pattern underneath the table: confidence and urgency are not evidence of method. A strong provider shows you a process, names its limits without being asked, and is comfortable telling you no application is worth submitting this quarter.
The 28-item scope-of-work checklist
Fee comparisons between providers are meaningless until scope is normalized. A $3,000 quote covering research, two review rounds, and submission is not more expensive than a $2,000 quote covering a single draft with no revisions; it is a different product. Before signing, and before comparing anyone’s price to anyone else’s, walk both quotes through the same checklist.
Grant writing scope-of-work checklist28 items across seven sections: deliverables, client inputs, timeline and reviews, fees and payment, exclusions and boundaries, confidentiality and access, and acceptance and handoff. Every item is a yes-or-no check against the provider’s written scope.
CSV checklistThree items on the list deserve emphasis because they are the ones providers most often leave vague. Named deliverables by document: “grant writing support” is not a deliverable; “one letter of inquiry and one full proposal to two named funders” is. Client inputs with due dates: most blown timelines are blown by the client, and a fair scope says what you owe and when. Handoff: you should end any engagement owning editable files and a reusable core narrative, because a provider whose work product evaporates when they leave has sold you dependency, not capacity.
Hire, train in-house, or do it yourself
The honest version of this decision starts with volume and staff time, not with how intimidating the first application feels.
- Fewer than two applications a year, small asks: do it yourself. A first small proposal to a local funder is genuinely learnable; our first grant proposal path walks the 30-day version, and the total effort is smaller than managing a consultant would be.
- Two to six applications a year, and a staff member has four or more hours a week: train in-house. This is the most common situation and the most commonly misdiagnosed one. Buying proposal development here means renting a capacity you will need forever; a structured course plus templates builds it once. See our breakdown of what a beginner grant writing course must include before choosing one.
- Two to six applications a year, and genuinely no staff time: hire proposal development, but scope it per application and keep funder selection in-house with your own eligibility screen. Outsourcing the go or no-go decision to the person paid per proposal is a conflict you do not need.
- More than six applications a year, or federal opportunities in play: hire systems and training first, then decide whether ongoing development help is still needed. High volume without internal infrastructure fails no matter how good the hired writer is.
- The proposal exists but has never been outside the building: buy review and editing only. It is the cheapest engagement on the menu and often the highest leverage per dollar.
Whichever branch you take, keep the outcome boundary in view: a competent provider improves the clarity, completeness, and fit of what you submit, and that is worth paying for, but no service can guarantee an award, and we cannot guarantee one either. Buy scope, verify method, own your files, and let the funder’s decision be the one thing nobody sold you.