Renegotiate cofounder roles whenever the company changes shape: a fundraise, a first senior hire in a founder's area, crossing about 20 people, or one founder quietly picking up work nobody assigned. Write down what each of you really does today, agree who owns which decisions, and date the new split so you can revisit it.
Why don't founding roles survive growth?
Because they were assigned by whoever was in the room at the start. At the start, two or three people split everything and titles are placeholders. The "CTO" is whoever writes the code. The "COO" absorbs whatever nobody else is doing.
Growth breaks that. New functions appear, like sales, people and finance. Old ones get too big for one person, and engineering turns into a team with its own managers. Ed Batista notes that as the company grows larger and more complex the co-founders' roles and responsibilities will diverge. The founder closest to the work early on is not automatically the right person to run it at ten times the size. That is normal. It means the agreement needs a way to change. Our guide to cofounder roles and responsibilities shows how to name scope precisely the first time, which makes every later change easier.
What should trigger the conversation?
Events that give you a reason that is not personal. First Round calls milestones like a fundraise or hiring senior leaders natural points to reassess whether a co-founder's title still fits their work.
- A first executive hire in a founder's area. Hire a head of engineering or sales while a co-founder runs that function, and their scope changes whether anyone names it or not. Name it before the hire starts.
- Crossing about 20 people. Y Combinator observes that below about 20 employees most companies have everyone report to the founder, and that what works at 20 can be disastrous at 40. Management layers have to form, so you have to decide who manages whom.
- A fundraise. The work that gets you to one round is often not the work that gets you to the next. Even if the CEO title stays put, what it requires day to day changes.
- Scope nobody assigned. The least visible trigger and the most common. Nobody decided the generalist would own finance, but they do now. That deserves a name and a decision.
Why do founders avoid it?
Because it can feel like a demotion. A co-founder whose title stays "CTO" while their scope shrinks to engineering can feel the loss, even when the company is healthier for it and their equity has not moved. Raising it can sound like telling a partner they are out of their depth.
Underneath sits a harder question: does my partner still think I can grow into this, or are they easing me out? Say that fear out loud. If the tension has become a real disagreement, our guide to cofounder conflict resolution shows how to keep the conversation from turning into a rupture.
How do you structure the renegotiation?
Skip "how do we feel about our roles". Start with what is on the ground.
- Write down current scope. What each of you decides, owns and gets asked about today, whatever your title says. Do not debate it yet. Seeing it written down is often a relief.
- Compare it to the original split. The gap between what each of you was meant to do and what you do now is the agenda.
- Agree the new split. Decide who owns which calls. Settle titles last.
- Write it down and date it. Verbal agreements about who owns what fade fast. Put it in your founder operating agreement, with the date and the reason.
- Set the next trigger. The next raise, hire or headcount milestone. First Round's advice on the co-founder pact is simple: revisit it regularly.
Why aren't titles the same as decision rights?
Because a title moves nothing on its own. If "Head of Product" becomes "Chief Product Officer" but still needs the other founder's sign-off on the same calls, the working relationship has not changed, and the resentment comes back.
Decision rights are the layer under the title: who approves a hire in a function, who owns the budget, who sets the roadmap without checking in, who speaks for the company to which investors and customers. Pilot's guide is blunt that with more than two co-founders you must really understand who is actually in charge, and who owns what. Spell this layer out. When a first executive joins in a founder's area, define both people's decision rights at the same time. Our piece on onboarding an executive without breaking alignment covers how.
Frequently asked questions
- How often should cofounders renegotiate roles and titles?
- Tie it to events rather than the calendar. A fundraise, a first senior hire in a founder's area, and the point where everyone can no longer report to a founder are the natural moments. Between those, talk about how your roles are changing in your regular check-ins so drift never builds up unnoticed.
- Is renegotiating roles the same as changing titles?
- No. A new title without a matching change in who decides, who holds the budget and who hires is cosmetic. The renegotiation has to name which calls each founder owns. The title is the least important output, and changing it alone usually brings back the same resentment within a few months.
- What if a cofounder refuses to talk about roles?
- Refusal is usually fear of demotion, not disagreement about the facts. Start by writing down the scope each of you already holds today, since it is hard to argue with what someone is already doing. If the refusal lasts, treat it as a warning about how harder talks, like equity or an executive hire, will go.
- Should a first executive hire trigger a role renegotiation?
- Yes, and before the hire starts. If you bring in a head of sales while a cofounder has been running sales, that cofounder's scope shrinks whether anyone says so or not. Agree the new split, and what the cofounder takes on instead, before day one, so the new hire inherits a clear remit.