Questions to ask a potential co-founder before you commit

A potential co-founder is someone you might build a company with for the next ten years, and the questions you ask before you commit are the cheapest test you will ever run. This guide lists the ones that matter, the answers that should worry you, and how a short trial project turns good conversations into a real decision.

Why ask before you commit?

Choosing a co-founder is closer to a marriage than to a hire. You share ownership, risk and most of your waking hours, and you cannot simply give notice when it does not work. Noam Wasserman, who studied thousands of start-ups for his book The Founder's Dilemmas, found that most failures of promising companies trace back to people problems inside the founding team, not to the market or the product. His article on the founder's dilemma shows how often those problems were visible from the start and simply never discussed.

The good news is that the conversation is cheap. A few hours of honest questions cost nothing, while a split after a year costs the company, the friendship and often the idea. There are long question lists for this, such as First Round's 50 questions for co-founders or the Founder Institute's 34 questions. You do not need all of them. You need the hard ones, in the right order.

What should you ask about motivation and goals?

Start with why. Why do they want to found a company, and why now? What does success look like in five years: a company they run for life, a sale, or a technology they want in the world? Would they take venture money, with the growth pressure that comes with it, or do they want a smaller business that pays its people well?

These answers do not have to be identical, but they have to be compatible. One founder who wants to sell in three years and one who wants to build for twenty will fight over every decision that touches growth, hiring and funding. Ask also what they would do if this company fails. Someone with a plan B is not less committed; someone who has never thought about it has not understood the risk.

A question that reveals a lot: what have you failed at, and what did you learn? Everyone who has built something has failed at parts of it. A person who cannot name a failure either has not tried much or does not reflect, and both get hard under pressure.

What should a potential co-founder say about time and money?

Be concrete. How many hours a week can they give now, and from when could they go full-time? What has to be true before that: a savings cushion, a partner's agreement, the end of a notice period? How long can they work without a salary, in months, not in feelings?

Founding is a full-time job sooner than most people expect. In a survey of 128 pre-seed to Series A founders, Antler found that 75 percent work 60 hours a week or more. A potential co-founder who plans to keep a job for a year is not a bad choice, but the plan has to be explicit, and it has to show in the equity.

Money questions are uncomfortable and necessary. Will each of you put in money, and how much? What happens if the company needs more and only one of you can pay? What salary do you each need, and when? Someone who avoids these questions now will avoid them when the bank account is empty.

How do you talk about roles, decisions and equity?

Roles first. Who does what, and where do your skills overlap enough to cause friction? Two people who both want to own the product will argue every week. Decide who has the final say on product, on hiring and on spending, and how you will decide when you disagree. Many teams agree on one CEO and a rule for ties, for example an advisor both trust.

Then equity. How should you split it, and why? The answer tells you how the other person values contributions, risk and their own role. If they propose 50/50 in the first minute, ask what they expect each of you to put in, and read our guide on how to split equity between co-founders. Ask about vesting too: a co-founder who refuses a one-year cliff is telling you something.

Finally, the exit. What happens if one of you wants to leave in year two? What if one of you stops performing? Nobody likes these questions, and the teams that answer them early are the ones that survive the case.

Which answers are red flags?

Some answers should end the conversation, or at least pause it:

• Vague commitment. "As much as I can" or "we will see" instead of hours and a date for full-time.
• No failures. A career with nothing that went wrong, or blame for every setback on other people.
• Avoiding money. Changing the subject when salary, savings or investment come up.
• Equity by reflex. 50/50 without a thought, or a large share for the idea alone.
• Different speeds. One person wants to launch next month, the other wants to perfect the product for a year.
• A reference nobody wants to give. Ask for someone who worked with them under pressure. Hesitation is an answer.

One red flag is rarely final. Two or three in the same conversation usually are.

How do you test it before you sign?

Conversations show intentions. Work shows behaviour. Before you sign a founder agreement, run a trial project: two to four weeks, one real deliverable, a date and a result you can judge together. A landing page with the first sign-ups, ten customer interviews, a prototype in front of three users. Agree beforehand what good looks like.

Watch how the other person handles the small things: whether they do what they said, how they communicate when they are late, how they take feedback, and whether you enjoy the work. Then take the answers from your conversations and the lessons from the project and write them down. That document is the first draft of your founder agreement, and it is the best protection you can give the company before it exists.

If you are still looking for the person to have these conversations with, Cofoundista shows you how matching works, and the open co-founder roles list what founders in Europe look for right now. If you want to join a venture, the page for co-founders explains how your terms and must-haves go into the fit score, so the first conversation already starts from shared expectations.