“We Kill” Hackathon

Do not start from your card statement. Start from the last time your agent could not do something: no API, an API behind a sales call, or pricing that assumes a human with a seat. That wall is your target.

Somebody sells the human version of that job, and their price is on a public pricing page. That published price is the only hard requirement, because the comparison is the entire point. There is no approved list, no category restriction, and no advantage to picking something famous.

Your build has to do the job a paying customer buys that product for, end to end, for at least one real use case. Running on live data, in front of a judge, handling bad inputs and empty results. A UI with mock data behind it is not an entry.

You do not have to match every feature. Name the workflow you replaced and name the ones you did not, because honest scoping scores higher than overclaiming every time.

Teams up to three. Register one entry with one bound social handle, name the whole team in the submission, and split the prize yourselves.

The Monid integration and the kill have to be new work built during the ten days, and your commit history has to show it. Building on top of something you already had is fine as long as the judged part was written inside the window.

Comparing your work to a named competitor on price and capability is normal and legal, and it is most of what makes these demos land. Four rules keep it that way: use current public prices, compare a plan someone can actually buy, show your real cost including failed runs, and criticise products rather than people.

Anything that reads as harassment of a company or an employee is removed from the competition.

You own it entirely. By entering you give Monid permission to show your submission, video and name in coverage of the hackathon. No license to your code, no assignment, no right of first refusal.