How This Team Navigated Cofounder Conflict, and Tripled Their Revenue

FoundersMarcus (CEO), Alex (Head of Engineering), and Nate (CTO) — three cofounders building an AI workflow product for finance, YC alumni.

ServiceCo-Founder Conflict Coaching and Executive Coaching — a mix of individual 1:1s, group sessions, quarterly retros, and ongoing async support over an extended engagement.

Duration18+ months, ongoing.

Doubled team size

Grew from 3 cofounders to a team of 6, with a culture built on the cofounders' own relationship.

Tripled revenue

Grew 3.5x, from $300K to $1.1M ARR in 18 months, while navigating cofounder tension and a growing team.

Improved funding position

Raised an additional $500K on top of their seed round, and are on track for a Series A.


The Challenge: Everyone had their hands in everything, and it was starting to weigh on the founders

A lot had happened quickly since founding their AI startup. About eight months out of Y Combinator, the team had raised money, built an early product, and were just starting to establish a repeatable sales motion.

But all three cofounders were doing everything at once: hiring, sales demos, customer onboarding, product direction, figuring out who the ideal customer even was.

In that environment, the early cracks in a cofounder team seem unassuming at first. But every collision and misunderstanding starts to eat away at trust, while resentment grows.

This was a team where everyone cared deeply about each other and the company, but couldn't stop stepping on each other's toes. For a founding team with history going back years, this was newer territory, and it came with the pressure of building a company together for the first time.

Marcus wanted coaching. What the team needed was something more.

He wanted to level up as a leader, bring out the best in his team, and build a culture of joy and appreciation.

But with every client he closed and every hire he onboarded, the stakes grew. The weight of those expectations made it hard to sleep, hard to relax, hard to make tough calls without constant rumination.

So he came to me for 1:1 coaching, having found me through a shared Y Combinator network.

"One of the things that stood out was that Jason was a YC founder, had worked in tech startups, and so I felt like he could understand us better than a CEO coach."

— Marcus

As a former YC founder, I understand the specific context of what early-stage founders carry: the investor pressure, the product uncertainty, the weight of decisions that affect people's livelihoods. That shared context made it easier for Marcus to open up so we could talk about the real issues.

A few months into the engagement, he realized his cofounding team, Nate and Alex, could benefit from the same kind of thought partnership and emotional support.

"I think it's important to talk about things, and our societal culture doesn't really encourage that. It causes a lot of downstream problems. Having someone to facilitate us talking as a team would help."

— Marcus

It wasn't because things had fallen apart. It was because it became clear that the individual work could only go so far without also addressing how the three of them functioned as a team.


The Process

"Jason was thrown into the early cofounder conflict, but really took the time to get to know each of us as individuals."

— Alex

Individual sessions: getting to know each person first

Before any group work, I spent a significant number of 1:1 sessions with each founder, understanding their personality, values, motivations, and what triggered them. This wasn't done to take sides, but to build a full picture of what each person was carrying into the room.

"Those early sessions were him trying to situate himself and understand the dynamics between the three of us, putting the pieces of the puzzle together. He was thrown into some of the early cofounder conflict but really took the time to get to know each of us as individuals."

— Alex

This is where my coaching foundation gets built: helping each founder feel validated in their experience so they can start to see what the other person might be thinking or feeling. That includes small, trust-building actions they could take with each other before the next session.

Between sessions, I'd occasionally take a last-minute call, respond to a voice memo when something needed real-time attention, or review a Slack thread to get more context ahead of the next one. Work like this doesn't always stay inside the session window.

Skill-building: practical tools for the moments when it matters

The group sessions introduced frameworks I designed to support the kind of conflict that emerges inside a founding team, not dramatic blowups, but the slow accumulation of feeling unheard. Based on what I'd learned in the individual sessions, I leaned most on three of them:

  1. The listen-and-reflect technique: before responding, confirm you actually understand what the other person said. This wasn't about agreeing with them, but about proving you heard them.
  2. Positive need communication: instead of "stop doing X" or "be less Y," say what you actually need. "I'd really appreciate it if you could do A, or remember to ask me about B" sounds simple, but it changes the dynamic.
  3. Processing after a fight: a Gottman-inspired conflict resolution sequence that let the team understand what led to a conflict, without relitigating it.

"The Gottman-based exercise was fantastic, affirming positive needs and using clear frameworks for resolving conflict, rather than just talking it through without any structure. It was incredibly valuable for us."

— Marcus

We also worked on something specific to this team: how they share information. Nate began responding more in real-time when he could. Marcus learned to give him space to process and write things down first. Two small shifts, and the dynamic between them noticeably changed.

Going deeper: the insecurities that live outside the startup

Part of what makes cofounder conflict hard to resolve is that it's rarely just about the startup.

The anxiety a CEO carries about making the wrong call is connected to something older than the company. The frustration a cofounder feels about not being heard echoes patterns that existed long before one particular Slack thread.

I helped each founder acknowledge the insecurities that existed beyond the business: the worry about being self-taught, the need for praise and encouragement, the parts of themselves they brought into the founding team without ever naming them.

That work made the group sessions land differently. When you understand why someone reacts the way they do, conflict stops feeling like an attack and starts feeling like information.

Team infrastructure: beyond the relationship

As the engagement deepened, the work expanded into how the team operated day to day. I helped facilitate quarterly retros and check-ins, and worked with them to establish a clearer engineering process, from idea to design to code to deployment. I recently led a round of 360 feedback for all three founders.

The relationship work and the operational work were never really separate. A team that communicates well makes better internal decisions. And clearer internal decisions mean fewer relationship flashpoints.


The Results: By learning to handle conflict instead of moving around it, the founders could refocus on growing the company

A team that doubled without breaking

In 18 months, the founding team of three grew to a team of six. The company raised an additional $500K in funding and grew revenue 3.5x, from $300K to $1.1M ARR.

Those numbers don't happen without a functioning team at the center of them. Startups at this stage don't scale if the founders are spending their energy managing each other instead of building the company.

Several potentially catastrophic crises, avoided

This is the result that doesn't show up in a revenue chart.

Early-stage startups don't usually fall apart because the product failed. They fall apart because the people at the top stop being able to work through hard moments together: a hiring decision that becomes a standoff, a product direction that turns into a rift, a moment of frustration that becomes a fracture.

This team had those moments. They just didn't become catastrophes.

"Having Jason has been like a forcing function to offload a little bit of the burden that comes with dealing with conflict. Having someone to gather all the information from both sides, plant suggestions for how the other person might feel, and be a forcing function for self-reflection. It has improved our relationship, which by nature has helped our business."

— Alex

A CEO who leveled up

Eighteen months in, Marcus is a different kind of leader: more confident in his decisions, better at selling, and more secure in his team's support for him, which freed him up to actually lead instead of managing his own anxiety.

A cofounder who learned to be heard

Alex made real progress, both in his relationship with Marcus and, more recently, in navigating the growing pains that came as the engineering team expanded and new differences in working style emerged with Nate.

The team plans to keep working with me. The form of it will evolve, less individual coaching for some, more collective sessions for the team as a whole, because the investment in the relationship keeps paying off as the stakes keep rising.

"In the beginning, we didn't need Jason to resolve our problems because we didn't actually have that many of them. A couple of months in, we were under a lot of stress as a team because we'd just started the company and there was a bit of in-fighting between the three of us as founders, driven by a lack of product direction and maybe a lack of traction. So it's been very helpful having him in the mix."

— Marcus

As the company grows, the cofounders have more to handle. But they've learned to self-reflect and move through conflict instead of around it.

"Jason's coaching style is empathetic, geared toward self-realization, as opposed to telling you, 'This is the issue, this is the problem.' It was never definitive, which forces the person on the other side to do their own self-reflection. It's really just a muscle. The more you do it in the sessions, the more conscious you are of those things when you're actually in the heat of the moment."

— Alex

Names and identifying details changed. Quotes are from recorded sessions and client feedback. Outcomes are real.


Even the closest friendships can fracture under the weight of building something together.

Cofounder relationships are different from any other. You're peers, there's no higher authority to resolve your differences, and walking away is too difficult. That relationship has to be personally and emotionally strong enough to survive the hard periods, the ones where you don't have results, you don't have answers, and the only thing holding the company together is whether you still trust and respect the person sitting across from you. Most cofounder breakups don't come from a single blowup. They come from the small stuff that builds quietly, slowly making itself known, until it's too loud to ignore.

Fix that inside Co-Founder Conflict Coaching →

← Back to Case Studies