Afín / Use cases / Hackathons
Hackathons

From "looking for a team" to "we have a team" in 10 minutes

The biggest problem at a hackathon is not the idea. It's finding the developer, designer or business profile that completes the team.

Try it free at your next event See interactive demo
The problem

What you already know happens

Unbalanced teams

Four developers with no designer. Two designers with nobody to build. Nobody knows what skills the person next to them has.

Nobody makes the first move

Publicly looking for a team is awkward. The best profiles form groups with people they already know and newcomers are left out.

Hackathon time wasted

Every hour spent looking for a team is an hour not building. In 24-48h hackathons, the first two hours are critical.

The solution

How it works at your event

  1. Scan the QR at registrationEach participant states their role (developer, designer, business, data) and what they're looking for in a team. 30 seconds, no app.
  2. Complements appear automaticallyThe developer looking for a designer sees the designers available who are looking for a technical project. Matching is bidirectional.
  3. The wave confirms interest privatelyIf both wave back, contact is revealed and they can start talking. No unwanted messages, no pressure.
A typical moment
A developer is looking for a designer and a business profile for a fintech idea. In 10 minutes they have a team and can start building.

The first two hours go to the project, not to matchmaking.

After the event

Data for the next edition

How many participants connected, which profiles were most in demand, how many teams formed in the first 30 minutes. Metrics that justify the investment in the event.

When is your next hackathon?

Try it small first: free for events up to 30 participants.

Book a free demo
Also for Demo Days Conferences Trade Shows Corporate Events Accelerators