A stage for the product
Demo Day brings founder stories, product demos and support requests to investors, co-hosts and media audiences.
A public stage for builders.
A clear support path after it.
Bring promising Avalanche projects in front of investors and partners. Review their work together. Then connect agreed KPIs with concrete rewards and ecosystem support.
Agreed KPI → verified result → defined support
Proposed structure. Partner participation, the grant package and operating terms are agreed before launch.
Some teams have already engaged with Avalanche and need a practical next step. Others have a useful product and need an entry point into the ecosystem.
Demo Day brings founder stories, product demos and support requests to investors, co-hosts and media audiences.
Inspira’s screening and manual review combine with Team1’s ecosystem knowledge to establish what exists and what comes next.
The founder knows what to deliver, how it will be checked and which resource follows the result.
Demo Day is the core event. Preparation makes the stage useful; Milestone Desk turns the momentum into continued work.
Open applications and show the full opportunity around Demo Day.
A project pool, partner contributions and clear application materials.
The support plan is agreed with the KPIs. Founders know the result, evidence and support conditions before starting the work.
The same quality criteria apply to both groups. Previous grant recipients receive priority in review; each team still needs to earn its place on the stage.
Previously funded, reviewed or considered for support, including teams that need help finding their next step.
A credible product and a practical Avalanche integration or deployment plan. Prior work on Avalanche is not required.
Allocation applies to finalist places. Suitable teams from either group can join Milestone Desk.
Product, team, stage, working demo and technical links; previous Avalanche interactions, grants and commitments; work completed, blockers, support needed and the next product result.
New teams also explain why Avalanche, what will be integrated and who will deliver it.
The engine proposes findings. Inspira and Team1 review them manually.
Team, product, technical work, activity and Avalanche fit.
Founder questions, evidence review and a recommendation.
Ecosystem context, previous commitments and selection.
Presentation preparation, public exposure and an individual KPI plan with attached rewards or support.
Review feedback and a Milestone Desk plan agreed with Team1 around achievable results.
Clear reasons and, where gaps can be addressed, the information or conditions needed for reconsideration.
All applications are registered. Active KPI plans cover every finalist and other applicants meeting the shared criteria.
Explain the screening harness, its stages, evidence and questions, and the manual contributions of both teams. An approved example shows the path from project information to a finding and a KPI plan.
Public materials describe the actual work performed and use information approved for sharing.
Every admitted team agrees its KPI plan and publishes a post or short video: what it is building, how it will work on Avalanche and the next result it intends to achieve.
This applies to finalists and other admitted applicants. Technical completion is checked separately through the agreed evidence.
An online Demo Day in the 10X Founders format. Prepared founders show what they have built, explain their place on Avalanche and ask for the support needed next.
Promote the event, bring relevant networks and contribute defined rewards.
Review prepared profiles, ask questions and follow up with relevant founders.
Share announcements, partner reveals, finalist stories and results.
Major Avalanche project founders bring practical expertise and connections.
Investor outreach begins with 6–8 relevant funds. Names and contributions are revealed as confirmed.
Inspira prepares finalist demos, presentations and support requests. Investors receive concise reviewed profiles; hosts and partners introduce the teams.
Opening and partner introductions, founder pitches and demos, questions from Team1, VCs and ecosystem experts.
One winner is announced. Hosts explain rewards and the next milestone steps.
Record feedback and investor interest. Share results and coordinate relevant founder introductions.
Proposed slot. The final schedule follows the agreed number of finalists.
A defined scope around the winner’s needs: product and growth priorities, investment materials or relevant partnerships.
Amount, conditions and support package agreed before promotion.
Co-host and service partner contributions with clear scope and delivery terms.
The winner’s acceleration is an additional package. Each finalist receives KPIs and support linked to completing them.
Hosts select one winner using criteria published before the event: product quality, ability to execute, Avalanche relevance, demonstrated progress and fit with the available support.
The acceleration scope identifies working sessions, deliverables and the result the winner should leave with.
A milestone is the result. A KPI defines completion. Evidence demonstrates it. The support plan explains what follows.
The agreed user flow works on Avalanche.
A working demo and the technical evidence specified in the plan.
A defined infrastructure package, technical guidance or ecosystem promotion.
Examples guide plan design. Each provider confirms the resource, scope and eligibility before it is offered.
Work completed, evidence, blockers and next-period plan.
Refresh technical context with the screener. Manually check the result and involve specialists where needed.
Receive findings, open questions and proposed support actions across the active pool.
The responsible provider delivers agreed support. The founder receives the next action and review date.
Updates can be asynchronous. Additional reviews follow milestone conditions; calls address blockers and decisions.
What exists and the evidence behind the review.
The next result and verifiable completion criteria.
Demo, code version, usage data, transactions or other required proof.
Delivery, reviews, check-ins, delivery owner and reviewers.
Resource, scope, conditions and responsible provider.
Progress, blockers, review conclusions and support delivered.
Committed resources include package and delivery conditions. Further funding decisions include criteria, an owner and review timing. Every result retains its evidence and review conclusion.
Founders execute. Inspira coordinates. Team1 reviews and approves its support. Partners deliver their agreed contributions.
The event brings attention to builders. The shared support plan gives each contribution a purpose after the stage.
Ecosystem positioning, relevant channels and agreed builder support.
Existing builders re-engage, new products enter and ecosystem progress becomes visible.
Existing pipeline, manual review, selection, KPI alignment, grants and support decisions.
A reviewed builder pool and a clear basis for continuing support.
Recruitment, screening, partner coordination, founder preparation, Demo Day and Desk follow-up.
A joint event, continued screening cooperation and documented builder results.
2–3 co-hosts bring promotion, networks, event participation and defined rewards. They gain relationships with suitable builders and visibility for their contribution.
Media partners share application announcements, partner reveals, finalist stories, the event and results, bringing relevant founder content to their audiences.
Provide specific services for the winner or milestone plans, with named recipients and delivery terms. Projects arrive with identified needs and opportunities for continued work.
A contributor can be both co-host and service partner. Promotion and service commitments are defined separately.
5–7 VCs review project profiles, ask live questions and pursue relevant investment follow-up, with reviewed context and direct founder access.
Avalanche project founders provide practical product feedback and ecosystem connections, creating opportunities for collaboration with emerging builders.
Finalists prepare presentations, make public announcements and deliver KPI evidence. They receive a stage, promotion, investor and partner access, feedback and milestone support.
Other admitted applicants publish their announcement and execute agreed KPIs, with feedback and a support path developed with Team1.
These decisions turn the proposal into a programme founders can clearly understand and partners can deliver.
Anchor Partner, Hosts and named decision owners.
Eligibility, finalist count, criteria and 70–80% allocation.
Co-hosts, media, VCs and invited Avalanche founders.
Grant terms, acceleration scope and confirmed rewards.
Available resources, KPI conditions and named providers.
Founder posts or videos, screening coverage and distribution.
Biweekly reviews, feedback timing, capacity, duration and commercial terms.
Applications, screening, finalist reveal, Demo Day and follow-up.
Once aligned, Inspira prepares the form, partner materials, project-card template, founder instructions and event schedule.
Back to the overview