🎤Submission & Pitching

Practical guidance for turning a working build into a strong hackathon submission.

Strong submissions are usually simple, clear, and easy to evaluate.

The best official source here is Colosseum’s own submission workshop recap:

• Perfecting Your Hackathon Submission

What Usually Matters Most

• a clear explanation of the problem and who it is for

• proof that your team can actually ship

• a strong pitch video

• a direct technical demo that explains the build

• clarity about how and why you used Solana

• evidence of validation, traction, or user feedback when possible

Common Mistakes

• treating the pitch video like a hype montage

• being vague about the product and user

• not explaining the Solana-specific design

• forgetting repo or doc access for judges

• submitting something technically interesting but hard to understand

Recommended Workflow

1. lock the core story early

2. record the pitch only after the narrative is sharp

3. record the technical demo separately

4. test every link, repo, video, and doc before submitting

5. get feedback from mentors or peers before final submission

Local Support

• Build Station

• Book 1:1 Mentoring