Hey there!
You’ve been approved to organize a Daydream. Cool! But… Here’s the million dollar question: how?
There’s no “perfect, by-the-book” way of organizing a hackathon. But there are some strategies to make it the best event you can.
This guide is, and will always be, a work-in-progress. Despite popular belief, I, Deven Jadhav, am not an omnipotent Hackathon Deity™. I’m drawing from caffeinated hours spent staring at screens, lessons learned from organizing “great” hackathons (Scrapyard, Counterspell, etc), and my countless mistakes.
DM the if you have any ideas to improve this guide\!People ask me about hackathons a lot. They say “Dev, how do I run a hackathon?” and I say “hmmmmmmmm.” And then they say, “The f*** you mean, Dev?” and then I say “uhhhhhhhhhhhhh.”
So… this is an attempt to write down my thoughts on how to get started.
From the perspective of attendees, these are the things that make hackathons incredible:
However, there are some key tasks you need to complete before your hackathon:
SUPER IMPORTANT!! Slack is how we communicate with organizers. If your city doesn’t have a Daydream channel yet, make one!
Reach out to people you enjoy working with! Start with a Slack channel and a shared to-do list (including steps in this guide!). Delegate tasks based on what people want to do.
YES ✅ | AVOID ❌ |
---|---|
Diverse set of skills (ex: Sponsorship, Web Dev, Marketing, Game Dev for workshops) Good vibes and willing to put 100x enthusiasm for the day-of | Creating a large team (inefficient) Too small of a team (NOT 1 person) Trying to organize everything with fancy project management tools |
I’d HIGHLY suggest meeting your team in-person to get to know everyone. Good vibes = happy team = fun organizing.
We have partnered with HCB to offer you Daydream accounts—with no extra fees.
The PoC will get a link to your Daydream event’s HCB org, and an onboarding video to help you get started!
Want a city@daydream.hackclub.com email? This will be coming to event PoCs soonTM! This is a shared Google Workspace account that the team can use to send out mass, personalized communications to attendees, and should be the contact email listed on your website so people can ask you questions.
(it’s kind of awesome. Google Workspace ftw)
You can either choose to make your own design with custom art, etc or clone our standard template.
A good hackathon budget generally only needs three things:
… And maybe supplies.
But a great hackathon needs:
Track your cost PER ATTENDEE. This will help prevent you from spending too much!
Well-planned budgets have:
Estimate your attendees as 50% of total signups. It might seem unintuitive, but from all our experience: half of the people who sign up show up!
You will get $7.50 per sign-up from HQ (this number will depend on where you’re running your event) to spend on food. Spend wisely!
Your hackathon cannot happen if you don’t have a venue. You could have a million dollars in sponsors but none of it matters if you have nowhere to host your participants. Finding a venue is arguably the most important part of hosting a hackathon. Lock in.
This should be your first priority.
Reach out to cafes, makerspaces, libraries, and even your school if you’re in a pinch.
What makes an awesome venue:
Check out our Venue Guide for more info.
Raising money can be one of the most tricky parts of running a hackathon! You may ask: “But Dev, I’m not an English student…I can’t write emails!” Here’s how to start:
PLEASE check out our sponsorship guide.
Outreach is an ESSENTIAL part of hackathons. No participants → No game jam. But how do you reach the ✨right people?✨
Email CS teachers: Make a video with your team and ask them to CC their students or post on Google Classroom! Check out JPEG’s video (here).
Email local organizations and clubs: FIRST Robotics teams, your student council, CS clubs, etc
Post on Instagram and social media! This is where people can discover your event. AND people will trust your event more if they see it’s on instagram and has nice branding. This is also a good resource for announcements and FAQs.
Post in parent group chats! Facebook, Whatsapp, WeChat. This is VERY effective in reaching beginners.
Print out posters and put them up 1) schools 2) libraries 3) even the gym
Also, tips: PLEASE reach out to mentors for beginner-focused game jams. Look for game devs and previous hackathon participants (local university students!).
Check out our Outreach Tab for more info.
Run of show → Time block it.
Leave a 30 minute window after submissions are due. (see a sample run of show here)
Key rules for organizers (Please read OUT LOUD with your team!):
Organizing Daydream is going to be one of the hardest things you’ve done so far. The Hack Club team is here to support you through the process, and promise to be reliable partners while you work on Daydream!
That being said, Hack Club HQ is not organizing this event directly. We will do everything we can to help you have great ownership, but we expect you to take ownership of your event, be proactive, reach out to us when you need support and be an equally reliable partner.
Contact method | Expected response time | When to use? |
---|---|---|
#daydream in the Hack Club Slack | 24 hours or sooner | Any general questions! Especially helpful for things that other organizers can answer for you. |
Email daydream@hackclub.com | 48 hours (Guaranteed response) | Anything that is high priority, involves personal information, or cannot be discussed publicly |
Request a 30 minute call with a Daydream mentor (maximum of two calls a month) | You can usually book a call 3-4 days in advance! | For more complicated situations that need context, or when you need advice from someone experienced in different situations! |
And we’re here to give it to you. Reserve a 10 minute call with Meghana, RenRan, or Augie to talk about your event and any help you need! Link here
You’re not just building a hackathon. You’re building a space where someone might code their very first game. Meet their best friend. Find their love ♥️ (for tech).
That’s our daydream. And we’re so, so excited to see what you’ll build.