Grant Allocation Calculator
Plan milestone-based funding and prioritize grant projects
Milestone Allocation
Payment Schedule
Configure grant to see schedule
| Milestone | % | Stables | Tokens | Total |
|---|---|---|---|---|
| Total | - | - | - | - |
Grant Size Tiers
When to Use Grant Allocation Calculator
New Grant Structuring
Team asks for $50K. How to structure milestones? Use the calculator: $7.5K upfront (15%), then $12.5K per milestone for MVP, beta, and launch. Protects both sides.
Quarterly Budget Planning
$500K for Q1 grants. How to allocate across categories? Use Program Budget: 45% dev ($225K), 25% ecosystem ($125K), etc. Know exactly how many grants each category can support.
Application Review
20 applications, limited budget. Score each on impact, feasibility, team. High-impact + proven team = priority. Removes subjective bias from decisions.
Stables vs Token Mix
Grantee needs operational runway but you want alignment. Calculate: 60% stables ($30K for salaries/costs), 40% tokens ($20K vested). Both parties happy.
Milestone Tracking
Project completed milestone 2. What's their next payment? Check schedule: $12,500 stables + $8,333 tokens due. Clear documentation for treasury committee.
Grant Reports
Monthly community update? Show: "Funded 8 grants totaling $180K. 45% to development, 30% ecosystem. Avg grant size $22.5K." Data-driven transparency.
Frequently Asked Questions
Grantee missed a milestone - now what?
First: understand why. Life happens, scope creep happens. Options: 1) Extend deadline with clear new date, 2) Reduce scope and proportionally reduce remaining payment, 3) Terminate and keep remaining funds. Most grants allow one extension. Document everything for governance audit trail.
How much upfront is too much?
Rule of thumb: 10-20% for unknown teams, up to 30% for proven teams. Never >50% upfront. Exception: very small grants ($5K or less) where milestone overhead isn't worth it. For large grants ($100K+), consider even smaller upfront % since absolute amounts are larger.
Should we fund competing projects?
Yes, often. Competition drives innovation. Two teams building similar tools? Fund both if budget allows - best one wins users, and you have redundancy. Exception: very niche infrastructure where only one solution makes sense. Communicate transparently that there are parallel grants.
Token vesting for grant payments?
Common approach: tokens vest 6-12 months after receipt. Prevents immediate dumping. Some DAOs use cliff + linear (3 month cliff, then monthly over 9 months). Match to milestone timeline - final milestone tokens might vest longer since there's less leverage after completion.
How to handle scope changes mid-grant?
Scope changes are normal in software. Small changes: document and proceed. Major changes: formal amendment with revised milestones and possibly revised budget. If scope grows significantly, consider new grant proposal rather than endless amendments. Keep original scope documented.
What's a reasonable approval process?
Tiered by size: Micro ($1-5K) = committee approval, 1 week. Small ($5-25K) = committee + community review, 2 weeks. Medium ($25-100K) = full governance vote, 3-4 weeks. Large ($100K+) = multi-stage vote with discussion period, 4-6 weeks. Speed matters for small grants.
No comments yet. Be the first to share your thoughts!