Skip to main content
How to find and vet a startup cofounder
  1. How To/

How to find and vet a startup cofounder

7 mins·
Ben Schmidt
Author
I am going to help you build the impossible.

Finding a cofounder is one of the most significant decisions you will make for your business. It is often compared to a marriage because of the time commitment and the emotional weight involved. However, the goal is not simply to find someone you like. The goal is to find a partner whose skills and temperament fill the gaps in your own profile. This article explores how to look at your own needs objectively and how to put a potential partnership through its paces before signing any legal documents. We will cover the necessity of a skills audit and the implementation of a thirty day trial period to move past theory and into actual production.

When I work with startups I like to see the founding team as a puzzle. If two pieces have the same shape, they cannot connect to build a larger picture. Most people gravitate toward others who are just like them. Engineers look for engineers and salespeople look for salespeople. While this feels comfortable, it often leaves the business with massive blind spots. To build something that lasts, you need to be honest about what you do not know. This process is about building a foundation that can withstand the pressure of growth and the inevitable friction of the startup environment.

Auditing for complementary skills

#

Before you look for a partner, you have to look at yourself. I suggest making a list of every task required to run the business over the next twelve months. This includes writing code, designing interfaces, managing finances, selling to customers, and hiring staff. Once you have this list, mark which items you can do at a professional level and which ones you find draining or difficult. This is your personal audit. It helps you identify exactly what your cofounder needs to bring to the table.

When I help founders with this, we categorize skills into two main buckets: technical and business. Technical skills involve the actual creation of the product. This might be software engineering, hardware design, or manufacturing. Business skills involve the operations and market side. This includes growth marketing, sales, legal compliance, and fundraising. If you are a deep tech person, you likely need someone who can handle the market side. If you are a career salesperson, you need someone who can build the vision you are selling.

Consider these questions during your audit:

  • Which tasks do I consistently procrastinate on because I lack the skill?
  • If I were to focus only on my strengths, what specific roles would be left vacant?
  • Does the business require a deep level of technical expertise that I do not possess?
  • Who will be responsible for the first ten sales or the first thousand users?

Sourcing and screening candidates

#

Once you know what you are looking for, you can begin the search. This is a journalistic exercise in finding the right data points. You can look in your existing network, attend industry events, or use dedicated cofounder matching platforms. When you meet someone who seems like a fit, do not jump straight into equity discussions. Treat the first few meetings as interviews. You are looking for alignment on values and work ethic more than a shared love for the idea.

I often tell founders to look for evidence of past work. Ideas are cheap, and in a startup, the ability to execute is the only thing that moves the needle. Ask for examples of projects they have completed. Ask about times they have failed and how they handled the aftermath. You want to see how they think when things go wrong. If they spend more time talking about the potential payout than the actual work required, that is a red flag. You need a builder, not a dreamer.

Questions to ask a potential partner:

  • What is your personal financial runway and risk tolerance?
  • How many hours per week can you realistically commit to this right now?
  • What is your preferred method for handling serious disagreements?
  • Why do you want to build a company instead of taking a high paying job?

The thirty day trial project

#

You cannot truly know if you can work with someone until you actually work with them. I recommend a thirty day trial project. This is a self contained piece of work that has a clear beginning and end. It should be difficult enough to cause some stress but small enough to finish in a month. This is the ultimate vetting tool because it moves the relationship out of the theoretical and into the practical.

During this month, do not worry about the long term structure of the company. Focus on the work. If one of you is technical and the other is business focused, the goal could be to build a functional prototype and get five potential customers to sign a letter of intent. This requires both people to perform. If the engineer builds the tool but the business person fails to find any customers, you have discovered a mismatch in skill or effort. It is better to find this out now than after you have vested equity for two years.

Consider these metrics during the trial:

  • Did both parties meet their internal deadlines?
  • How did the communication flow during high stress moments?
  • Was the quality of the output up to the necessary standard?
  • Did the partnership result in more work getting done than if you were alone?

Navigating the unknowns and taking action

#

There will always be unknowns when starting a business. You cannot predict the market, the competition, or how your relationship will evolve over five years. However, movement is always better than debate. If you spend three months debating the perfect equity split before you have even built a product, you are wasting time. The goal of the vetting process is to get enough confidence to start moving. Once the thirty day trial is over, you should have enough data to make a decision.

When I work with teams, I notice that the best ones do not wait for certainty. They identify the biggest unknown and they run toward it. If the unknown is whether you can work together, the trial project is the solution. If the unknown is whether the market wants the product, building a minimum viable product is the solution. Do not get stuck in a loop of talking about the business. The act of doing will reveal the truth faster than any conversation or contract ever could.

Questions for the end of the trial:

  • Are we moving faster together than we were apart?
  • Do I trust this person to make decisions when I am not in the room?
  • Are we spending more time building or more time arguing?
  • Can we sustain this level of effort for the next several years?

Building a solid foundation

#

The startup journey is difficult and the environment is often chaotic. By auditing your skills and stress testing your partnership, you are reducing the internal chaos so you can focus on the external challenges. This is not about finding a perfect person. It is about finding a functional partnership that can solve problems. If the trial project works, then you can move into the formal legalities of vesting schedules and shareholder agreements.

Success in a startup is rarely about a single brilliant idea. It is about the ability of a small team to execute consistently over a long period. By being rigorous in your vetting process, you are showing respect for the work and for the impact you want to have. You are building something remarkable by ensuring the people at the core are the right ones for the job. Keep building, keep moving, and let the work dictate your next steps.