co-founder
How to Find a Co-Founder
Finding a co-founder comes down to three things: working out what you actually need from a partner, meeting enough people that you're choosing rather than settling, and testing the fit on real work before either of you commits. Most people get the first one wrong, which is usually why the rest goes sideways.
Most searches start with "I need a technical co-founder", because that's the version of the problem everyone talks about. Plenty of teams don't need one. If you can already build but nobody's using the thing, a partner who can get a stranger to pay you is worth more than a second engineer, and hiring for the wrong gap costs you months.
The other thing worth saying up front is that this is genuinely hard. Most people you meet won't be right, and the ones who are usually already have someone. That doesn't mean lowering the bar. It means looking in more places than you'd like to, and taking the early conversations more seriously than a coffee chat.
Do you actually need a technical co-founder?
Only if building the thing is the part that's stopping you. That sounds obvious, but it's the question most people skip, and so they go looking for an engineer when the business is stuck somewhere else entirely.
Work out which part is jammed. If you've got a waiting list and no product, you need someone who can build. If you've got a product and twelve users after six months, you need someone who can sell, and adding another engineer just gets you a better version of a thing nobody's bought. If you're strong on both but the numbers scare you, a co-founder with a finance or operations background is more useful than either.
There's also the option nobody mentions, which is not taking a co-founder at all. A contractor or a small agency can build a first version, and it costs money rather than half your company. That trade is worth doing the maths on: a few thousand for an MVP against 40 or 50 percent of everything you build afterwards. The case for a co-founder is that you get someone who takes the risk with you and keeps taking it at 2am in month nine, which no contractor will. Just make it a decision rather than a default.
What you're actually looking for
Complementary skills are the obvious part, and they're the easy part. The things that decide whether it works are less visible.
Firstly, do they ship. Not "are they smart", not "are they experienced": do things they say they'll do actually appear. You'll find out more from one small delivered thing than from an hour of conversation about vision.
Secondly, do they disagree well. You're going to disagree about pricing, about hiring, about when to launch, and how that goes the first three times is roughly how it'll go for the next four years. Someone who can say "I think that's wrong, and here's why" without it becoming an atmosphere is rarer than you'd expect.
Thirdly, are you in the same place on money and time. Somebody who needs a salary in four months and somebody who can go two years unpaid are running two different businesses, whatever they agree in the first meeting. This is the one that quietly kills teams, and it's easy to check early.
And underneath all of it, you want somebody you can be honest with when things are going badly, since that's most of the first two years.
Where to actually look
Roughly in order of hit rate, because the good ones are almost never the ones that scale.
People you've already worked with. Old colleagues, people from a previous startup, whoever you did that side project with in 2023. You already know how they work under pressure, which is the expensive thing to find out. Go through your last three jobs properly, name by name, before you do anything else. Most people skip this because it feels too easy.
Communities where people build in public. Indie Hackers, domain-specific Discord and Slack groups, local founder meetups, hackathons. The move here is to be visible doing the work rather than to post "looking for a technical co-founder", which reads as an ask with nothing behind it. Someone who's watched you ship three things is a completely different conversation from a stranger.
Co-founder matching platforms, including PartnerUp. These are how you meet people outside your existing circle, which matters if your network is all in one industry or one city. Treat the introduction as the start of the process, not the end of it.
Hackathons and short collaborations. A weekend of building with someone tells you more than a month of messaging. It's a low-cost way to run the test in the next section without anybody having to call it a test.
One thing to watch for: the person who's enthusiastic in every conversation and unavailable every time there's work to do. They're common, they're pleasant, and they'll cost you two months if you're not paying attention to the gap between what gets said and what gets done.
How do you test the fit before committing?
Do a real piece of work together, with a scope and a deadline, before anyone signs anything. Two to four weeks is usually enough.
Pick something small and genuinely useful: ship a landing page and get 50 people on a waiting list, build one working feature, run 20 customer conversations and write up what came back. It needs a clear finish line, otherwise you both drift and learn nothing. Agree who's doing what and when it's due, in writing, even though it'll feel excessive for a two week project.
Then watch what happens rather than how it feels. Did the work arrive when they said it would? When something slipped, did you hear about it early or find out on the deadline? Did they push back on anything, or agree with everything you suggested? Constant agreement is usually a bad sign, it typically means they're being polite rather than invested.
For example, if you agree they'll have a working prototype by Friday and on Thursday they tell you it'll be Monday because the payment provider's sandbox is broken, that's a good outcome. You got told early, with a reason, and you can plan. The same slip discovered on Friday night with no message is the same delay and a completely different signal.
Expect this to be awkward to propose. It can feel like you're auditioning somebody you already like. But a fortnight of real work is a much cheaper way to find out than eleven months and a lawyer, and anyone worth building with will understand exactly why you're asking.
The conversations to have before you commit
Have these before the equity conversation, since the answers change what a fair split even looks like.
Money. How long can each of you personally go without income? Be specific, in months. If you don't know what the company's runway looks like either, the runway calculator works it out from your cash and monthly burn, and it's free to use.
Time. Who's full time, and when? "As soon as we raise" is a plan, but it's worth knowing whether that means three months or a year, and what happens if the raise doesn't land.
Decisions. Who decides when you can't agree? Splitting the company 50/50 with no tiebreak sounds fair right up until the first real disagreement, at which point you find out there's no way to resolve it.
Leaving. What happens if one of you walks in month eight? This is the conversation people most want to skip, and it's the one that determines whether a bad month becomes a dead company.
If somebody won't have these conversations before you start, that's your answer. Not because they're a bad person, but because you've just learned they avoid difficult subjects, and there are a lot of difficult subjects ahead.
What to put in writing
Once you've decided, write it down while everybody still likes each other. A founders agreement covering the equity split, vesting, roles, decision-making and what happens when someone leaves is a couple of pages, and it's the difference between a bad situation and an expensive one.
Two pieces of it are worth reading about properly. How you divide ownership is covered in how to split equity between co-founders, including why an even split isn't automatic. And every founder's shares should be on a schedule, which is what founder vesting explained goes through: four years with a one year cliff is the standard, and it means a co-founder who leaves in month eleven walks away with nothing rather than a quarter of your company.
Yes, it's paperwork, and yes it feels premature when there's nothing to divide yet. That's exactly why it's the right time. Nobody's fighting over a company worth nothing, and the agreement you write now is the one you'll be glad of later.
Give it the time it deserves
Founders spend nine months choosing a co-founder far less often than they spend nine months regretting one. It's closer to hiring than to dating, and it's the highest-stakes decision in the early life of a company, so it's worth being slow and a bit awkward about.
If you'd like to meet people who take building as seriously as you do, that's exactly who PartnerUp is for.
Frequently asked questions
- How do you find a co-founder if you have no network?
- Start by building in public somewhere people can see the work, whether that's a community for your domain, a hackathon, or posting what you're making. People who've watched you ship something are far easier to approach than strangers. Co-founder matching platforms are worth using too, but treat them as a way to meet people rather than a shortcut past getting to know them.
- Do you need a technical co-founder?
- Only if building the thing is what's actually stopping you. If you can build but nobody's using it, distribution is the gap and a second engineer won't fix it. Work out which part of the business is stuck before you decide what kind of person you're looking for.
- How long should you work with someone before making them a co-founder?
- Long enough to see them deliver something real, which usually means a few weeks on a defined piece of work with a deadline. You're looking for whether they do what they said by when they said, and how they handle it when you disagree.
- What should you agree with a co-founder before starting?
- Money, time, equity, and what happens if one of you leaves. Agree how much runway each of you has personally, when each of you goes full time, how the equity splits and vests, and who decides what when you disagree. Put it in a founders agreement before there's anything valuable to argue over.