CEO vs. Cofounder: Navigating the Power Dynamic

One of you is CEO and one of you is not. In the first year that was a formality for the incorporation documents and a name for investors to email. Somewhere between thirty and a hundred people it becomes real, and the asymmetry that both of you agreed was meaningless starts producing consequences neither of you has discussed. This page is written for both sides, because the non-CEO cofounder’s position is genuinely under-examined and the honest version of it is worth stating plainly.
What’s inside
The asymmetry is real, and usually undiscussed
What the title actually changes
Four ways the dynamic goes wrong
What the CEO owes the other founder
The non-CEO cofounder’s actual position
Making it explicit
Where Blomma fits
The asymmetry is real, and usually undiscussed
Most founding pairs handle the title by deciding it does not mean much. That is sincere and it stops being true at scale, for reasons that have nothing to do with either person’s intentions.
The company creates the asymmetry whether you want it or not. Investors treat the CEO as the accountable party. The board’s relationship is with the CEO. Employees work out who has the final say and route accordingly. Press and candidates default to the CEO as the company’s voice. Every one of those is an external force acting on your internal arrangement, and collectively they will produce a hierarchy regardless of what you two agreed.
So the choice is not whether there is an asymmetry. It is whether it is explicit or ambient. Explicit is considerably better for both founders: the CEO gets clarity on what they actually decide, and the other founder gets a defined role instead of a slowly narrowing one. Ambient asymmetry is what produces the specific injury of a founder discovering, over two years, that they have less authority than they thought and nobody ever said so.
The conversation is awkward precisely because you both said it did not matter. Having it anyway is the whole job.
What the title actually changes
Worth being concrete, because the vagueness is where the damage lives.
Final say on shared decisions.In practice, when the two of you cannot agree, the CEO decides. This is the substance of the title and the part most often left unstated. Saying it out loud is better for both of you than the alternative, which is discovering it during a disagreement.
Accountability to the board.The CEO answers for the company’s performance. That is a real weight, and it is a legitimate reason the CEO’s judgment carries more on questions of company direction.
Ownership of the external narrative.The CEO is the default voice to investors, press, and the market. This has a cost for the other founder that is rarely acknowledged — their contribution becomes less visible externally, permanently.
Default routing of ambiguity.Anything undefined ends up with the CEO. This is the mechanism by which a non-CEO founder’s scope narrows without any decision being made.
What the title does not change: it is not a judgment of capability, it does not make the CEO’s domain expertise better than the other founder’s, and it does not entitle the CEO to override a co-founder inside a domain that founder owns. Those distinctions need stating, because in practice they get eroded by the routing effect above.
Four ways the dynamic goes wrong
The CEO overrides inside the other founder’s domain.Usually with good intentions and on something they care about. Each instance is defensible; the pattern tells the other founder that their ownership is conditional, and it tells the whole company the same thing. This is the most common failure and the most damaging, because it removes the other founder’s authority in front of an audience.
The non-CEO founder relitigates decisions after they are made.In hallways, with their own team, or by slow non-execution. Understandable when they feel unheard, and it undermines the company more than a direct argument would — and it produces exactly the distrust that leads to being cut out further.
The scope narrows with nobody deciding it.No conversation, no announcement. Meetings happen without them, new senior hires arrive with authority they were not consulted on, decisions get made and reported afterwards. The founder experiences this as being sidelined and cannot point to a moment, which makes it almost impossible to raise without sounding aggrieved.
The CEO title is nominal and nobody decides anything.The opposite failure. A CEO who will not exercise the final say produces a company where genuine disagreements never resolve, executives cannot tell who to follow, and everything contested stalls. This is worse for the other founder too, because ambiguity is where their scope quietly disappears.
What the CEO owes the other founder
If you hold the title, four obligations that are not optional if you want the relationship to last.
Consult before deciding in their area, genuinely.Most founder resentment about decisions is resentment about not having been asked. Being consulted properly is what makes not deciding tolerable, and it costs you an hour.
Do not override inside their domain, and if you must, do it privately and explain why.The private part matters as much as the reasoning. An override in front of the team is a public statement about their standing.
Tell them when their scope is changing, before it changes.Structural change communicated by structural change is the cruellest version, and it is the default unless you deliberately do otherwise.
Share the external credit deliberately.The narrative will default to you. Redirecting some of it — in board meetings, in press, internally — is a small effort and it addresses a real and permanent asymmetry.
And one more: say plainly what the title means. A CEO who leaves the authority ambiguous to avoid an awkward conversation is transferring the discomfort onto the other founder, who now has to guess.
The non-CEO cofounder’s actual position
The part that most content about founding teams skips.
Your authority is real but derived, and that is worth understanding rather than resenting. What you own, you own because it is defined — not because being a founder confers it. Which means the most valuable thing you can do is get your ownership written down: which outcomes, which decisions, what escalates. Undefined authority erodes; defined authority holds.
The signals you are picking up are probably accurate. Founders in this position routinely doubt their own perception because nobody confirms it. Scope narrowing, decisions elsewhere, new hires with more latitude — those are real, and you are not imagining them.
Raise it yourself rather than waiting. This is the highest-value move available and it inverts the dynamic: a founder who says “I think my scope has drifted and I want to talk about what I actually own” is negotiating from strength. A founder who waits until they are resentful is negotiating from grievance.
And decide what you actually want. The assumption that you should want more authority is worth testing. Plenty of founders are more valuable and considerably happier owning a deep domain than a broad one — and choosing that deliberately is a completely different outcome from having it happen to you by drift.
What does not work: relitigating decisions after the fact, building a case privately, or using the team as an audience. Those feel like the available options when you have no defined authority, and each of them accelerates exactly what you are trying to prevent.
Making it explicit
One session, and the output is a page.
Name the four things the title actually carries, and confirm you both agree. This is the conversation neither of you has had, and most of the value is here.
Write down what each founder owns — outcomes, and the decisions inside them. Confirm the non-CEO founder holds real decision rights, not just responsibility.
Agree what happens on genuinely shared decisions, including the deadlock rule. “The CEO decides” is a legitimate answer and it needs to be said, along with how the other founder’s dissent gets heard.
Agree the consultation norms and the override protocol — what the CEO does when they need to overrule something in the other founder’s domain.
Then revisit annually, because scope drifts every time the company changes size, and an annual redivision is how you catch drift before it becomes grievance.
Where Blomma fits
This is a conversation both founders avoid for opposite reasons. The CEO avoids it because asserting the authority feels like a demotion of someone they respect. The other founder avoids it because raising it feels like admitting they have less standing than they thought.
Blomma is an always-on AI career coach with no stake in your arrangement. If you hold the title, use it to work out what you actually want the title to mean and how to say it without it landing as a demotion — and to check honestly whether you have been overriding inside your cofounder’s domain. If you do not hold the title, use it to test whether the signals you are reading are real, to work out what you genuinely want to own over the next three years, and to prepare the conversation as a negotiation from strength rather than a grievance. Where the situation warrants a human who has been in a founding pair, bring one in..
The power asymmetry between a CEO and a cofounder is structural, permanent, and entirely workable — provided it is stated. What does not work is the arrangement most founding pairs default to, where both of you agree it does not matter and then spend three years discovering that it does.
