Accepted founders only

Summer Hackathon hackpack

Everything you need once you are in: where to go, what to bring, how the weekend runs, and exactly how projects will be judged.

See the agenda Practical info
At a glance

The important stuff, without the fluff.

This page is the single source of truth for accepted teams. If anything changes, it gets updated here first and then repeated in the WhatsApp group.

Dates 21-23 August, 2026
Location Stockholm archipelago area
Exact address Shared with accepted founders 7 days before check-in
Format IRL, overnight, build-first weekend
Bring

What to pack

  • Laptop, charger, headphones
  • Extension cord or power strip if you have one
  • Warm layer for late-night building
  • Running shoes or outdoor shoes
  • Toiletries and any medication
Agenda

Three days. Very little wasted motion.

Friday

Lock in

  • 16:00 Check-in and room assignment
  • 18:00 Dinner
  • 19:00 Opening kickoff, rules and intros
  • 20:00 Team formation and idea narrowing
  • 21:00 Build sprint starts
Saturday

Build day

  • 08:30 Breakfast
  • 09:30 Standup and traction check
  • 10:00 Customer calls, shipping, iteration
  • 14:00 Midpoint review with organizers
  • 18:30 Dinner
  • 20:00 Demo coaching and final push
Sunday

Demo day

  • 08:30 Breakfast
  • 10:00 Final submission deadline
  • 11:00 Live demos begin
  • 13:00 Judges deliberate over lunch
  • 14:00 Winners, closing remarks and departures
Judging criteria

How teams will actually be scored.

Traction

  1. 5 points Clear proof of demand. The team has paying users, revenue, signed LOIs, pilot customers, or strong active usage from real users.
  2. 4 points Strong market signal. The team has waitlist signups, demo requests, serious customer conversations, or users who clearly want to test the product.
  3. 3 points Some validation. The team has spoken to potential users or customers and received positive feedback, but there is no strong commitment yet.
  4. 2 points Weak validation. The team has a reasonable assumption about demand, but little direct proof from real users.
  5. 1 point No clear traction or validation. The idea is mostly based on assumptions.

Problem & Validation

  1. 5 points The problem is specific, painful and clearly validated with real users, customers or data.
  2. 4 points The problem is clear and believable, with some evidence that it matters to the target group.
  3. 3 points The problem makes sense, but the urgency or customer pain is not fully proven.
  4. 2 points The problem is broad, vague or not clearly connected to a real user need.
  5. 1 point The problem is unclear, unvalidated or feels like a solution looking for a problem.

Business Potential

  1. 5 points Clear customer, clear business model, strong scalability and a believable path to becoming a real company or product.
  2. 4 points Good commercial potential with a reasonable customer segment, pricing logic and growth path.
  3. 3 points Some business potential, but the customer, pricing or go-to-market strategy needs more clarity.
  4. 2 points Could be useful, but it is unclear who would pay or how it would scale.
  5. 1 point No clear business model, customer or path beyond the hackathon.

Originality

  1. 5 points Highly original, memorable or surprisingly creative. The idea or execution feels meaningfully different.
  2. 4 points Fresh angle on an existing problem or a creative combination of technologies.
  3. 3 points Solid idea, but somewhat familiar or similar to existing products.
  4. 2 points Mostly a basic version of something that already exists, with limited differentiation.
  5. 1 point Very generic idea with no clear unique angle.