> For the complete documentation index, see [llms.txt](https://docs.superteamde.fun/superteam-germany-guilds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superteamde.fun/superteam-germany-guilds/hackathon-hub/submission-and-pitching.md).

# Submission & Pitching

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](https://blog.colosseum.com/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](https://de.superteam.fun/buildstation)
* [Book 1:1 Mentoring](https://superteamdao.notion.site/colosseum-hackathon-2025#1e8794d3ba3380a7bfe1d2428dd4db04)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.superteamde.fun/superteam-germany-guilds/hackathon-hub/submission-and-pitching.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.