How to Find a Cofounder (and Know if They're the Right One)
How to find a cofounder: decide if you need one, where to look, how to test working together, and what to agree on equity, roles and vesting first.
Mythex Team · · 6 min read
To find a cofounder, start with people you have already worked with, then widen to communities where people who build things in your field spend time. Before you commit, work together on a real, time-boxed project, talk openly about money, goals and roles, and put equity under a written vesting agreement. The right cofounder is someone whose skills fill your gaps and who you can disagree with productively.
A cofounder is one of the biggest decisions you'll make for a company, and one of the hardest to undo. It's worth going slower than feels comfortable.
First: do you actually need one?
Many companies are started by solo founders, and many are started by teams. Neither is automatically right. Ask what you need a cofounder for.
| Good reasons | Weak reasons |
|---|---|
| The work needs a skill you don't have and can't reasonably learn or buy | You feel lonely or want reassurance |
| You want someone to share decisions and risk long term | You want free labour |
| The investors you plan to approach usually expect a team | Someone was enthusiastic when you described the idea |
| The workload is genuinely more than one person | Everyone says you should have one |
If your gap is a specific task — a logo, a landing page, a first prototype — a freelancer, an adviser or a tool may cover it. Today a non-technical founder can often build and test a first version with an AI app builder, which changes the old "find a technical cofounder first" advice. See hire a developer or build with AI for how to weigh that.
What to look for
Complementary skills
The classic pairing is one person who builds and one who sells, but the principle is broader: between you, you should cover building the product, reaching customers, and running the business. Two people with the same skills often end up doing the same half of the work.
Shared values, not shared personality
You don't need to be alike. You do need to agree on things that are hard to change later:
- Ambition: a sustainable small business, or a shot at something large?
- Money: how long can each of you go without a salary?
- Funding: bootstrap or raise? (See bootstrapping vs venture capital.)
- Time: full-time now, full-time later, or side project?
- Ethics: what you would and wouldn't do to win a customer.
Evidence of follow-through
Look at what the person has finished: a product, a side project, a team they led, a hard job they stuck with. Past behaviour is better evidence than enthusiasm in a first meeting.
Where to look
Roughly in order of how much trust you start with:
- People you have worked with. Former colleagues, classmates, collaborators on open-source or side projects. You already know how they behave under pressure.
- Second-degree connections. Ask people you trust: "Who is the best [engineer / salesperson / operator] you've worked with who might want to start something?" Specific asks get better answers than "know anyone?".
- Communities in your field. Industry groups, meetups, online forums and Discord or Slack communities where people who do the work spend time. Contribute first; don't open with a pitch.
- Cofounder-matching platforms and programs. Some accelerators and startup communities run matching services. They're useful for meeting people, but you start with zero shared history, so the trial period matters more.
- Hackathons and build weekends. A compressed way to see how someone works, communicates and handles a deadline.
A useful habit: talk publicly about what you're building. A short post describing the problem you're working on and the kind of partner you want attracts people who care about that problem.
How to test working together
Don't decide over coffee. Decide after building something.
Run a trial project
Pick a piece of real work you can finish in two to six weeks: a set of customer interviews, a landing page and waitlist, a clickable prototype. Agree up front that no equity is promised until the end. Watch for:
- Do they do what they said, when they said?
- How do they react when the plan changes or something fails?
- Can you disagree and reach a decision without resentment?
- Do you both come out of a work session with more energy, or less?
Have the hard conversations early
Use this list as an agenda. If a topic feels too awkward to raise now, it will be much worse later.
- What does each of us need to earn, and when?
- What happens if one of us wants to leave?
- Who has the final say on product? On hiring? On money?
- What does success look like in three years for each of us?
- How many hours a week can each of us commit, honestly?
- What would make you want to shut the company down?
Check references
Ask to speak with two or three people they have worked with closely. Ask specific questions: "How did they handle a missed deadline?" "Would you start a company with them?"
Agree on equity, roles and vesting
Write these down before either of you puts in serious time. This is general guidance, not legal advice — rules differ by country, so have a lawyer draft the actual documents.
Equity
There is no correct split. Common considerations:
- Future contribution matters more than the idea. Most of the work is still ahead.
- Full-time vs part-time. Someone keeping a day job is taking less risk.
- Cash and assets. If one founder puts in money, that can be treated as an investment instead of affecting the founder split.
Whatever you choose, both people should be able to explain why it feels fair.
Vesting
Vesting means founders earn their shares over time instead of receiving them all at once. A common structure is four years with a one-year "cliff": nothing vests if someone leaves in the first year, then shares vest gradually. Vesting protects both of you — if a cofounder leaves after three months, they don't walk away with half the company.
Roles and decisions
Write down who owns which areas (for example, product and engineering vs sales and operations) and how you'll break a deadlock. Titles matter less than clarity about who decides.
A founder agreement checklist
- Equity split and vesting schedule
- Who owns the code, designs and brand (assigned to the company, not individuals)
- Roles and decision rights
- Time commitment and salary expectations
- What happens if a founder leaves, is removed, or stops contributing
- How you'll resolve disagreements
Red flags
- They want significant equity before doing any work.
- They won't discuss money, commitment or what happens if things go wrong.
- They're between jobs and clearly looking for a salary more than a company.
- They talk about the idea but haven't talked to any customers.
- Your gut says no and you're overriding it because you want a partner badly.
If you don't find one yet
Keep going on your own. Validating the idea and getting early users makes you far more attractive to a potential cofounder — people are more willing to join something that is already moving. How to validate an app idea and how to get your first 100 customers are good next steps.
Building a first version before you find a partner
If the missing skill is building software, you may be able to get quite far alone. With Mythex, you describe the app in chat and an AI agent builds a working web app with a database and a public link, so you can put something real in front of customers — and in front of potential cofounders. It's free to start; the quickstart shows the first steps. A working prototype also makes the trial project concrete: you can see how a potential partner improves on something that already exists.
Questions
Where is the best place to find a cofounder?
Usually your existing network: former colleagues, classmates and people you have already built something with. Cofounder-matching sites, local startup events and online communities in your field help too, but a stranger needs a longer trial period before you commit.
Do I need a technical cofounder to build an app?
Not always. AI app builders and no-code tools let a non-technical founder build and test a first version alone. A technical cofounder matters more once the product is complex, needs to scale, or when investors expect one.
How should cofounders split equity?
There is no single right split. Base it on expected future contribution, not just who had the idea, and put it under a vesting schedule so someone who leaves early doesn't keep a large share. Get the agreement written up with a lawyer.
How long should I work with someone before making them a cofounder?
Long enough to see them handle a real setback. Many founders work on a small, time-boxed project together for several weeks first, with no equity promised until both are sure.