Daily Rambam · Startup Mensch · Standard
Mishneh Torah, Eruvin 8
Hook
The tech ecosystem is obsessed with a lie called "optionality."
Your venture capitalists tell you to keep your options open. Your product managers tell you to build highly extensible, abstract architectures so you can pivot easily. Your sales team wants to chase both Enterprise whales and transactional SMBs at the same time. You are told that in a volatile market, the winner is the one who holds the most open doors.
This is a fatal strategic error. Optionality is not free; it has a devastating carrying cost.
When you refuse to commit to a single direction, you do not double your opportunities. Instead, you paralyze your organization. Your engineering team builds half-baked features for two different user personas. Your marketing budget is split down the middle, failing to achieve a critical mass of customer acquisition in either segment. Your sales reps write custom contracts that your customer success team cannot support.
By trying to expand your boundaries in opposite directions simultaneously without a clear, pre-defined decision rule, you do not get the best of both worlds. You get squeezed into what the Sages call the "overlap zone"—the narrow, stagnant intersection where your conflicting strategies cancel each other out. You end up with zero momentum, a burning runway, and a team suffering from strategic whiplash.
This is the exact operational crisis that Maimonides addresses in the eighth chapter of Hilchot Eruvin. The laws of eruvin—the physical and legal boundaries that dictate where a person can walk and carry on the Sabbath—are not just ancient ritual mechanics. They are a masterclass in spatial economics, resource allocation, and strategic commitment.
The Rambam lays down a hard, uncompromising law: you cannot establish two boundaries in opposite directions for the same day. If you try to play both sides without a structured, pre-declared conditional framework, the law strips you of your mobility. You are restricted to the narrowest common denominator. If you push the contradiction to its limit, you are legally paralyzed—you cannot move from your place.
As a founder, you must understand that strategy is not about what you choose to do; it is about what you choose not to do. If you do not define your boundaries before the market closes, the market will define them for you, and the results will be highly restrictive.
Let us analyze how the mechanics of the Rabbinic eruv can save your startup from the paralysis of unstructured optionality, and teach you how to build a highly disciplined, execution-oriented operational framework.
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
"One may not deposit two eruvin - one in the west and one in the east - so that one will be able to walk for a portion of the day [in the direction of] one of the eruvin, and to rely on the second eruv for the remainder of the day. [The rationale is that] one may not make two eruvin for a single day...
If a person erred, and established two eruvin in two different directions, because he thought that this was permitted, or he told two people to establish an eruv for him, and one established an eruv to the north and one established an eruv to the south, he may walk only in the area common to both of them...
Therefore, if one established an eruv 2000 cubits to the east and the other established an eruv 2000 cubits to the west, the person may not move from his place."
— Mishneh Torah, Eruvin 8:1-2
Analysis
Insight 1: The Trap of Unstructured Optionality and the "Overlap Zone"
The core strategic hazard of the startup journey is the split focus. In Mishneh Torah, Eruvin 8:1, the Rambam states:
"One may not deposit two eruvin - one in the west and one in the east - so that one will be able to walk for a portion of the day [in the direction of] one of the eruvin, and to rely on the second eruv for the remainder of the day."
An eruv t'chumin is a physical deposit of food placed up to 2,000 cubits from a town's boundary before the Sabbath, which legally establishes that spot as the person's "home" for the day. This allows them to walk an additional 2,000 cubits from that new point.
The human desire is natural: "I want to walk 2,000 cubits East in the morning to visit a friend, and 2,000 cubits West in the afternoon to attend a lecture." You want to capture two distinct market opportunities in a single operational cycle.
But the Halachah is unyielding: "one may not make two eruvin for a single day." Mishneh Torah, Eruvin 8:1 Why? Because your identity—your strategic center of gravity—can only be in one place at a time. You cannot have two operational centers of gravity. If you attempt to establish two centers of gravity, you violate the integrity of your boundaries.
What happens when you ignore this rule? The Rambam details the exact mathematical penalty for this error:
"If a person erred, and established two eruvin in two different directions... he may walk only in the area common to both of them."
Mishneh Torah, Eruvin 8:2
Consider the math of this penalty. If you send two agents to establish boundaries—one who deposits an eruv 1,000 cubits to the East, and another who deposits an eruv 500 cubits to the West—you do not get a combined 3,500 cubits of mobility. Instead, your mobility is restricted to the intersection of the two overlapping zones. You are permitted to walk only 1,000 cubits to the West and 1,500 cubits to the East.
If you push this to the extreme—placing one eruv at the absolute Eastern limit (2,000 cubits) and another at the absolute Western limit (2,000 cubits)—the overlap is zero. The result?
"the person may not move from his place."
Mishneh Torah, Eruvin 8:2
This is the ultimate Halachic metaphor for startup gridlock.
When you allow different departments in your company to set up conflicting operational boundaries, you paralyze the firm.
If your VP of Product (Agent A) builds features to support a high-volume, low-touch PLG model (West), and your VP of Sales (Agent B) promises highly customized, high-touch integrations to close an enterprise pilot (East), they have placed two eruvin in opposite directions.
They did this "because they thought that this was permitted" Mishneh Torah, Eruvin 8:2—they framed it as "hedging our bets" or "maximizing market reach."
But because these two strategies require completely different engineering, support, and marketing architectures, the company cannot execute either.
The customer support team is overwhelmed by enterprise demands they aren't staffed to handle, while the self-serve product funnel is broken because engineering resources were diverted to build custom APIs.
The company is caught in the "area common to both of them" Mishneh Torah, Eruvin 8:2—the dead zone of mediocrity. You cannot acquire enterprise clients because your product lacks enterprise-grade security, and you cannot acquire SMBs because your product is too complex. You are legally, operationally, and financially unable to move from your place.
[West Eruv: PLG / SMB] <--- (Your City / Current State) ---> [East Eruv: Enterprise Whales]
| |
Requires: Self-serve, Requires: Custom APIs,
automated onboarding, high-touch support,
low price point. long sales cycles.
\ /
\ /
v v
[STRATEGIC GRIDLOCK: The "Area Common to Both" is empty space]
* Result: Burning runway, zero growth, organizational paralysis.
Insight 2: Operationalizing the "If-Then" Pivot (The Principle of B'reirah)
The Torah is not blind to the reality of market volatility. It does not demand that you blindly march off a cliff in one direction when the environment changes. The Rambam provides a highly sophisticated mechanism for managing uncertainty, but it requires absolute structural discipline:
"It is permissible for a person to establish two eruvin in two opposite directions and make the [following] stipulation: 'If tomorrow there is a mitzvah or a necessity that arises and requires me to walk in this direction, then it is this eruv that I am relying upon, and the other eruv is of no consequence...'"
Mishneh Torah, Eruvin 8:2
This is the Halachic basis for a structured, disciplined pivot. The Sages rely on the legal principle of b'reirah (retroactive clarification or selection). Under this principle, when the Sabbath begins, your legal home is retroactively determined to be at the location of the eruv that corresponds to the necessity that actually arose.
But notice the critical constraint: the stipulation must be declared explicitly before the Sabbath begins.
You cannot wake up on Saturday afternoon, look at the weather, and casually decide which eruv you want to use. The conditional logic must be locked in, codified, and signed off before the period of twilight (beyn hash'mashot).
As Steinsaltz notes in his commentary on Mishneh Torah, Eruvin 8:2, b'reirah is a powerful tool in Rabbinic law, but it is not a license for opportunism. It is a tool of pre-calculated adaptability.
In startup operations, this means you are allowed to have a Plan A and a Plan B, but you are not allowed to execute them simultaneously, nor are you allowed to decide which one to execute based on raw, real-time emotion without pre-established triggers.
A disciplined founder does not say: "We are building an AI developer tool, but maybe we will sell it to marketing teams if things don't work out." That is unstructured optionality.
A disciplined founder says: "We are building an AI developer tool (Plan A). We have deposited our primary resources here. However, we have established a conditional eruv (Plan B): if our customer acquisition cost (CAC) for developers exceeds $150 for three consecutive months, or if our product-market fit (PMF) score remains below 40% after 1,000 signups, we will execute our pivot to marketing teams on day 91. If those triggers do not hit, Plan B is of 'no consequence' Mishneh Torah, Eruvin 8:2, and we will not spend a single dollar of capital or an hour of engineering time on it."
By codifying the "if-then" triggers beforehand, you protect your team from the psychological trauma of constant micro-pivots. You establish a clear, objective decision rule that retroactively validates your change of direction, preserving your organizational integrity and preventing the resource-splitting that leads to the "overlap zone."
Insight 3: The Reality of Resource Reachability (The "Fit to be Eaten" Rule)
Your backup plan is completely useless if you do not have the resources to execute it today. This is the hard truth of operational reach, codified by the Rambam in Mishneh Torah, Eruvin 8:11:
"The statement made previously... that a person may establish two different eruvin in two directions for two days applies only when it is possible for the person to reach both of the eruvin on the first day [without departing from his Sabbath limits]. If, however, it is impossible on the first day for him to reach the eruv for the second day, the eruv for the second day is invalid."
Why is the second eruv invalid?
"the mitzvah of eruv [can be fulfilled only] with a meal that is fit to be eaten while it is still day."
Mishneh Torah, Eruvin 8:11
If the food you deposited for the second day is located 3,000 cubits away, and your boundary for the first day only allows you to walk 2,000 cubits, you cannot physically reach that food on the first day.
Because you cannot reach it, it is not "fit to be eaten" by you during the critical transition period of twilight. Even though the food physically exists, and even though you own it, it is legally non-existent for you. Your option is void.
[Your House] =================== 2,000 Cubit Limit ===================> (Cannot Reach)
|
[Plan B / West Eruv]
(Located at 3,000 cubits)
* INVALID option.
* Not "fit to be eaten."
This is the exact failure mode of the "paper pivot."
Founders frequently pitch their board on a secondary market opportunity, a strategic partnership, or an enterprise sales motion that they claim serves as their safety net.
"If our self-serve consumer app fails to monetize," the founder argues, "we can easily pivot to licensing our proprietary algorithm to financial institutions."
But let us apply the Rambam's reachability test: Is that enterprise licensing deal "fit to be eaten" today?
Do you have an enterprise sales team? Do you have SOC2 Type II compliance? Do you have the balance sheet strength to survive an 18-month procurement cycle? Do you have the legal resources to negotiate master service agreements with Tier-1 banks?
If the answer is no, then that option is located 3,000 cubits away from your current operational limits. It is completely out of reach.
You cannot rely on it for "the second day" (your next funding cycle or strategic phase) because you cannot access it from your current position on "the first day."
Assuming an option is valid when you lack the capability to execute it is a form of corporate self-delusion.
If your runway is 6 months, and your pivot requires 12 months of R&D, your pivot does not exist. It is a meal that cannot be eaten while it is still day.
Your options must be physically, financially, and operationally realistic within your current boundaries, or they are a dangerous illusion that distorts your strategic reality.
Policy Move: The "Conditional Optionality Register" (COR)
To eliminate unstructured optionality and prevent your team from being trapped in the "overlap zone," you must implement a strict operational policy: The Conditional Optionality Register (COR).
No department, team lead, or executive is permitted to allocate resources, write code, or pitch clients on any strategic path that deviates from the core company focus unless that path is registered, quantified, and authorized under a strict conditional framework.
===========================================================================================
CONDITIONAL OPTIONALITY REGISTER (COR)
===========================================================================================
[Project Name] : Project Horizon (Enterprise Sales Pilot)
[Primary Focus] : B2B Self-Serve PLG Platform (Plan A)
-------------------------------------------------------------------------------------------
[1. THE TRIGGER] : If and only if self-serve signups fall below 5,000/month AND
average contract value (ACV) of inbound enterprise requests
exceeds $75,000 for two consecutive quarters.
[2. CAPARRYING COST]: Maximum 10% of engineering capacity (4 Sprints max) to build
basic enterprise auth (SAML SSO). Zero sales hires.
[3. THE REACH TEST]: Do we have the cash runway to sustain a 6-month enterprise sales
cycle? Yes (Current runway is 18 months).
Option Reachability Ratio (ORR) = 3.0 (Valid).
[4. THE EXPIRY] : If the enterprise pilot does not close within 120 days of trigger
activation, Project Horizon is declared "of no consequence" and
all resources revert to Plan A.
===========================================================================================
The Policy Implementation Protocol
Step 1: Establish the "Single Eruv" Default
The default state of the company is absolute focus. The executive team must define the "Primary Boundary"—the single customer persona, the single distribution channel, and the single product value proposition that the company is executing for the current planning cycle (e.g., the next two quarters). All OKRs, KPIs, and resource allocations must align with this boundary.
Step 2: Mandate COR Registration for "Hedging" Activities
If a product manager or executive wants to explore a secondary market, run a pilot in a different vertical, or build features for an adjacent customer segment, they must submit a formal COR proposal to the leadership team. The COR must define four parameters:
- The Explicit Trigger (The Stipulation): The precise, quantitative market signal or internal metric that will activate this option. This is your b'reirah clause. Until this trigger is pulled, no code is deployed to production, and no sales outreach is conducted.
- The Option Carrying Cost: The maximum amount of engineering, marketing, and capital resources allowed to be spent on preparing the option. This cost cannot exceed 10% of the total company bandwidth. If preparing the option requires diverting core resources from the primary boundary, the registration is rejected.
- The Reachability Test: A mathematical proof that the company possesses the capability, runway, and expertise to execute the option today without requiring external capital or miracles.
- The Expiry Date (The Sabbath Limit): The date upon which the option, if not activated by the trigger, is automatically terminated, wiped from the codebase, and declared "of no consequence."
Step 3: Implement the Option Reachability Ratio (ORR) KPI
To enforce the reachability rule of Mishneh Torah, Eruvin 8:11, every proposed option must calculate its Option Reachability Ratio (ORR) before it can be registered.
$$\text{Option Reachability Ratio (ORR)} = \frac{\text{Current Available Runway (in Months)}}{\text{Time to Liquidity/Execution of the Option (in Months)}}$$
- Rule of Execution: If the ORR is less than $1.5$, the option is invalid and cannot be registered. You do not have the operational "reach" to touch this option. You are forbidden from spending a single dollar or hour of developer time preparing for it. Focus all your resources on extending your primary boundary instead.
Board-Level Question
The Context
At your next board meeting, your venture capitalists will likely push you to expand your target addressable market (TAM). They will look at your flatting growth curve in your core market and suggest that you "explore enterprise opportunities" while simultaneously "keeping the self-serve developer motion alive." They will frame this as a low-risk way to explore new revenue streams.
This is a classic "two eruvin" trap. They are asking you to place an eruv in the East (Enterprise) and an eruv in the West (PLG) without a clear, conditional decision rule. They want the benefit of both markets, but they are not the ones who have to manage the operational friction, the split codebase, and the cultural division of the team. If you agree to this unstructured approach, you will end up in the "overlap zone," and your company will grind to a halt.
You must confront this advice directly, using a highly disciplined, analytical framework to force a decision.
The Question to Ask the Board
"If we commit our resources to pursuing both the enterprise sales motion and our self-serve product development over the next two quarters, we will split our engineering capacity and sales focus down the middle.
According to our internal metrics, our product-market fit score in our core self-serve market is currently 35%, and we have 12 months of cash runway.
If we split our focus, we will not achieve the product improvements required to scale self-serve, nor will we have the runway to survive the 9-month sales cycle required for enterprise procurement. We will trap ourselves in the middle—unable to close enterprise deals and losing our self-serve base.
Therefore, I want to ask the board: What is the single, quantitative trigger that will cause us to officially pivot from self-serve to enterprise, and are we prepared to completely shut down the self-serve motion and reallocate 100% of our engineering and marketing resources to enterprise the moment that trigger is pulled?
If we are not prepared to define that trigger today, we must reject the enterprise motion entirely and focus our remaining runway on dominating our core market."
===========================================================================================
THE BOARDROOM DECISION TREE
===========================================================================================
Are we pursuing both motions?
|
+---> YES (Unstructured)
| * Result: "Overlap Zone" / Paralysis.
| * High CAC, split engineering, dead company.
|
+---> NO (Halachic Focus)
* Define single Eruv (Primary Boundary).
* Set up COR for Plan B with explicit triggers.
* Execute with 100% operational alignment.
===========================================================================================
The Expected Pushback and How to Defeat It
Your board members will likely respond with standard VC platitudes:
- "We don't need to make a hard choice today. Let's just run a few enterprise pilots and see what happens."
- "We can walk and chew gum at the same time. Let's keep both doors open."
You must defeat this pushback with the logic of the Rambam's reachability and carrying-cost rules:
- Expose the Secret Carrying Cost: Explain that "running a few enterprise pilots" is not free. It requires SOC2 compliance, custom security reviews, legal negotiations, and dedicated support engineering. Show them the data: every hour your team spends on a custom enterprise pilot is an hour taken directly from your core product roadmap. You are setting up an eruv in the East that is pulling your Western boundary inward, shrinking your overall mobility.
- Apply the Reachability Test: Show them the math. If your enterprise sales cycle is 9 months, and your runway is 12 months, your ORR is $1.33$. According to the reachability rule, the enterprise option is invalid because you do not have the financial reach to survive the transition.
- Demand the "If-Then" Commitment: Insist on a written stipulation. If the board wants to pursue the enterprise pilots, they must agree to a specific trigger: "If we do not close at least $150k in contracted ARR from these pilots within 90 days, we terminate the pilots, delete the custom code, and return to 100% PLG focus." If they refuse to commit to this trigger, they are asking you to commit slow strategic suicide in the overlap zone.
Takeaway
The ancient Sages understood a fundamental law of human and organizational behavior: you cannot occupy two places at once.
If you attempt to expand your boundaries in opposite directions without a highly disciplined, pre-defined conditional framework, you do not double your freedom. You lose it.
You end up trapped in the "overlap zone"—the narrow, stagnant space of compromise where your conflicting strategies cancel each other out, leaving you unable to move from your place.
As a founder-friendly ethics coach applying the Torah to business, my advice to you is sharp and uncompromising:
- Pick Your Direction: Establish your "single eruv"
Mishneh Torah, Eruvin 8:1for the current operational cycle. Define your target customer, your core product, and your primary distribution channel with absolute clarity. Align 100% of your resources, your engineering team, and your marketing budget with this boundary. - Rule Out Phantom Options: Apply the reachability test of Mishneh Torah, Eruvin 8:11 to every "backup plan" or "pivot opportunity" in your deck. If you do not have the runway, the team, or the capabilities to execute that option today, it is not a plan—it is a dangerous distraction. Declare it invalid and remove it from your strategic roadmap.
- Codify Your Triggers: If you must build a backup plan, do not leave it to chance or real-time emotion. Use the principle of b'reirah
Mishneh Torah, Eruvin 8:2. Establish a Conditional Optionality Register (COR). Define the exact quantitative triggers that will activate the option, the maximum carrying cost you are willing to spend preparing it, and the precise date upon which it will expire.
Do not let the VC-driven obsession with "optionality" dilute your focus and paralyze your company. Define your boundaries, lock in your stipulations, and execute with the absolute, unyielding clarity of Halachic law.
Go build.
derekhlearning.com