Founders ask us two versions of the same question: “Am I allowed to apply to several grant programs at once?” and “Will it look bad if I do?” In general the answer is yes, you may, and no, it will not. Applying in parallel is normal, and reviewers know teams do it. What gets teams into trouble is something else: two programs paying for the same work, or a program learning about the other application from someone other than you.
This guide covers what to check before you send anything, how to disclose parallel applications, how to split milestones so that no two grants pay for the same thing, how to get several tailored applications out of one document, and how to keep track of the replies.
What is generally allowed, and what to check
There is no single rule. Each program sets its own terms, they differ, and they change, so we do not summarise any program’s exclusivity rules here. Check each program’s terms and its application form before you apply. These are the points to look for:
- Other funding. Many forms ask what you have already received and where else you have applied. Answer completely. If the form does not ask, disclose anyway (see below).
- Already-funded work. A program may decline to pay for a deliverable that another funder has paid for, or may fund only work that has not started yet. Retroactive programs are the opposite: they pay only for work already delivered.
- Ecosystem conditions. An ecosystem program funds work on its own stack and may attach conditions about where the project deploys or launches. Two such conditions from two chains can contradict each other. Find that out before you sign, not after.
- Licence and IP. Some programs require open source, and some name the licences they accept: on our tracker, Aleo lists open source as required and the Filecoin Foundation lists MIT/Apache-2. Make sure every program you apply to can live with the licence you chose.
- Reporting. Each grant brings its own milestones, reports and payment schedule. Three grants means three sets of obligations.
If the terms are silent on something that matters to you, ask the program’s contact and keep the answer in writing.
How to disclose parallel applications
Put a short “Other funding” section in every application, with three lines: received, pending, planned. For each entry name the program, the amount if it is settled, and which milestone the money is for. For example: “Pending: an application to [program] for milestone 2, the mainnet integration. This application covers milestone 1 only.”
Then keep it current. If one program says yes while another is still reviewing, tell the second one the same week. It costs one email. Being open gives a reviewer nothing to object to; an undisclosed overlap they find on their own gives them a reason to decline that has nothing to do with your project.
Split milestones so no two grants pay for the same work
The rule is one deliverable, one payer. Before applying anywhere, break the roadmap into milestones that can be checked separately, then assign each one to the program whose focus it serves:
- The chain-specific piece (a deployment, an integration with that chain’s tooling) goes to that chain’s foundation or community fund.
- The chain-neutral, open-source piece (a library, a benchmark, research) goes to a public-goods or research-oriented program.
- The first product milestone, the one that shows there is a company here, goes to a fund’s grant program.
Give every milestone its own budget, and let no line item appear in two budgets. Where a cost is truly shared, such as an audit or infrastructure, split it explicitly and show the split in both applications.
Sometimes two programs say yes to overlapping scope anyway. Do not quietly accept both. Tell both, keep the milestone with one, and offer the other the next milestone on your roadmap. That keeps the facts straight and both relationships intact.
One master document, tailored one-pagers
Write everything once in a master document: the thesis, why it has to be on-chain, the team with links, the full roadmap cut into milestones, the budget per milestone, the evidence you can ship, and the other-funding table. You will rarely send it as it is; every application is cut from it.
For each program, produce a one-pager that changes three things and nothing else:
- The fit paragraph. Why this program, in the words of its own stated focus.
- The milestone. The one you assigned to this program.
- The ask. An amount inside the program’s stated range that matches that milestone’s budget.
Team, dates, links and numbers stay identical in every version. Inconsistent facts between two applications do more damage than any parallel application. Our one-page grant application template on GitHub is CC0-licensed: fork it once as the master, then copy it per program.
Some programs do not take a free-form page at all. On our tracker, Polkadot OpenGov Treasury proposals are submitted on-chain, Project Catalyst and the Stellar Community Fund are decided by community vote, and Superteam Earn has you apply with a single profile. The master document still supplies the content; the format is theirs.
Track every reply
A spreadsheet is enough. One row per application: program, date sent, which version you sent, the milestone assigned, the amount, the contact, the stated reply time, the status and the next action. Add a column for “disclosure updated” so that a yes from one program reliably triggers a note to the others.
Timelines differ a lot, which is another reason to apply in parallel. From the notes on our tracker: Aleo lists initial feedback within one week, Aave Grants DAO takes rolling applications and announces new grantees monthly, the Interchain Foundation runs quarterly rounds, and the Filecoin Foundation lists a three-month review cycle. Apply to the fast and rolling programs first. Follow up once after the stated window has passed, then leave it. When a no arrives, log the reason next to the row; our 14-day playbook for a rejected application covers what to change before the next send.
To build the list, search and filter the Web3 Grants Tracker by program type, compare ticket and stage, then open the program pages for each program’s stated amounts, focus and how to apply.
How we handle parallel applications
ZK Prime Capital does not ask for exclusivity, and we accept the same document you wrote for another program. The application is one link and one paragraph: link the one-pager you already have and say what the grant unlocks. Grants are $5K–$75K, non-dilutive, for idea- and prototype-stage teams building on-chain AI agents, DeFAI or ZK infrastructure, and every application gets a reply within 5 business days. Tell us what else is pending or funded. Work another program has already funded is evidence you can ship, which is one of the things we look for; just send us a different milestone.
Applying to several programs this month? Assign each one its own milestone, keep the disclosure line current, and send us the same one-pager. Apply with your project ▸