Cofounder reference check questions should reveal behavior under pressure.
Not reputation. Not charisma. Not whether the person is generally smart, impressive, or likable.
You are trying to learn how they work when stakes are high, when feedback is uncomfortable, when deadlines slip, when conflict appears, and when they have to keep showing up after the exciting part is over.
That is the signal you need before equity.
This is for you if
Use this guide if you have a serious potential cofounder and are close to making the relationship formal.
It is especially useful if:
- You have already had strong conversations with the candidate.
- You are about to split equity.
- You want outside signal before signing.
- You have only seen the person in networking, school, or social settings.
- You are deciding whether concerns are real or just anxiety.
If you are earlier in the process, start with questions to ask before choosing a cofounder, then use reference checks after the person becomes a serious candidate.
Why cofounder references are different
A cofounder reference is not an employment reference.
You are not only asking whether the person can do a job. You are asking whether they can be trusted with ownership, pressure, ambiguity, conflict, and long-term commitment.
That means your questions should focus on patterns:
- How they handle disagreement.
- Whether they do what they say.
- How they behave under stress.
- Whether they communicate early or hide problems.
- How they respond to feedback.
- Whether others would build with them again.
Y Combinator recommends trial work and reference calls when evaluating potential cofounders. That advice matters because chemistry in a few conversations is not enough.
Who to ask
Ask for references who have seen the candidate in real work.
Best references:
- Former cofounders.
- Former managers.
- Former direct reports.
- Close collaborators.
- People who worked with them under pressure.
- People who saw them in a failed project, not only a successful one.
Less useful references:
- Close friends who never worked with them.
- Investors who only saw the polished version.
- Advisors with limited contact.
- People who only know them from school or networking.
Ask for at least two references. If the person resists all reference checks, treat that as signal. It may be explainable, but it should be discussed.
How to run the call
Keep the call short, specific, and respectful.
Open with context:
"I am considering building a company with [Name]. I am trying to understand how they work under real conditions before we make a formal commitment. I would love your candid perspective."
Then ask behavior-based questions.
Do not ask:
- "Are they good?"
- "Are they smart?"
- "Do you recommend them?"
Ask for examples.
Cofounder reference check questions
Use these questions as a menu. You do not need all of them in every call.
1. How did you work with them?
Start with context.
Ask:
- What was your relationship to them?
- How long did you work together?
- What was the project or company stage?
- What were they responsible for?
- How much pressure was the team under?
You need to know whether the reference actually saw relevant behavior.
2. What are they unusually good at?
This helps identify real strengths, not just generic praise.
Follow up:
- Can you give me a specific example?
- Where did that strength matter most?
- What kind of environment brings out their best work?
Listen for concrete stories. "They are great" is weak signal. "They took over customer calls when the launch broke and kept the team calm" is useful.
3. What is hard about working with them?
This is one of the most important questions.
Ask it directly and calmly.
Follow up:
- When does that show up?
- How do people usually adapt to it?
- Did they know this about themselves?
- Did they improve over time?
Every founder has sharp edges. You are trying to learn whether the edge is manageable or dangerous.
4. How do they handle conflict?
Cofounder conflict is not hypothetical.
Ask:
- What happens when someone strongly disagrees with them?
- Do they seek truth, control, speed, consensus, or avoidance?
- Can they change their mind?
- Do they escalate conflict or de-escalate it?
- Can you remember a specific disagreement?
Compare this with what you learn from the CofounderFit assessment, especially communication and decision-making.
5. How do they behave under stress?
Stress reveals the real operating system.
Ask:
- What are they like when deadlines slip?
- What are they like when the team is uncertain?
- Do they communicate early when something is wrong?
- Do they become sharper, quieter, controlling, avoidant, or more collaborative?
- How do they recover after a hard period?
If you hear "they disappear when things get tense," pay attention.
6. How reliable are they?
Reliability is not only about working hard.
Ask:
- Do they follow through on commitments?
- Do they communicate when they cannot deliver?
- Do they overpromise?
- Do they need structure to stay focused?
- Can others depend on their judgment?
Founders can survive skill gaps more easily than trust gaps.
7. How do they handle feedback?
Ask:
- Are they open to direct feedback?
- Do they get defensive?
- Do they change behavior after feedback?
- Do they give feedback well?
- What kind of feedback style works best with them?
A cofounder who cannot receive feedback will make every hard conversation more expensive.
8. What kind of founder role would fit them best?
This question is useful because references may see role fit more clearly than character.
Ask:
- Would they be stronger as CEO, CTO, product lead, commercial lead, operator, or technical partner?
- Where would you not put them?
- What kind of cofounder would complement them?
- What support would they need?
Use this alongside cofounder roles and responsibilities.
9. Would you start a company with them?
Ask this near the end.
Then pause.
Follow up:
- Why or why not?
- Under what conditions?
- What would you want to agree before doing it?
The nuance matters more than the yes or no.
10. What should I ask them before committing?
This gives the reference permission to help you diligence the relationship.
Ask:
- What topic should we discuss before equity?
- What would you want to see in a trial project?
- What should I not assume about them?
- What is the biggest risk in partnering with them?
This often surfaces the most useful signal.
Red flags in reference calls
Pay attention when you hear:
- "They are brilliant, but..."
- "They need the right kind of manager."
- "They do not like being questioned."
- "They are amazing when motivated."
- "They can be hard to pin down."
- "They had conflict with several people, but it was not their fault."
- "I did not work with them long enough to know."
None of these automatically means do not proceed.
They mean test the concern before you split equity.
Use the cofounder trial collaboration checklist to create real signal.
How to use the answers
Do not treat reference calls like a vote.
Treat them like a risk map.
After the calls, write down:
- Strengths that appeared across references.
- Risks that appeared across references.
- Questions you still need to ask the candidate.
- Behaviors to test in a trial project.
- Agreement terms that should be explicit.
Then compare the reference signal with your direct experience, assessment results, and trial collaboration.
What to do next
Use this sequence:
- Ask your potential cofounder for two or three work references.
- Run short behavior-based calls.
- Compare patterns with the CofounderFit assessment.
- Test the biggest open question in a real trial collaboration.
- Discuss equity, roles, vesting, and decision rights.
- Capture your calls with the cofounder reference check template, then draft the agreement with the cofounder agreement generator.
References will not predict everything.
But they can save you from committing with only the version of the person you have seen so far.
Sources and further reading: Y Combinator's questions to discuss with a potential cofounder, First Round Review's founder dating playbook, and CofounderFit's cofounder questions checklist.