If you are moving to San Francisco to find a technical co-founder, you are doing the right thing. The density is real. But the advice you will read is mostly "go to events and be interesting", which is not a plan.
This is a more useful version, including where we fit and where we do not.
Start with the uncomfortable part
A co-founder is not a hire and not a friend. You are asking somebody to give up a salary and several years for equity in something that does not work yet. People do not agree to that after one coffee.
In practice a real co-founder relationship comes from one of three places.
- Someone you have already worked with. Fastest and most common. Go through your last three jobs before you go anywhere else.
- Someone you build something small with first. A weekend project, a contract, a hackathon. You learn more in two weeks of shipping together than in twenty coffees.
- Someone you are around often enough that trust builds without a meeting. This is the one a house can help with, and it is the slowest to start and the most durable once it does.
Everything below is about the third route, because that is the one geography changes.
Why proximity works better than events
At an event you get twenty minutes with somebody performing their best self. You both leave with a LinkedIn connection and no information.
Living near people gives you the opposite: low intensity, high frequency, unguarded. You see how somebody reacts when a launch goes badly. You see whether they ship on a Sunday or talk about shipping. That is the actual data you need about a co-founder, and there is no way to get it in an hour.
One of our residents put it this way:
"The residents were all cracked and at various different stages in their startup careers. I can honestly say I made friends for life in this house and the atmosphere is very social."
Dillon Roberts, building an AI native law firm at Alaro
Note what that says and does not say. It says friends and social. It does not say he found a co-founder, and we are not going to imply that he did.
What we can and cannot tell you
Being direct, because this is the part that decides whether we are useful to you.
What is true: we run four houses with 47 rooms between them, and residents are solo founders, co-founders, technical builders, designers and operators at startup stage companies. There is a dinner every week, a mastermind every two weeks, and investor dinners every two weeks. Residents host their own events too.
What we do not track: whether anyone has found a co-founder here. We have not measured it in a way we would be willing to publish, so we are not going to claim it. If a house tells you it produces co-founders, ask for two names and a date.
What changes weekly: how many current residents are technical and how many are actually looking. That is the number you need and it cannot live on a web page without going stale. Ask on a tour, for the specific house, and ask to speak to a resident with nobody from the company on the call.
The turnover problem, honestly
Our minimum stay is one month. That is flexibility when you are the one arriving and churn when you are the one staying. Some of the people you meet in week one will be gone by week six.
For finding a co-founder that cuts both ways. You meet far more people than you would in a normal lease, which raises your chances of meeting the right one. You also get less time with each, which means you have to move faster from meeting somebody to building something with them.
The practical response is to stop waiting. If somebody interesting arrives, propose a weekend project in the first fortnight rather than the first quarter.
A plan for your first 90 days
If you are landing soon, this is a schedule that works.
- Weeks 1 to 2. Do not pitch anyone. Meet everyone in the house, learn what they are building, and be useful to two of them. Reputation inside a house travels in days.
- Weeks 3 to 6. Run a small project with one or two people you like working near. A weekend build, not a company. You are testing how they work, and they are testing you.
- Weeks 6 to 10. Have the direct conversation with anyone the project went well with. Equity, time, money, and what happens if it does not work. If that conversation is awkward now, it will be worse in a year.
- Weeks 10 to 13. Decide. If nobody in your immediate circle is right, widen out: their friends, the mastermind, the events you have now been to often enough to be a known face at.
Ninety days is enough to know. It is not enough if you spend the first sixty being polite.
What to actually look for
People optimise for skill and end up with a stranger who codes. The things that break founding teams are not technical.
- Do they ship when nobody is watching? You can only see this over weeks.
- How do they behave when something fails? Also only visible over weeks, which is the argument for proximity.
- Do you disagree well? Have one real disagreement on purpose before you commit.
- Do they want the same size of outcome? A lifestyle business and a venture attempt need different people.
- Can they afford the next 18 months? Unromantic and the most common quiet reason a co-founder leaves.
Where a house does not help
- If you need a specialist. A house of a dozen people will not contain the one ML researcher you need. Go to the research groups.
- If you are not building yet. Proximity converts a project into a partner. With no project you are just at dinner.
- If you want it fast. Trust from proximity takes weeks. If you need somebody next Monday, hire a contractor.
The short version
Check your own history first. Then put yourself somewhere you see the same builders often, build something small with them quickly, and have the hard conversation early. A coliving house helps with the seeing-often part and nothing else, which is genuinely useful and is not the same as being introduced to a co-founder.
If you want to see whether ours is that kind of room, look at the four houses, check the pricing, and book a tour. Ask who is technical, ask who is looking, and ask to talk to a resident directly.
