I have not found my cofounder yet. This is the system I am using while I look, and it is still changing as I meet people and try working together.
Sometimes the best conversation starts around a rough product or a real customer problem. Sometimes two people find the direction together. I am open to both. What matters is giving the relationship something real to do before chemistry fills in the missing evidence.
The first thing we work on may not become the company. It still gives the relationship somewhere real to happen.
I meet potential cofounders through introductions, programs, matching platforms, and the rooms I spend time in. I care about energy, ambition, and whether I want to spend a lot of time with someone. An exploratory match can still be fun, valuable, and clarifying when it ends. Ending early leaves both people free to keep looking, and sometimes that is what makes the right partnership possible later.
I wanted a way to keep the useful parts of intuition without letting chemistry make the whole decision. So I built a system around three questions: who is this person, who do we become together, and are we trying to build the same kind of company?
The relationship I actually want
As a cofounder, my natural range is across the whole company. I can talk to users, shape the product, build an MVP, sell, market, work through the financials, and handle much of the operating work. I still want to stay close to the product and the technical decisions behind it.
The most likely complement is someone with deeper technical expertise or real depth in the field we choose. I already ship early versions myself. Their depth should expand the kinds of companies we can build and how far we can take them.
I am open on category. I love consumer and community products because they sit close to people, and I am equally drawn to deep technical and hard-tech problems that take time to understand and are genuinely difficult to make work. A partner who already knows one of those worlds would bring a real advantage. What matters more is the ambition to go all the way into the problem together, learn fast, and stay with it when the easy answers run out.
I want a relationship where either founder can represent the whole company. I can walk into a call and explain the technical layer. My cofounder can pitch the product, the vision, and the financials when I am not in the room. We should each have areas of unusual depth, but neither of us should become a translator for half the company.
I also want someone with an opinion of their own. A founding relationship should contain two real minds. I want someone who can change my mind and be changed by evidence. If every difficult decision still comes back to me, I have found help, not a cofounder.
Five traits, grounded in people
Generic cofounder lists usually give me a set of adjectives: technical, ambitious, resilient, smart. They are easy to agree with and hard to use.
I started somewhere more personal. I listed people I already admire, then wrote down what I actually admire about them. Friends, builders, collaborators, people who make a room better. The repeated behaviors became my criteria.
The five traits I am testing for now are:
- Curiosity that moves. An interesting question does not stay a conversation for long. By the next time we speak, it has become a note, a prototype, or a conversation with someone who knows more. Their curiosity leaves evidence.
- Independent judgment with character. They have their own view and can say the hard thing without becoming cruel. How they treat waitstaff, junior people, and anyone with no status upside tells me more than how they act around investors.
- Ownership under ambiguity. When the plan breaks, they look for the missing information, find the next step, communicate early, and keep moving. They take difficult work seriously without making the difficulty everyone else's problem.
- Commitment with adaptability. They stay after novelty fades and accept real opportunity cost. They can change direction when the evidence changes without keeping every exit half-open.
- Complementary depth with whole-company ownership. They bring a serious spike, test whether their work holds beyond the obvious examples, and explain it clearly enough for other people to make decisions with them. They remain curious about users, product, business, and everything outside their lane.
The list will keep getting more precise as I work with more people. I would rather refine it from behavior I have observed than pretend a borrowed checklist is objective.
These traits tell me something about the person. They do not tell me whether we become a strong pair.
What happens between us
I am drawn to something I think of as joyful intensity. We can take ambitious work seriously without making every difficult hour feel heavy. The standards and urgency are high, but there are still jokes, spontaneity, and the feeling that we are lucky to be building this together.
Does that intensity give both of us energy, or does it drain more than it gives? Can we challenge each other without turning disagreement into a contest? Do we each create momentum the other could not create alone?
Mutual respect matters more to me than matching personalities. I want to be genuinely impressed by how my cofounder thinks, and I want the respect to run in both directions. The best pairing is probably high variance with shared standards: different strengths, real admiration, and enough trust to let each person lead.
Whether we want the same company
Two good people can work well together and still want different companies.
Before making anything official, I want clarity on why we are building, what success means, how much of our lives we are ready to commit, and what would make either of us leave. We should talk about pace, location, runway, fundraising, decision rights, and who owns which calls.
Equal respect does not mean every decision needs consensus. I want clear ownership, direct discussion, and a way to move after we disagree.
What I notice before we work together
Before I look at credentials, I pay attention to the conversation itself.
Who drives and who listens? Do we build on each other's ideas, or perform at each other? Is the conversation about users, product, and the company, or mostly identity and access? Do I feel sharper in this conversation, or smaller? Does their energy make the room more alive without making it revolve around them?
Then I write down what happened the same day. First impressions are generous editors. A week later, a charismatic conversation can become deeper and more decisive in memory than it really was.
I ask what I learned about the person, what I learned from them, and how I felt after leaving. Calm and energized is different from relieved that the call is over. I map what I observed across the person, the pair, and the company we might want to build. High chemistry with little evidence is a reason to slow down.
The notes give my intuition something concrete to argue with. They stay provisional until real work confirms or overturns them.
Build before the title
Alignment talk is cheap, and I can talk for hours, so it is an especially bad test for me.
The useful test is a sprint. Pick one painful problem. Talk to users. Build an ugly version. Put a deadline and a demo at the end. A weekend prototype can reveal more than months of hypothetical role design.
I watch how we scope, how we communicate when something breaks, who notices the boring task, and what happens when nobody assigned the next step. Does urgency make us clearer or more chaotic? Can better evidence change the plan without making the decision personal? Do we test the solution beyond the examples that make the demo look good?
The cofounder title, equity conversation, and public story can wait. Output should exist first.
If the short sprint works, it earns a test closer to the real company: a longer build, customer calls, a demand signal, and references from people who have worked with both of us. That is where commitment after novelty, ownership, and repair become easier to see.
What I stopped optimizing for
I want a force multiplier, not a stamp.
I stopped treating impressive markers as commitment evidence. Logos, network, investor fluency, and access to good rooms are useful. They remain weak proxies until I see repeated behavior.
If I would not choose someone without their credentials, I should not choose them for the credentials. If I feel that I need another person's profile to make the company look fundable, the deeper task is building enough proof of my own.
I also learned something less flattering about myself. I am team-oriented enough to slide into hosting someone else's experience. I include, smooth, anticipate, and resolve friction internally before the other person even sees it. That instinct is useful in many rooms. Inside a founding relationship, it can quietly redirect energy from the product into maintaining the partnership.
I need a partnership where both people share the emotional and operational load without one person orchestrating everything. Direct disagreement is fine; contempt and ego games are not.
Where outside advice helps
Most of the underlying principles were already familiar from working in teams and watching founders. I use YC talks, Paul Graham, founder accounts, and lessons from accelerator programs as a pressure test. They sharpen the questions around respect, stress, references, equity, decision rights, and whether both people stay exposed to the whole company. They do not answer the central question for me.
Sources I return to: Paul Graham, What We Look for in Founders, Harj Taggar, How to Find the Right Co-Founder, Alice Bentinck, The Co-Founder Checklist, and Alexander Weber, How I Found My Co-Founders.
The reading improves my questions. The relationship and the work answer them.
The question I come back to
Are we playing the same game, and does working together make both of us faster?
I am a product builder who can take a problem from user conversations to an early product. The most likely complement is someone whose technical or domain depth expands what we can build, who has an opinion of their own, and who wants to own the whole company with me. I would rather test that relationship through work than spend another month designing it in calls.
If that sounds like your way of working, send me what you are building or the problem you keep coming back to. That is where I would rather begin.