Guide
How to find a co-founder, and what to look for
Finding a co-founder is a hiring decision you make with almost no data. Here is how to run the search deliberately instead of waiting for luck.
A co-founder is the highest-stakes relationship in an early company and the one people put the least process into. Most co-founder pairs form by accident — a friend, a classmate, whoever was nearby. Sometimes that works. More often it produces a partnership that is hard to change later because nobody ever said out loud what they expected.
You can do better by treating it as a real search.
Know what gap you are filling
"I need a technical co-founder" is usually too vague. Be specific about what the first 12 months actually require:
- Is the risk mostly building the product, finding customers, or understanding the domain?
- What can you do yourself well enough for now, and what genuinely blocks you?
- What do you want to still be doing in three years — and what are you hoping to hand off?
A co-founder should cover a gap that is real, near-term, and one you cannot cheaply close another way.
Where to actually look
The people worth co-founding with are usually already building something. That means the search is less about posting an ad and more about being where the work is visible:
- Communities organised around projects. Somewhere you can see what people build and how they think — a member directory with real skills and a feed of work in progress beats a list of titles.
- Collaborations before commitment. Contribute to someone's open project, or invite someone into yours. A month of real work tells you more than ten coffees.
- Your own past. Former colleagues and collaborators are a strong pool precisely because you already have shared-work data.
On FoundBrew, this is the default motion: people post what they are building and the roles they need, and others join based on fit rather than a pitch.
What to look for
- Shared standards, different strengths. You want overlap on how good is good enough and how you treat people, and difference on skills.
- Behaviour under friction. How do they act when something breaks or you disagree? Manufacture a small version of this before you commit — build something together with a deadline.
- Independent motivation. They should want this even if you were not involved. Borrowed conviction does not survive the first hard quarter.
- Willingness to make it explicit. Someone who will happily talk through equity, roles, decision-making, and what happens if one of you leaves is showing you they can do the hard conversations.
Before you commit
Write down, together: what each person owns, how equity vests, how you will make decisions when you disagree, and what the exit looks like if one of you wants out. Founder vesting with a cliff protects both of you. This is not pessimism; it is the same instinct that makes you back up your code.