A rejection from a grant committee usually contains one line of substance, and that line is rarely about your idea. Most of the declined applications founders show us after a “no” somewhere else failed on process: the committee could not tell what the money buys, when it lands, or why this particular program should be the one paying for it.
That is good news, because process is fixable in two weeks. Quality takes years. Below is the sequence we suggest to teams who come to us after a rejection. None of it requires a new product, a new deck or a new team.
Why the “no” is usually about process
- Committee load. Ecosystem programs read hundreds of applications per cycle, and the first pass is short. If the thesis, the ask and the deliverable are not visible on the first screen, the application is sorted into “later”, and “later” is where rejections come from.
- Missing milestones. “Extend runway”, “grow the team” and “continue development” are not milestones. A committee funds a thing it can check off. When the application does not name one, the reviewer would have to invent it, and reviewers do not do that for you.
- Wrong ticket size. Asking several times what a program typically writes, or a fraction of its minimum, gets declined before anyone reads the technical section. The amount signals whether you understood the program at all.
- Wrong program. Foundations fund their ecosystem, protocols fund their usage, funds fund your company. An agent that routes swaps on one chain is a strong ask for that chain’s foundation and a weak one for a public-goods round.
None of these say “the idea is bad”. They say “the reviewer could not evaluate the idea”. Fix that and you are back in the pile that gets money.
Days 1–3: re-scope to one milestone
Take the rejected application and delete everything that is not needed to reach one concrete, checkable milestone. For most early teams that is an MVP on testnet, a working integration, or a benchmark someone else can reproduce. One milestone, one date, one amount. If your roadmap has four phases, keep phase one and compress the rest into a single sentence at the end.
The test: could a reviewer who has never spoken to you verify, on the date you named, whether the milestone happened? If the answer needs a call with you, the milestone is not concrete yet.
Days 4–7: line-item the budget, ship a demo link
A grant budget is not a valuation. It is a bill of materials for the milestone: engineering weeks, review or audit, infrastructure, and nothing else. Three to six lines, each with a number, adding up to the ask. If a line does not move the milestone forward, cut it. If the total lands outside the program’s range, resize the milestone rather than padding or squeezing the numbers.
Then produce something a reviewer can open: a contract deployed to testnet, a hosted demo, a repo whose README runs in one command, a two-minute screen recording. Polish is not the point. A committee that can click on your work spends its few minutes evaluating it instead of guessing whether it exists.
Days 8–10: one page, plus the traction you already have
Rewrite the application onto a single page. Committees do not reward length; they reward finding the answer to each of their questions where they expect it. The four things that get funded are the same everywhere: a specific thesis rather than a category, a reason it has to be on-chain, evidence you can ship, and a milestone the money completes. Our one-page application template is built around exactly those four. We published it because it is the format we want to receive ourselves.
Traction goes in the evidence section, and it does not have to be revenue. Commits, testnet transactions, users of a previous project, a partner who has agreed in writing to integrate, a waitlist with real names. Small and verifiable beats large and vague. If you were rejected once, say so: “Applied to X in July; feedback was scope. This version is scoped to one milestone.” It explains why you are back, and it shows a team that iterates on feedback.
Days 11–14: choose where to re-apply
Programs come in two shapes, and they reward different timing.
- Rolling programs accept applications at any time and review continuously. The Ethereum Foundation’s Ecosystem Support Program is the usual example, though it now also runs open rounds alongside its standing wishlist and RFPs, so check the current process before you send anything. Ours works this way too. Rolling programs are the right first stop after a rejection: there is nothing to wait for, and your revised version reaches a reviewer while the work is still fresh.
- Round-based programs open for a window, close, and decide in a batch. Gitcoin runs seasonal quadratic-funding rounds; retroactive and community-voted funds follow a similar calendar. If the next round is more than a month away, apply to a rolling program in the meantime and use the round as a second shot with a milestone already in progress.
Our Web3 Grants Tracker lists the active programs we watch, with type, typical ticket, stage and notes on whether a program is rolling or runs in rounds, so you can pick two or three that match your chain, your stage and your amount in one afternoon. Apply to more than one. Foundations, protocols and funds do not exclude each other, and a milestone already funded by one of them is stronger evidence for the next.
What happens when you send a rejected application to us
We accept the same document. If you wrote a one-pager for another program, do not rewrite it for us: the application asks for one link and one paragraph, so drop the link to the document you already have and say what the grant unlocks. No deck. Every application gets a reply within 5 business days.
What we fund is narrow on purpose: on-chain AI agents, DeFAI and zero-knowledge infrastructure. Grants are $5K–$75K, sized to one concrete first milestone, typically getting an MVP to testnet. No equity and no token allocation is taken at the grant stage. Idea-stage is fine; $3.1M has gone to 60+ teams this way, many of them with nothing but a thesis and a repo when they applied.
When the milestone ships, there is an optional next stage that most grant programs do not have: a $50K–$250K investment in a priced round, incubation (tokenomics and go-to-market), and a token launch through the fund’s launchpad. It is a separate, later decision on both sides. But it is why a rejection elsewhere is not much of a signal to us. We are not funding an application; we are funding the first step of something we may want to keep backing.
Rejected somewhere else recently? Do the fourteen days above, then send us the result. Apply with your project ▸