The completion numbers are harsh
Opportunity Hack reports that solo hackers finish at 9.8 percent while teamed registrants finish at 39.7 percent. It also reports solo projects ship 46 percent of the time, while teams of 3 or more ship 93 percent+ of the time.
That does not mean solo is doomed. It means solo needs a smaller idea, fewer dependencies, and a demo path you can finish without waiting on anyone else.
Solo works when the surface is tiny
Parable Rhythm won overall first place in the AWS PartyRock Generative AI Hackathon with an interactive crime-thriller game built around PartyRock widgets. It is a good solo-style pattern because the demo surface is clear and the platform removes backend weight.
If you go solo, pick one user, one input, one output, and one memorable moment. Avoid projects that need frontend polish, backend infra, data cleaning, and live pitching all at once.
Team size has a ceiling
MLH recommends team sizes of 1 to 4 and says hackers have the most success with a maximum of 4. Devpost judge Maria Yarotska said a really big team is not a red flag, but it is pinkish because contribution and bounty distribution can become uneven.
The sweet spot is not the largest possible group. It is a group where every person owns a visible piece: demo, backend, frontend, data, hardware, or pitch. If someone has no owner area, the team will feel bigger and move slower.
Join late only with clarity
Devpost's online teamwork guide says teams should introduce skills and share basic project concepts before joining. That is the minimum bar for late matching.
Ask three questions before joining: what is the demo path, what is already built, and what can I own by deadline. If the team cannot answer, stay solo or find another room.
Use the decision rule
Go solo when the project is mostly one stack, the demo can be recorded by you, and the judging criteria do not require a wide system. Form a team when the idea needs multiple surfaces or when presentation quality matters as much as code.
The point is not hero mode. The point is shipping. Opportunity Hack's data says teams finish more often, so solo should be a deliberate scope choice, not a fallback after avoiding team formation.
< read by a human · updated as things change >
browse hackathons