Mishneh Torah, Marriage 6

Hook

The greatest risk a founder faces isn’t a competitor or a market shift; it is the "implicit assumption." We negotiate deals, hire executives, and sign term sheets based on unspoken expectations. We operate under the delusion that if we meant something, the other party must have understood it. But in the high-stakes world of venture, an unstated condition is a liability waiting to be litigated.

The Rambam, in Mishneh Torah, Marriage 6, lays out a rigorous framework for conditional agreements. He isn’t just talking about marriage; he’s providing a masterclass in risk mitigation for commercial contracts. The "founder dilemma" is the gap between a handshake and a contract. If your conditions aren't explicit, twofold, and legally sound, you are building your company on quicksand. The Rambam forces us to stop "jesting and teasing"—the professional equivalent of "we’ll figure it out later"—and instead demands the precision of a surgeon. If you aren't defining your terms clearly, you aren't just being "founder-friendly"; you are being professionally negligent.

Text Snapshot

"Every [valid] conditional agreement whatsoever - whether with regard to kiddushin, divorce, commercial transactions or other questions of business law - must conform to the following four rules... a) the stipulation must be twofold [with both a positive and negative statement]; b) the positive aspect must be stated before the negative aspect; c) the stipulation should be mentioned before the completion of the deed... d) the stipulation must be something that is possible to comply with." Mishneh Torah, Marriage 6:1-2

Analysis

Insight 1: The Principle of Explicit Duality

The Rambam insists that a condition must be "twofold," stating both the positive and negative consequences. In business terms, we call this defining the "happy path" and the "exception handling." Founders often get excited about the "what if we succeed" scenario but neglect the "what if we fail" reality. If your partnership agreement says, "We will split equity 50/50," but fails to state, "If the CTO leaves within 12 months, the equity reverts," you have failed the Rambam’s test. A condition that is not stated in both directions is effectively an absent condition. It leaves the door open for ambiguity, and in court, ambiguity is always resolved against the drafter.

Insight 2: Sequencing is Strategy

The Rambam mandates that the stipulation be mentioned before the deed. In startup life, this is the difference between a "condition precedent" and a "condition subsequent." If you close a deal and then try to add a requirement, you are effectively negotiating from a position of weakness. You have already granted the benefit; now you are begging for the concession. The Rambam teaches that the condition is the architecture of the deal, not the trim you add at the end. If you have already transferred the IP or the cash, you have lost your leverage to dictate the terms of the exchange.

Insight 3: The "Impossible Condition" Test

The Rambam highlights that if a stipulation is impossible to fulfill—like "ascend to the heavens"—the entire condition is disregarded as "jesting and teasing." Founders frequently fall into this trap by promising impossible KPIs to investors or VCs to secure funding. When you set milestones that cannot be achieved, you are effectively signing a contract that has no legal standing. This isn't just unethical; it’s a failure of business logic. A condition must be within the capacity of the parties to fulfill. If your business model relies on a counterparty doing the impossible, you aren't building a company; you are engaging in "jesting and teasing" with your stakeholders' capital.

Policy Move

The "Conditional Rigor" Protocol (CRP): Implement a mandatory "Clause Review" for every contract or MOU exceeding $50k in value. No deal is finalized until the "Four Rules" are applied to every major contingency:

1. The Double-Bind: For every "If X happens, then Y," there must be a written "If X does not happen, then Z."
2. Pre-Deed Audit: The legal team must certify that the stipulation is recorded prior to the execution of the primary benefit (e.g., funding, transfer of assets).
3. Feasibility Check: Every condition must be accompanied by a "feasibility memo" signed by the relevant department head, confirming the requirement is realistically achievable.
4. The "Nullity" Clause: If the above are not met, the default must be explicitly stated to protect the firm from being trapped in an ambiguous legal state.

KPI Proxy: "Days to Resolution of Contractual Ambiguity." (Goal: Move this to zero by requiring that no contract is signed without the four rules being met).

Board-Level Question

"If we were to face a catastrophic failure of this partnership tomorrow, which of our current contractual 'conditions' would be thrown out by a judge because they were poorly phrased, stated too late, or were fundamentally impossible to achieve? Are we operating on 'handshake' logic, or are we operating on 'Mishneh Torah' precision?"

Takeaway

The Rambam isn't interested in your intentions; he is interested in your stipulations. In business, intentions are irrelevant—only the explicit, twofold, pre-deed, and possible conditions survive the test of time. If you cannot articulate the negative case as clearly as the positive case, do not sign the deal. Stop teasing the market, stop teasing your investors, and start building with the cold, hard precision of a mensch. Precision is the ultimate form of respect for your counterparty and the ultimate defense for your equity.