Why structured questions beat chemistry
Choosing a co-founder is one of the few decisions in a young project that is genuinely hard to undo.
You can change your product, your name, even your market, but changing a partner mid-build costs momentum, trust, and often the project itself.
That is why the conversations you have before committing matter more than any pitch or resume.
This guide gives you practical questions to ask a potential co-founder.
It explains what each question tests and how to turn answers into evidence rather than vibes.
The goal is not a perfect interview script.
It is a way to learn what you actually need to know before you share ownership, time, and reputation with someone.
Enthusiasm is easy to mistake for compatibility.
Two people can be excited about the same idea and still fail together because they disagree on commitment, money, or decision-making.
Good questions surface those disagreements while they are still cheap to resolve.
Y Combinator's co-founder matching team makes a similar point.
Like a romantic partner, a co-founder is someone you will depend on and spend years with.
You probably should not marry someone after one date, and it takes more than one video call to decide whether to build a company with someone.
They encourage matched founders to meet and, when appropriate, work together on a time-boxed trial project with clear expectations and goals to vet compatibility source.
So treat the questions below as the conversation layer, and a small trial project as the evidence layer.
Together they give you a far better read than a single impressive chat.
What problem are you solving, and what is your unique insight?
Ask your potential co-founder to explain the problem in plain language, then push one level deeper: what do they know about this problem that most people do not?
Michael Seibel of Y Combinator describes a unique insight as something specific.
It usually comes from customer conversations, product analysis, or personal experience.
He notes that passion does not help here; stating a weak insight forcefully makes someone look worse, not better source.
What this tests: whether your potential partner has done real thinking, or is running on enthusiasm.
If their answer is vague or full of jargon, that is information.
If they can name specific users, specific frustrations, or a specific reason existing solutions fall short, that is a strong signal.
Who is this for, and how do you know?
Listen for evidence of contact with real people who have the problem.
Someone who has talked to potential users, watched them struggle, or lived the problem themselves will answer with specifics.
Someone who has only read about the market will answer with generalities.
How do you think this makes money?
Seibel splits startups into those that know how they will make money and those that have not figured it out yet, and warns against offering a potpourri of business models at once.
His advice: own the simple business model source.
You do not need a finished plan.
You do need a potential partner who can discuss money without flinching, because money conversations do not get easier after you commit.
Unsure whether a business model needs to exist first?
We cover that tradeoff in Do You Need a Business Model Before Finding a Co-Founder?
How many hours per week can you actually give this, starting when?
Get concrete.
'A lot' means nothing.
Ask what else competes for their time: a job, studies, family, other projects.
Then ask when that changes.
Two people can both be sincere and still be incompatible if one can work evenings only and the other expects full-time pace from month one.
Are you working on anything else right now?
This is not an accusation.
Side projects are normal.
The point is to understand where your project sits in their priorities and whether that matches your expectation.
A mismatch discovered now is a negotiation.
The same mismatch discovered after you have built for months is a rupture.
What would make you stop?
This question sounds negative, but it reveals a lot.
Someone who says 'nothing, ever' is either not thinking or performing.
Someone who can name their real stopping conditions, such as running out of savings or a specific milestone not being reached, is being honest about risk.
Honesty here predicts honesty later, when things get hard.
How should we split equity, and why?
Seibel lists the equity split among the questions he cares about when evaluating a team, noting he hopes the answer is equal or close to equal source.
Whatever number you land on, the reasoning matters more than the figure.
Ask how they would handle it if one person contributes more over time, or if one person leaves early.
Their answer tells you whether they think about fairness as a fixed snapshot or an ongoing conversation.
What do you need to earn, and by when?
Personal financial pressure shapes behavior.
A partner who needs income soon will push for different decisions than one who can go a long time without pay.
Neither is wrong, but the difference must be on the table before you commit, not after.
How do you feel about spending money on this?
Ask about their instincts on tools, contractors, and paid experiments.
You are not negotiating a budget yet.
You are checking whether your defaults are compatible, because small spending disagreements compound quickly.
What do you do well, and what should I never ask you to do?
The second half is the valuable part.
People who know their limits are easier to build with than people who claim they can do everything.
Ask for an example of something they did well and something they struggled with.
Specific stories beat self-ratings.
Who decides what, when we disagree?
You do not need a full governance structure on day one.
You do need to know whether your potential partner expects consensus on everything, wants clear domains of ownership, or defers to whoever has the strongest argument.
Any of these can work.
Unstated assumptions about decision-making are a classic source of co-founder conflict.
What is your track record with finishing things?
Ask about the last project they saw through to the end, and the last one they abandoned.
Everyone abandons things sometimes.
What matters is whether they can talk about it plainly and whether their pattern matches the kind of commitment your project needs.
How do you prefer to communicate, and how fast do you expect replies?
Mismatched communication expectations cause more friction than skill gaps.
One person may see a slow reply as normal; the other reads it as disengagement.
Compare preferences now, and agree on a rhythm you both can sustain.
How do you handle feedback?
Try it directly: give one piece of genuine, mild criticism during your conversations and watch what happens.
Do they get curious, defensive, or dismissive?
You will be giving each other feedback constantly.
The first reaction you see is a preview.
What does success look like for you in a year?
This question quietly checks alignment on ambition.
One partner may want a sustainable side project; the other may want a funded company.
Neither goal is wrong, but they pull the project in different directions.
Better to find out early.
Turning answers into evidence
Answers are claims.
Before you commit, convert the most important claims into something observable:
- Run a time-boxed trial project. This is the approach YC recommends for matched co-founders: work together with clear expectations and goals before deciding source. Pick something small, real, and finishable. For help scoping it, see how to choose the right small project before you commit and its short proof sprint version.
- Watch how they behave, not just what they say. Do they show up when they said they would? Do they finish their part? Do they raise problems early or hide them?
- Test clarity. Seibel suggests an email test: write a two-sentence explanation, send it to a smart friend, and ask them to explain it back. If they ask clarifying questions, revise source. Do this together. How your potential partner handles the unglamorous work of being understood tells you a lot about building with them.
- Write down what you agreed. After your conversations and trial, summarize hours, roles, equity thinking, and decision-making in a short shared document. The act of writing surfaces assumptions neither of you noticed.
A simple way to run the conversation
You do not need to interrogate.
Spread these questions across a few meetings, and answer them yourself too.
The best version of this process is mutual: both of you are evaluating, and both of you are being evaluated.
That symmetry keeps the tone honest instead of adversarial.
A workable sequence looks like this:
- One or two conversations covering the idea, commitment, and money questions.
- A small trial project with a clear end point and agreed expectations.
- A debrief where you both say what worked and what did not.
- A written summary of what you are agreeing to before anything formal happens.
If you are still weighing whether to start alone instead of waiting for a partner, the timing tradeoffs are covered in Start Solo Now or Wait for a Co-Founder?
And if you want the broader context on how ideas die before launch, why most ideas fail before they even start is a useful companion read.
The bottom line
The right questions do not find you a perfect co-founder; no checklist can.
They do something more useful: they reveal whether two people share the same honest picture of the work, the time, the money, and the decisions ahead.
Ask them early, answer them yourself, and back the answers with a small trial before you commit.
Compatibility is not something you feel in one conversation.
It is something you observe over a few, with the stakes kept low.
Take the next step with Ideoreto. Use the ideas in this guide as a starting point for your next project.
Register for Ideoreto to get started.