Problem Statement

The conceptualization of FlowMint was born out of the direct pain points experienced during HackSpire 2025.

The HackSpire 2025 Experience

During HackSpire 2025, the workflow was heavily fragmented across multiple unlinked platforms:

The Pain Points Analyzed

1. Lack of Team Cohesion: Google Forms treats every submission as an isolated entity. It cannot natively understand that User A, User B, and User C belong to Team X. This made tracking team-level completion nearly impossible.
2. Duplicate Storage: Because the PPT was a team requirement but the form was individual, multiple members of the same team uploaded the exact same PPT. This led to massive storage bloat in Google Drive and confusion for reviewers over which file was the "final" version.
3. No Resubmission Logic: If a team uploaded an incorrect screenshot, the organizers had to manually email the team, ask them to resubmit via a new form or email, and manually stitch the new data to the old spreadsheet.
4. No Reviewer Dashboard: Shortlisting was done by color-coding rows in Google Sheets, which is prone to accidental edits, lacks an audit trail, and cannot scale to hundreds of reviewers.
5. Communication Blackhole: Participants had no way of knowing if their submission was accepted, rejected, or pending review without asking organizers directly on Discord/WhatsApp.

FlowMint was architected specifically to solve these five critical failures.