Daily Rambam · Startup Mensch · On-Ramp

Mishneh Torah, Eruvin 8

On-RampStartup MenschJune 28, 2026

Hook

Founders are addicted to "optionality." You build your cap table, your product roadmap, and your GTM strategy with the intention of keeping every door open for as long as possible. You want the Series A funding and the exit path; you want the enterprise contract and the PLG scale. We treat our business architecture like a hedge fund, constantly hedging against the future to ensure we aren’t caught in a "locked-in" state.

But here is the brutal reality: Optionality is often a euphemism for lack of commitment. When you try to be everywhere, you end up being nowhere. This week’s text from the Mishneh Torah, Eruvin 8—a chapter detailing the laws of establishing a "Sabbath boundary"—isn’t about theology; it’s about the physics of focus. Rambam teaches us that if you try to establish two contradictory foundations for your "place," you end up with the intersection of both, which is often a smaller, more restricted space than if you had simply picked one.

In business, when you hedge your strategy so aggressively that you fail to commit to a singular direction, you don't double your reach. You effectively gridlock your organization. You cannot scale by keeping your options open; you scale by choosing a boundary and owning it.

Analysis

Insight 1: The Fallacy of Bifurcated Strategy

Rambam writes: "One may not deposit two eruvin—one in the west and one in the east—so that one will be able to walk [in either direction]." Mishneh Torah, Eruvin 8:1. The logic is clear: you are defining your "place." If you attempt to define your company’s core identity as "the enterprise platform for X" and "the consumer tool for Y" simultaneously, you don't get the benefits of both markets. You get a diluted brand and a confused team.

Decision Rule: Consistency creates capacity. When you choose one direction, you gain the full 2,000-cubit range of that strategy. When you split your focus, you are limited to the "area common to both," which is mathematically smaller. In startup terms, if you dilute your focus between two disparate user personas, your product will satisfy neither. Your "Sabbath limit" (your effective market reach) shrinks to the overlap—the lowest common denominator of both strategies.

Insight 2: Conditional Planning vs. Strategic Commitment

There is a fascinating exception in the text: "It is permissible for a person to establish two eruvin... and make the following stipulation: 'If tomorrow there is a necessity that arises... it is this eruv that I am relying upon.'" Mishneh Torah, Eruvin 8:3. This isn't about doing two things at once; it’s about contingency planning.

Decision Rule: Decouple your pivots from your core. You can have a "Plan B," but you must define the trigger. Rambam notes that if the person doesn't choose, the eruv is of no consequence, and they remain in their original city. If your company is constantly in "conditional mode" without a clear, stated trigger, your team is effectively paralyzed, waiting for a decision that never comes. You must define the "mitzvah or necessity" (the market signal) that forces the pivot. Without the trigger, your conditional strategy is just indecision disguised as agility.

Insight 3: The Cost of "Preparation"

Rambam warns against performing work on a holiday for the sake of the next day: "It is forbidden to prepare on the Sabbath for a holiday or on a holiday for the Sabbath." Mishneh Torah, Eruvin 8:17. He emphasizes that these are "two different expressions of holiness."

Decision Rule: Respect the sanctity of the current sprint. Startups often fail because they are so busy "preparing for the next round" or "building for the next feature set" that they fail to execute the current one. If you are in a "Sabbath" (a period of intense focus on existing customers), don't sabotage it by treating it as a training ground for your next "Holiday" (a new product launch). When you try to build the next iteration during the current one's cycle, you pollute the data, the focus, and the team's output. Success is found in completing the current cycle before initiating the next.

Policy Move

The "Single-Threaded Boundary" Policy. Most organizations struggle with cross-functional drift because they try to manage "dual-track" goals that aren't actually aligned. I propose an immediate policy shift: Every project lead must declare their "Eruv" for the quarter.

  1. The Declaration: At the start of every quarter, each department head must submit a single "Boundary Statement." This statement defines where their team’s influence stops and where their primary objective sits.
  2. The Constraint: If a team tries to claim two, they must provide the "trigger clause"—the specific KPI that, if hit (or missed), forces them to abandon one and commit fully to the other.
  3. The Audit: If a team is found to be "carrying" (doing work that serves a future, uncommitted goal at the expense of current deliverables), they are in violation of the policy.

KPI Proxy: Resource Allocation Ratio (RAR). Measure the percentage of engineering/ops hours spent on "Core Deliverables" (The Eruv) vs. "Hedging/Speculative Work." If your RAR drops below 80% on core work, you have effectively created two eruvin and halved your team’s effective speed.

Board-Level Question

"We are currently pursuing a dual-strategy (Strategy A and Strategy B). If we were forced to cut our resources by 50% tomorrow, which of these two 'bounds' would we abandon instantly to save the other? If we cannot answer that immediately, why are we currently maintaining the overhead of both?"

This question forces the board and the executive team to confront the reality of their "Sabbath limit." It moves the conversation from the comfort of "keeping options open" to the necessity of strategic survival. It exposes whether the current "two-track" approach is a calculated contingency or a lack of conviction.

Takeaway

The law of eruvin isn't about building fences; it’s about defining your territory so you can move within it freely. A founder who refuses to pick a path isn't being "strategic"—they are being indecisive. Rambam shows us that by trying to cover two directions at once, you end up trapped in the center.

Stop hedging. Start boundaries. Pick your Eruv.