Why specificity matters in a co-founder search
When you start looking for a co-founder, one of the first questions is how narrow to make your search.
Ask for too little and you will wade through endless mismatched conversations.
Ask for too much and you may filter out someone who would have been a great partner.
This guide gives you a practical way to decide which preferences to hold firm, which to keep flexible, and how to write a search brief that attracts the right people.
A co-founder is one of the most consequential decisions in a startup.
Y Combinator notes that building with a co-founder helps productivity and morale, and that only a small share of its top companies came to YC without one.
Finding a committed co-founder is genuinely difficult.
So YC built a matching platform where founders state their interests, location, and skills preferences Y Combinator co-founder matching.
Because the stakes are high, vague searches waste months.
'Someone technical who gets it' is not a search criterion.
But an over-specified wish list, such as a specific former employer, a specific framework, and a specific neighborhood, can hide good matches behind arbitrary filters.
The goal is calibrated specificity: precise where it truly matters, loose where it does not.
The three layers of co-founder preferences
A useful way to think about your criteria is to sort them into three layers.
- Commitment layer. How much time will they invest, are they ready to go full-time eventually, and how do they handle risk? YC encourages matched founders to work together on a time-boxed trial project with clear expectations before committing, precisely because one video call is not enough to judge this YC's guidance on trial projects.
- Complement layer. Which skills and role coverage do you actually need? If you build product, you may need someone who sells or who handles the technical side. This layer is about gaps, not clones.
- Preference layer. Location, industry interests, working style, age, background, and similar. These matter, but most are more flexible than founders initially assume.
Most over-specific searches happen in the third layer.