The Clause No One Wants to Write

What the Agreement Actually Covers

A founder posted this week about a co-founder split that ended six years of partnership and cost him $140,000 in legal fees, lost clients, and equity disputes. His conclusion, after working through the full accounting of what the breakup required, was that he would still take a partner if he started over. He would take a partner because going solo is slower and lonelier than most people who have not done it understand. But he would do one thing differently. He would write down, on day one, exactly what happens the day they stop. That sentence contains every lesson most founders learn only after they have already paid for it.

The standard partnership agreement covers the mechanics of beginning. Equity splits, vesting schedules, role definitions, intellectual property ownership, non-compete terms. These are the clauses both sides negotiate with genuine care, because they govern the period when both parties are aligned and motivated, when the company is new and the relationship has not yet been tested by anything more complicated than a shared vision and a signed document. The dissolution clause sits at the back of the same agreement, drafted quickly, reviewed briefly, and signed with the implicit understanding that it is the section you will never need, because the partnership will work, because you have already agreed on so much, because the alignment feels real and the momentum feels durable.

The dissolution clause is treated as the pessimistic section. The one written for a version of the future neither side believes in at the time of signing. This is the exact mechanism by which most partnership failures become as expensive as they do.

The Cost of the Missing Structure

When no one has written the exit, every difficult conversation eventually has to build the framework for ending while simultaneously surviving the conflict that made ending necessary. The partner who wants out and the partner who does not are not simply negotiating the relationship in those conversations. They are constructing the rules of the negotiation in real time, under emotional pressure, without a shared reference point, while also trying to keep the business operational, the team stable, the clients unaware, and the story coherent for whoever is watching from the outside.

This is not a negotiation. It is an improvisation performed by people who are already in pain, over terms that should have been settled when both parties still trusted each other's judgment. The founder who posted this week spent $140,000 on a problem that a well-drafted document would have reduced to a procedural disagreement. The cost was not primarily financial. It was the six months of operational paralysis, the three key hires who left because the company felt unstable, the client relationships that went cold because neither partner knew who had the authority to maintain them while the dissolution was in progress. The legal fees were the most visible number. The damage underneath them was larger and less countable.

The behavior pattern that produces this outcome is not carelessness. It is optimism, structured as a decision. The founders who skip the dissolution framework are not naive about the fact that partnerships fail. Most of them have watched other partnerships fail, have read the post-mortems, have used words like "aligned" and "complementary" with specific care precisely because they have seen what happens when those qualities are assumed rather than verified. They skip the clause anyway, because writing it requires imagining, in concrete procedural detail, what the end of this particular partnership looks like, and that imagination produces a feeling that most founders interpret as bad faith.

Writing the dissolution clause feels like planning to fail. It is actually planning to survive.

The Document That Changes the Conversation

The founders who build the most durable partnerships are not the ones who never face dissolution. They are the ones who faced it in paper form before it became a live situation, who sat across from their future partner in the first month of the relationship and worked through, explicitly and without comfort, exactly how the company would be unwound if the partnership did not hold. That conversation is uncomfortable in a way that produces real information. The partner who resists the conversation reveals something. The partner who approaches it without defensiveness reveals something different. The document that comes out of it is worth less than the process of creating it, because the process is the first real test of how both sides handle a disagreement that neither of them wants to be having.

The structure of a dissolution framework is not legally exotic. It covers client ownership and continuity, which partner retains which vendor relationships, how IP is divided or licensed, what happens to the brand, how team members are allocated, and what the payout timeline looks like for any partner buyout. Most of this is already determined implicitly by the operational reality of the business, meaning one partner runs the client relationships and one runs the product, one partner holds the vendor accounts and one holds the bank relationships. Writing it down does not create the division. It acknowledges the division that already exists, and gives both parties a reference point that was built in a moment of trust rather than in a moment of conflict.

The founder who posted about his $140,000 breakup was not describing a failure of chemistry or vision or even strategy. He was describing the cost of a governance gap that both parties agreed, implicitly, to leave open. They left it open because filling it required a conversation about failure at the exact moment when everything felt like it was succeeding. That timing is not coincidental. It is the condition under which most founders decide to skip the clause, because the partnership is young and the relationship is warm and the cost of the conversation feels higher than the probability of ever needing the document.

The probability calculation is exactly backwards. The partnership that starts well enough to feel like it will never need the clause is the partnership most likely to need it, because it has been built on the assumption that the alignment will hold, and assumptions that are never tested do not hold under the kind of pressure that mature partnerships eventually produce. Founders who understand this build the framework first, before the business is large enough to make the conversation complicated, before the equity is valuable enough to make the division contentious, before either party has developed a private narrative about what the partnership owes them that the other side has never heard.

onSpark was built to surface the right partnerships before the agreements are written, matching founders on the specific operational and behavioral factors that predict performance under pressure. But the clause itself, the one that governs the day the pressure exceeds what the relationship can hold, belongs to the founders. Write it while you still like each other. The document will not make the relationship worse. The absence of it will.