You started this company together. There was a time when you were completely aligned — on the vision, on the approach, on what you were building and why. That time feels far away now.
The conversations are harder. Decisions that used to take 20 minutes now take three meetings and still feel unresolved. The product roadmap discussions have an edge to them. You’ve started going around your technical co-founder on some things because the friction of including them doesn’t feel worth it. They’ve noticed. The engineering team has noticed. Your best engineers are watching this and updating their assumptions about the company’s future.
This is one of the most dangerous situations a startup can be in — not because it’s unresolvable, but because it tends to get worse when avoided. Here’s how to think about it clearly.
What Kind of Misalignment Are You Actually Dealing With?
Not all co-founder conflict is the same, and the intervention depends heavily on what’s actually broken.
Strategic misalignment: You want to go upmarket. They want to stay in the SMB lane. You want to accelerate toward an acquisition. They want to build for the long run. This is a disagreement about direction, and it’s the most solvable version — it’s a conversation about strategy that can involve a board, an advisor, or structured offsite work.
Role and authority misalignment: You’ve grown past the stage where technical decisions and product decisions were the same thing, and neither of you has adjusted to that. Your co-founder is used to having final say on product because in the early days, product was technology. That’s no longer true, and the new authority structure was never explicitly negotiated.
Trust erosion: This is the most dangerous one and the most common substrate for everything else. Decisions were made that felt unilateral. Commitments weren’t kept. Something happened — maybe a specific incident, maybe a slow accumulation — and one or both of you has stopped giving the other the benefit of the doubt.
Be honest with yourself about which of these you’re actually dealing with. Most co-founder conflicts have elements of all three, but one is usually primary.
The Trap of Letting It Drift
The most common mistake in this situation is believing that it will improve naturally as the company gets through its current pressures. It won’t. The next funding round, the next product launch, the next big customer — each feels like the moment when you’ll finally have the space to address this. That moment never comes, and the relationship erodes further with each avoidance.
The other trap is making personnel changes without addressing the underlying dynamic. Some CEOs in this situation start thinking about restructuring — bringing in a VP of Engineering, reducing the co-founder’s scope, renegotiating their role. Those can be legitimate moves, but if they’re done without a direct conversation about what’s happening, they land as an attack, not a solution. The co-founder feels managed out rather than brought into the problem.
What an Honest Conversation Actually Looks Like
The conversation most people avoid is the direct one: “I feel like we’re not aligned on X, Y, and Z, and it’s affecting how we work together. I want to understand what you’re seeing, and I want us to figure out how to fix it.”
This conversation is hard because it requires vulnerability and because the answer might be something difficult — a genuine strategic disagreement, an acknowledgment that the roles need to change, or a recognition that the trust problem is deeper than either of you has admitted.
A few things that help:
Go off-site. Don’t have this conversation in the office, over Slack, or squeezed between two other meetings. Give it real time and a neutral location.
Use a facilitator. A board member you both trust, a company advisor, or an outside executive coach can change the dynamic enough to make the conversation productive when you’re too close to it. This is not weakness. It’s smart use of resources.
Separate the relationship from the role questions. First, try to repair or clarify the personal trust and communication dynamic. Then, separately, address whether the structure of your roles makes sense for the company’s current stage. Conflating these two things makes both harder.
The Structural Question: Have You Outgrown Each Other?
Sometimes co-founder conflict isn’t about communication or trust — it’s about the company genuinely needing something different from what either of you agreed to at the start.
The technical co-founder who was perfect for zero to $2M revenue is not always the right CTO for $2M to $20M. The skills are different. The work is different. The relationship with the engineering team needs to be different. If your co-founder is exceptional at hands-on technical work but struggling with the organizational and strategic scope that comes with growth, that’s not a personal failure — it’s a very common pattern.
This is the hardest conversation because it requires separating the person from the role, and in a co-founder relationship those two things are deeply entangled. But if you’re growing and one of you isn’t growing with the company, the honest conversation now is infinitely better than the crisis later.
What the Team Is Watching
Your engineers are not naive. When the two of you are in conflict, they know. They see it in how decisions get made and unmade. They feel it in the way certain topics go quiet. They hear it in the hallway conversations. The most talented ones are already updating their assumptions about whether this company is somewhere they want to be in 18 months.
The longer the misalignment is visible without being addressed, the more damage it does to the organization below you. The team takes their cues from the founders. If the founders can’t resolve conflict, the team learns that conflict here isn’t resolved — it’s endured.
Co-founder misalignment is one of the specific situations where having someone from outside the relationship can be genuinely useful — not to take sides, but to help structure a conversation that keeps getting avoided. In a 15-minute call, I can help you figure out whether what you’re describing is a structural problem, a trust problem, or something else — and what the next honest step looks like. Book a free 15-min call.
Related: Is My CTO in Over Their Head? | Technical Co-Founder Scaling Problem | First 90 Days as a New CTO
