Edit wiki/how-to-plug-in.md — SF Builder Scene

---
sources:
- web research april 2026
- personal experience
tags:
- guide
- newcomer
- networking
- getting-started
title: how to plug in
type: topic
visibility: public-edit
---

# how to plug in

practical guide for someone new to SF's builder scene. not platitudes — actual steps.

## before you arrive

1. **set up your discovery feeds.** subscribe to these before you land:
   - [Cerebral Valley newsletter](https://cerebralvalley.beehiiv.com/) — weekly AI event roundups
   - [Luma SF](https://luma.com/sf) — follow specific organizers, not just the city feed
   - [GarysGuide](https://www.garysguide.com/events?region=sf) — broadest SF tech events calendar
   - [Bay Area Founders Club](https://bayareafoundersclub.substack.com/) — weekly event digests

2. **have something to show.** SF respects builders. if you can demo something — anything — you're already ahead of 80% of people who show up to events. a half-built prototype beats a polished pitch deck.

3. **pick your lane.** are you AI? biotech? SaaS? consumer? the scene is big enough that you need to focus. the AI lane is the most active right now.

## your first week

### day 1-2: get oriented

- walk [[vibe-guide|SOMA]], [[vibe-guide|Hayes Valley]], and the [[vibe-guide|Mission]]. get the geography in your body.
- grab coffee at Sightglass (SOMA) or Four Barrel (Mission). bring your laptop. look approachable.
- sign up for a [[spaces|coworking day pass]] at [[spaces|The Commons]] ($70/mo is a no-brainer) or [[spaces|Mox]].

### day 3-4: attend your first events

start with these (in order of approachability):

1. **[[events|Sundays in SF]]** — weekly coworking + demo. low-pressure, show up and work on your thing. this is the easiest on-ramp.
2. **[[events|AI Tinkerers]]** — if you're technical and building AI. live code demos only. high signal.
3. **any Luma event with <100 RSVPs** — smaller events are better for your first week. you'll actually talk to people.

avoid: massive networking mixers, anything that costs >$50 to attend (unless it's a legit conference), anything that describes itself as "exclusive" without being invite-only.

### day 5-7: go deeper

- apply to [[communities|South Park Commons]] if you're exploring what to build
- attend a [[events|Frontier Tower]] event for the full SF experience
- look at [[hacker-houses|hacker house]] options if you're staying long-term
- find the Luma page for your specific interest area and RSVP to the next 3 events

## how to not be cringe

this section exists because people need it.

**do:**
- lead with what you're building, not where you went to school or where you worked
- ask people what they're working on and actually listen
- follow up within 24 hours if you have a genuine reason to (not "great to meet you!" — something specific)
- show up consistently to the same events. regulars > tourists.
- bring something to share — a demo, a take, a skill. the scene runs on reciprocity.

**don't:**
- introduce yourself with your LinkedIn headline
- ask "so what do you do?" as an opener (ask "what are you building?" or "what are you excited about?")
- collect business cards / contacts like Pokemon. 3 real conversations > 30 handshakes.
- name-drop investors or companies you're "connected to"
- pitch people unprompted. read the room.
- wear a Patagonia vest unironically. (half-joking)

**the meta-rule:** SF's builder scene rewards people who are building things and are genuinely curious about what others are building. it punishes people who are performing. the difference is obvious and everyone can tell.

## the acceleration playbook

once you're past the first week:

### month 1: become a regular
- pick 2-3 [[events|recurring events]] and don't miss them
- get a [[spaces|coworking membership]] so you have a daily spot
- aim for 5 genuine connections (people who'd grab coffee with you again)

### month 2: contribute
- host a small dinner or working session (even 4-5 people counts)
- share your work publicly — demo at [[events|Sundays in SF]], post on Twitter/X
- start getting invited to things (this happens naturally if month 1 went well)

### month 3: you're in
- by now you should have a crew — people you see weekly, work alongside, get introduced through
- consider [[hacker-houses|hacker houses]] or [[communities|community programs]] for deeper immersion
- start introducing other people to each other. this is how you become a node.

## the resources

| what you need | where to go |
|---|---|
| a place to work | [[spaces|spaces]] |
| a place to live with builders | [[hacker-houses|hacker houses]] |
| events to attend | [[events|events & meetups]] |
| communities to join | [[communities|communities & orgs]] |
| neighborhood guide | [[vibe-guide|the vibe guide]] |

## the uncomfortable truth

SF's builder scene is genuinely welcoming to people who are building. it is not welcoming to people who are networking. the difference sounds subtle but it's everything. come with something to show, something to learn, and genuine curiosity — and the city will open up faster than you expect.

---

**2026-04-11** (from web research + personal experience): initial how-to guide. the first-week playbook is: Commons membership → Sundays in SF → AI Tinkerers → Frontier Tower event → apply to SPC if exploring. the anti-cringe advice is real and important.