How to apply to Adalwin Ignite (and actually get funded)

Most grant applications are written to impress. Ours is read to understand. The difference matters, because the people reading your Ignite application are not scoring buzzwords — they're trying to picture you building the thing. This is how to make that easy for them.

The three stages

There's no committee, no quota, no secret rubric you have to reverse-engineer. The process is three real conversations about your work, and each one is decided by people.

1. 1Written application — about 30 minutes, online, saves as you type. You describe the problem, the user, your solution, and your team. Pick a track: Prototype if you've already built something, Idea if you haven't shipped yet.
2. 2Video round — shortlisted teams record 3–5 minutes. Every member on camera, no editing required. We want to see the people, not a polished trailer.
3. 3Final presentation — in person, in Pune. Demo what you have, talk through where it goes. Selected teams get the grant and start onboarding.

What we actually read for

When we read an application, four things jump off the page — and none of them is your CGPA.

• A real problem. Not “there is no app for X.” A problem you can describe because you, or someone you've actually spoken to, has felt it.
• A specific user. “Students” is not a user. “Second-year diploma students in Pune who commute 90 minutes and can't find verified PG listings” is a user.
• Evidence you can build. A repo with commits. A rough demo. A screenshot of the ugly v0. For the Idea track, a sharp plan for what you'd build first.
• Why you. The unfair, specific reason this team is the one — you live the problem, you've shipped before, you can't stop thinking about it.

The mistakes that sink strong teams

We see the same avoidable misses again and again. Don't be these:

• Vagueness. “We use AI to revolutionise education.” We can't fund a sentence that could describe a thousand companies. Be concrete or be forgotten.
• No proof of motion. If you've been “planning” for a year with nothing to show, that tells us something. A weekend of real building tells us more than a month of polishing slides.
• Hiding the team. One name on a four-person project, or a “technical co-founder we'll find later.” At least one member has to be able to personally build it. Say who that is.
• Writing for a robot. Long, formal, keyword-stuffed paragraphs. We read for substance. Simple English — or Hindi/Marathi-mixed — is completely fine.

Picking your track

Same grant, same bar — the only difference is the evidence you bring. If you've built anything a few people can use, apply to Prototype and give us a link we can open. If you have a sharp plan and the itch but nothing shipped, apply to Idea and show us how you'd start. We wrote a whole post on choosing if you're on the fence.

Before you hit submit

Read your application back as if you were a stranger. Would they understand what you're building in the first two sentences? Would they believe you can build it? If yes, send it. If you're not selected, you can reapply next cohort — it's never held against you, and teams that keep building usually come back stronger.

That's it. No connections, no referrals, no famous-college requirement. The application is open now for Ignite Edition One, Pune. Start it here — it saves as you type, so you don't have to finish in one sitting.