I need help to make my project win the hackathon happening at my college. I have three members on my team, but all of them are pretty much useless. I’ve got only four hours left to finish the project, prepare the presentation, and deliver it on November 10. Basically, I did both the vibe coding and the actual coding myself and managed to build a decent product, but there’s still more work to do. So, is anyone up for helping out?
I might be able to help
Guys Made the IDS and submitted the project.
Good luck.
Forgot to update.. But won it, became 3rd as solo developer.
Solo-built a hackathon project, 4 hours left — need help finishing and presenting.
You don’t need a developer — you need your 3 teammates doing everything that ISN’T code. Hackathon judges score presentation and demo equally to the product itself. Your teammates can build the entire pitch deck with Gamma in 20 minutes and record a backup demo video with Loom in 5 minutes — no code required. Stop adding features, freeze what you have, and hardcode fake data for anything unfinished. The pitch wins hackathons, not the codebase.
Submit at least 30 minutes early. Teams get disqualified for missing required fields (video, README, screenshots, repo link). Assign one teammate to fill out the submission platform RIGHT NOW while you code.
🏆 Full 4-hour battle plan + delegation playbook + judge defense
Why This Works
Hackathon judges explicitly don’t score code quality — MLH’s official rules confirm messy code, bad comments, and inefficient algorithms are irrelevant. They score four things equally: technology use, design, learning, and completeness of the experience. Serial winners (20+ hackathon victories) all confirm the same pattern: teams that win usually build less than they planned — they’re just disciplined about building the right things.
One marketing manager who won a 20-team internal hackathon puts it bluntly: the entire hackathon should be spent on the slide deck, because you’re judged only on the minutes you present.
Hour 1-2: Feature Freeze + Hardcode
Write a 5-bullet demo script: what does the user see → click → get? Anything not on that list — stop building it. This is called “demo-driven scope” — if it’s not in the demo, it doesn’t exist.
For half-built features your demo needs: return hardcoded JSON, use a static data file, pre-fill forms with sample inputs. A Microsoft innovation consultant with 20+ patents says directly: mock data is expected and acceptable. Just label it “sample data” in your README.
Trick: Paste this into Cursor or Copilot: “The demo path is: user opens app → clicks X → sees Y → result Z. Make this exact path work with no errors. Everything else can be broken.” One prompt. Messy codebase → demo-ready.
Hour 2-3: Teammate Assignments (Zero Code)
| Teammate | Task | Tool | Time |
|---|---|---|---|
| #1 — Slides | Build pitch deck | Gamma — type one sentence, full deck in 30 sec | 20 min |
| #2 — Submission | Fill every Devpost field + record backup demo | Loom — one-click screen recording | 35 min |
| #3 — Pitch + Q&A | Write emotional opener + anticipate judge questions | Google Docs | 25 min |
Teammate #1 — Slides: Gamma generates a complete hackathon pitch deck from a single sentence prompt in ~30 seconds (free tier, 400 AI credits). Prompt: “Create a 6-slide hackathon pitch deck for [project] solving [problem] using [tech].” Customize 15 minutes. Export to PDF or Google Slides. You never touch this.
Teammate #2 — Submission + backup video: Open Devpost (or whatever platform). Fill in: project name, tagline, description, tech stack, team members, category/track. Draft a 5-section README: What It Does → How We Built It → Challenges → Built With → What’s Next. The moment one feature works end-to-end — open Loom, hit record, click through the happy path narrating what’s happening, stop. That 2-minute video is insurance. If the live demo crashes, the pivot line is: “Let me show you our backup video while I troubleshoot.” Judges respect foresight.
Teammate #3 — The 15-second hook: The opening line separates you from every team that starts with “Hi, we’re Team X.” Use one of these instead:
- “Last week, I tried to [your problem] and it took [absurd effort]. That’s what [X] people deal with every day.”
- “[Big number] people face [problem] yearly. We fixed it in 4 hours.”
- “I’m going to [do X] in [Y seconds]. Watch.”
Same teammate preps 5 backup slides for Q&A. Most common judge questions and how to answer when you vibe-coded:
| They ask… | You say… |
|---|---|
| “Walk me through your architecture” | Explain what you chose and why — not how AI wrote it |
| “How is this different?” | One specific differentiator, one sentence |
| “What would you build next?” | 2-3 realistic features showing product thinking |
| “What was hardest?” | Name a real decision, not a bug |
Judges don’t check code — entire 2025-2026 hackathons are built around vibe coding. They care whether you understand your own product. 10 minutes of prep covers you.
Hour 3-4: Deploy + Rehearse + Submit
Deploy to Vercel or Netlify — free, one command, instant live URL. Use this AI prompt: “Generate a clean README.md with sections: What It Does, How We Built It, Challenges, What’s Next.”
Record the Loom backup if you haven’t. Rehearse the pitch twice with timer. Cut anything over the time limit. Submit everything with 30 minutes to spare.
The Sponsor Prize Shortcut
Grand prize = you vs 200 teams. Sponsor/category prize = you vs 5-10 teams. Check your hackathon’s prize list right now. If a sponsor has an API prize (“Best Use of X”), a single integration in the final hour qualifies you for a separate track with a fraction of the competition. Even a simple Google Maps embed or free weather API call counts.
Don’t force it though — a coherent story beats a shoehorned API every time.
/ 
Quick Reference
| Do |
Don’t |
|---|---|
| Freeze features — only build what’s in the demo script | Add “one more feature” until the deadline |
| Hardcode mock data for unfinished parts | Spend 2 hours on backend nobody sees in demo |
| Assign every teammate a non-code task | Let 3 people watch you code |
| Record a Loom backup video | Risk a live-only demo on hackathon WiFi |
| Open pitch with a story or stat | Lead with “Hi, we’re Team X” or your tech stack |
| Submit 30 min early with all fields filled | Scramble at the last second with empty fields |
| Check sponsor prizes for side tracks | Compete only for grand prize against everyone |
Your Situation → Do This
| You’re thinking… | Do this instead |
|---|---|
| “I need more developers” | Put your 3 teammates on slides, submission, and pitch prep |
| “There’s still more work to do” | Freeze features, mock the rest, make one demo path bulletproof |
| “My teammates can’t help” | They build the presentation, fill Devpost, and record backup video |
| “I should code until the last second” | Stop coding 90 min before deadline — pitch prep wins hackathons |
| “Judges will see my code is AI-generated” | They literally don’t check code — they check pitch and demo |
You said you did both the vibe coding and actual coding yourself and built a decent product — that’s already ahead of half the teams. Now stop building and start presenting. Put those 3 teammates to work, freeze the feature list, and own that pitch. Reply if you get stuck on any of this 
!