The first site should start the work. It should not carry the whole story.
SAUNA. is a hard-capped outdoor sauna programme: 2,100 numbered outdoor projects. Indoor installations possible, shaped to the building. Lugano is intended as the first operating case.
The memo should explain the project in the same order as the keynote: story, design, manufacture, system, vision, then stress test. The economics matter, but they should come after the reader understands what is being built.
Small room. Long memory.
The origin is not a spreadsheet. It is a sauna ritual: heat inside, cold outside, family in one small room, and a habit that lasts.
Bitcoin matters because it shaped the time horizon: build for decades, keep the system understandable, and make the energy logic visible where it is useful.
Designed to last quietly.
SAUNA. is designed with Groundwork Studio in Copenhagen, led by Morten Bo Jensen. The design goal is not novelty for its own sake. It is a calm product language that can hold across many sites.
Each project may be bespoke in location, orientation, material sourcing, and use, but it should still be recognisably part of the same system.
KOERNER is the construction reference.
KOERNER Saunabau gives the project a sauna construction standard: tolerances, ventilation, timber, heat, moisture, and what holds up after years of use.
Outside DACH, the goal is not necessarily to ship a finished cabin from Germany. The goal is to document the standard well enough that local craftsmen, contractors, and suppliers can execute approved work where local execution makes sense.
2,100 numbered outdoor projects.
This is the point the memo needs to make clearly. The cap applies to the outdoor programme. Indoor installations possible, shaped to the building.
Separate LYN from SAUNA.
LYN should become the quieter background layer: origin, documentation, tools, specification logic, and company context. SAUNA. should become the clear public product and operating company, especially when `sauna.website` becomes the main domain.
Calm sauna sites, built with collaborators.
The work can include private projects, hotels, residences, and operated sites. Lugano is the first operating case because the context can understand Bitcoin, hospitality, energy, and private networks.
The first site should test demand, build execution, operating data, M4 feasibility, and the handover from product idea to working sauna.
The numbers should test the story, not replace it.
The previous memo led with operating profit, payback, and the 21-unit allocation. That can make the project look like only one small spa raise.
The cleaner use of the memo is to show what the first site is meant to prove, then expose the assumptions: site economics, build responsibilities, revenue lines, M4 logic, and what improves on the next site.
Use the first site to make the next one easier.
The ask should read as capital to complete the first operating case and document the process: site, build package, local contractor work, operating launch, partner materials, and first supervised units.
The memo should answer three plain questions: what is being built, who is responsible for what, and what does the first site teach us for the next one?
Plain framing: LYN develops the system. SAUNA. is the product and operating company. KOERNER anchors the construction standard. Local teams execute approved work. Lugano should prove the product, the build process, and the operating model.
Draft only. Not an offer. No forecast. The point of this page is narrative clarity before rewriting numbers, terms, or subscription documents.