Networking in SF

Pull up luma.com/sf on a random Sunday in late July and this is what’s on: a founder gala at Frontier Tower, a robotics meetup in Yerba Buena, two hackathons, a late-night builders cafe in the Mission — and roughly half of them already waitlisted. That density is the promise. Alex Finn posted that he had dinner with Naval Ravikant in his first two days living in the city, and that six months of SF beat nine years of New York. Clara Gold’s six-month report went the other way: the best place on earth to build, one of the worst to stay fully human, and the only events that were worth it were small curated dinners.

Both are right, which is the point of this page. Networking here is not one activity. It is six or seven distinct channels, each with its own rules and its own failure mode. Pick two or three and go deep.

The map

Channel	What it is	Cost	How you get in
Luma host calendars	The rail almost every SF tech event runs on	Free	Subscribe to hosts; many events take a short application
Hackathons	Weekend builds, AI-heavy, nearly every week	Free	Apply via Cerebral Valley or AI Tinkerers listings
Coffee walks	The SF default first 1:1	Free	You suggest it
Cold DMs on X	The channel that works here and almost nowhere else	Free	Etiquette below
Curated dinners	8–12 people, the highest-density format	Usually free (host or sponsor pays); hosting budgets on page 21	Get invited once, then volunteer, then host (see page 21)
Recurring communities	Same faces weekly — run clubs, demo nights, desi groups	Mostly free	Show up three weeks in a row
Frontier Tower	16-floor deep-tech hub at 995 Market, 3+ events a day by its own count	$190/mo or $1,800/yr "citizenship"	Application at frontiertower.io
SHACK15	Founder social club upstairs in the Ferry Building	~$2,000/yr as last reported	Member referral to apply; or a member's guest invite

Nothing on this list checks your credit score, your SSN, or your visa class. Housing and banking will make you feel like you arrived yesterday; the networking layer runs at full speed from day one, and your first 90 days should lean on it hard.

Which two or three channels depends on what you’re short of. Short of customers: X plus the hackathons and demo nights where your users already gather — the demo is the pitch. Short of investors: curated dinners and the warm rooms, and read the polite-no table on the culture page (19) before your first meeting rather than after. Short of peers or a co-founder: recurring communities and hackathons, where shared work does the filtering for you. Short of a job — the operator’s case, covered below — coffee walks and communities of practice, because hiring here moves through the dinner-and-group-chat graph long before it reaches a listing.

Events: Luma is the rail

Jargon: Luma — the event platform (luma.com) that almost every SF tech event runs on. RSVPs, waitlists, and host calendars all live there.

Most SF events never surface on Luma’s public discover page — by some counts the large majority are unlisted and only visible if you follow the host’s calendar. So don’t browse; subscribe to 10–15 host calendars (see our Live Events Calendar page) and let events come to you. Partiful is the second layer — house parties and socials rather than talks — and note it genuinely gates on a US phone number, so sort your eSIM first (see the apps page).

Filter hard. The test for a good event: a named host with a track record, a specific topic, and an application or capped guest list. Red flags: “networking mixer” with no agenda, open bar as the headline, 500+ RSVPs. The city runs a permanent circuit of ticketed mega-mixers that fail every part of that test — they are theater, and I think the kindest thing this guide can do is tell you to skip them entirely. One or two high-value events a week beats five random ones. You are optimizing for repeat encounters with the same people, not raw contact volume.

Many SF events now ask for your LinkedIn or a short application before approving you. Fill these out properly — hosts curate the room, and a blank profile gets rejected. The waitlists you’ll see on half the good listings are the same mechanism: apply the day the event posts, not the day before it happens.

The annual anchor is SF Tech Week (Oct 5–11, 2026, run by a16z). The public calendar is maybe half of what’s happening that week — the value is in unlisted side dinners, and you get into those by asking the hosts of the small events you did attend.

The other half of the hidden graph is group chats — the WhatsApp and Discord threads where hosts drop events before they’re listed and intros get traded in real time. There is no application form for these; you get added by someone who has seen you twice, which is the repeat-encounters thesis converting into infrastructure. Once you have that context, ask for the add explicitly — “is there a group where this crew coordinates?” is a normal question here, not a presumptuous one.

Hackathons: the fastest way in for technical founders

SF runs weekend hackathons nearly every week — AI agents, voice, bio x AI, robotics. Cerebral Valley and AI Tinkerers are the two rails to watch. A hackathon compresses six months of networking into 48 hours: you build alongside people, and shared work creates real trust in a way small talk never does. Demo something, even if it’s rough — the demo is the networking.

Coffee walks

The SF default for a first 1:1 is not a conference room; it’s a 30–45 minute walk with coffee. Suggest it explicitly: “Want to do a coffee walk near [neighborhood]?” It lowers the stakes, and walking side-by-side makes candid conversation easier than sitting across a table. On volume: Catarina Chia’s 50-plus coffee chats over her first months (field notes below) work out to three or four a week — I’d treat that as the ceiling, not the target, if you’re also running a company. Two or three, each ending with a concrete next step or an intro you owe, compounds fine.

Cold DMs on X

Cold DMs work in SF in a way they don’t in most cities — but only done right. The etiquette, per people who receive hundreds of them:

Do	Don't
Engage with their posts for a week first	DM out of nowhere with "can we hop on a call"
Keep it under ~70 words, one clear ask	Send your deck in message one
Make a small, specific ask ("does X apply to Y?")	Ask for 30 minutes of their time
One follow-up after 48 hours, then stop	Bump three times

Asking for a call is a big ask; asking a sharp, specific question is a small one. Start small. One founder’s claim — that Twitter is the best way to tap into the tech SF network, arguably more than being here — overstates it only slightly. The DM channel compounds with the public one: post a demo, a teardown, a real number, and the replies start flowing toward you instead.

Dinners, and hosting before you feel ready

An 8-person curated dinner produces more real relationships than a 200-person mixer. And there’s a rung below hosting that costs nothing: volunteer. Most SF events run understaffed — message the organizer on the Luma page and offer to work check-in or take photos, and you’ve upgraded yourself from attendee to team, with a reason to talk to everyone who walks in. Thank the organizers on your way out regardless; they’re the best-connected and least-thanked people in the room, and helpers get invited back, sometimes onto the stage. Once you’ve met people you like, host one yourself — it’s the strongest networking move available to a newcomer, and you don’t need to feel established to do it. One hack from a serial dinner host: go around the table and have each person introduce the person to their left, not themselves. Everyone has to have one real conversation before dinner starts, and nobody gets to recite their pitch. Venues, budgets, and the sponsor model are on the Where to Host Events page (21).

Recurring communities, and the rooms with doors

Relationships compound with frequency. A weekly community — same faces every week — builds trust far faster than a monthly one. When choosing between two groups, pick the one with weekly cadence. The desi founder communities (TiE SV, FUNDA, SaaSBoomi US and the rest) are mapped with entry paths on the Desi Directory (16); pick one anchor there, then make sure at least half your meetings by month three are outside it — the reasoning is on the culture page (19).

Two physical rooms are worth knowing about specifically. Frontier Tower (995 Market St) has become the gravitational center of the deep-tech scene: sixteen themed floors, event venues on floors 2 and 16, and a calendar that runs multiple events a day, many open to non-members via Luma. Membership — they call it citizenship — is $190/month or $1,800/year, by application. You do not need to join to benefit; following its open events calendar for a month is the cheap way to find out whether you’d use it. SHACK15, upstairs in the Ferry Building, is the softer-edged founder club — coworking with bay views by day, AI events and dinners by night. It’s referral-gated: a member nominates you, and membership last reported around $2,000/year. The honest path in as a newcomer is a member’s guest invite or one of its ticketed public events, not the application form. Neither room is necessary; both are shortcuts to density if the free channels are already working for you.

Sports and wellness

A large share of SF networking happens in workout clothes. Founders Running Club meets Saturdays in the Panhandle — casual pace groups, walkers welcome, coffee after. Run clubs, pickleball, South Bay cricket leagues (see the Weekends page), and cold plunges all function as networking with the pitch pressure removed. Show up three weeks in a row and you have a network.

If you’re an operator, not a founder

Half this guide’s readers are operators, and the channels reweight for you. “What are you building?” still opens every conversation — have an answer about your craft or the problem you own, because “I work at X” ends conversations here in a way it doesn’t in Bangalore. Recurring communities and coffee walks move up your list: hiring in this city runs through the dinner-and-group-chat graph, and the person who pulls you into your next role will be someone who has watched you think out loud three times, not a recruiter. Hackathons still work if you’re technical — shipping something on a weekend is the fastest way to become legible to the founders who are hiring. [decision before lock: The Product Folks is exactly this kind of operator community and it’s ours — include here with a disclosure line, route through the Desi Directory (16), or leave out?]

If you live in the South Bay

Half this guide’s housing and grocery pages assume you might land in Sunnyvale, Fremont or Milpitas — cheaper, closer to the desi infrastructure, kinder to families. The networking maths runs the other way. The founder scene has re-concentrated hard in SF proper: on the Luma pull that opened this page, nearly every listing sat in the Mission, SoMa, Yerba Buena or Dogpatch; Palo Alto and Stanford had one event each. What’s local to you is the thinner, older layer: TiE SV in Santa Clara, the cricket and run circuits on the Weekends page, corporate-adjacent meetups. Catarina Chia’s arc in the field notes below is the honest template: she treated the Santa Clara commute as the price of the SF graph and paid it deliberately. I’d recommend the same structure — one protected SF evening a week, planned around the train (see Getting Around, 11), plus one local anchor with weekly cadence — rather than pretending the two scenes are interchangeable. They aren’t.

The corridor twist: your evenings are India’s mornings

SF events run 6–9pm, which is 6:30–9:30am IST the next day — exactly when your Bangalore team wakes up and your standup wants you. This collision is where corridor networking runs aground: people quietly stop showing up by month two. Solve it structurally, not nightly: pick two protected event evenings a week and tell your India team those are immovable, and move recurring India syncs to your early morning, which is their evening. And spend your first-month advantage while you have it — “I just moved to SF” is the best cold-outreach line you’ll ever hold, and it expires (see the Week 1 page).

The two rules that govern everything

Don’t pitch first. The give-first norm is real here: lead with curiosity or a useful offer, and let the other person ask what you’re building. Pitching in the first five minutes marks you as a taker. The full translation of this — and how to read the polite American no — is on the culture page (19).

The 24-hour rule. Follow up within 24 hours of meeting someone, while they still remember you. Reference something specific from the conversation and, ideally, include something useful — a link, an intro offer. No generic “great to meet you.” And past the first dozen people, memory stops scaling: a plain spreadsheet of who, where, and what you owe them beats every networking app.

The one-line version of both, from conor brennan-burke: “let the personal drive the professional” — trust is the only scarce resource here, and it doesn’t accrue to people who treat every conversation as pipeline.

Field notes from the timeline

The scene documents itself on X, and the reports agree with each other more than you’d expect. Catarina Chia’s ten-month arc is the fullest worked example: 30-plus events and 50-plus coffee chats stacked on a Santa Clara commute, her own game night hosted early instead of waiting for invites, and by the end of it a City Hall meeting with the mayor — attend, then host, then get pulled upward. The standing joke — alli’s “is this a networking chat or a date?” — survives because the city can’t tell, and Marijana’s corollary holds: everything in SF eventually becomes a networking event, Giants games, saunas, hot tubs and gym floors included. Miranda Nover’s version of the compliment is that networking here opens with what you’re building, where New York opens with who you know.

The counter-position deserves airtime too, because serious builders hold it. Harald Schäfer thinks the circuit is mostly hype — put your head down and build. Will Henry’s framing is that New York founders network half the week while SF founders disappear and ship. They’re not entirely wrong, and this page is built to survive their critique: one or two events a week, protected shipping time, and the demo as the best networking there is.

[placeholder — Shonik/Suhas lived-experience anecdotes to add before content lock]

One caveat this page owes you: the venue layer churns fast. Frontier Tower is barely a year and a half old; South Park, the original startup quad, is down to its last operating restaurant as of this month even as VC offices move back in. Trust the channels on this page longer than the addresses, and check the date stamp at the top before you cross town on our word.

Do this now

• ☐ Subscribe to 10 Luma host calendars from our Events Calendar page
• ☐ Pick your 1–2 events for this week; apply/RSVP today — the good ones waitlist
• ☐ Register for one hackathon in the next 30 days via Cerebral Valley or AI Tinkerers
• ☐ Show up to Founders Running Club this Saturday
• ☐ Draft your 70-word cold DM template and send three this week
• ☐ Block your two protected event evenings and move India syncs off them
• ☐ South Bay-based? Block one SF evening a week around the train and pick one local anchor
• ☐ Set a recurring 15-minute daily slot for 24-hour follow-ups

Nobody tells you

• Most SF events are hidden from Luma’s discover page — the real event graph lives in host calendars and group chats, which is why following hosts beats browsing.
• Application-gated events are a feature, not friction: the host is curating who’s in the room, which is exactly why the room is worth being in.
• The people you meet twice matter far more than the people you meet once. Optimizing for repeat encounters — weekly clubs, recurring series — beats maximizing new contacts.
• None of this asks for an SSN, a credit file, or a visa category. Networking is the one system in this city that works for you at full speed from the day you land — front-load it while the bureaucratic systems catch up.
• Partiful gates on a US phone number and Luma fills by application, so the $20 eSIM and a filled-out LinkedIn are, weirdly, networking infrastructure.