For the first few years, AvanSaber had no org chart, because an org chart of two people is just two names and a line, and we already knew the line. Varun ran the company. I built the products. We are now past a decade of that arrangement, and the line has not really moved, which I think is the most useful thing I can tell another founder about partnership. The split that works is the one you can still describe in a single sentence ten years later.
People romanticize co-founders, or they tell horror stories. The truth in our case is quieter than both. We are not best friends who finish each other's sentences, and we have never thrown a chair. We are two people with genuinely different wiring who decided, early and on purpose, to stop competing for the same job.
The clean split: business and building
Varun is the CEO. He owns the company as a business: the customers, the commercials, the direction, the parts that involve persuading the outside world that any of this is worth paying for. I am the CTO. I own the company as a machine: what we build, how it is built, and whether it stays standing when someone leans on it. When a customer asks a question, the answer almost always belongs cleanly to one of us, and we both know which.
This sounds obvious. It is not how most early companies actually behave. Two technical founders will quietly fight over architecture. Two commercial founders will quietly fight over the deck. The thing that saved us was that neither of us wanted the other's job. I have no desire to run a sales call. He has no desire to review a database schema. That lack of overlap is not a weakness in the partnership. It is the partnership.
Where the split gets messy
It is clean until it is not, and the place it stops being clean is always the same: anything that is both a business decision and a building decision at once. Which product gets the next two engineers. Whether we take on a customer whose needs will bend the roadmap. How much of a quarter we spend on something that pays off in two years or not at all.
Those calls live exactly on the seam between us, and early on we were bad at them. I would treat a roadmap question as purely technical. He would treat it as purely commercial. We were both half right, which is the most annoying way to be wrong.
The best decisions we make are the ones neither of us could have reached alone, and was certain about until the other pushed back.
How we actually settle it
What we landed on is unglamorous. For anything on the seam, the person whose domain carries more of the risk gets the final call, and the other one gets a real, listened-to objection first. If a decision will mostly be felt by customers, it is his. If it will mostly be felt at 2am by whoever is on call, it is mine. And whoever does not get the call has agreed, in advance, to disagree and commit rather than relitigate it for a month.
The trust that makes this work is not vague good feeling. It is specific. I trust that he is not optimizing for looking right. He trusts that I am not gold-plating something for my own satisfaction. We earned that read on each other slowly, by being wrong in front of each other and not making it weird.
What a decade taught me
The thing I did not expect is how much a good co-founder functions as a second kind of judgment, not just a second pair of hands. A lot of what I have learned about backing people and learning from them started with Varun, because he was the first person whose disagreement I learned to treat as information rather than friction.
If you are picking a co-founder, I would worry less about shared passion and more about a clean division of who owns what, plus enough trust to lose an argument gracefully. The shared passion fades on the hard Tuesdays. The division of labor is what gets you to Wednesday. We run everything we build, which means there is always plenty to disagree about. Ten years in, the disagreements are still the most productive part of my week.