Mishneh Torah, Divorce 8 · Startup voice, On-ramp

Hook

Founders are addicted to "conditional" thinking. We structure our lives and businesses around "if-then" scenarios: If we hit ARR targets, then we raise the Series B. If the lead dev commits, then we ship the feature. We treat these conditions as flexible, assuming we can iterate on the terms as we go. But as any founder who has tried to rewrite a term sheet post-signature knows, reality is unforgiving.

The text in Mishneh Torah, Divorce 8 is not about marriage; it is a masterclass in the mechanics of contractual finality. Rambam teaches that when you create a condition, you are creating a new legal reality. If the condition is sloppy, twofold-deficient, or poorly timed, the entire agreement collapses. Founders often treat "handshake" conditions or side-letters as soft, thinking they can "fix" them later if the wind blows differently. Rambam argues the opposite: once the instrument (the "get") is in play, the power to modify it vanishes. The dilemma is simple: do you have the discipline to define your conditions with absolute precision before the action, or are you comfortable with your business being legally and operationally void because you were too lazy to clarify the "if" and the "then"?

Analysis

Insight 1: The Principle of Pre-Conditioning (Fairness)

Rambam establishes four non-negotiable rules for any conditional agreement: the condition must be twofold, positive before negative, stated before the action, and physically possible to perform. He writes, "If one of these rules was not kept... the stipulation is nullified; it is as if there were no condition at all."

Decision Rule: In business, "soft" milestones are the death of clarity. If you are setting a performance incentive or a vesting cliff, you cannot imply the condition—you must state it as a formal, twofold, pre-emptive clause. If you tell a team, "We will bonus if we grow," you have failed. If you say, "If we hit $1M ARR, you get $50k; if we don't, you don't," you have a valid contract. Fairness in business is not about kindness; it is about the total absence of ambiguity. If you don't define the "not" (the negative aspect), your agreement is a ghost.

Insight 2: The End of Modification (Truth)

"Therefore, once the get reaches the woman's possession, [the husband] can no longer nullify the get, add to his conditions or add a further condition." This is a harsh reality for the control-freak founder. Once you hand over the equity or the contract, you lose the right to move the goalposts.

Decision Rule: Your power to negotiate ends the moment you transfer the asset. Founders who attempt to "add a further condition" after the deal is signed are not just annoying; they are acting in bad faith. If you find yourself wanting to retroactively add a condition, you have lost the right to lead. Truth-telling requires acknowledging that the deal is done. If you want to change the terms, you must essentially "re-give" the deal—you must start from scratch. Stop looking for loopholes in your own signed contracts.

Insight 3: The Danger of "Doubtful" Status (Competition)

Rambam frequently uses the phrase "the status of the divorce is in doubt" (safek) when conditions are handled improperly. In the context of a startup, safek is the equivalent of a stalled fundraise or a blocked M&A exit.

Decision Rule: Ambiguity is a competitive disadvantage. If your partnership agreements or customer contracts are "doubtful" due to poorly worded clauses, you aren't just taking a risk—you are inviting paralysis. If a contract is written such that a court (or a lead investor) could look at it and say, "We aren't sure if this is valid," you have lost. You must prioritize legal hygiene as much as product velocity. A "doubtful" status is a hole in your cap table that will swallow your company during due diligence.

Policy Move

The "Instrument-First" Rule: Adopt a policy where no verbal or informal conditions are accepted for any high-stakes agreement (equity, revenue-share, or termination). Every conditional agreement must be explicitly written as a standalone addendum executed before the primary action (e.g., before the stock grant or the contract signing).

Process Change: Before signing any agreement with a condition, the Lead/Founder must answer these two questions in the comment section of the doc:

1. "Is the negative consequence (the 'then' if the condition fails) explicitly stated in the document?"
2. "If the counterparty fulfills the condition tomorrow, is there any ambiguity about whether the action is complete?"

If the answer is no, the document is rejected. No "we'll figure it out" clauses.

Board-Level Question

"Looking at our current commercial contracts and employee equity agreements, how many of them rely on 'implied' or 'understood' conditions that would fail a strict legal stress test?"

This forces your leadership to move from the mindset of "we know what we meant" to "what does the instrument actually say?" It shifts the conversation from intent (which is soft) to execution (which is measurable). As we are in the midst of Sukkot, a holiday that teaches us to dwell in a fragile structure (the Sukkah) while trusting in the absolute, unchanging nature of the law, let your contracts be like the Sukkah: defined by strict dimensions and rules, yet providing the safety to operate under a higher authority.

Takeaway

The law of the get is a reminder that in business, precision is a form of integrity. You cannot build a durable company on "understood" conditions. If your contracts are not airtight, your business is not real. You are either in the business of clear, binding, professional agreements, or you are in the business of "doubtful" outcomes. Choose clarity; it is the only way to scale.