A few years ago, I wrote a grant proposal for a NAMI affiliate applying to a private foundation. It was a solid project with a clean budget and a clear community insight statement. But I added one thing most proposals leave out: a short passage explaining how the project would scale. I spelled out what we would accomplish with the amount we requested, and what we would add if the funder were able to invest more.
Weeks later, a check arrived in the mail. It was $5,000 higher than what we had asked for. No phone call, no negotiation. The foundation simply decided to give more because I had shown them exactly where the additional dollars would go.
That check taught me something I have been teaching ever since: your ask is not a fixed point. It is a starting position. The proposals that get funded well, whether the award lands above or below the request, are the ones that tell the funder in advance how the work flexes.
In this article
Funders rarely have your exact number
Most grant writing instruction treats the budget as a sealed envelope. You calculate the project cost, you request that amount, and you wait for a yes or a no. The trouble is that funders are working from their own constraints, not yours. A program officer may have $35,000 left in a cycle and a $30,000 request in front of them. Or they may have $20,000 and a stack of $30,000 asks.
When your proposal only describes the project at one funding level, you have handed the funder a binary: fund it exactly, or do not. When you describe how the project scales, you give them a third option, and that third option is often where the extra money lives.
How to write scalability into the proposal
Take the two-day music festival from the budget narrative post, the $102,000 project that draws more than 25,000 people and is free to everyone, funded from sponsorships, a state tourism grant, city lodging tax dollars, in-kind venue use, and vendor fees. In that post, the lens was the state tourism grant, and that particular opportunity was capped at $30,000. A hard cap is the one place scale up language has nowhere to go: a funder cannot exceed a ceiling it has already published, no matter how strong your case. Scale back language still matters when a cap is in play, because partial awards are common, but the surprise larger check lives with the opportunities that leave room above your ask.
Do not assume you can tell which is which by funder type. Some foundations cap their awards, and plenty of government programs never publish a ceiling at all. The only question that matters is whether this specific opportunity has room above your ask, so read the guidelines closely and, when they are silent on the point, ask the program officer before you decide there is no upside to writing in your scale up tier.
So picture taking that same festival to a funder whose guidelines leave room above the ask, the way the foundation behind the NAMI check did. You request $30,000 toward the $102,000 total, and you add a short passage on how the work flexes. Here is the kind of scalability language I would write, usually near the end of the project description or inside the budget narrative.
Scale up: "With additional investment, the festival adds a free family activity zone and expanded accessibility services, including ASL interpretation and a sensory-friendly hour, deepening access for an event that already welcomes more than 25,000 people at no cost to attend." The extra dollars are attached to specific, countable additions. The funder can see exactly what another $5,000 buys, and every dollar of it widens free access rather than padding overhead.
Scale back: "At a reduced funding level, the festival preserves its core stage programming and stays free and open to the entire community, with adjustments to the number of featured artists and the scope of marketing." Notice what this language does not say. It does not say we can deliver the whole thing for less, and it does not quietly put a price on a festival the community knows as free.
The same project, three award scenarios
Funded at the request, $30,000: You execute the project as written. The budget narrative and the project description already match, so there is nothing to renegotiate.
Funded above the request, $35,000: Your scale up tier activates. The family activity zone and the expanded accessibility services were already on the page, so you are not scrambling to justify a surplus or quietly hoping no one asks what you did with the extra money. The plan was written down before the check cleared. This is the NAMI scenario: an opportunity with room above the ask, a clear picture of what more money buys, and a check that came in higher than the request.
Funded below the request, $20,000: This is where most grant professionals get caught flat footed. Your scale back language protects the core, and your diversified funding stack absorbs part of the gap, so the festival still happens with its integrity intact. This is also where the Walk Away Framework belongs. There is a floor below which the project cannot run honestly, and naming that floor in advance is part of writing scalability with integrity. A partial award is not automatically a yes, and knowing your floor keeps you from accepting money for a project you cannot actually deliver.
Whichever scenario lands, remember to revisit your logic model. Scaling a project up or back changes your outputs and often your outcomes, so the numbers you reported in the proposal need to travel with the new funding level when you build your work plan and your reporting.
The line you should not cross
Scalability language is powerful, and like most powerful things, it can backfire. The mistake is writing scale back language that signals you can deliver the full project for less money. Do that often enough, and you train funders to lowball you, because you have taught them the ask was padded.
The fix is in the framing. Frame scale back as protecting core impact while reducing reach or trimming add-ons, never as the same work at a discount. Frame scale up as specific additions tied to specific dollars, so the funder sees a return rather than a wish list. Scalability done well reads as discipline, not flexibility for its own sake.
Plan past the check
Building scalability into a proposal does more than hedge against a partial award. It signals that you run a thoughtful organization, one that has planned past the check and knows precisely how its work grows or contracts with the resources available. Funders notice that. Once in a while, they reward it with $5,000 you never asked for.
Frequently asked questions
What does it mean to write scalability into a grant proposal?
It means adding language that shows the funder how the project expands or contracts with the funding level. A scale up tier describes what specific additions more money would buy. A scale back plan describes how the project protects its core if the award comes in low. You are giving the funder more than a single fixed picture of the work.
Where in the proposal should scale up and scale back language go?
Usually near the end of the project description or inside the budget narrative, wherever the funder is already thinking about cost and scope. Keep it short. A few sentences tied to specific dollars and specific outcomes do more than a long passage.
Will offering a scale back option make a funder give me less?
Only if you frame it carelessly. If your scale back language reads as "we can do the same work for less," you teach the funder the ask was padded, and you invite a lower offer. Frame scale back as protecting core impact while trimming reach or add-ons, never as a discount on the full project.
How do I know whether a funder has room above my ask?
Read the guidelines first. Some opportunities publish a hard cap, and a funder cannot exceed a ceiling it has already set. Others say nothing about a maximum. Do not assume funder type tells you the answer, because some foundations cap awards and many government programs do not publish one. When the guidelines are silent, ask the program officer.
What should I do if I am funded below what I requested?
Go to your scale back plan and protect the core of the project. Revisit your logic model, because fewer dollars usually means fewer outputs and sometimes different outcomes, and your reporting needs to match the new reality. Know your floor in advance: there is a funding level below which the project cannot run with integrity, and a partial award is not automatically a yes.
Does scalability language work for every grant?
Scale back language is useful almost everywhere, because partial awards are common. Scale up language only pays off when the opportunity has room above your ask. With a hard cap, there is nowhere for a larger number to go, so put your energy into the scale back plan instead.
Is this just a polite way of padding my budget?
No, and the difference is disclosure. Padding hides flexibility you never tell the funder about. Scalability puts the flexibility on the page, tied to specific additions and specific cuts, so the funder sees exactly what each dollar does. One erodes trust. The other builds it.
If you want to go deeper than weekly tips, this is the kind of strategy we build into every module of the Certificate in Grant Writing. The next cohort starts September 22.
Not ready for that yet? Join the Spark the Fire newsletter and get practitioner level grant writing like this every week.
Allison Welch, M.Ed., GPC, is one of approximately 30 GPA-approved trainers nationally and founder of Spark the Fire Grant Writing Classes, LLC. She has 25+ years of experience as a grant writer, trainer, and reviewer, and is the creator of the Certificate in Grant Writing and the author of the forthcoming book The "Of Course" Factor: A Guide to Meaningful Grant Writing (October 2026).