6
16 Comments

Finding Your Perfect Cofounder

You may have read in articles or heard in discussions that a relationship with a co-founder is kind of like a marriage. Both yes and no. Yes, it is true in terms of how a relationship develops in a movie, where there is a honeymoon phase, gradual discovery of the other person, some frustration, a long evolution, and, if you're lucky, an equal, fulfilling relationships, support, and other good things.
However, the similarities are only superficial because the dynamics and essence of these relationships are very different from marriage because they are driven by much more specific goals.

TL: DR When I decided to radically change my activities and launch a startup despite a lack of connections and experience in tech, I reached out to the few people I knew in the field. However, every attempt to find the right cofounder failed in some way, affecting the success of the projects I started. I needed to figure out how to find the right person to help me successfully launch my next startup, which is a part of my personal mission.

I
I'm an art director/creative director/strategic marketing guy turned startup founder, previously started two startups (both failed). I decided to leave my previous professional life behind and launch my first startup a few years ago. My job had almost nothing to do with tech. And I found myself in a situation where I had an idea and a desire but no resources or knowledge to put it into action.

This didn’t stop me, I searched for information and quickly realized that a good technical cofounder would be extremely beneficial in launching a successful startup. But where do you get one, and what kind of person should it be? It was only clear that it had to be someone in charge of the development.

I reached out to the few tech people I knew, and voila! I was introduced to a potential cofounder. Only one. When he realized that a serious commitment was required, he left before we even began development, and I'm alone again. I spent another couple of months looking for a replacement, but it was futile.

Eventually, I was able to get the app up and running by hiring an external dev team. Sure, I recognized that this was not the best option for a variety of reasons: it was expensive; it was difficult to expect a strong involvement in the product's creation, and the connection with the project and the funder was solely based on financial interest.

I began the next project on my own as well, testing a few basic hypotheses. Because I did not intend to hire an external team this time, I began looking for a cofounder once again. I found him on one of the internet forums. After a few months, it became clear that there was an issue with a lack of commitment as well as skills.

After a while, I invited another developer who was on the same hackathon team as me. He was far more productive than the previous one. We eventually decided to pivot because we discovered a new promising niche where we could apply the same technology. Then the pandemic struck, rendering our efforts futile. Most importantly, it turned out that our goals, relationships, and ability to work through challenges were not on parallel tracks.

A few days later, I sat down and thought about what deeply important problem I had that I desperately wanted to solve but never did. The answer came to me almost instantly: chronic procrastination. I did some quick research and discovered that the same issue affects a large percentage of people around the world.

While researching, developing an MVP, and validating hypotheses, I realized that this was it. The problem itself, as well as this entire field (psychology/neurosciences), are not only exciting but also completely align with my inner motivations and goals (some would call it a mission).

With very promising MVP results in hand, I (yes, once again) decided that now was the right time to bring in a tech cofounder. The search was finally narrowed down to four sources: my network, subreddit r/cofounder, Y Combinator Co-founders Match, and this thread on Indiehackers. I wrote a short intro about myself, the project, the stage I'm currently in, and who I'm looking for.

To have a clear reference point, I sat down and asked myself, "Ok, who would be my ideal co-founder, and what qualities seem important to me based on my previous experience?" I did a document on which I relied during my search. It was important for me to write down all of my thoughts on this rather than hope that "I understand everything anyway."

After that, I placed a new post in the above-mentioned communities and started browsing YC CF Match profiles.

II
A few dozens of people from around the world responded.
Many of them were talented people and strong developers with extensive work experience, including CTO positions in other startups.

All in all, after discussing the terms, the trial period, the areas of responsibility, and our expectations of each other, we started working on the product with one of the candidates.

Now fast forward a few months. We went through a bunch of situations, including the honeymoon period, three or four crises, and the product's evolution. As I reviewed our results and the dynamics of our relationships, I realized that it was probably best for the business and for both of us to go our separate ways.

The two main factors that led to this decision were my cofounder's lack of interest in the problem the product solves and psychology in general, which resulted in poor performance as well as a lack of common interests and themes to discuss. This may sound harsh, but I believe we should have split up much sooner.

III
As I progressed through this quest and analyzed my actions and outcomes, I came to the following conclusions:

0
Setting up meetings with multiple candidates is worth the effort. One person, even if they meet some criteria, is not a choice; it is self-delusion, which will manifest sooner or later. A startup is a long game, and it's worth taking the time to find and communicate with the right people so that I don't have to start the process all over again, possibly at a time when it's completely unnecessary.

1
Homework is crucial. It involves learning the fundamentals of the business I'm running, such as the market, the state of things, the method of company development (venture capital or bootstraping), and the roadmap.

The other part may be more tricky – it is about understanding myself, my values, and motivations, assessing my resources, evaluating what the business requires now and in the medium term, and determining what type of cofounder I should seek.

2
A thorough review of each potential cofounder (it is assumed that this is a stranger from the Internet). What and how he/she says, what he/she asks, what values he/she communicates, how he/she reacts to specific events and changes, the degree of involvement in the problem, and the creation of the best product.

It should be given no less attention during the joint work. And this assessment should be done as frequently as possible, perhaps once a week. If problems are left unattended, they tend to worsen.

As a founder swimming in uncharted waters, I should do the same with myself.

3
Red flags. These can be any signals that cast doubt on a person, his/her qualities, goals, intentions, or values. Ignoring them is a ticking time bomb in business and relationships.

4
Hard skills. They are difficult to assess for a non-technical funder, and vice versa. You could enlist the assistance of someone you know who is knowledgeable about the subject. However, there could be a difficulty: this is not a typical job interview, and there is no one who can share the responsibility. It makes sense to search open sources for information, such as GitHub. In general, it is beneficial to be attentive and creative. All of this, of course, will not give guarantees, but still.

5
The person who invites the cofounder automatically becomes a leader. So, it's crucial to exercise leadership. Of course, it's not about being the alpha. This role may shift over time, but not in the initial phase. Taking responsibility is an essential part of leadership.

6
All of this leads me to believe that empathy, self-discipline, attention management, calmness, and clarity are a founder's best friends. In addition to the well-known qualities and skills that everyone is familiar with.

IV
Andreessen Horowitz's Marc Andreessen claims that approximately 50% of cofounders divorce, yet the firm prefers to work with teams of 2+ cofounders.

I don't think a cofounder is absolutely necessary for everyone. Many super-cool solo founders have built fantastic products and businesses. With a clear vision and some personal qualities and resources, you can get far enough with an external dev team until you have one of your own. However, I think that starting a startup is somewhat similar to climbing a difficult mountain in that having the right partner in the bunch motivates you to move forward, look for and find better ways, express your best qualities, learn new things, and learn to trust. In other words, it greatly increases your chances of reaching the summit.

posted to Icon for group Looking to Partner Up
Looking to Partner Up
on September 5, 2022
  1. 3

    This was a beautiful read, thanks for taking the time.

    In my situation I realised that If I start building what I can with no code, when I get stuck I reach out to people in forums with a sense of urgency. I schedule a call with generous souls who respond, if they are interested in what I am building and can help me get unstuck it's a very good signal worth exploring further.

    Finding a co-founder is so similar to dating, personally I think having a set criteria and measuring everyone against it hasn't worked for me but knowing what I bring to the table has. Moving forward I want to focus on soliciting acts of generosity followed by enthusiastic conversations and sprints on shared passion projects.

    Like you my skill is selling things, designing things and understanding customers needs so the best complementary skill for me is someone who builds things. My process unearths people who love building things so much that they are willing to help others in their spare time.

    Thanks for sharing I wish you the best of luck. Let me know if you ever want to connect and talk about what you are working on.

    1. 1

      Thanks, Solomon.

      I do the same when I build my MVPs, and it works great at that stage.

      Agree with your idea about firm criteria setting etc. Although I believe one should measure the probability of making a great product and having nice relationships doing it together for years to come. It probably isn't as crucial when it's a pet project or something like that.

      Anyways, you've made some great points on the process. Would love to chat with you.

  2. 1

    Agree with this completely. Out of curiosity, how have you decided to approach the cofounder issue now? Have you found someone (and if so, how) or have you discovered a workaround?

    1. 1

      I described my approach in the chapter III here if I get your question correctly.

      Not yet. A lot of meetings with prospective people though. The only workaround I think about is a founding team instead of a full-bodied cofounder.

  3. 1

    Great Overview of the process . I have always used Gloria's dating playbook as my starting guide with great success as a base to build on finding the right fit. https://review.firstround.com/the-founder-dating-playbook-heres-the-process-i-used-to-find-my-co-founder

    As a long-distance runner who never liked track - the analogy of going the distance I find to be a slightly better analogy than the marriage one. Some marriages are shotgun weddings that don't end up long term, while some last a lifetime.

    I actually had a 3 person co-founding team where we decided the business wasn't feasible based on the data before we got to market and we parted ways after closing the business. Before we did, we explored each others ideas.

    Now these were amazing real partners/founders - but at the end of the day the passion for the other businesses was not there, hence the parting. But from a technical skill set I would work with that team again any day.

    I agree the passion to keep driving the business is so critical in the early stage.

    Which is why I know even my current search for a startup cofounding marketing partner will be so darn difficult.

    1. 1

      100% agree with your passion statement. Another source of power here is the purpose, which is somehow connected with a passion I guess.

      I'm thinking about sport walking half-marathon now :)

  4. 1

    Good read!
    On point 4. Hard skills yes, but in what technologies?
    There are tools nowadays that let you do things in one hour that were not possible to do in one year before. Those tools are not learned in corporations too often, and people that lost the touch with coding in last 3 years did not hear about them.
    Ex. make a backend in Java and one in Hasura.

    It can be a the kindest, most amazing leader, hardworking engineer, writes quality code,
    if the tool he/she uses gets you there in one year I'm not sure of you would not be better off with one that gets the app done in 3 months with enough quality, before the "honeymoon" is over, before you got to know him/her well you are on-boarding clients.

    I would say you get good advise on the tech choice and then find the person.

    1. 1

      Great point! Could you please elaborate a bit more on that? What tools for what use cases for instance?

      1. 1

        For example:
        Backend:

        • Hasura.io (open source, self hosted or not) generates a very performant CRUD GraphQL API instant in kind of no-code manner. If your data structure fits relational database model. For many apps e.g. just a glorified CRUD with a bit of custom stuff on backend this would be an amazing solution. The API can be extended with other custom endpoints but the CRUD itself is blackbox.
        • Amplication.com generates an actual Nestjs backend with a CRUD api , here is not blackbox you actually get the code and can modify every single coma. Build with NestJS, the most "bateries included" node framework, and prisma orm biggest time saver in the node orm space .
          frontend:
          Recently it's up and coming tools that get a Figma design and output React presentational components https://www.animaapp.com/ https://clapy.co/ - many developers were amazed that such tools exist. Now these do not seem to work perfectly in all situations but if it does in 80 or 90 % its still a big gain.
          then on the design side:
          if you do not have a designer (and as indiehackers 2 co-founders startup that could be the case) do not go with scss and not even tailwind, use a library like https://chakra-ui.com/ or mui.com
        1. 2

          and if you considered and you cannot use those tools or similar for the backend and you need to go the classic development route there are 2 tech stacks that are the fastest:

          • Nodejs framework(not classic Express there are better options) + react / vue
          • Laravel + Vue

          And GraphQL probably for more than 50 % of the cases.

          That's all, hands down in 2022.

          Yes Django , Ruby on Rails, .NET were good too but 4 years ago, and we did love them and they were the best then. I am yet to see someone coming from these tech stack to Node + React or Laravel+vue and not say it's noticeable the difference in speed of development.

          Yes there are use cases for other languages like C, java go and rust . Example: you have a very simple app but the performance needs to be crazy good, but those are not your standard indie project I suspect, if you are in that field prob both co-founders are deep in tech.

          Fun fact: Regarding this tradeoff when choosing technologies performance vs speed of development: I have not seen a startup that picked the wrong tech stack that was good at speed of development but ended up causing problems at performance. I see on regular bases too powerful but slow to develop kind of stack picked. Back-ends build in Java in one year, relatively simple models, 2 native apps when a react-native would suffice from performance perspective etc.

          1. 2

            I think you've got a damn healthy approach to how to build early-stage startup software. The last sentence is 100% spot on.

            My take on that is when you're just trying to take off your idea (and you're not a deep tech or biotech) and even later on the "speed+low cost (resources spend)" combo is the king.

    2. 1

      I'm not talking about no-code solutions, those are good for MVPs and rarely can get you to a usable product.
      I'm talking now about more in between no-code and classic development, where you auto generate lot of the standard generic parts but you can have full control to modify what was generated.

  5. 1

    This landed in my inbox at the perfect time. I have been searching for a cofounder for the past month or so and it's been a difficult journey finding the "right" person after all culture is important when you are this early. This was a beautiful read.

  6. 1

    Thank you for taking the time to write out and share your experiences. A thoroughly interesting read that has given me a lot to consider on my journey.

    1. 1

      Thanks, I hope it helps on your journey.

Trending on Indie Hackers
Why Indie Founders Fail: The Uncomfortable Truths Beyond "Build in Public" User Avatar 139 comments Your AI Product Is Not A Real Business User Avatar 87 comments The Clarity Trap: Why “Pretty” Pages Kill Profits (And What To Do Instead) User Avatar 34 comments I built an enterprise AI chatbot platform solo — 6 microservices, 7 channels, and Claude Code as my co-developer User Avatar 29 comments Stop Building Features: Why 80% of Your Roadmap is a Waste of Time User Avatar 27 comments I got let go, spent 18 months building a productivity app, and now I'm taking it to Kickstarter User Avatar 18 comments