How to Host a Tech Meetup: Step-by-Step Guide + 20 Event Ideas (2026)

The best tech communities aren't built online. They're built in rooms: a few dozen people, some pizza, a laptop on a projector, and someone saying "wait, show me how you did that."
This is a step-by-step guide to hosting a tech meetup from scratch, whether it's your first event for a campus club or the tenth for a city community. It covers format, venue, budget, speakers, promotion, a run-of-show you can copy, and what to do after. Then there are 20 meetup ideas, from build nights to board games.
It's based on what we've learned running TinyFish events with student and community leaders, from a 90-minute build night at UCL to a 24-hour hackathon in India.
Last checked: October 2026.
TL;DR
- Start small and specific: 20–40 people, one clear format, one clear audience.
- Venue can be free: campus rooms, coworking spaces and sponsor offices.
- Food is your biggest cost: budget roughly $5–15 per person, depending on whether it's pizza or a proper meal.
- Expect no-shows: for free events, plan for 35–45% of RSVPs not showing up, and send a reminder the day before.
- Use Luma + LinkedIn + Discord to promote, and post a recap within 24 hours.
- Want support? Request a TinyFish event at tinybounties.com, or become an ambassador at tinyfish.ai/ambassadors.
Step 1: Pick your format and audience
Decide two things before anything else: who it's for, and what they'll do when they get there.
- Audience: beginners, experienced developers, founders, designers, or students from one campus. "Everyone" is not an audience.
- Format: build night, talk + Q&A, demo night, panel, workshop, or social. Hands-on formats get people talking to each other; talks get people listening.
- Size: 20–40 people is the sweet spot for a first meetup. Small enough to talk to everyone, big enough to feel like a community.
Tip: hands-on events build communities faster. At UCL Build Night, students shipped 30 working web agents in 90 minutes, and judging them live turned it into a show everyone stayed for. Here's how to win a hackathon with AI if you want to see what makes builds stand out.
Step 2: Find a venue (free options first)
- Campus rooms: most universities let student societies book rooms for free. Book early, since popular rooms go weeks ahead.
- Coworking spaces: many host community events for free in the evenings in exchange for exposure.
- Sponsor offices: tech companies often host meetups in their office and cover food.
- Cafés and bars: good for socials; ask about a minimum spend instead of a room fee.
Check: Wi-Fi that handles everyone at once, enough power sockets, a screen or projector with the right adapters, and accessibility.
Step 3: Pick a date and time
- Weekday evenings (6–9 PM) work best for professionals; late afternoon works for students between classes and dinner.
- Avoid exam weeks, public holidays, and nights with big competing events.
- Give people 2–3 weeks' notice. Less and they're booked; more and they forget.
- Pick a regular slot (e.g. the second Thursday of each month) once you're running more than one. Consistency builds habit.
Step 4: Set a budget
For most meetups, food is the biggest cost.

| Item | Rough cost | Notes |
|---|---|---|
| Pizza | ~$4–5 per person | Budget chains with deals; ~3 slices per person if it's the meal |
| Proper meal (catering, salads) | ~$12–15 per person | A salad stretches a pizza order cheaply |
| Drinks | ~$1–3 per person | Water, soft drinks, coffee for morning events |
| Venue | Often free | Campus, coworking, sponsor office |
| Stickers / swag | Optional | Ask sponsors for theirs |
| Prizes | Optional | Gift cards or swag for build nights |
Order for your expected turnout, not your RSVP count. Free events typically see 35–45% of RSVPs not show up, so 100 RSVPs might mean 55–65 people. Ask about dietary needs on the sign-up form.
Need funding? Companies sponsor student and community events all the time. Pitch them early with your audience, expected numbers and what they'll get (a talk slot, logo on the event page, a recap post).
Step 5: Find speakers
- Start with your own community: someone who built something interesting is often a better speaker than a famous name.
- Ask local founders and engineers: most say yes to a 10-minute talk if you make it easy.
- Ask sponsors: many companies send someone to demo their product.
- Keep talks short: 10–15 minutes plus Q&A. Two short talks beat one long one.
- Send speakers the details a week before: time, length, audience, setup, and who'll meet them at the door.
Step 6: Promote it
- Luma: create the event page with a clear title, a good cover image, and complete host profiles. People are more likely to come when they can see who's hosting. Add co-hosts so your team can manage it together.
- LinkedIn: post from your own account and your co-hosts'. Tag speakers and sponsors so it reaches their networks.
- Discord, WhatsApp and campus groups: post where your audience already talks. Here's how to grow a Discord server around your events.
- Reminders: send one the day before and one 2 hours before. Reconfirmation reminders cut no-shows significantly.
- Use more than one channel. The best hosts mix channels instead of relying on one.
Step 7: A run-of-show you can copy
Here's a 2-hour evening meetup:

| Time | What happens |
|---|---|
| 6:00 PM | Doors open, food, name tags, Wi-Fi on the screen |
| 6:20 PM | Welcome (5 min): who you are, the plan, house rules |
| 6:25 PM | Talk or demo 1 (15 min + 5 min Q&A) |
| 6:45 PM | Talk or demo 2 (15 min + 5 min Q&A) |
| 7:05 PM | Hands-on part: build, discuss or lightning demos (40 min) |
| 7:45 PM | Show and tell or winners (10 min) |
| 7:55 PM | Thank-yous, group photo, next event date |
| 8:00 PM | Hang out and pack up |
Step 8: On-the-day checklist
- Arrive an hour early. Test the projector, adapters, mic and Wi-Fi.
- Put up signs from the entrance to the room.
- Have a check-in (Luma's check-in or a simple list) and name tags.
- Put the Wi-Fi, schedule and links (Discord, feedback form) on the screen.
- Assign someone to take photos (with people's consent).
- Assign someone to welcome newcomers and introduce them to others.
- Start on time, even if the room isn't full.
Step 9: After the event
- Post a recap within 24 hours: photos, highlights, shout-outs to speakers and sponsors.
- Send a feedback form (3 questions max: what was great, what to change, what next).
- Thank speakers and sponsors personally.
- Announce the next date while people are still excited.
- Track the numbers: RSVPs, attendance, new members, cost per attendee. They make your next sponsor pitch much easier.
20 tech meetup ideas

Build nights and hackathons
1. 90-minute build night: one theme, everyone builds, show and tell at the end.
2. Mini hackathon: a 4–8 hour challenge with a small prize.
3. 24-hour hackathon: the big one. Teams, mentors, judging and lots of coffee. (Like Build With Bharat, where 700+ builders spent 24 hours building.)
4. "Fix my side project" night: people bring half-finished projects and help each other ship.
5. AI agent build night: build an agent that works on the live web, judged live. See 25 AI project ideas for inspiration.
Demo nights
6. Demo night: 5-minute demos, no slides, just the product working.
7. "Built this weekend" demos: only projects started that week.
8. Startup demo night: student or early-stage founders demo to a friendly crowd.
Talks and panels
9. Lightning talks: 5 minutes each, 6–8 speakers.
10. "How I built it" talk: someone walks through a real project, including what broke.
11. Founder or engineer panel: 3 people, one host, audience questions.
12. Tool deep dive: a hands-on workshop on one tool or API.
Career events
13. Portfolio review night: experienced people review student portfolios and GitHub profiles.
14. Internship hunt with AI agents: everyone builds an agent that finds and tracks real internships. Here's how to find internships with an AI agent.
15. Mock interview night: pair up and practise technical interviews.
16. Resume and LinkedIn workshop: quick fixes that make a real difference.
Social
17. Game night: board games and snacks. Low pressure, great for newcomers.
18. Build + board games: build for an hour, play for an hour.
19. Community dinner: a long table, no agenda, good conversations.
20. Outdoor walk or picnic: a casual meetup in a park, great in good weather.
Want TinyFish at your next meetup?
TinyFish is one API that lets AI agents use the live web: search it, read pages, click through websites and monitor changes. It's a great fit for build nights, hackathons and workshops, because people can build something real in an evening.
- Run an event: request a TinyFish event at tinybounties.com and we'll help with the format, workshop content and, where it fits, support for your event.
- Lead a community: join the TinyFish Ambassador Program to run events in your city or campus and earn rewards for the people you bring in. Sign up at tinyfish.ai/ambassadors.
- Looking for other programs to lead? See community ambassador programs to lead in your city.
Keep reading
- How to Grow a Discord Server from Scratch (for Tech and Student Communities, 2026)
- How to Become a Developer Advocate (DevRel) with No Experience (2026)
- How to Become a Brand Ambassador with No Experience (and Get Paid) in 2026
- How to Organize a Hackathon: Step-by-Step Guide + Free Checklist (2026)
- How to Get Sponsors for Your Event or Hackathon (+ Email Template)
Follow TinyFish for event ideas and community spotlights: X (@Tiny_Fish) · LinkedIn (TinyFish) · Instagram (@tinyfish_ai)
AI disclosure
Content on this website may be created or refined with the assistance of AI tools and is subject to human editorial review.



