Choosing Your Co-Founders
A co-founder is someone whose absence would force you to rebuild the company, not just fill a role - find them by identifying your gaps first, not by starting with who you like.
Fahim Saleh did not find me through a LinkedIn post or a pitch competition. He found me through a joke.
I had built a website called IsTomorrowHartal? - plain white background, Arial font, a yes or a no. That was it. During a period when Dhaka was paralyzed by political strikes and everyone was burning the same question into every WhatsApp group and Facebook thread, I just answered it in one click. The site got 40,000 views on day one. 80,000 the next.
Fahim saw it floating around and messaged me. “How much to sponsor this?” I threw out $200 expecting a laugh. He replied in seconds: “Cool. Send me payment details.”
A few days later I was sitting in his office at HackHouse in Banani . Wooden floors, glass walls, whiteboards full of actual ideas. He was building a venture studio. The plan was simple: take business models that already worked in New York or Jakarta and make them work in Dhaka. He had the vision, the money, the track record. What he didn’t have was someone technical who actually lived here, understood this city, knew how the roads worked and which government office you needed to navigate and what a Bangladeshi user would and wouldn’t do on a smartphone.
That was the gap. And I fit it exactly.
He needed me because I could build the product, and because I was from here. I understood the chaos. I could navigate it. That’s the only reason I became his co-founder at HackHouse. Not because we were old friends. Not because I impressed him at a networking event. Because I filled a specific, critical hole in what he was trying to build.
That’s the first thing most founders get wrong. They don’t go looking for what they’re missing. They go looking for someone they already like.
Know Your Gaps Before You Go Looking
Before you even start thinking about who, you need to be brutally honest about what. What does this company actually need to survive? Not what would be nice to have. What is it that you literally cannot build without?
Every company needs at least two roles: a builder, and a seller.
Fahim’s answer was obvious: local technical execution. He was Bangladeshi by heritage but a New Yorker by everything else. He had the capital, the frameworks, the Silicon Valley thinking. But he couldn’t build the product, and he didn’t know how to move inside Bangladesh. Without someone who could do both, HackHouse was just a well-funded idea.
My answer, when I later co-founded Pathao, was different. I needed someone who could run ground operations while I stayed close to product. Someone who could negotiate with a government office in the morning and manage fifty riders in the afternoon without losing their composure at either.
The gap tells you who you need. Start there. Don’t start from the person and then work backwards trying to justify the choice.
Build Shared History Before You Build a Company
Fahim and I had months of working together at HackHouse before anything became official. We saw how each other thought. We disagreed. We moved fast. We had friction and got past it. By the time real pressure came, we weren’t strangers still figuring each other out. We already had a language.
This matters more than people admit. A co-founder relationship you jump into cold is the startup equivalent of marrying someone you met at an airport. It might work out. But you’re gambling the most important relationship in your company’s life on zero data.
Work on something together first, even something small. A contract project, a shared problem, a prototype built over a weekend. Watch how they handle setbacks. Watch what they do when you disagree. Watch whether they go quiet or go loud when things get hard. That’s your real interview. Everything else is just conversation.
This Is Closer to Marriage Than You Think
People say choosing a co-founder is like choosing a spouse. I used to think that was a metaphor. Now I think it’s an understatement.
When Pathao was in full build mode, I was at the office or on calls for ten, eleven, twelve hours a day. Some days more. My co-founders were the first people I spoke to in the morning and the last I messaged at night. We ate together, panicked together, argued about cash flow at 1am together. There were stretches where I saw my co-founders more than I saw anyone else in my life, more than family, more than friends, more than the person I was supposed to be dating.
Think about what that means before you sign anything.
In a marriage, you choose someone you want to build a life with. In a co-founder relationship, you’re choosing someone you’re going to solve problems with for ten to twelve hours every single day, under financial pressure, with other people’s livelihoods at stake, with investors watching, with a market that doesn’t care about your feelings. That is a more intense operating environment than most marriages ever face.
And just like a marriage, the cracks don’t show up on day one. They show up in year two when you’re exhausted and the money is tight and you realize you each had a completely different picture of where this was going. The resentment builds quietly. The small irritations compound. One person thinks they’re carrying more than their share. The other thinks the same. And suddenly you’re not building a company together, you’re managing a relationship that’s slowly breaking.
I’m not saying don’t do it. I’m saying treat it with the same seriousness. You wouldn’t propose to someone you met twice. Don’t hand out equity to one either.
Align on the Personal Stuff First
Before the product, before the strategy, before the deck, sit down and have the uncomfortable conversation about what each of you actually wants.
One person wants to build something big and sell it in five years. The other wants to build something that lasts and hold it forever. One person has three kids and needs to be home by seven. The other has no obligations and will work until they physically collapse. One person needs a large exit to justify the sacrifice. The other would be happy with a profitable small company.
These mismatches don’t explode immediately. They ferment. And they always surface at the worst possible moment, usually when the company is either close to success or close to collapse, the two times you can least afford a crisis at the top.
Get it all on the table before you start. You don’t need identical goals. You need compatible ones, and you need to actually understand what the other person is walking in with.
Two to Three. No More.
Keep the founding team small. Two to three people, four at an absolute stretch.
I have seen nine-person founding teams walk into a room. That is not a founding team. That is a committee with equity. The more co-founders you have, the more complex every decision becomes, the harder the equity conversation gets, and the easier it is for misalignment to quietly hollow out the structure from the inside while everyone is still smiling at each other in meetings.
One person carries the vision. One person builds the product. One person owns operations or growth. Beyond that, you’re just adding politics.
A Co-Founder Is Not Just an Early Employee
The test is simple: if this person left tomorrow, could you replace them?
If the answer is yes, they are a first hire, not a co-founder. A co-founder is someone whose absence would require you to fundamentally rebuild what you’re doing, not just fill a role but rethink the foundation. Not just someone who was there early, or works hard, or shares your energy. Someone structurally essential.
When Fahim picked me for HackHouse, that was the test he was applying even if neither of us named it. Without a technical, local co-founder, everything he wanted to build was theoretical. I wasn’t nice to have. I was load-bearing.
Get that clear before you hand out the title. Get it clear before you hand out the equity. Because undoing it later is expensive, painful, and sometimes fatal.
Before You Commit, Answer These
Use these five questions as a filter before you make it official.
One: Can you clearly name two or three things this company cannot survive without that you personally cannot provide? If you can’t name the gap, you’re not ready to fill it.
Two: Have you worked through at least one real conflict with this person and come out the other side without permanent damage? Harmony under good conditions means nothing. You need data from a bad day.
Three: Do you both know what the other actually wants from this, financially and personally? Not what you assume. What they’ve told you directly.
Four: If this person disappeared tomorrow, would you have to rebuild the company or just hire a replacement? One of those answers makes them a co-founder. The other makes them employee number one.
Five: Can you sit across from this person for ten hours in a bad week and still respect them? Because that week is coming. Multiple times. Make sure the answer is yes before you’re already inside it.