Video summary

How to win a hackathon

Main summary

Key takeaways

Educational

Main ideas / lessons (how to win a hackathon)

The speaker shares five actionable tips (framed as “methods”) that successful teams use to improve their chances of winning. The emphasis is on preparation, execution speed, and meeting hackathon constraints—especially deadlines.

5 top tips (detailed methods)

1) “Lockbox method”

Purpose: Build a mindset and presence that signals you’re there to create real technology—not just attend.

How to apply:

  • Don’t treat the hackathon as “free food”; show judges that your goal is to build something meaningful.
  • Make sure judges clearly understand who your team is and what you’re building.
  • Demonstrate a real startup orientation (turning the project into something with real value).

2) “AA method”

Purpose: Stand out visually and tangibly during the pitching/demo stage.

How to apply:

  • Create something visually impressive that clearly differentiates your team.
  • Build something tangible that judges/attendees can actually see and interact with.
  • Prefer “showable” outputs (e.g., mobile apps, working demos, physical/interactive components).
  • Assume you’ll be pitching against many teams (at least ~15), so differentiation is critical.

3) Come up with the idea before the hackathon

Purpose: Beat the competition by arriving prepared with a clear, tested direction.

How to apply:

  • Use the limited event time (roughly 36 hours, sometimes 48) efficiently.
  • Before arriving, invest your own time to:
    • Understand the technology involved
    • Identify what it can do
    • Define the problem you will solve
  • Aim to finalize your idea within the first hour of the event rather than spending the first 10 hours figuring out what to build.

4) Start coding as soon as possible

Purpose: Execution speed compounds advantage.

How to apply:

  • If you already prepared an idea, begin building immediately.
  • Coding is encouraged, but alternatives are acceptable:
    • Prepare a presentation
    • Use “no-code” tracks
  • Key principle: don’t wait—start the core work early.

5) Don’t miss the deadline (and don’t chase perfection)

Purpose: Late submissions harm judging fairness and reduce your chances of winning.

How to apply:

  • Submit on time (examples given: 12:01 / 12:05, or even 12:30 when deadlines are at 12).
  • Avoid spending extra time polishing one “perfect” detail at the expense of timely delivery.
  • Treat the hackathon as a constrained “build something working” sprint, not a perfection project.

Deadline analogy (10 steps):

You might only reach steps 1–2 (or step 3), but you can’t realistically reach step 10 in time. The goal is to submit what you have—early-stage and functioning—not to delay until it’s perfect.

Closing message / outcome described

  • The speaker claims these five tips can help beginners go from knowing nothing to raising millions of dollars via their first startup.
  • Viewers are encouraged to apply the principles at the next hackathon and sign up using a link provided in the video description.

Speakers / sources featured

  • Speaker (unnamed narrator): The main person delivering the tips (no name provided in the subtitles).
  • Emy: Mentioned as a hackathon pro.
  • JJ: Mentioned as a hackathon pro.
  • Silicon Valley’s biggest VCs: Mentioned generally (no specific names provided).
  • YC: Mentioned as a startup accelerator (no specific individual sources).

Original video