Everyone in this field will tell you to apply for more grants. This post makes the opposite case. Sometimes the most valuable move you can make on a grant is the decision not to write it, and almost nobody teaches you how to tell the difference. Below, I'll walk you through how I decide which grants are worth pursuing, which ones to walk away from, and how to say no without burning a single bridge.
Table of Contents
The application that never should have crossed my desk
The proposal landed in my review queue a few cycles back. Strong organization. Good people doing real work. And an application that never should have been written.
The funder's priorities were rural health access. The applicant was an urban health care organization. The work was real, the writing was solid, and on the surface it looked like a match, because health is health. But the proposal never once addressed the word that defined the entire opportunity: rural. Whether they missed it in the guidelines or saw it and decided to write around it, they spent what I'd guess was forty hours building a strong case for money the organization was never going to get.
I read the whole thing, because that was my job as a reviewer. But I knew by the second page what everyone else at that table knew. This was a no. Not because the work wasn't worthy. Because it wasn't a fit, and no amount of beautiful writing was going to make a rural health funder care about an urban organization that never explained how it would reach a single rural patient.
Here's the part that stayed with me. That organization didn't have a writing problem. It had a decision problem. The grant was lost the moment someone said "let's go for it" instead of "let's be honest about whether this is ours to win."
I've spent 25 years on every side of this table. Grant writer, reviewer for private foundations and federal agencies, nonprofit staffer, consultant. And the single most underrated skill I've watched separate the people who thrive from the people who burn out is not persuasive writing. It's the discipline to walk away.
Why we don't walk away (even when we should)
The whole culture of this field pushes in one direction: apply. Apply for everything. You miss 100% of the shots you don't take. Free money is out there if you just hustle for it.
I understand where it comes from, and I'll be the first to say it's well-intentioned. But it's also how good grant writers run themselves into the ground. Instrumentl's 2026 shadow work study of more than 1,000 grant professionals found that the typical grant pro already loses about 29.5 hours a week to invisible, manual labor, the kind that never appears in a job description. That's before you add a single application you were never positioned to win. Pile those on, and you don't end up with more funding. You end up burned out.
A few things make walking away hard, and naming them helps:
The board member who's already excited. Someone on the board read about a grant, forwarded it with three exclamation points, and now there's an expectation that of course you'll apply. Saying no feels like telling them their idea was bad.
The "free money" myth. Grants are not free. They are some of the most expensive money an organization can take on, once you count the writing, the matching requirements, the reporting, and the strings attached to how it gets spent.
Scarcity thinking. When budgets are tight, every opportunity looks like one you can't afford to skip. The irony is that chasing every opportunity is exactly what keeps an organization broke and overextended.
For consultants, the invoice. If you bill by the hour or by the project, every application you talk a client out of is money you didn't make this month. (If you work on value, this barely registers: you simply steer the client toward a better-fit opportunity and sub it in.) I'll come back to why walking away is the right call even when it does cost you the fee.
What the wrong grant actually costs you
When people weigh whether to apply, they usually only look at one side of the ledger: what we might win. The cost side is where the real damage hides.
Opportunity cost. The forty hours you spend on a mismatched application are forty hours you didn't spend on the three grants you actually could have won. There is always a better use of that time, and it's almost always a grant that fits.
The administration trap. Some grants cost more to manage than they award. A $15,000 restricted grant with quarterly narrative reports, a separate financial audit requirement, and rigid spending categories can quietly consume a staffer's time for a year. This is not a rare problem. In the same Instrumentl study, 87% of organizations reported walking away from, delaying, or downsizing a grant because the process was too heavy, and 22% turned one down specifically because they couldn't manage the reporting. You won, and you still lost. (Instrumentl is a Spark the Fire partner, and signing up through that link helps fund Certificate scholarships.)
Mission drift. This is the quiet one. When an organization keeps reshaping itself to qualify for whatever funding is available, it slowly stops being the organization it set out to be. You can chase your way right off your own mission.
Staff burnout. Every rushed, low-odds application your team grinds out at the last minute is a withdrawal from a finite account. Do it enough and your best people leave.
Funder relationships. Reviewers remember. When you submit something that's clearly not a fit, you're not just losing this cycle. You're teaching a funder that your organization doesn't read guidelines carefully, which is the last impression you want to leave with someone you'll be asking again next year.
Six signals that you should walk away
Over the years I've boiled the walk-away decision down to a set of honest questions. Here are six of the signals I look for first. If two or three of these are flashing, slow down before you commit.
Mission fit. Does this grant fund what you already do, or what you'd have to invent yourself into to qualify? The second one is a trap.
Funder fit. Have they actually funded organizations like yours, at your size, in your geography, doing your kind of work? Before you read one word of their guidelines, pull their Form 990 (free on ProPublica's Nonprofit Explorer or Candid). On a private foundation's 990-PF, the full grants list lives in Part XV, Line 3; on a community foundation's standard 990, check Schedule I. Three years of actual awards will tell you more than any mission statement.
True cost. If you win, what will it cost you to administer? Add up the reporting, the match, the restrictions. Then decide whether the award is worth the management.
Capacity. Do you have the people to do the funded work AND handle the compliance that comes with it? Winning a grant you can't deliver on is worse than not winning.
Strength of your case. This is not about whether you're big, mainstream, or well-known. Some of the most competitive applications I've ever scored came from small organizations serving a very specific community, precisely because they could prove they were the right ones to do the work. The honest question is whether you can back every requirement with evidence: real outcomes, a clear plan, the track record to deliver. If you can't substantiate that case yet, the answer might be "not this cycle," not "not us."
Timing. Is the deadline forcing a rushed application you already know will be weak? A strong application next cycle beats a desperate one this week.
None of these questions is hard on its own. The discipline is in actually asking them, out loud, before the momentum of "let's go for it" takes over. That's exactly why I built them into a structured tool, so the decision happens on purpose instead of by default. More on that at the end.
Two organizations, one funding cycle
Picture two organizations heading into the same twelve months.
Organization A applies for everything. Eighteen applications. The team writes nights and weekends to keep up. They win two. One of the wins is a small, heavily restricted grant that pulls their program director into reporting work for the better part of a year. By spring, their strongest writer is updating her resume.
Organization B runs every opportunity through a go/no-go filter first. They apply for six grants, all of them genuine fits. They win three. Every win advances the mission, the team has the bandwidth to deliver, and they finished the year with the energy to build relationships for next cycle.
Organization B did less and got more. Not because they wrote better. Because they decided better.
For the consultants reading this: Organization B is also the client who refers you, renews you, and tells everyone you're the one who finally brought sanity to their grant strategy. If you bill by the hour or the project, the application you talk a client out of this month is the trust that keeps them for three years. If you work on value, you're not losing anything at all. You just point them at a better-fit opportunity and sub it in. Either way, the math favors the no.
How to say no without burning the relationship
Knowing you should walk away is one thing. Telling someone is another. Here's how I handle the three hardest conversations.
To a board member or executive director. Don't reject the grant, reframe the goal. "I love that you're thinking about new funding. I looked at this one closely, and here's why I think it would cost us more than it returns. Here are two that fit us much better." You're not saying no to their ambition. You're redirecting it somewhere it can actually win.
To a client. Lead with their interest, not your invoice. "I could write this for you, and I'd bill you for it. But I don't think you'd win, and I'd rather you spend that money on the two grants where you've got a real shot." Clients can tell the difference between a vendor protecting a fee and an advisor protecting their outcomes. The second one is who they keep.
To a partner organization that wants you on their application. Collaborative grants are everywhere, and "will you join ours?" can be a hard ask to refuse without feeling like the difficult one. Be straight and specific: "I want to keep working with you, and I don't think this particular grant is the right vehicle for us. Here's why, and here's the kind of partnership where I think we'd both come out ahead." Protecting a partnership means being honest about the fit, not saying yes to keep the peace.
Walking away is the strategy
We treat the decision to apply as the strategic move and the decision not to apply as a failure to act. It's backwards. Walking away from the wrong grant is one of the most strategic things you can do, because it protects the only two resources that actually win grants over time: your team's energy and your funders' trust.
This is what centering purpose over hustle looks like in practice. Not applying for less out of fear. Applying for the right things on purpose, so the work you win is work you're proud to deliver.
You don't have to apply for that grant. Sometimes the smartest decision you'll make all year is the application you choose not to write.
Take the guesswork out of the decision
I built the six signals above, plus the rest of the questions I use, into the Go/No-Go Grants Assessment Guide. It walks you through the decision step by step so you can make the call with confidence instead of momentum. Get the Go/No-Go Grants Assessment Guide here.
Get this in your inbox first
Every week I send one practitioner-tested idea like this one straight to working grant writers and consultants, before it ever hits the blog. Join the newsletter here. It's the best way to think about grants like a reviewer, not a rookie.
FAQ
How do I know if a grant is worth applying for? Start with fit before effort. Confirm the funder has supported organizations like yours, at your size and in your geography, doing similar work. Then weigh the true cost of winning, including reporting, match requirements, and restrictions, against the size of the award. If the grant doesn't fund what you already do or would cost more to administer than it returns, it's usually a walk-away.
Isn't applying for more grants the way to win more funding? Not usually. Spreading yourself across every opportunity tends to dilute the quality of each application and wear out your team. Organizations that filter for genuine fit apply for fewer grants, put real effort into the ones that matter, and finish the year with the capacity to deliver and to build funder relationships for the next cycle.
How do I tell my board or executive director that we shouldn't apply for a grant they're excited about? Reframe rather than reject. Acknowledge the goal behind their interest, explain specifically why this opportunity would cost more than it returns, and offer one or two better-fitting alternatives. You're redirecting their ambition toward funding you can actually win, not shutting it down.
As a grant consultant, doesn't talking a client out of an application cost me money? In the short term, yes. Over time, the client you steer away from a losing application is the client who trusts your judgment, renews, and refers you. Protecting their outcomes builds the kind of relationship that's worth far more than a single project fee.
Allison Welch, M.Ed., GPC, has 25+ years of experience and is one of approximately 30 GPCI-approved trainers nationally. She is the founder of Spark the Fire Grant Writing, creator of the Certificate in Grant Writing, and author of the forthcoming book "The "Of Course" Factor: A Guide to Meaningful Grant Writing" (October 2026).