Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 316:32-317:1
Hook
Every venture-backed founder is obsessed with one metric above all: Net Revenue Retention (NRR). In the pressure-cooker of scaling a business, the temptation to "manufacture" retention is overwhelming. When your product value proposition begins to plateau, or when a leaner competitor enters the market with a cheaper, faster solution, the temptation shifts from building a better product to building higher walls.
You start introducing "switching costs." You design proprietary data formats that make data export a nightmare. You instruct your product team to hide the "Cancel Subscription" button under four layers of nested settings. You instruct your sales team to slip auto-renewing, multi-year lock-ins into the enterprise agreements, complete with exorbitant early-termination fees.
In the short term, your spreadsheet looks beautiful. Your churn rate drops, your LTV/CAC ratio stabilizes, and your Series B lead investor is impressed. But underneath the hood, you have committed an ethical and operational sin: you have stopped retaining your customers and have started holding them hostage. You have crossed the line from running a business to running a digital prison.
This is not just a modern SaaS problem. The mechanics of trapping, binding, and containing are deeply analyzed in Jewish law. Specifically, the laws of Shabbat—which parse the physical world into precise categories of creative labor—draw an incredibly sharp line between legitimate containment and unethical entrapment.
The Arukh HaShulchan, written by Rabbi Yechiel Michel Epstein in the late 19th century, dissects the laws of Trapping (Tzad) and Tying (Koshair) in Arukh HaShulchan, Orach Chaim 316:32-317:1. These texts are not dusty legal archives; they are the ultimate operational manual for defining the ethical boundaries of customer retention, contract design, and platform lock-in.
As a founder, you need to know: Are you tying a healthy, temporary knot of mutual commitment, or are you weaving an inescapable, predatory trap? Let’s look at the text to find the ROI-minded, ethically sound answer.
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
ערוך השולחן, אורח חיים ש"ט:ל"ב "כל שאינו מחוסר צידה, פירוש שהוא ניצוד ועומד, שבידו לחוטפו בפעם אחת בלי שום תחבולה – אין בו משום צידה... אבל אם עדיין צריך תחבולה ללכדו, אף על פי שהוא במקום סגור, יש בו משום צידה."
ערוך השולחן, אורח חיים ש"י:א' "קשר של קיימא ומעשה אומן – אסור מן התורה... אבל קשר שאינו של קיימא ואינו מעשה אומן, אלא קשר הדיוט שנעשה לפי שעה ואחר כך הותר – מותר לכתחילה."
Translation:
Arukh HaShulchan, Orach Chaim 316:32 "Any creature that does not lack trapping—meaning it is already considered trapped, such that it is in one's hand to grab it in a single movement without any strategy or trickery—there is no prohibition of trapping in it... But if it still requires a strategy or trick to catch it, even if it is already within a closed space, the prohibition of trapping still applies."
Arukh HaShulchan, Orach Chaim 317:1 "A permanent knot that requires professional craftsmanship is forbidden by Torah law... But a knot that is not permanent and does not require professional craftsmanship, but is rather a layman’s knot made temporarily and intended to be untied later, is permitted from the outset."
Analysis
To run a high-growth startup ethically, you must understand the structural difference between voluntary alignment and forced containment. The Arukh HaShulchan provides three distinct decision rules that govern how we design our products, structure our contracts, and treat our customers and partners.
┌────────────────────────────────────────┐
│ CUSTOMER ENGAGEMENT SPECTRUM │
└───────────────────┬────────────────────┘
│
┌────────────────────────┴────────────────────────┐
▼ ▼
┌──────────────────────────┐ ┌──────────────────────────┐
│ VOLUNTARY UNION │ │ PREDATORY ENTRAPMENT │
│ (Ethical Retention) │ │ (Unethical Lock-in) │
├──────────────────────────┤ ├──────────────────────────┤
│ • Layman's Knot │ │ • Professional Knot │
│ (Flexible Contracts) │ │ (Predatory Legalese) │
│ • Open Garden │ │ • Trapping (Tzad) │
│ (Zero-Friction Exit) │ │ (Data Hostage/Friction)│
└──────────────────────────┘ └──────────────────────────┘
Insight 1: The "Easily Reachable" Rule (Fairness in Retention & Data Portability)
In Arukh HaShulchan, Orach Chaim 316:32, Rabbi Epstein tackles a core halachic question: When is an animal considered "trapped"? The boundary line is defined by friction. If an animal is in a space where you can grab it "in a single movement without any strategy or trickery" (שבידו לחוטפו בפעם אחת בלי שום תחבולה), it is already considered trapped. Closing a door on it does not constitute a new act of trapping.
However, "if it still requires a strategy or trick to catch it, even if it is already within a closed space" (אף על פי שהוא במקום סגור), then securing it further is a violation of the laws of trapping.
Apply this directly to your product’s data architecture and user experience. When a customer signs up for your platform, they entrust you with their data—their intellectual property, customer lists, transaction histories, or creative assets.
If they decide to leave your platform, is that data "easily reachable" in a single step, or does retrieving it require "strategy or trickery"?
If your offboarding flow requires a customer to dial a phone number during restricted business hours, sit through a high-pressure retention pitch from a customer success representative, or manually copy-paste their data because your export tool only outputs corrupted CSV files, you have violated the "Easily Reachable" rule. You are using "strategy and trickery" (תחבולה) to keep them contained.
In the physical world, trapping a wild animal is a display of dominance that strips the creature of its natural autonomy. In the digital economy, trapping a user by manipulating their data portability is a display of market dominance that strips the buyer of their economic autonomy.
The Decision Rule:
Your customer retention must be based entirely on utility, not utility-hostage dynamics. If a user wishes to leave, their exit pathway must be as frictionless as their entry pathway. If onboarding takes three clicks, offboarding must not take ten.
The data they generated on your platform belongs to them. Keeping it behind a proprietary wall where it is not "easily reachable" is the digital equivalent of trapping a creature that belongs in the wild.
Insight 2: The "Professional vs. Layman Knot" (Truth in Contract Design)
In Arukh HaShulchan, Orach Chaim 317:1, we pivot to the laws of Koshair (Tying). The Torah prohibits tying a "permanent knot that requires professional craftsmanship" (קשר של קיימא ומעשה אומן). Conversely, a knot that is temporary and requires only a layman’s skill (קשר הדיוט שנעשה לפי שעה) is permitted from the outset.
This halachic distinction is a masterclass in contract design.
A contract is a knot. It binds two independent economic agents together for a common purpose. In business, there are two ways to tie this knot:
- The Professional Knot (Kesher Shel Kayama / Ma'aseh Uman): This is a contract engineered by highly paid corporate attorneys, filled with dense legalese, hidden auto-renewal clauses, asymmetric indemnification, and complex jurisdiction stipulations. It is designed to be permanent, structurally incomprehensible to the average founder or customer, and virtually impossible to untie without expensive litigation.
- The Layman's Knot (Kesher Hedyot / Na'aseh L'fi Sha'ah): This is a transparent, plain-English agreement. It binds the parties for a defined period of mutual benefit, is easily understood by a non-lawyer, and contains clear, fair, and accessible pathways for dissolution when the relationship has run its course.
┌─────────────────────────────────────────────────────────────────────────┐
│ CONTRACT TYPE COMPARISON │
├────────────────────────────┬────────────────────────────────────────────┤
│ The Layman's Knot │ The Professional Knot │
│ (Halachically Permitted) │ (Halachically Restrictive) │
├────────────────────────────┼────────────────────────────────────────────┤
│ • Plain-English terms │ • Dense, obscure legalese │
│ • Transparent exit paths │ • Asymmetric termination fees │
│ • Mutual, dynamic value │ • Traps parties in dead value exchanges │
│ • Low untying friction │ • High litigation cost to dissolve │
└────────────────────────────┴────────────────────────────────────────────┘
Many founders believe that "good business" means tying the tightest knot possible. They want their customers locked in for three years with no out-clause. They want their vendor agreements to be heavily biased in their favor.
But the Arukh HaShulchan warns us against the hubris of the "permanent, professional knot." When you tie a knot so complex that it requires "professional craftsmanship" to untangle, you are creating a rigid, brittle system.
In the volatile startup ecosystem, rigidity is death. If your customers are bound to you by legal compulsion rather than ongoing value delivery, they will grow to resent your brand. They will actively work against your interests, badmouth your product in backchannel VC networks, and churn the millisecond the contract expires.
The Decision Rule:
Contracts should be as simple and flexible as possible. They should be "layman’s knots"—clear, fair, and designed for a specific timeframe (לפי שעה).
If your legal agreements require a customer to hire an external legal team just to understand how to terminate the relationship, you have built a Kesher Shel Kayama through predatory means. True economic alignment does not require legal handcuffs.
Insight 3: The "Scope of Liberty" Rule (Healthy Competition and Walled Gardens)
Let's look deeper at the relationship between trapping (Tzad) and tying (Koshair).
- Trapping restricts an entity's physical space; it places walls around a free agent.
- Tying binds two separate entities together, restricting their movement relative to each other.
When a founder builds a platform ecosystem—such as an API network, an app store, or a marketplace—they are acting as a mini-sovereign. They control the rules of the environment.
The temptation for platform sovereigns is to use both trapping and tying to crush competition. They "trap" developers by charging high platform tax rates (e.g., the classic 30% app store fee) while simultaneously "tying" them through exclusivity clauses that prevent them from launching on competing platforms.
Rabbi Epstein notes that even if an animal is already in a "closed space" (במקום סגור), if it still requires strategy or effort to catch it, the act of trapping is still prohibited.
This means that just because a customer or partner has entered your ecosystem (a "closed space"), you do not possess absolute ownership over them. They still retain their fundamental economic liberty.
When platform companies use anti-steering provisions (preventing developers from telling users about cheaper options outside the app store), they are violating this principle. They are using "strategy and trickery" to capture transactions that would otherwise occur in the free market.
The Decision Rule:
Your platform must not turn its ecosystem partners into captive economic agents. If you run a marketplace or a platform, your partners must remain free to operate outside your ecosystem.
You must win their loyalty through superior infrastructure, distribution, and demand generation, rather than through restrictive exclusivity clauses and anti-steering policies that exploit their structural dependence on your platform.
Policy Move
To operationalize these insights, you must transition your company from a culture of "forced retention" to a culture of "earned retention." The most effective way to do this is to implement The Clean-Cut Protocol across your Product, Legal, and Sales departments.
THE CLEAN-CUT PROTOCOL
│
┌─────────────────────┼─────────────────────┐
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ PRODUCT TEAM │ │ LEGAL TEAM │ │ SALES TEAM │
├───────────────┤ ├───────────────┤ ├───────────────┤
│ One-Click │ │ Plain-English │ │ No-Penalty │
│ Data Export │ │ Contract Term │ │ Out-Clauses │
└───────────────┘ └───────────────┘ └───────────────┘
The Policy: The Clean-Cut Protocol
1. Product Team Mandate: One-Click Data Portability & Self-Serve Cancellation
- No Dark Patterns: The option to cancel a subscription or delete an account must be accessible in the main user settings panel. It must not require more than two clicks, and it must never require a phone call, live chat with a retention agent, or manual review.
- Standardized Data Export: At any point, without contacting customer support, a user must be able to export their entire data history in a clean, standardized, machine-readable format (such as JSON or CSV). You will not charge an "export fee" or throttle download speeds to discourage migration.
2. Legal & Sales Team Mandate: The Layman’s Contract Standard
- The "Plain-English" Cover Page: Every enterprise contract must include a one-page, bulleted summary at the very beginning. This summary must explicitly state:
- The duration of the agreement.
- The exact cost, including any automatic price escalators upon renewal.
- The precise steps required to terminate the agreement at the end of the term.
- The absence of any hidden early-termination fees.
- The "No-Penalty" Out-Clause: If your company fails to meet agreed-upon Service Level Agreements (SLAs) for two consecutive months, the customer has the immediate right to terminate the contract with zero financial penalty and receive a pro-rata refund of any prepaid fees.
The Metric: The Time-to-Exit Friction Ratio (TEFR)
To measure your compliance with this ethical standard, your board must track a new, non-traditional operational metric: the Time-to-Exit Friction Ratio (TEFR).
$$\text{TEFR} = \frac{\text{Average Hours to Fully Offboard a Customer and Export Data}}{\text{Average Hours to Onboard a Customer and Ingest Data}}$$
The Target:
$$\text{TEFR} \le 1.5$$
If it takes your team 2 hours to onboard an enterprise customer, but it takes 20 hours of legal reviews, manual data extraction, and back-and-forth emails to offboard them, your TEFR is 10.0.
This indicates that you are running a digital prison. You are relying on "trapping" (Tzad) to maintain your revenue metrics.
By driving your TEFR down to 1.5 or lower, you force your product and customer success teams to focus entirely on delivering actual value. If customers can leave easily but choose to stay, your NRR is a genuine reflection of product-market fit, not a manufactured illusion of legal coercion.
Board-Level Question
To ensure this policy is not just a written document but an active corporate value, the board of directors must hold the executive team accountable.
At your next board meeting, present the following question to your CEO, VP of Product, and VP of Sales:
"If we removed all contractual lock-ins, proprietary data formatting, and exit friction from our product tomorrow, what percentage of our revenue would churn within 90 days—and does our product value proposition survive the answer?"
┌────────────────────────────────────────┐
│ BOARD-LEVEL EVALUATION │
└───────────────────┬────────────────────┘
│
┌────────────────────────┴────────────────────────┐
▼ ▼
┌──────────────────────────┐ ┌──────────────────────────┐
│ SCENARIO A: > 15% │ │ SCENARIO B: < 15% │
├──────────────────────────┤ ├──────────────────────────┤
│ • Product-Market Fraud │ │ • True Product-Market Fit│
│ • Artificial Retention │ │ • Ethical Alignment │
│ • High Strategic Risk │ │ • Sustainable Growth │
└──────────────────────────┘ └──────────────────────────┘
Deconstructing the Question:
1. Exposing Product-Market Fraud
If your executive team admits that removing exit friction would lead to a catastrophic spike in churn (e.g., greater than 15% of your annual recurring revenue), then your business model is built on a foundation of ethical and structural fraud.
You do not have true product-market fit. You have "lock-in fit."
Your revenue is being sustained by the legal and technical barriers you have erected around your customers. This is a massive strategic risk; the moment a competitor emerges with an open-source or highly compatible alternative that bypasses your lock-in, your customer base will collapse.
2. Shifting the Capital Allocation Strategy
If the answer reveals a high vulnerability to churn, the board must mandate a shift in capital allocation.
Instead of spending capital on aggressive sales strategies or legal maneuvers to tighten contract language, resources must be redirected to product development.
You must make the product so valuable, so intuitive, and so integrated into the user's daily workflow that they choose to stay even when leaving is completely free.
3. Protecting Brand Equity and LTV
A customer who stays because they are locked in is a toxic asset. They will actively discourage their peers from purchasing your software.
Conversely, a customer who knows they can leave at any time but chooses to remain is a brand evangelist.
By forcing the executive team to confront the reality of their retention mechanics, you protect the long-term enterprise value of the company.
Takeaway
The Arukh HaShulchan teaches us that true containment must never rely on "strategy or trickery" (תחבולה), and that healthy commitments should be structured as flexible, transparent agreements rather than permanent, complex knots (קשר של קיימא ומעשה אומן).
In the modern startup ecosystem, your competitive advantage should never be the height of your walled garden or the complexity of your legal agreements.
Build a product that is so good, and run a company that is so fair, that your customers choose to stay bound to you even when the gate is wide open.
Stop trapping. Start delivering.
derekhlearning.com