HACKATHON — 30 HOURS

WCC Launchpad 30

Thirty hours to turn one problem worth solving into a working product. National, online, free to enter, with ₹50,000 in cash and PPO opportunities for the top three teams.

Date
4 Oct — 5 Oct 2026
Starts
10:00
Runs for
30 hours
Joining
Details sent to everyone who registers
Kind
hackathon
Who it is for
Students, developers, designers and first-time builders.
agentic aiopen innovationeveryday automationonlinebeginner-friendlyproduct building

WCC Launchpad 30 is a national online hackathon for students, developers, designers and anyone else who wants to find out what an idea looks like once it has to run.

You get thirty hours to pick a problem that genuinely exists, build the one journey through it that matters, and show that it works. You do not need a startup, a rehearsed pitch, or years of experience behind you. You need a problem worth solving and the willingness to build.

The aim is not the biggest project in the room. It is the clearest possible proof that your idea can work. A small product with one reliable, well-made workflow beats a pile of half-finished features almost every time.

30

Hours to build

₹50,000

Cash prize

100+

Winners

1–4

Per team

[ Brief ] // What you are being asked to do

Take one problem worth solving and turn it into something people can use, in thirty hours.

What you leave with

  • A working product or prototype whose central workflow actually runs
  • Source code judges can reach before the deadline
  • The problem you chose and the evidence that it is real

Team size

1 to 4. Every participant belongs to one team only.

Who can come

School and college students, developers, designers, no-code builders, first-timers and early-stage teams. Under-18s may be asked for a parent or guardian's permission.

[ Schedule ]

  1. Sun 4 Oct, 10:00The brief, the tracks and the submission list go out. Building starts.
  2. Mon 5 Oct, 14:00Submissions close. Everything on the list is in, or it is not.
  3. Mon 5 Oct, 16:00Building period ends. Judging begins on what was submitted.
  4. After the eventJudging on what was submitted, and then the winners are announced.

[ Judging ]

User insight and problem evidence15 points

How well do you understand the person you are building for? Research, observation, interviews or survey data that shows the problem is real.

Strength of the core solution24 points

Does the product solve the problem you named, directly? Is the main workflow focused, useful, and does it produce a clear outcome?

Technical depth and reliability24 points

How well have you used what you chose? Does it work consistently? Are the integrations, data flows and AI components put together with thought?

Originality and differentiation15 points

What makes this different from the tools that exist and the ideas that show up at every hackathon? A distinctive insight, interaction or approach.

Real-world usability12 points

Could the intended user work it out without a walkthrough? Is it accessible and practical in the setting it is meant for?

Responsible design and trust10 points

Privacy, security, bias, transparency, accessibility and human oversight, where they are relevant. Do users keep control of the decisions that matter?

[ What you get ]

  • ₹50,000 in cash, split across the top three teams
  • PPO opportunities for the top three teams
  • 100+ winners across the hackathon and the mini-challenges
  • T-shirts, pens and stickers
  • Miro AI access, n8n, a .XYZ domain and Lovable Premium
  • A verifiable digital participation certificate
  • Sponsor challenges and surprise rewards through the thirty hours
  • A functional product you can put on a résumé or in a portfolio

[ Tracks ]

Choose one track from those below. A track is the area you work in — it is not a problem statement. Inside the track you pick, you identify your own problem and build the solution to it. Nobody hands you a brief, and finding a problem worth solving — then showing it is real — is the first thing the judges score. Interdisciplinary projects are welcome, but the entry has to name its primary track.

01

Agentic AI

Systems where AI agents reason, plan, use tools and finish useful work with proper human oversight. Judged on how useful the agent is, how well it is orchestrated, how reliably it runs, and how clearly a human stays in control.

  • Research and knowledge agents
  • Customer-support agents
  • Personal productivity assistants
  • Multi-agent collaboration
  • Business-process automation
  • Developer and coding agents
  • Responsible autonomous workflows
  • Industry-specific copilots

02

Open Innovation

A real problem, solved with whatever technology fits. The problem should be specific, the user should be clear, and the solution should measurably beat what people do today.

  • Accessibility
  • Climate and sustainability
  • Healthcare operations
  • Finance and commerce
  • Civic technology
  • Community platforms
  • Logistics and mobility
  • Creator tools
  • Safety and trust

03

Everyday Automation

Tools that take a repetitive, unglamorous job off someone's day and do it reliably. The result is measured in time given back and mistakes stopped — an automation that has to be watched every run has not automated anything.

  • Personal and team workflow automation
  • Documents, forms and paperwork
  • Inbox, calendar and scheduling
  • Data entry, cleanup and reconciliation
  • Reports and status updates that write themselves
  • Small-business and household operations
  • Monitoring, alerting and follow-ups
  • Glue between the tools people already use

[ Rules ]

  1. The core product must be built during the official hackathon period.
  2. You may research and discuss ideas before the event.
  3. Existing libraries, APIs, frameworks and open-source components are allowed.
  4. Templates or code you wrote earlier must be clearly disclosed.
  5. Only work done during the event counts towards judging.
  6. AI, no-code and low-code tools are allowed.
  7. Every participant belongs to one team only.
  8. The project must be the team's own work.
  9. Plagiarised, copied or misleading submissions are disqualified.
  10. Respect software licences, intellectual property and user privacy.
  11. Projects must not promote illegal, harmful or discriminatory activity.
  12. Everything on the submission list has to arrive before the deadline.
  13. Judges may ask for repository access or other proof of development.
  14. Organisers may remove anyone who disrupts the event or breaks community guidelines.
  15. The judges' decision is final.

[ Questions ]

Is it free?

Yes. Registration costs nothing.

Can I take part on my own?

Yes. Solo entries are allowed, and so are teams of up to four.

Can beginners enter?

Yes. The event is built for first-timers and experienced builders alike, judged on the same criteria.

Can my team come from different colleges?

Yes. Members can be from different institutions, cities or backgrounds entirely.

Can I use AI tools?

Yes. Disclose the significant ones in your submission.

Can I change track?

Yes, any time before final submission. Only one primary track can be selected.

Is deployment compulsory?

Strongly recommended. If you cannot deploy, provide a reliable executable demo and a video.

Will everyone get a certificate?

Certificates go to participants who submit a valid project on time and follow the rules. Registering alone does not qualify.

[ Partners ]

Title sponsor

[ Finished ]

This one has run

Registration is closed and the event is over. Everything above is what it was. The ones still open are on the events page.

[ Terms and agreements ]

These are the participation, certificate, judging and conduct terms that every We Code Coders event runs under, this one included.

Read the terms and agreements in full