Build Open City Join the waitlist

Working guide · Customer edition 1.1

Build a local community in the city you call home.

Turn it into a real-world social club, and make it strong enough to travel with you.

Open City is a repeatable way to build a local community around a place. For most people, that place is the city you already live in. This is the working guide: worksheets, gates, and an order to follow. It is not a book you read once and then improvise.

Join the waitlist

The order

Build the community before you depend on the event.

You start with an owned website and a digital community. You use that to find members, learn what they want, and create one recurring in-person gathering. Then you recruit people who can help run the room, until the city keeps working when you travel, get sick, move, or open another city.

  1. Website
  2. Primary messaging community
  3. Backup channel
  4. Local platform adapter
  5. Recurring in-person club
  6. Local operator handoff

Five layers

What a working city actually has.

Build them in this order. A recurring event is easier to fill when a digital room already exists. The digital room matters more when it keeps sending people into a physical one.

01

Owned front door

A website for discovery, trust, tracking, and consent. Minimum: a join path, events, rules, and email capture.

02

Primary community

The daily social layer. Default is a WhatsApp Community, or a locally validated equivalent. A moderator owns it.

03

Backup and local adapter

A backup channel, with Telegram as the practical default, plus a local app only when the people you want already use it.

04

Real-world club

One recurring flagship gathering. A captain runs the room. A deputy can run the next one without them.

05

Continuity

Shared operating notes, access control, and a handoff so the founder does not have to be in the room.

What you work through

One city, in order.

  • A city brief and a small paid smoke test before you spend on a full build.
  • The site, the messaging stack, and written rules before you invite people.
  • The first members, then a captain, a deputy, and a moderator.
  • One flagship format, run the same way each time, before you add more.
  • A 90-day launch plan, local articles, and a few partners.
  • A weekly operating rhythm, and money that sits around the community instead of blocking the door.
  • Account control and a handoff. A move, a second city, or a license comes only after the first city can run without you.

What this is not

Do not start with the heavy version.

Do not begin with a custom app, a leased clubhouse, a complicated membership program, a giant calendar, or ten empty chat groups. Do not build three weekly events before one recurring gathering is reliable.

Every number in the guide that is not tied to an outside source is a test target. It is a starting point, not a forecast or a guarantee.

The rule for the whole guide: a city is not ready to replicate until it can keep its digital community active and run its recurring gathering without the founder physically present.

The offer

Join the waitlist.

Build Open City is the working guide as a full system: the model, the gates, the worksheets, and the operating order. Customer edition 1.1. Research foundation October 2026. Leave your email to join the waitlist for Build Open City.