The clock starts. You have 24 hours. Your team has an idea scribbled on a napkin. By tomorrow, you need a working app, a compelling demo, and a story that makes judges care. How do you get from here to there?
This is the step-by-step playbook that hackathon winners follow — from the moment the problem statement drops to the final demo.
Step 1: Understand the Problem (Hour 0-1)
Don’t start coding. Start thinking. Read the problem statement three times. Ask yourself:
- Who has this problem? (Be specific — “students in tier-2 colleges” not “people”)
- Why hasn’t it been solved? (What’s the gap?)
- What would a solution look like to the user?
The teams that win hackathons aren’t always the best coders — they’re the ones who understand the problem most deeply.
Step 2: Define Your MVP (Hour 1-2)
You can’t build everything in 24 hours. Pick ONE core feature that demonstrates your solution. Everything else is nice-to-have.
Ask: “If our app could only do one thing, what would make judges say ‘wow’?”
Write it down. That’s your MVP. Everything you build should serve this one feature.
Step 3: Sketch Before You Code (Hour 2-3)
Draw your screens on paper. Map the user flow. Decide your tech stack. Divide work among team members so everyone can code in parallel.
A good split for a 4-person team:
- Person 1: Backend API + database
- Person 2: Frontend UI
- Person 3: AI/ML integration or core logic
- Person 4: Design, content, and demo preparation
Step 4: Build Fast, Not Perfect (Hour 3-18)
This is the longest phase. Key principles:
- Use AI coding tools aggressively — describe what you want, let the AI generate boilerplate
- Use existing libraries — don’t build what you can npm install
- Commit frequently — nothing worse than losing 3 hours of work to a git conflict
- Test the happy path first — make sure the demo flow works before handling edge cases
- Communicate constantly — “I’m stuck on X” is better than silence for 3 hours
Step 5: Feature Freeze (Hour 18)
Stop adding features 6 hours before the deadline. Use the remaining time to:
- Fix bugs in existing features
- Polish the UI (colors, spacing, loading states)
- Prepare the demo script
- Write a clear README
- Test the entire flow end-to-end
Step 6: Craft Your Story (Hour 20-22)
Your demo isn’t a feature walkthrough — it’s a story. Structure it as:
- The problem (30 seconds) — make judges feel the pain
- Your solution (30 seconds) — the “aha” moment
- Live demo (2 minutes) — show it working
- Impact (30 seconds) — who benefits and how
- Tech stack (30 seconds) — what you used and why
Step 7: Demo Day (Hour 24)
Tips for the final presentation:
- Have a backup video recording in case the live demo breaks
- Make eye contact with judges, not your screen
- Anticipate questions about scalability, security, and business model
- Be honest about what you didn’t finish — judges respect transparency
The Secret Ingredient
The teams that consistently win hackathons on Reskilll share one trait: they build something they genuinely care about. When you’re passionate about the problem, it shows in your demo, your code, and your energy at 3 AM.
Find a problem that matters to you. The rest follows.