Dear SaaStr: How Do You Deal With an Unreliable Co-Founder?

Dear SaaStr,

My co-founder is… inconsistent. Sometimes they’re brilliant and all-in. Other times they vanish, miss deadlines, “forget”
meetings, and I’m left explaining to customers (and my own stress hormones) why the roadmap is now a work of fiction.
We split equity early, we’re friends-ish, and I’m trying to build a real companynot a reality show called
Where Did My Co-Founder Go? What do I do?

Signed,
Trying to Build, Not Babysit

First: you’re not “dramatic.” An unreliable co-founder is not a minor inconvenience. It’s a structural risklike building
your house on a trampoline. The goal isn’t to “win” against your co-founder. The goal is to protect the company, your
customers, your team, and your own ability to keep showing up.

Here’s the playbook founders use when they want to be fair, move fast, and still sleep occasionally. It’s part
communication, part operations, part legal hygieneand yes, part grown-up breakup talk.

Step 0: Confirm the Problem (Because “Unreliable” Has 4 Different Meanings)

“Unreliable” is a symptom. Before you jump to “fire the co-founder” (or “move to a cave”), get specific about what’s
actually happening. Most cases fall into one of these buckets:

1) Capacity problem

They might be overloaded, dealing with personal constraints, or simply in the wrong role. They’re not malicious; they’re
mismatched.

2) Commitment problem

They like the idea of being a founder more than the work. They show up when it’s fun (vision, brainstorming,
podcasts) and disappear when it’s hard (shipping, selling, support).

3) Clarity problem

The company has fuzzy ownership. No one knows who owns what, so everything becomes optional. Optional work becomes
unreliable work.

4) Integrity problem

This is the red-alert category: they misrepresent progress, blame-shift constantly, or create chaos that forces you to
cover for them. If reliability is low and trust is eroding, you’re not fixing a workflowyou’re fixing a fracture.

Your next steps depend on which bucket you’re in. So let’s translate “unreliable” into observable facts.

Step 1: Build a Simple “Reality Dashboard” (No Drama, Just Data)

You don’t need a 40-slide performance review. You need a one-page scoreboard that answers: “What did we agree would
happen, and did it happen?”

• Commitments: deliverables, meetings, customer calls, code releases, hiring tasks
• Deadlines: what date/time “done” meant
• Impact: what slipped because they didn’t deliver (customer, revenue, product, team)
• Pattern: one-off misses vs. repeated misses

This matters because founder conflict often becomes a fog-of-war problem: feelings and assumptions replace shared facts.
The dashboard is your flashlight. Also, it keeps the conversation from becoming a courtroom drama where Exhibit A is a
screenshot from three months ago.

Quick gut-check: if you’re hesitant to write commitments down because it feels “too harsh,” that’s a sign you’re already
compensating for unreliability. Healthy teams love clarity. Only flaky systems fear it.

Step 2: Have the Conversation You’ve Been Avoiding (With Structure)

The biggest mistake founders make is waiting until they’re furious. Anger is honest, but it’s a terrible project manager.
Instead, schedule a dedicated 60–90 minutes. No phone. No Slack. No “quick sync.” This is a co-founder meeting, not a
drive-by complaint.

A simple script that doesn’t light the building on fire

1. Start with the shared mission: “I want us to build a great company together.”
2. State facts: “We agreed on X by Friday. It didn’t happen. This has happened Y times this month.”
3. State impact: “I had to cover customer calls and rewrite the plan. It’s hurting trust and velocity.”
4. Ask for their reality: “What’s going on? Is this a capacity issue, a role issue, or a commitment issue?”
5. Decide outcomes: “Let’s pick a clear plan for the next 30 days and evaluate honestly.”

Keep your tone calm and direct. Think “adult airline pilot,” not “angry podcaster.” You’re not performing. You’re solving.

Use “nonviolent communication” energy, not “Twitter thread” energy

A surprisingly effective approach is to separate observation from interpretation.
“You missed three customer calls” is an observation. “You don’t care” is an interpretation. Lead with observations. If
you need to discuss motivation, do it after the facts are on the table.

Also: slow down. Founders love speed. But in conflict, speed can turn into a bulldozer that flattens trust. If you rush,
you’ll “resolve” the conversation and then re-live it every week forever.

Step 3: Re-Draw Roles and Decision Rights (Because Co-CEO Energy Creates Confusion)

A lot of co-founder unreliability is actually role ambiguity. When two people feel like they own everything, they
often own nothing. Make the org chart realeven if the “org” is currently two humans and a dream.

• One owner per outcome. Example: “Revenue pipeline is owned by Alex. Product shipping is owned by Sam.”
• Define decision domains. Who decides on pricing? Hiring? Roadmap changes? Fundraising timelines?
• Clarify CEO responsibilities. Someone must be accountable for the company-level calls.

This is not about ego. It’s about accountability. If you’re both “co-CEOs” in practice, you may be accidentally creating
a system where no one is fully on the hook. If you do keep shared leadership, you still need a tiebreaker mechanism:
board, advisor, or explicit domains.

Step 4: Install an “Accountability Operating System” (So You’re Not Managing by Vibe)

If your company runs on vibes, the most charismatic person winsand the most reliable person burns out.
Replace vibes with a lightweight operating cadence:

Weekly co-founder meeting (non-negotiable)

• 15 minutes: scoreboard review (what shipped, what sold, what broke)
• 15 minutes: commitments for next week (3–5 max per person)
• 15 minutes: risks and decisions
• 15 minutes: “co-founder health” check (what’s working, what’s tense)

Written commitments (one shared doc)

Make it boring and obvious. The magic is that it exists. If your co-founder consistently refuses to commit in writing,
you just learned something important.

Escalation rules

• 24-hour rule: if a deadline will be missed, flag it at least 24 hours before (with a new date and reason)
• No silent slips: surprises are the enemy of trust
• Two misses = review: repeated misses trigger a reset conversation, not another “it’s fine” shrug

This system feels “corporate” until you realize the alternative is “chaos,” which is just corporate with worse snacks.

Step 5: Tie Equity to Reality (Vesting Exists for a Reason)

Let’s talk about the part founders avoid because it feels awkward: equity and control. If your co-founder isn’t
performing, you must protect the cap table. Not to punish thembecause the cap table is the company’s future.

The norm: founder vesting (usually 4 years with a 1-year cliff)

Many startups use time-based vesting so ownership is earned through continued contribution. Common structures include a
one-year cliff (nothing vests until month 12) and then monthly vesting thereafter. The point is simple: if someone stops
contributing early, they don’t keep all the upside from other people’s work.

Founder stock repurchase / buyback rights

In many setups, the company can repurchase unvested shares if a founder leaves. That can be the difference between a
clean separation and a multi-year cap table headache.

Don’t DIY legal moves while emotional

If you’re heading toward a change in equity, roles, or separation, consult a startup attorney. You want to handle:

• Unvested shares treatment (repurchase rights, forfeiture mechanics)
• IP assignment (make sure company code/work belongs to the company)
• Confidentiality and post-departure access
• Tax details (including things like 83(b) elections in restricted stock situations)
• Founder “leaver” terms (some companies differentiate “good leaver” vs “bad leaver” scenarios)

Founder breakups are common. The best ones are boring, documented, and fair. The worst ones are emotional, ambiguous,
and litigated. Aim for boring.

Step 6: Decide Whether You’re Repairing… or Replacing

After the conversation and the operating system, give it a defined windowtypically 30 days (maybe 60 if there’s a
legitimate capacity/health constraint and they’re actively addressing it). Then evaluate using the same scoreboard you
created earlier.

Green flags (repair is working)

• They acknowledge the pattern without defensiveness
• They show consistent improvement quickly (not perfectionconsistency)
• They proactively communicate risks before deadlines
• They accept role clarity and accountability

Red flags (replacement or separation is likely)

• They deny facts that are clearly documented
• They get angry at the existence of accountability
• They make promises without behavior change
• Trust keeps shrinking, even when you try to fix process

One brutal founder truth: indecision has a cost. If you keep waiting for a person to become someone else, the company
pays the billin lost customers, lost morale, and your own burnout.

Step 7: If You Need to Separate, Do It Like a Professional (Not Like a Subtweet)

Co-founder separation should feel calm and final, not chaotic and vengeful. Here’s what “clean” looks like:

1) Make the decision, then communicate once

Don’t negotiate with yourself for three months. Decide privately (ideally with counsel/advisors), then talk. Aim for one
clear message: “This isn’t working. Here’s the separation plan.”

2) Offer a fair off-ramp

Depending on contribution and situation, an off-ramp might include:

• Keeping what’s vested (if any)
• A consulting transition period (short, defined, paid if appropriate)
• A title adjustment (e.g., from co-founder to advisor) if they’re staying involved in a limited way

3) Protect the company

• Revoke access (email, repos, payroll, banking) on a planned timeline
• Confirm IP and confidentiality obligations
• Update cap table and paperwork

4) Communicate to the team and customers with confidence

Keep it simple: “X is transitioning out. We appreciate their early work. Here’s what changes (and what doesn’t).”
Don’t air grievances. Your customers want reliability, not lore.

If you have investors or serious prospects, tell them promptly with a calm plan. Most experienced investors have seen
founder changes before; what scares them is not the changeit’s the chaos.

Step 8: Prevent the Sequel (Because Your Next Co-Founder Shouldn’t Be a Surprise)

Whether you repair or replace, treat this as a systems lesson. Co-founder relationships need maintenance. Some founders
literally write “co-founder vows”explicit agreements about communication, conflict, and expectationsand revisit them
periodically.

Simple prevention moves that actually work

• Monthly retro: what’s working, what’s not, what needs to change
• Quarterly role reset: as the company evolves, roles must evolve
• Conflict rules: surface conflict early; don’t smooth it over
• Founder agreements: vesting, IP, decision rights, separation mechanics

A co-founder relationship is like a two-person product. If you don’t maintain it, bugs multiply. If you fix issues when
they’re small, you rarely need dramatic rewrites.

Specific Examples (Because Advice Is Cheap and Context Is Everything)

Example A: The “Brilliant But Missing” Technical Co-Founder

The CTO-type co-founder delivers heroic bursts, then disappears for days. The CEO is stuck translating silence into
confidence for customers. The fix often starts with role clarity and cadence:

• Define a weekly shipping target (small, frequent releases)
• Set a “no-ghosting” rule for customer-impacting issues
• Move big projects into smaller milestones with dates
• If the pattern continues, consider reducing scope: they own core architecture, not every deliverable

If they can’t operate with predictable cadence, you may need a new engineering leadeven if they remain involved as an
advisor. The company needs reliability more than legend.

Example B: The Sales Co-Founder Who Loves Talking, Hates Follow-Through

They’re fantastic on the first call and vanish when it’s time to update CRM, send follow-ups, or run the pipeline.
The fix is measurable output:

• Weekly pipeline review with “next steps” documented
• Minimum activity metrics (calls, emails, demos) tied to outcomes
• Clear ownership: they own revenue, not “good vibes in the market”

If they resist measurement, you may be dealing with a commitment problem, not a skills problem.

of Founder “Experience” Patterns (What People Usually Learn the Hard Way)

Founders who’ve dealt with unreliable co-founders often report the same surprising lesson: the situation rarely improves
through hints, patience, or heroic compensation. It improves through clarityor it ends through a clean separation.
Here are a few common “from the trenches” patterns (shared as composites, not as any single real company):

Pattern 1: The Reliability Gap Becomes a Culture Tax

In early-stage startups, the team watches the founders like hawks. If one founder misses commitments and the other
quietly covers, the company learns a dangerous rule: reliability is optional if you’re senior enough. Even with a tiny
team, this can show up fastmissed internal deadlines, fuzzy ownership, and “someone will handle it” thinking. The fix
founders describe most often is public clarity: each founder owns specific outcomes, and weekly commitments are visible.
Not to shame anyonejust to make reality shared. Once the team sees that commitments matter for everyone, momentum
returns and resentment fades.

Pattern 2: “Friendship First” Can Quietly Kill the Startup

When co-founders are friends (or former classmates), founders often delay direct feedback because they don’t want to be
“mean.” The irony: avoidance usually hurts the friendship more than the honest conversation would have. The most
successful friend-founder pairs tend to separate “people love” from “business accountability.” They’ll say something
like, “I care about you, and I also need the company to work.” They use written commitments as a neutral toolso it’s
not one friend nagging another; it’s the plan checking the results. Many founders say that once they finally got direct,
the friendship either stabilized (because expectations were clear) or the breakup became kinder (because they stopped
building resentment in silence).

Pattern 3: The Turning Point Is Usually a Deadline With Consequences

Founders often describe a moment when they realized the pattern wasn’t “a rough patch.” It was the system.
The turning point comes when they set a short, specific window30 dayswith measurable expectations and a pre-decided
fork in the road. For example: “We will ship these three milestones, hold these customer calls, and maintain weekly
founder check-ins. If we do this consistently, we continue. If not, we change roles or separate.” The key detail is the
consequences are real. Without consequences, the window becomes theater.

Pattern 4: Clean Separations Protect Everyone’s Future

When separations go well, founders often emphasize how “boring” the process felt: clear paperwork, respectful language,
and fast operational handoffs. The departing founder keeps dignity. The remaining founder keeps the company.
The team gets stability. Customers get continuity. And investors get a signal that leadership can make hard calls. In
contrast, founders who postponed the decision too long often describe the opposite: a slow erosion of trust, increasing
conflict, and a cap table mess that made fundraising harder than it needed to be.

The punchline (the unfunny one): unreliability doesn’t just slow you downit quietly changes who you become as a leader.
You start planning around absence. You start tolerating ambiguity. You start carrying two jobs. The “right” move is the
one that restores a truthful system: clear commitments, clear ownership, and a team that can trust what’s promised.

Final Take

Deal with unreliability like a founder, not a roommate. Get specific, install accountability, and make a decision on a
real timeline. If your co-founder steps up, greatyou just leveled up your operating maturity. If they don’t, you’re not
“being harsh.” You’re protecting the company from becoming a lifelong group project where only one person gets a grade.

Build with adults. Ship with adults. Raise money with adults. And if you can’t, adjust the team until you can.