Managing Resentment Between Cofounders as You Scale
The tell is disproportion. A late reply, a tone in a message, who presented at the board meeting — something small carries far more weight than it should, for both of you. That is the reliable signature of resentment, and it means there is a backlog: a set of things one or both of you has been keeping track of and not saying. Resentment is the most common way founding relationships end, and it almost never ends over the thing that finally triggers it. This page is about finding the backlog and clearing it.
What’s inside
Resentment is unexpressed accounting
The four ledgers
Why it attaches to small things
How to clear a backlog
The structural prevention
When it is already terminal
Where Blomma fits
Resentment is unexpressed accounting
Resentment is not an emotion so much as a running total. Somewhere in the background you are keeping score — of what you carried, what went unacknowledged, what you gave up — and the score is private because each individual entry seemed too small to raise.
That structure explains its behaviour. It compounds, because entries keep accruing and none get cleared. It is invisible to the other person, because nothing was ever said. And it eventually gets expressed at a magnitude wildly out of proportion to the triggering event, because the trigger is not what is being responded to.
It also explains why the usual repair fails. Addressing the trigger — apologising for the late reply, explaining the board meeting — clears one entry and leaves the total untouched. Both founders leave the conversation confused: one because the apology did not land, the other because they cannot explain why it did not.
So the work is not managing the feeling. It is finding out what is on the ledger and clearing it entry by entry, which is more tedious and considerably more effective.
The four ledgers
Four categories account for nearly all founder resentment. Most founders have entries in more than one.
Load.Who carried more — hours, scope, the unpleasant work, the risk. The most common ledger and the fastest-compounding, because entries accrue weekly. It is also the one most distorted by information asymmetry: you have complete data on your own effort and partial data on theirs, so both of you can be honestly convinced you carried more.
Recognition.Who got credit. Externally — press, investors, the market’s story of the company — and internally, in front of the team. This ledger fills fastest for the non-CEO founder, because the external narrative defaults to the CEO regardless of anyone’s intent. Rarely raised, because complaining about credit feels petty, which is exactly why it accumulates.
Authority.Who got to decide, and who found out afterwards. Every decision made without consultation is an entry. This ledger is the one most reliably fixed by structure rather than conversation, because its cause is undefined decision rights.
Sacrifice.What each of you gave up outside the company — salary, another opportunity, health, a relationship, time with family. Almost never discussed, and the deepest, because it is not about the company at all. A founder who took a lower salary for three years while their cofounder had other income has an entry that no amount of operational fairness addresses.
Name which ledgers are live for you. Founders who do this often find the loudest current argument sits in one ledger while the real backlog is in another.
Why it attaches to small things
The disproportion is diagnostic, and understanding the mechanism makes it less bewildering for both parties.
A small event is safe to have a reaction to. Raising “I have carried this company for two years and you have not acknowledged it” is enormous, exposing, and hard to say without sounding aggrieved. Raising “you were forty minutes late to the leadership meeting” is available, proportionate on its face, and does not require you to make yourself vulnerable.
So the small thing becomes the vehicle. You are not angry about the lateness; the lateness is admissible evidence for a case you have not filed. And your cofounder, responding reasonably to the lateness, is answering the wrong charge — which is why they experience your reaction as excessive and you experience their response as dismissive.
The practical use of this: when either of you notices disproportion, treat it as a signal to look for the ledger rather than an argument to win. The question “what is this actually about?” asked without sarcasm is the most useful sentence available in a founding relationship.
How to clear a backlog
A backlog is cleared in a dedicated conversation, not in the flow of work. Some structure helps.
Prepare separately, in writing.Each of you writes what is on your ledger — specific entries, in the four categories. Not accusations; entries. This is the step that does most of the work, because half of what surfaces has never been articulated even privately.
Set the terms before you start.Both of you will hear things that feel unfair, and the agreement is that nobody defends in the first pass. The purpose of the first pass is disclosure, not resolution. Founders who allow defence in the first pass never get past entry three.
Go one at a time and acknowledge before you respond.“I didn’t know you felt cut out of the pricing decision” before any explanation. Acknowledgement is what clears an entry; explanation, offered first, preserves it.
Expect the asymmetry and do not litigate it.One of you will have a longer ledger. That is not evidence of who was wronged more; it is partly personality. Comparing list lengths is the fastest way to waste the session.
Separate what needs an apology from what needs a structural change.Most entries need the second. Load imbalance needs a redivision of roles. Authority entries need written decision rights. Recognition entries need a deliberate change in how credit is shared. Sacrifice entries mostly need to be heard, and sometimes need terms adjusted.
Then close it explicitly.Say out loud that the ledger is cleared, and mean it — which means not reintroducing cleared entries in future arguments. Reintroducing them is the thing that makes founders unwilling to do this exercise twice.
Allow two sessions. One to disclose, one to decide what changes.
The structural prevention
Clearing a backlog is remedial. Preventing one is a matter of frequency and a small number of habits.
Raise things in the week they happen. The whole mechanism of resentment is accumulation, and accumulation is defeated by frequency rather than courage. A founding relationship absorbs a hundred small corrections easily and cannot absorb one two-year backlog.
Hold a standing founder session that is explicitly not status — fortnightly, for what is drifting. Its existence means raising something does not require creating an occasion, which is the barrier that produces most silence.
Write down decision rights, which removes the authority ledger almost entirely. Most authority resentment is not about losing a decision; it is about not knowing whether you had the right to it.
Redivide roles annually from the outcomes up, which catches load imbalance before it has been running for years.
And share credit deliberately, especially if you hold the CEO title. The external narrative will default to you, permanently, and correcting it costs you very little.
When it is already terminal
Sometimes the backlog is too large or too old to clear, and it is worth recognising the markers rather than running the exercise four times.
Entries that keep regenerating after being acknowledged. If clearing one surfaces two older ones indefinitely, you are not working through a backlog; you are looking at a relationship where the accounting has become the relationship.
Acknowledgement that does not reduce the charge. If your cofounder hears an entry, genuinely accepts it, changes something — and the resentment is undiminished — that suggests the resentment is no longer about the entries.
And resentment that has become identity. When one founder’s account of the company is primarily a story about what they endured, the ledger has stopped being a list and become a lens.
In those cases the honest path is renegotiating the arrangement substantially or separating, rather than another clearing session. That is not a failure of effort; it is information about what the effort has already established.
Where Blomma fits
The reason backlogs go uncleared is that the first step — articulating what is actually on your ledger — requires admitting things that feel small, petty, or vulnerable. Most founders have never said them to anyone, and the person they would normally think out loud with is the person the list is about.
Blomma is an always-on AI career coach with no stake in the relationship. Use it to write your ledger honestly, including the recognition and sacrifice entries that feel too petty to name — those are usually the load-bearing ones. Use it to sort each entry into what needs acknowledging versus what needs a structural change, which is what stops the session from becoming an emotional exchange with no output. Use it to prepare for the entries on their list that you expect to find unfair. And use it to notice, in the moment, when a disproportionate reaction to something small means you have a ledger you have not opened. Where the situation warrants a human, or a third party in the room, bring one in..
Resentment is the most common ending for founding relationships and among the most preventable, because it is not caused by disagreement. It is caused by a hundred small things that were true and never said.