How to announce a cofounder's departure to the team

Announce a cofounder's departure to the team by leading with what is changing, confirming what is not, and naming who people can go to with questions, in one meeting rather than a trickle of messages. Say it before word spreads on its own. A gap of even a few hours gives rumor more room to work with than the truth ever gets.

What should you say when a cofounder is leaving?

Say what is changing, say what is not, and say who owns the decisions that used to run through the person leaving. Those three lines matter more than any explanation of why.

People rarely panic over the departure itself as much as over what it means for them day to day. Will their manager change. Will the roadmap hold. Will payroll run on time. Answer the practical questions before anyone has to ask them out loud in front of colleagues. If you cannot answer one yet, say so plainly and give a date when you will.

Who should hear the news first?

The board or key investors hear it first, then anyone who reports directly to the departing cofounder, then the rest of the team together in one sitting. Customers and partners come after the team has heard it, never before.

This order protects the people closest to the change from finding out secondhand. A direct report who learns from a group chat that their manager is leaving starts the transition already distrusting how it is being handled. Tell them in person, even briefly, before the wider meeting.

What exactly should the announcement cover?

Cover five things, in order, and nothing else needs to be improvised in the room.

• What's changing: the departing cofounder's role, who inherits their responsibilities, and any reporting lines that move
• What isn't changing: the product roadmap, customer commitments, pay, and benefits
• Who to go to: name the specific person for day to day questions starting now, not "we'll figure it out"
• Timing: last working day, effective date, and whether there is a transition period
• What comes next: when there will be a follow up, even if the answer is just a date on the calendar

Write this down before the meeting as a short document, not notes in your head. If you read from it, you are less likely to get pulled into questions the room is not ready to hear answered yet.

How do you stop rumors before they start?

Deliver one message, live, to everyone who needs to hear it, on the same day. Rumors fill whatever gap you leave open, and a staggered rollout where some people know for a week before others creates exactly that gap.

Limit who knows in advance to the people who need to plan around it, like whoever is covering the departing cofounder's work on day one. Everyone else should hear it from you, in the room, at the same time. If someone outside the company could plausibly hear it first, such as a close customer or an investor who talks to your team, tell the team before that call happens, not after.

What has to change in your agreements after a cofounder leaves?

Equity, decision rights, and who signs off on what all need updating in writing, not left as an assumption carried over from when there were two of you. A departure is exactly the moment old agreements stop matching reality.

This is what a Blueprint is for: one written document of who owns what, how decisions get made, and what happens if someone leaves, that you both signed and keep current. If the departure follows a disagreement that never got resolved, settle that first. A Conflict Session gives each of you space to write your account alone, then puts one joint summary in front of both of you, so the version you bring to the team is one you have actually agreed on. If you are the one leaving, our guide on telling your cofounder you want to leave covers that conversation. If the partnership itself is ending, read the cofounder breakup guide for what to settle before you tell anyone else.