hackathon-cash-prize

Hackathon Cash Prize

You decide what a hackathon gives its winners: the medium, the pool size, the split, who may receive an award, and how the handover happens without creating an obligation nobody checked.

Organizers ask about cash first. Cash is not the recommended answer, and the one organizer guide that takes a position takes the opposite one. Read the medium menu before assuming the user needs a number.

What you own, and what is already decided

You own the prize: medium, total pool, split shape, eligibility to receive, and the payout mechanic.

• The rank is not yours. samber/dev-event-organizer-skills@hackathon-judging produces the ranked outcome per track and hands it to you. Turn a rank into an award. Never re-open a placement, and never let the size of a prize influence who won it.
• The rules document is not yours. samber/dev-event-organizer-skills@hackathon-brief-design owns the published brief, including eligibility to compete: who may enter, at what age, from where, in what employment. You own the narrower question of who may legally receive an award once a rules-eligible team has won. Hand that text to the brief rather than drafting a rules document yourself.
  • Neither skill drew this split before this one existed. State it plainly when you present it, because a reader who has used the brief skill expects eligibility to live there.
• The ceiling is not yours. samber/dev-event-organizer-skills@event-budget sets the Prizes line inside the overall P&L. Propose a pool and a split that fit inside whatever that line carries.
  • Never invent a pool size independent of it. If that line does not exist yet, say so rather than sizing against nothing.
  • That skill names this one and describes the hand-off the same way, so you consume an agreed boundary rather than assert one.
• A sponsor-funded prize is sold elsewhere and delivered elsewhere. samber/dev-event-organizer-skills@event-sponsor-pricing prices the add-on that funds it; samber/dev-event-organizer-skills@event-sponsor-fulfillment delivers it as a tracked perk. You decide its shape - medium, split, eligibility - once the sponsorship is signed.
  • Neither of those skills names this one, and neither says anything about a competition prize: the fulfillment skill's only prize rung is the booth raffle below.
  • So you assert this boundary into empty space rather than repeat an agreement. Say so.
• A raffle prize is not a competition prize. A booth raffle is an attendee incentive open to any attendee, and it belongs to samber/dev-event-organizer-skills@event-sponsor-fulfillment. A competition prize is awarded on a judged rank. Both are sponsor-funded and both are called "prize", but the mechanics differ and so do the eligibility questions.

Every ranking below is a default, not a law. After the interview, re-rank each menu against what you know: a sponsor's credits already in hand, an organizer with no legal entity, a hardware event whose participants want components, a returning event whose last edition already published a prize structure.

Interview

Ask one question at a time, multiple-choice where possible. Questions 4-9 exist because the menus turn on them and no other question surfaces the facts they carry.

1. What does the Prizes line in the event budget carry, and has it been set at all? (Fixed input - you size inside it, you do not raise it.)
2. What track and place structure did the brief already publish, and did any of it promise a prize? Read the published rules before designing anything; a prize promised in writing is a commitment, not an option.
3. Which sponsors fund a prize, what did they buy, and is the funding cash, product credits, hardware, or an opportunity their own company controls?
4. Could any winner be a minor, and could any winner be outside the organizer's own country? Ask both explicitly - these two facts delete rungs from two menus and no other question surfaces them.
5. Does the organizing team have its own legal entity, or does it run under a school, a company, or a fiscal host? This decides who can even sign a payout, and how long money takes to move.
6. Are organizers, volunteers, mentors, judges or sponsor employees allowed to compete, and if so, may they win? These are two different permissions and most events conflate them.
7. Do you want the prize to buy attention before the event, or to reward the winners after it? A prize sized for marketing and a prize sized for the winners are different decisions with different failure modes.
8. What is the effort ceiling: organizer hours before the event, whether anyone will chase a winner for paperwork afterwards, and how reversible a mistake can afford to be?
9. By what date must the prize structure be published, and is this a one-off edition or a recurring event whose structure should still hold next year?

Q7 through Q9 move specific rungs. Name which as you re-rank.

• A near publication date (Q9) promotes the media that need no procurement lead time: recognition and credits first, cash only where the medium menu's delete conditions do not fire. It demotes gear, which the same menu's backorder warning puts furthest out.
• An attention-before-the-event intent (Q7) is the only thing that promotes a flagship pool. A reward-the-winners intent leaves it starved.
• A one-off edition (Q9) promotes the sponsor-funded pool, whose fundraising is already being done elsewhere. A recurring mandate promotes what is written once and reused, the standard-form payout text and the published eligibility paragraph, and it is what makes a counsel review worth its cost across editions rather than once.
• A low effort ceiling (Q8) deletes the flat-across-many-tracks split, whose entire cost is the per-winner check repeated.

Workflow

1. Run the interview. Read the budget's Prizes line (Q1) and the published brief (Q2) first.
2. Answer the medium question before the size question. The medium decides which legal categories are even live, and half the sizing conversation disappears once the prize is not money. Load references/prize-medium-catalog.md.
3. Size the pool inside the Prizes line, and separate the organizer's own baseline from the sponsor-funded part. They have different ceilings and different owners.
4. Choose the split shape against the track structure the brief already published, not against a blank page.
5. Write the eligibility-to-receive text and hand it to samber/dev-event-organizer-skills@hackathon-brief-design for the rules document. Load references/eligibility-to-receive-text.md.
6. Pick the payout rigor rung, and name every exposure category the chosen medium and winner pool trigger. Route each one - never answer it. Load references/payout-exposure-categories.md.
7. Publish the prize structure in the brief before submissions close. A prize announced after teams have chosen what to build has already failed at motivating anything.
8. On the day, take the ranked outcome from samber/dev-event-organizer-skills@hackathon-judging and award against the published structure. Record what was actually handed over, to whom, and what remains outstanding.

Present the structure section by section for validation - medium, pool, split, eligibility, payout mechanic - before any of it reaches the published brief. Publication is the point of no return, because a published prize is a promise.

If your harness has persistent memory, record:

• the medium and why
• the pool and the ceiling it fit inside
• the split shape
• the eligibility carve-outs
• which exposure categories were routed to whom

Prize medium

Five rungs:

1. Cash
2. Gear: hardware, components, tools a participant keeps.
3. Credits and vouchers: cloud or SaaS credits, gift cards, makerspace credit.
4. Opportunity: a conference ticket, a mentorship slot, an interview or investor introduction.
5. Recognition only: a trophy, a title, a public write-up, no transferable value.

The value axis here is counterintuitive. MLH's organizer guide frames the prize decision as behavioural rather than monetary: prizes "say a lot about who you are as a community, why you are there in the first place, and they influence the vibe of your event - big time." MLH states its own position on cash: "While cash prizes are easy for events, we do not recommend them. The perceived value of a cash prize is much lower than traditional prizes."

That claim's direction shifts the default order. It is one organizer's stated position, not a measured comparison of outcomes.

• value (what the winner perceives and what behaviour the prize rewards, per the framing above): opportunity > gear > credits > cash > recognition only
• effort (sourcing hours, procurement, coordination with a third party, chasing a winner afterwards): opportunity > gear > credits > cash > recognition only
• compliance cost, as the review each rung triggers and the reversibility it costs: cash > credits > gear > opportunity > recognition only
• efficiency: gear > recognition only > credits > cash > opportunity

Value and effort run in the same order across all five rungs. So no pair exists where one rung has value greater than or equal to another's and every cost less than or equal. Resist the temptation to manufacture a disagreement by calling cash the cheapest rung outright: cash is cheapest to procure and dearest to hand over, which is why that cost sits on the compliance axis rather than the effort axis.

The compliance axis is what re-orders this menu, and it is why the default is neither the most valued rung nor the cheapest. Cash moves through a payment rail to a named individual, and that rail pulls in the tax, cross-border and minor-payout categories; a keyboard handed over at a table does not. Credits sit beside cash because a redeemable, resellable code carries monetary value without ever touching a bank.

That payment rail is documented practice, not a hypothesis. Devpost's own prize-claim process requires a cash winner to submit a tax-identification form before funds release, with a separate form for an international individual and another for an organization, and the platform states plainly that working out which one applies is each winner's own responsibility. General tax-compliance practice treats a gift card or voucher the same way it treats cash for reporting purposes, and values physical merchandise through a fair-market-value mechanism instead: the sourced reason credits sit beside cash on this axis rather than beside gear.

The opportunity rung's place on this axis rests on reasoning alone. It stays the menu's least confident cell, so name it as an open question when you present the ordering.

• Gear - the default. MLH's own recommended direction, and the one rung that pairs high perceived value with no payment rail. It costs real procurement hours and carries a known constraint: many items will be backordered, so order prizes early to have them in time. It also carries a unit-count consequence the other rungs do not, covered on the split menu.
• Recognition only. Neither a fallback nor a demotion. hackathon.guide's author runs events on this rung deliberately: "don't make winners and losers. Just don't. There has never been beer, competitions, or time pressure at my hackathons." That is a civic-tech organizer's own practice, so the rung is genuinely chosen, though it does not necessarily fit a competitive student event.
  • Support from a different angle: MLH, PennApps, Papers We Love and NASA Space Apps all lead their public positioning with learning, building and sharing rather than prize size. An event positioned that way and awarding recognition only reads as consistent, not cheap.
  • Promotion condition, keyed to Q7: the prize rewards the winners rather than buys attention, or Q5 says the team has no legal entity and no fiscal host, in which case this is the only rung that needs neither.
  • Favour a form that outlives the ceremony. A trophy passed from cohort to cohort, or a public acknowledgement from someone the winners will recognise, holds value longer than a certificate nobody keeps.
• Credits and vouchers. Cheap when a sponsor already holds them (Q3) and near-free to that sponsor, which is why they appear in sponsor-funded tracks more than anywhere else. They carry expiry dates, redemption regions and account requirements a winner can fail to satisfy months later. State the expiry in the published prize structure or you will hear about it.
• Cash. Cheapest to procure and top of the compliance axis, which is why efficiency ranks it fourth rather than first. Delete it, from this menu and from the axis lines above, when Q4 says a winner could be a minor or outside the organizer's country, or Q5 says there is no legal entity and no fiscal host. The machinery to pay it correctly does not exist yet in those cases, and a cash prize parked at the bottom of a menu quietly becomes the plan at the ceremony.
• Opportunity - the starved option: top of value, top of effort, so efficiency never picks it. MLH names this rung in its own catalogues: conference tickets, "Lunch with your hero", a company visit, and an introduction to present to a seed funder in its hardware guide.
  • Its legal treatment is unsettled: an award that functions as a job or investment introduction plausibly intersects employment or securities rules in some jurisdictions. Name that as an open question when you offer it.
  • Promotion condition, keyed to Q3: an external party - a sponsor's hiring team, a conference, an investor - has committed in writing.
  • Delete it, from this menu and from the axis lines above, when no such commitment exists: an opportunity the organizer cannot actually deliver is the one prize that fails publicly, after the winner has been announced.

The full medium catalogue, the receipt-and-return practice, and the unit-count arithmetic are in references/prize-medium-catalog.md.

Total pool size

Four rungs:

1. No monetary pool
2. Modest pool: sized to the Prizes line.
3. Sponsor-funded pool: the organizer's own baseline is nothing and the pool scales only with signed commitments.
4. Flagship pool: deliberately sized to be the event's headline.

• value (submissions drawn and turnout - argued, not measured): flagship > sponsor-funded > modest > no monetary pool
• effort (fundraising, budget negotiation, and the procurement or payout volume that follows): flagship > sponsor-funded > modest > no monetary pool
• compliance cost: flagship > sponsor-funded > modest > no monetary pool
• efficiency: sponsor-funded > modest > no monetary pool > flagship

All three axes run in the same order. In every one of the six pairs the higher-value rung is _s

...