Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 316:19-24
Hook
Every venture capitalist in Silicon Valley is obsessed with the concept of "moats." We are told that a great product is not enough; you must build high switching costs, construct proprietary lock-ins, and erect barriers to entry that make it impossible for your customers to leave. The goal, in modern business parlance, is to achieve "customer capture."
But as a founder, you have to ask yourself a brutal, late-night question: Is your customer staying with you because they love your product, or because you have taken them hostage?
There is a razor-thin line between a natural competitive advantage and predatory confinement. When you intentionally design your platform to make data extraction prohibitively expensive, when you use predatory terms of service to choke out competitors, or when you trap your users in a digital cage where the exit door is buried under layers of dark patterns, you are no longer a value creator. You are a trapper.
In the classical halakhic framework of Shabbat, one of the thirty-nine forbidden categories of creative labor is Tzeid (Trapping). The sages spent centuries defining the exact mechanics of what constitutes "trapping" an animal: What size space constitutes confinement? When is an animal considered already under your control? What if you close only one of two open doors?
These are not dusty, ancient debates about deer and flies. They are highly sophisticated legal and ethical analyses of confinement, control, and the moral limits of capture.
Applying the insights of the Arukh HaShulchan (Orach Chaim 316:19-24) to your startup’s product strategy, terms of service, and competitive positioning will reveal a hard truth: Artificial lock-in is a form of ethical bankruptcy that ultimately destroys long-term enterprise value.
If your business model relies on trapping your users rather than serving them, you are not building a sustainable moat; you are building a prison. And eventually, the prisoners will break out.
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
ארוך השולחן, אורח חיים ש"ט:י"ט-כ"ד "...כל שאינו מחוסר צידה, פירוש שאין צריך לרוץ אחריו לצודו אלא ניתרס ביד אחת או בפסיעה אחת, אין בו משום צידה..." "...ואם סגר הדלת בפני הצבי, הרי זה חייב משום צד. ואם היו שתי דלתות וסגר אחת מהן, אינו חייב עד שיסגור את השנייה..." "...כל שאין במינו ניצוד, פירוש שאין דרך בני אדם לצודו לצורך הנאת גופו או עורו... אם היו מזיקים, מותר לצודן שלא יישכו..."
Context
In these passages from Arukh HaShulchan, Orach Chaim 316:19-24, Rabbi Yechiel Michel Epstein delineates the boundary lines of the Shabbat prohibition of trapping (Tzeid). He explores the transition from a state of freedom to a state of confinement. The text analyzes three core variables:
- The physical effort required to secure an object (the "one-stride" rule).
- The sequential mechanics of closing off escape routes (the "two doors" rule).
- The intent and nature of the trapped entity (distinguishing between commercial exploitation and defensive containment of harmful pests).
Analysis
Insight 1: The "One-Stride" Rule — Natural Retention vs. Coercive Lock-In
In Orach Chaim 316:19, the Arukh HaShulchan introduces a fundamental metric for determining whether an act of trapping has occurred:
"...כל שאינו מחוסר צידה, פירוש שאין צריך לרוץ אחריו לצודו אלא ניתרס ביד אחת או בפסיעה אחת, אין בו משום צידה..." "Any creature that is not lacking trapping—meaning, one does not need to run after it to catch it, but rather it can be secured with a single hand-movement or a single stride—there is no prohibition of trapping in it..." Arukh HaShulchan, Orach Chaim 316:19
In the eyes of Halakha, if an animal is already so close and slow that you can reach out and grab it in "a single stride" (pesiah achat), it is legally considered already trapped. Closing a cage door around it does not change its status; it was already under your domain.
Translate this directly to your customer retention strategy.
There are two ways to keep a customer:
- Natural Utility: Your product is so integrated, valuable, and superior that the customer has no desire to run away. They are voluntarily within your "single stride" because of the immense value you provide.
- Coercive Lock-in: The customer wants to run, but you have constructed artificial barriers—exorbitant data egress fees, proprietary file formats, or punitive contract terms—that physically prevent them from leaving.
If your product relies on the second method, you are guilty of ethical Tzeid. You are taking an entity that wants to flee and actively trapping them.
Consider the modern SaaS landscape. When a cloud data warehouse provider charges nominal fees to upload data but levies massive, punitive fees to export that same data (egress fees), they are not winning on product. They are building a digital cage. They are waiting until the customer’s data is inside their walls, and then they are slamming the door shut.
The Arukh HaShulchan’s "one-stride" rule offers us a profound decision rule: If a customer’s decision to stay with your platform requires them to overcome artificial friction, you have crossed the line from value creation to predatory trapping.
The Decision Rule
Your customer retention must be driven by pull factors (product quality, customer service, continuous innovation) rather than push factors (contractual penalties, data hostage-taking, proprietary silos). If a customer wants to leave, the exit path must be as frictionless as the onboarding path. If onboarding takes "one stride," offboarding must not take a marathon.
Insight 2: The "Last Door" Fallacy — The Ethics of Sequential Lock-In
How do companies trap their customers? Rarely do they do it all at once. It is almost always a gradual, boiling-frog strategy. You start with an open platform, attract a massive developer ecosystem, and then slowly, systematically, shut down the exit points.
The Arukh HaShulchan addresses this exact multi-stage confinement process:
"...ואם סגר הדלת בפני הצבי, הרי זה חייב משום צד. ואם היו שתי דלתות וסגר אחת מהן, אינו חייב עד שיסגור את השנייה..." "If one closed the door in front of a deer, he is liable for trapping. But if there were two doors, and he closed only one of them, he is not liable until he closes the second door..." Arukh HaShulchan, Orach Chaim 316:21
This halakhic mechanics-of-confinement analysis is incredibly sharp. If a room has two open doors, closing one door does not constitute trapping, because the deer can still escape through the second. The legal liability—the completion of the act of Tzeid—occurs only when the final door is closed.
In business, founders often justify unethical, incremental lock-in policies by pointing to the doors they still leave open.
- "Yes, we deprecated our open API, but developers can still scrape our public pages!" (Closing the first door).
- "Yes, we banned web scraping, but users can still manually export their data to CSV!" (Closing the second door).
- "Yes, we made CSV exports limited to 100 rows at a time, but they can still copy-paste!" (Closing the final door).
You cannot escape ethical liability by pointing to the fact that the trap is not yet fully sealed. If your strategic roadmap is designed to systematically close every alternative exit until the user has no choice but to pay your monopoly rent, you are executing a trapping strategy.
This is exactly what happened in the famous API deprecation wars of the early 2010s and continues today with major social media networks and platform giants. Platforms built their entire valuation on the backs of third-party developers who built apps using their open APIs. Once the platforms achieved critical mass, they closed the doors one by one, effectively trapping the users and killing the businesses of the developers who helped build them.
The Arukh HaShulchan teaches us that we must look at the ultimate outcome of our sequential decisions. If the closing of the "second door" is the inevitable final step in your monetization strategy, then you are a trapper from the moment you close the first door.
The Decision Rule
You must maintain platform transparency. If you market your platform as "open" to attract users or developers, you cannot retroactively close the doors of interoperability once they are locked inside. Any change to data portability or API access must be grandfathered in for existing users, ensuring that the "doors" they entered through remain open to them.
Insight 3: The "Noxious Pest" Exception — Ethical Boundaries of Defensive Containment
Is trapping ever permitted? In the physical world, we do not treat a rabid dog or a venomous scorpion the same way we treat a harmless deer. The Halakha recognizes this critical distinction:
"...כל שאין במינו ניצוד, פירוש שאין דרך בני אדם לצודו לצורך הנאת גופו או עורו... אם היו מזיקים, מותר לצודן שלא יישכו..." "Any creature whose species is not normally hunted—meaning, it is not the way of people to hunt it for the benefit of its body or its hide... if they are harmful, it is permitted to trap them so that they do not bite..." Arukh HaShulchan, Orach Chaim 316:23
Here, the Arukh HaShulchan draws a brilliant ethical line between two types of trapping:
- Commercial Exploitation: Trapping an animal for its "body or its hide"—i.e., to extract commercial value from its confinement. This is strictly forbidden on Shabbat.
- Defensive Containment: Trapping a "harmful pest" (mazikin) to prevent it from causing injury or damage. This is permitted because the intent is not exploitation, but protection.
In the business ecosystem, this distinction is highly relevant to how you handle competitors, bad actors, and IP litigation.
As a founder, you will face threats. You will face malicious scrapers trying to steal your proprietary data, patent trolls trying to extort you, and bad actors attempting to disrupt your platform. In these cases, using aggressive "trapping" mechanisms—such as IP blocking, defensive patent litigation, or restrictive covenants—is ethically defensible. You are trapping a mazik (a harmful pest) to protect your creation.
However, many founders use these defensive tools as a pretense for offensive, anti-competitive market capture. They use patent portfolios not to protect their unique innovations from theft, but to "trap" early-stage competitors in endless, expensive litigation that they cannot afford. They use overly broad non-compete agreements to trap low-level employees who pose zero threat to the company’s intellectual property, simply to suppress wages and prevent talent mobility.
If you are trapping to extract value from the confinement of others (commercial exploitation), you are on the wrong side of Torah ethics. If you are trapping strictly to prevent documented, objective harm to your platform or people (defensive containment), your actions are justified.
The Decision Rule
Audit your legal and technical defensive measures. Are your non-compete agreements, patent filings, and platform blocks designed to protect your legitimate assets from clear, harmful threats (mazikin), or are they designed to commercially exploit and suffocate fair competition? If it is the latter, you are violating the ethical boundaries of defensive containment.
THE ETHICAL TRAPPING MATRIX
High | -----------------------------------------
| | |
| | UNETHICAL TRAP | NATURAL MOAT
| | (Coercive Lock-In) | (High Product Value)
| | |
CUSTOMER | -----------------------------------------
VALUATION |
| [One-Stride Rule]
| Customers stay because
| it is naturally easy.
|
Low | -----------------------------------------------------------------
| | |
| | DEFENSIVE SHIELD |
| | (Harmful Pests Only) |
| | |
| -----------------------------------------------------------------
+------------------------------------------------------------------
Low High
CUSTOMER FREEDOM
Policy Move: The Frictionless Portability Standard (FPS)
To operationalize these insights and ensure your startup is building a natural moat rather than an ethical trap, you must implement the Frictionless Portability Standard (FPS).
This policy ensures that your customer retention metrics are honest, your product-led growth is genuine, and your platform remains on the right side of the "one-stride" rule.
The Operational Protocol
1. The "Equal-Friction" API Mandate
Any data structure, integration, or content that a user can import into your platform in under 60 seconds must be exportable in an industry-standard, structured format (e.g., JSON, CSV, or parquet) in the same amount of time, with zero manual approval gates.
If you have a "one-click import" from a competitor, you must build a "one-click export" to that same competitor. If your export process requires the customer to "contact sales" or "submit a support ticket," you have constructed an unethical trap.
2. The Transparent Egress Pricing Model
You are prohibited from charging markups on data egress that exceed 110% of your actual infrastructure cost (e.g., AWS/GCP data transfer rates).
Your margin must be earned on your software's computation and user experience, not on holding the user's data hostage. Charging a premium to let a customer leave is the modern digital equivalent of charging a ransom.
3. The "Sunset Clause" for Platform Terms of Service
If you make a material change to your platform’s API access, data ownership policies, or interoperability features, you must grandfather in all existing customers and developers for a minimum of 18 months.
This ensures you cannot execute a sequential trap by baiting developers onto your platform and then suddenly closing the "second door."
The Metric: Friction-to-Value Ratio (FVR)
To measure your compliance with this policy, your engineering and product teams will track the Friction-to-Value Ratio (FVR) as a core KPI.
$$\text{FVR} = \frac{\text{Time to Export Entire Account Data Store (Minutes)}}{\text{Time to Onboard & Value Realization (Minutes)}}$$
- The Goal: An FVR of $\le 1.0$.
- The Math: If it takes a customer 10 minutes to sign up and experience their "Aha!" moment on your platform, it should take them no more than 10 minutes to completely export their data and walk away.
- The Danger Zone: If your FVR exceeds $1.5$, your product is relying on coercive lock-in. You are carrying massive ethical and regulatory risk, and your churn metrics are artificially suppressed by customer capture rather than customer delight.
Board-Level Question
"If we eliminated all data migration barriers, contract termination penalties, and proprietary software locks tomorrow, what percentage of our revenue would churn within 90 days?"
This is the ultimate truth-telling question for a startup board. It forces the executive team to look past vanity metrics like Net Revenue Retention (NRR) and confront the reality of how that retention is actually achieved.
If your executive team answers, "We don’t know, but probably a significant portion," then your business is carrying massive, unpriced toxic risk.
[ TOXIC RISK PROFILE ]
COERCIVE LOCK-IN REGULATORY TARGET
(High Egress Fees / Dark Patterns) (FTC / Antitrust Scrutiny)
│ │
▼ ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ Artificially │ ───> │ Vulnerability to│ ──────> │ Catastrophic │
│ Suppressed │ │ Open-Source │ │ Brand Decay │
│ Churn Metrics │ │ Disruption │ │ & Value Loss │
└─────────────────┘ └─────────────────┘ └─────────────────┘
You are highly vulnerable to:
- Regulatory Intervention: The FTC, EU, and global antitrust bodies are actively targeting dark patterns, predatory non-competes, and data silos. If your business model relies on these traps, a single regulatory pivot can wipe out your enterprise value overnight.
- Disruptive Competitors: A competitor who enters your market with an "open-source" or "fully portable" alternative will easily steal your customer base. Customers hate being trapped; the moment an escape hatch appears, they will take it, even if the competitor's product is slightly less feature-rich.
- Brand Decay: Trapped customers are highly vocal detractors. They will ruin your Net Promoter Score (NPS), poison your brand on social media, and ensure that your Customer Acquisition Cost (CAC) rises exponentially over time.
A healthy startup board must demand that the company’s valuation be built on Product-Led Moats (network effects, proprietary AI models trained on consented data, superior UX) rather than Legal-Led Traps (punitive contracts, data hostages).
If your retention is real, you do not need to hide the keys to the exit door.
Takeaway
The Arukh HaShulchan reminds us that the line between freedom and confinement is defined by the doors we open and close.
In the venture-backed world, it is tempting to build moats out of steel cages. But true, Torah-aligned business ethics demand that we build moats out of deep valleys of value, keeping our doors wide open.
If you love your customers, let them go. If they don’t come back, your product wasn’t that good in the first place. Stop trapping, and start building.
derekhlearning.com