How to find a co-founder, also a technical one

To find a co-founder is to find the one person who fills the gap your start-up cannot close otherwise and carries the risk with you for years. Most founders search too vaguely and too locally. This guide shows how to write the brief, where the right people are, how to test a match, and what to agree first.

Why is it so hard to find a co-founder?

Two reasons. The first is supply: fewer people than you think want to co-found rather than join a funded company as an early employee. Among new start-ups, about a third now start solo, according to Carta's Solo Founders Report, and part of that is founders who looked and did not find. The second is matching: the people you know are usually like you. A business founder's network is full of business people, and the technical co-founder they need is in rooms they never enter.

The search is also hard because the stakes are high. A co-founder shares equity, decisions and years. Founders know that, so they hesitate, and the hesitation costs months. The way out is a process: a clear brief, many conversations, a real test, and a clear deal.

How do you write the brief?

Before you look anywhere, write one page. If you have not decided yet whether you need a co-founder at all, our guide do you need a co-founder comes first. The brief holds:

• The gap. What the company needs that you cannot do or buy: build the product, sell to hospitals, run operations. Name the role, not a personality.
• The venture. The problem, who has it, what exists so far: customers, a prototype, a waiting list, nothing yet. Honest is better than impressive.
• The commitment. How much time you give, from when you are full-time, how long you can go without salary.
• The offer. The equity range you have in mind, whether a salary is possible and when, and that vesting applies to everyone, including you.
• The must-haves. The few things that are not negotiable: a location, a skill, full-time from a date.

This brief is what you tell people at events, give to incubators and university programmes that bring founders and co-founders together, and publish in a co-founder search. It lets the right person recognise themselves, and it saves you weeks of conversations with the wrong ones.

Where are the people you look for?

Look where the people with the missing skill already build and meet, and where people deliberately look for a founding team.

• Your own network, one step out. Not your friends, but their colleagues: ask ten people for the one person they would start a company with. Warm introductions still produce most founding teams.
• Programmes. Incubators, accelerators and university spin-off programmes bring founders together on purpose. Entrepreneur First and Antler match individuals into teams before there is an idea; many regional incubators run co-founder events and keep lists of people who want to join a team.
• Communities of builders. Hackathons, developer meetups, open-source projects, AI and maker communities, university labs. A technical co-founder is there as a builder first, and that is how you meet them.
• Your industry. The best co-founder for a health start-up may be a nurse who is tired of the problem, not a developer. Look among the people who feel the pain.

Go wide first. Talking to twenty people to find one is normal.

How do you find a technical co-founder in particular?

A technical co-founder wants three things: a real problem, a partner who can sell and a fair deal. Most pitches offer the opposite: a finished idea, a request to "just build it", and a vague promise of equity.

So show the problem, not the solution. Bring evidence: customer interviews, a waiting list, a letter of intent, your own domain knowledge. Show what you will do that they cannot: sell, raise, run the business, know the market. And make the deal clear from the start. A technical co-founder who builds the product for a year is a co-founder, with a share that reflects that, and with vesting that protects both of you. If the first question from your side is "how little equity would you take", you will meet the wrong people.

Be ready to be tested too. Good technical people check whether you can get customers before they commit. Having talked to fifty potential customers, as the pre-seed guides of investors such as Unusual Ventures recommend, is the best thing you can bring to that conversation.

How do you test a match before you commit?

Conversations show intentions; work shows behaviour. Use the questions to ask a potential co-founder over two or three meetings, then run a trial project with the best candidates: two to four weeks, one real deliverable, a date and a result you can judge together.

Watch three things. Whether they do what they said. How they communicate when something is late or wrong. Whether you want to spend the next years with this person. A trial project ends either with a founder agreement or with a clean goodbye, and both are good outcomes.

What do you agree before you announce the team?

Roles, decisions, equity, vesting and the exit, in writing. Decide who has the final say on product, hiring and money, and how you resolve a tie. Split equity by contribution, with the method from our guide on how to split equity between co-founders, and tie every share to vesting with a one-year cliff. Agree what happens if one of you leaves in the first years.

Hellmann and Wasserman found that 73 percent of teams split their equity within the first month, often in one conversation. Take the conversation seriously, and the team you found will survive the first hard quarter. If you are a founder with a gap to fill, start your search on the page for founders; if you want to join a venture, the page for co-founders shows how your terms and must-haves become part of the match.