Proposed · venue and dates unconfirmed
Whistler Bounty House.
An illustrative three-to-five-day sprint where a company team and selected builders concentrate on one defined challenge, then leave with a demo and a decision.
Truth before theatre
An illustrative flagship, not an announced retreat.
Hackhouse has not booked or partnered with the candidate property. Dates, capacity, programme, sponsorship, builder compensation, travel, meals, and price are all to be confirmed through a signed pilot scope.
The founder supplied an external candidate listing as a reference for the kind of environment being considered. This page uses a generated concept image rather than copying third-party listing photography.
View the external candidate reference ; opens a third-party page in a new tabVenue criteria
Built for work. Chosen for recovery.
These are requirements for a future venue and operating plan, not claims about a secured property.
Work-ready
Reliable connectivity, shared work area, and private calls would be mandatory venue criteria.
Small cohort
The pilot is designed for a tightly composed combined team, not a conference-sized audience.
Shared table
Meals and house operations are part of the working rhythm and priced in the signed scope.
Recovery
Space to reset matters, but skiing and amenities remain optional, not the programme.
Secure by agreement
NDA, data, devices, repositories, IP, and access revocation are set before arrival.
Demo-led
The retreat ends with working evidence and explicit next steps.
Illustrative operating rhythm
Five days. One decision path.
The three- and five-day formats are the initial pilot hypothesis. Seven- and thirty-day stays remain future research, not part of the first offer.
- Day 0 · Arrive
- House orientation, security and access check, team dinner, challenge briefing, and a shared definition of done.
- Days 1–3 · Build
- Quiet deep-work blocks, direct working sessions with the internal team, concise daily decision reviews, and shared meals.
- Day 4 · Integrate
- Join the work into a demonstrable system, document what is fragile, and prepare the final decision, not a pitch deck.
- Day 5 · Demo
- Show the evidence, decide what ships, assign the next owner, and close every data and repository access path.
Help decide whether Whistler should be first.
The application demo captures role, proof-of-work links, community interest, and 3/5/7/30-day preferences without sending or storing them.