Main deliverables in a hackathon

Main deliverables in a hackathon

Hackathons, as you may already know, have one ultimate goal: the solution to the challenge.

The way groups deliver this solution is called… wait for it: deliverable!

Yeah, quite objective, hum? And there are numerous forms of deliverables possible in a hackathon. Today, we’ll talk a little about the main ones:


Not being a deliverable that necessarily requires code, the prototype is often a format widely used in ideathons. Some of the most commonly used types of prototypes are:

  • Business model

Answer all possible questions about what your project is about; how can you solve the pain presented in the challenge; why your idea is different and better than others and how it can make a profit.

  • Validation Search:

A way to test and prove, through data, if your audience would consume the product your team created and if it really solves the problem. Google forms and concept testing are some of the data collection formats.

Functional Prototype:

The difference between this format and the first one we listed its already in the name: it works. No, you don’t have to develop the solution 100% as your team has planned. But it needs to have a deliverable that runs at least some of the imagined functions. In this case, the prototype usually is coded.


I know, I know, all deliverables quoted here are presented through a pitch. But a pitch can also be the deliverable itself. Also another widely used format during hackathons with challenges that don’t require code development.

In this type of deliverable, the intention is to speak up, make THE presentation and convince the jurors that your theory would be beautiful if put into practice. If you need a little help we have a whole text dedicated to it, just click here.

These are just a few examples of the many possible deliverables in a hackathon. In the end, what matters is to make your deliverable as close as possible to what you and your team planned together.

Leave a Reply