Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 315:16-316:4
Hook
Every founder with a subscription business model or a software-as-a-service (SaaS) platform eventually faces a high-stakes temptation: the engineering of customer lock-in.
On paper, high Net Revenue Retention (NRR) and low churn rates are the holy grail of startup valuation. They are the primary metrics that venture capitalists look at when deciding whether to write a ten-million-dollar check. But how are you actually achieving those metrics? Is your product so remarkably valuable that your users wouldn't dream of leaving? Or have you built a digital prison—a cage of dark patterns, deliberately complex data structures, hidden cancellation buttons, and non-exportable databases that make leaving your platform an operational nightmare?
COERCIVE LOCK-IN (High Friction to Exit)
VS.
ETHICAL RETENTION (High Value to Stay)
The difference between these two strategies is not just a matter of customer satisfaction; it is a fundamental ethical boundary. If your retention strategy relies on making it practically impossible for a customer to migrate their data to a competitor, you are not running a business based on value creation. You are running a hostage operation.
In the classical halakhic framework of Shabbat, the laws of Ohel (constructing temporary or permanent shelters/partitions) and Tzeidah (trapping free-roaming creatures) deal with the exact physics of containment, boundaries, and restriction of movement.
By analyzing the rulings of Rabbi Yechiel Michel Epstein in the Arukh HaShulchan, Orach Chaim 315:16-316:4, we uncover a highly sophisticated operational blueprint for modern business architecture. The text challenges us to examine the systems we build:
- Are we setting up temporary boundaries to protect privacy and optimize workflows?
- Or are we building permanent traps that strip our customers and competitors of their agency?
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
The following excerpt from the Arukh HaShulchan outlines the core mechanics of trapping (Tzeidah) and the installation of temporary partitions (Ohel):
אורח חיים שטו:טז
"כל מחיצה שאינה עשויה להתיר... מותר לעשותה... אבל מחיצה המתרת... אסור לעשותה בשבת..."
"Any partition that is not made to permit... it is permissible to make it... but a partition that permits [an otherwise forbidden act]... it is forbidden to make it on Shabbat..." Arukh HaShulchan, Orach Chaim 315:16
אורח חיים שטז:א
"גדר צידה הוא שמכניס בעל חיים למקום שאין מחוסר צידה, דהיינו שיוכל לתפסו בריצה אחת או בשחייה אחת, ושאינו צריך עוד לרוץ אחריו..."
"The definition of trapping is bringing a living creature into a place where it is no longer lacking trapping—meaning, that one can grasp it in a single reach or a single lunge, and one no longer needs to chase after it..." Arukh HaShulchan, Orach Chaim 316:1
אורח חיים שטז:ב
"חיה ועוף שברשותו... אם הם בני תרבות שחוזרים לביתם בערב, אין בהם משום צידה..."
"Beasts and birds that are in his possession... if they are domesticated such that they return to their home in the evening, the prohibition of trapping does not apply to them..." Arukh HaShulchan, Orach Chaim 316:2
אורח חיים שטז:ד
"ואם סגר הדלת והיה צפור בבית... אם אינו יכול לקחתו בבת אחת, לא הוי צידה גמורה מהתורה..."
"And if he closed the door while a bird was in the house... if he still cannot capture it in a single grasp, it is not considered complete trapping under biblical law..." Arukh HaShulchan, Orach Chaim 316:4
Analysis
Insight 1: The Metrics of Capture – Defining Coercive Lock-In vs. Value-Driven Stickiness
In Arukh HaShulchan, Orach Chaim 316:1, Rabbi Epstein defines the precise legal threshold of trapping (Tzeidah):
"גדר צידה הוא שמכניס בעל חיים למקום שאין מחוסר צידה, דהיינו שיוכל לתפסו בריצה אחת..."
"The definition of trapping is bringing a living creature into a place where it is no longer lacking trapping—meaning, that one can grasp it in a single reach..."
This definition hinges on the elimination of the creature's agency. If the animal is confined to a space so small that its escape mechanics are reduced to zero, it is trapped. If, however, the space is large enough that the animal can still evade capture—even if it is technically indoors—it is not fully trapped under biblical law, as noted in Arukh HaShulchan, Orach Chaim 316:4:
"אם אינו יכול לקחתו בבת אחת, לא הוי צידה גמורה מהתורה..."
"If he still cannot capture it in a single grasp, it is not considered complete trapping..."
Translate this physical dynamic into the architecture of modern user retention and software ecosystems:
[ USER RETENTION SPECTRUM ]
Coercive Lock-In (Trapping) Value-Driven Stickiness (Domesticated)
--------------------------- --------------------------------------
* Proprietary, closed formats * Open APIs / Standard JSON exports
* Multi-click, hidden cancellation * Transparent, self-service billing
* High data-migration friction * Exceptional UX & continuous value
* User is "hostage" * User retains full agency to leave
When a startup builds a product, it must choose between two retention strategies:
- The Trapped Ecosystem (Coercive Lock-In): This is the digital equivalent of reducing the space to "a single grasp" (חד ריצה). You make your APIs completely closed, format user data in highly obfuscated proprietary databases, and design the user interface so that exporting data is functionally impossible. The user is technically free to leave, but the migration cost is so high that they are effectively immobilized. You have trapped them.
- The Domesticated Ecosystem (Value-Driven Stickiness): In Arukh HaShulchan, Orach Chaim 316:2, we learn about domesticated animals (בני תרבות) that "return to their home in the evening." For these animals, there is no prohibition of trapping, because they return voluntarily. They have alignment of interest with the owner.
Your customers should be like those domesticated animals. They should stay with your platform because your product continuously delivers outsized return on investment (ROI), not because you have locked the digital stable doors.
If your NRR is high because your product is an open ecosystem that users actively choose to use every day, that is an ethical, sustainable business asset. If your NRR is high because your customers are terrified of the operational downtime required to untangle themselves from your proprietary software, you have built a business model on Tzeidah.
Under a Torah-based business ethic, a startup mensch must always ensure that the customer has "room to run"—meaning, the technical and operational freedom to leave.
Insight 2: Ethical Boundary Setting – The Architecture of Information Firewalls
In Arukh HaShulchan, Orach Chaim 315:16, the text addresses the installation of temporary partitions (mechitzot):
"כל מחיצה שאינה עשויה להתיר... מותר לעשותה..."
"Any partition that is not made to permit... it is permissible to make it..."
Under Jewish law, a partition built on Shabbat is permitted if its purpose is simply to create privacy, block sunlight, or organize space. However, if the partition is built to "permit" an action that was otherwise legally prohibited (such as creating a private domain to allow carrying), erecting it is strictly forbidden.
This halakhic distinction provides a framework for how startups design internal data boundaries, privacy firewalls, and compliance silos.
[ PARTITION PURPOSE ]
│
┌────────────────┴────────────────┐
▼ ▼
Modesty & Privacy Circumvention of Law
(e.g., GDPR Compliance) (e.g., Anti-Competitive Silos)
│ │
▼ ▼
PERMISSIBLE PROHIBITED
In the modern tech ecosystem, founders are constantly erecting partitions. We build data silos, set up localized servers to comply with European data laws (GDPR), and construct information barriers between different business units (such as separating a platform’s first-party retail division from its third-party marketplace data).
- The Permissible Partition: If you are building boundaries to protect user privacy, secure intellectual property, or maintain operational modesty (tzniut), you are acting in alignment with halakhic principles. These partitions do not "permit" anything deceptive; they simply protect what is vulnerable.
- The Prohibited Partition (The Circumvention Wall): If you are building organizational or technical partitions specifically to "permit" something that should be illegal or unethical—such as burying predatory terms of service inside a nested series of user agreements, or siloing data to hide anti-competitive practices from regulators—you are violating the core rule of Arukh HaShulchan, Orach Chaim 315:16. You are using a structural partition to bypass ethical and legal boundaries.
For example, when Apple introduced App Tracking Transparency (ATT), it erected a partition between third-party advertisers and user data. If a startup complies with this partition to respect user privacy, it is ethical.
If, however, a platform creates a partition that blocks competitors from accessing user data under the guise of "privacy," while simultaneously using that exact same data internally to boost its own proprietary ad network, it has built a partition designed to "permit" anti-competitive self-preferencing. This is a direct violation of the principle that structural boundaries must never be used to legitimize predatory behavior.
Insight 3: Defensive Trapping – Mitigating Harm vs. Predatory Capture
A critical nuance in the laws of trapping appears in Arukh HaShulchan, Orach Chaim 316:3, which addresses how to handle harmful or dangerous creatures:
"כל חיה ועוף שנושכים ומזיקים... מותר לצודם שלא ישכו..."
"Any beast or bird that bites and causes damage... it is permitted to trap them so that they do not bite..."
While trapping is generally prohibited on Shabbat, the Sages permitted trapping harmful creatures (such as scorpions, venomous snakes, or rabid dogs) if they pose an active threat to human safety. The primary intent here is not commercial exploitation or sporting capture, but the preservation of safety and the mitigation of harm.
[ INTENT OF CAPTURE ]
│
┌────────────────┴────────────────┐
▼ ▼
Defense / Protection Predatory Exploitation
(Mitigate Active Harm) (Capture Competitor Value)
│ │
▼ ▼
PERMISSIBLE PROHIBITED
In the startup arena, this halakhic distinction governs the ethics of competitive warfare, defensive litigation, and intellectual property protection:
- Ethical Defensive Trapping: If a competitor is actively launching a malicious Sybil attack on your network, scraping your proprietary database in violation of your terms of service, or engaging in predatory IP theft, you are fully justified in deploying aggressive technical and legal "traps." This includes blocking IP ranges, filing for emergency injunctions, or implementing restrictive firewalls. Your intent is defensive: you are neutralizing a "biter" (מזיק).
- Unethical Predatory Trapping: If you are using patent portfolios, frivolous litigation, or exclusionary exclusive-dealing contracts to trap a smaller, harmless competitor who is simply offering a better product at a lower price, you are trapping for sport and market dominance.
The Arukh HaShulchan teaches us that containment is a powerful tool that must be reserved exclusively for defense and protection. Using the mechanisms of capture to suppress fair competition and extract monopoly rents is an abuse of systemic power.
Policy Move
To operationalize these principles of user freedom and ethical boundaries, your startup must move away from coercive lock-in and transition to an "Open-Data Escape Hatch" framework.
The policy change is simple but profound: implement a zero-friction, self-service data export and account deletion system.
[ DATA EXPORT WORKFLOW ]
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ User Decides to │ ───> │ Single-Click │ ───> │ Export Complete │
│ Leave Platform │ │ "Export Data" │ │ (Standard JSON) │
└──────────────────┘ └──────────────────┘ └──────────────────┘
│
▼
┌──────────────────┐ ┌──────────────────┐
│ Account Deleted │ <─── │ User Migrates to │
│ (Zero Friction) │ │ Competitor Easily│
└──────────────────┘ └──────────────────┘
The "Zero-Friction Exit" Standard Operating Procedure (SOP)
1. Technical Data Portability
Every user must be able to export 100% of their user-generated data, transaction history, and metadata in a universally readable, structured format (such as JSON, CSV, or XML) with a single click. This export must not be throttled, gated behind a paywall, or buried deep within the settings menu.
2. Self-Service Account Deletion
Eliminate the "Call Us to Cancel" or "Email Support to Delete Account" dark patterns. If a user can sign up for your product autonomously with a credit card in under two minutes, they must be able to cancel their subscription and completely delete their data autonomously in under two minutes.
3. Deprecate Proprietary Formats for Core Interoperability
Ensure that your software’s primary integration points rely on open, documented APIs. Do not deliberately write custom, non-standard code with the sole strategic intent of making migration to a competitor technically impossible.
Key Metric: The Friction-to-Value Ratio (FVR)
To measure the ethical health of your customer retention, your engineering and product teams will track the Friction-to-Value Ratio (FVR), defined as:
$$\text{FVR} = \frac{\text{Time to Complete Account Export & Deletion (Minutes)}}{\text{Time to Complete Onboarding & Account Creation (Minutes)}}$$
$$\text{Target Metric: } \text{FVR} \le 1.0$$
If it takes a user 2 minutes to sign up for your SaaS product, but it takes them 45 minutes of searching through help docs, emailing support, and waiting for a retention specialist to call them back to close their account, your FVR is 22.5.
This high ratio indicates that you are running a digital trap (Tzeidah). Your target metric must be an FVR of 1.0 or less, meaning it is just as easy to walk out of your digital storefront as it was to walk in.
Board-Level Question
To bring this ethical analysis into your company's strategic governance, the founder or board members should introduce the following question at the next quarterly board meeting:
"If we removed all exit friction tomorrow—allowing our customers to export 100% of their data and transition to our chief competitor with a single click—what percentage of our revenue would we lose, and what does that tell us about the true source of our enterprise value?"
[ BOARD DECISION MATRIX ]
│
┌─────────────────────────┴─────────────────────────┐
▼ ▼
High Revenue Loss Low Revenue Loss
----------------- ----------------
* Value is Coercive * Value is Real
* High Regulatory Risk * Strong Moat (Product)
* Low Valuation Multiple * High Valuation Multiple
* Action: Fix Product UX * Action: Scale Safely
Why This Matters to the Board and Investors
1. Unmasking Phantom Enterprise Value
If your high customer retention is driven by systemic friction rather than product excellence, your enterprise value is an illusion. You have built a moat out of concrete walls rather than superior product value.
The moment a competitor builds a automated "one-click importer" that breaks through your technical friction, your customer base will evaporate.
2. Mitigating Regulatory and Antitrust Risk
Regulators globally are cracking down on dark patterns and anti-competitive lock-in. The Federal Trade Commission (FTC) in the United States and the European Union's Digital Markets Act (DMA) are actively penalizing companies that make cancellation and data portability difficult.
By proactively auditing and reducing exit friction, your startup mitigates the risk of catastrophic regulatory fines and brand damage.
3. Enhancing Long-Term Valuation Multiples
Sophisticated acquirers and late-stage investors look at customer happiness metrics, such as Net Promoter Score (NPS) and customer lifetime value (LTV).
A company that retains customers because they want to be there (domesticated) will always command a higher valuation multiple than a company that retains customers because they have to be there (trapped).
Takeaway
The Arukh HaShulchan provides a timeless ethical truth for the digital age: true strength lies in building ecosystems of voluntary alignment, not structures of forced confinement.
A startup mensch does not build digital cages. They do not rely on the mechanics of trapping (Tzeidah) to inflate their SaaS metrics or protect their market share.
Instead, they build high-performing, open platforms that users actively choose to return to day after day.
By designing transparent boundaries, maintaining open APIs, and offering an effortless exit path, you build an enterprise rooted in truth and fairness. In the long run, the market rewards businesses that respect their customers' agency.
Build a product so exceptional that even when the digital doors are wide open, your customers choose to stay.
derekhlearning.com