Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 316:5-10
Hook
Every venture-backed founder is obsessed with "moats." We are told by board members, growth equity investors, and business school professors that the ultimate goal of a software platform or transactional ecosystem is to build high switching costs. We want to achieve high Net Revenue Retention (NRR).
But in the quiet of the late-night leadership meetings, a dangerous operational drift occurs. The line between building a product so valuable that customers never want to leave, and building a product so complex and punitive that customers cannot leave, begins to blur.
We introduce dark patterns in our cancellation flows. We charge exorbitant "data extraction fees" when a client wants to migrate their database. We draft multi-year enterprise agreements with auto-renewal clauses hidden in deep sub-pages of our Terms of Service. We tell ourselves this is just "maximizing lifetime value" (LTV) and "protecting our margins."
In reality, we have stopped being product innovators and have become digital jailers. We are no longer winning on product-market fit; we are winning on customer captivity.
This is not a sustainable business strategy; it is an ethical hazard that carries massive, unpriced operational risk. When a customer stays with you only because the friction of leaving is too painful, you have built a business on "hostage revenue." The moment a competitor emerges with an automated migration tool that vaporizes your switching costs, your customer base will churn overnight.
Halacha (Jewish law) addresses this exact dynamic through the laws of Tzeidah (trapping) on Shabbat. By exploring how the sages define a complete, illicit act of capture versus an open, fair-market dynamic, we can extract sharp, ROI-positive decision rules for modern business.
The Arukh HaShulchan Arukh HaShulchan, Orach Chaim 316:5-10 provides a brilliant, highly sophisticated framework for understanding when a capture is legitimate, when it is redundant, when it is predatory, and when it is defensive. As a founder, mastering these principles will help you build a high-retention business that commands premium valuation multiples without sacrificing your ethical integrity.
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
"כל שאינו מחוסר צידה... שאינו צריך תחבולות לצודו... אינו אסור מהתורה" "Any creature that does not require trapping... that does not require stratagems to capture it... is not biblically forbidden [to trap on Shabbat]."ונעשה כאילו הוא כבר ניצוד בידו. "And it is considered as if it is already captured in his hand." — Arukh HaShulchan, Orach Chaim 316:5
"אם צד חולה או זקן או סומא... שאינו יכול לברוח... פטור" "If one traps a sick, old, or blind animal... that cannot flee... he is exempt [from the labor of trapping]."שכבר הוא ניצוד ועומד. "Because it is already considered captured and standing." — Arukh HaShulchan, Orach Chaim 316:6
"אם צדן שלא לצורך אכילתם או להשתמש בהם אלא כדי שלא ישכו... מותר" "If one traps them not for the purpose of eating or using them, but rather so that they do not bite... it is permitted." — Arukh HaShulchan, Orach Chaim 316:10
Analysis
Insight 1: The Redundant Trap — Stop Building Artificial Friction for Captive Customers
In Arukh HaShulchan, Orach Chaim 316:5, the author deals with the core halachic definition of trapping (Tzeidah). He notes that if an animal is already in a small, enclosed space where it cannot escape, or if it is a domesticated animal that "comes when called" ("השורק לו והוא בא"), then closing a door on it or grabbing it does not constitute the biblical labor of trapping. Why? Because the creature is already captured.
The labor of trapping requires a transition from a state of freedom to a state of captivity. If you attempt to trap something that is already effectively in your possession, your action is halachically redundant.
Now, let's translate this to your SaaS platform’s customer retention strategy.
There are two ways to achieve high customer retention:
- The Domesticated Approach ("The Call and Response"): Your product is so deeply integrated into the customer’s daily workflow, and your customer service is so responsive, that when you "call," the customer "comes." They stay because of organic alignment, continuous value delivery, and trust.
- The Artificial Trap: The customer wants to leave because your product quality has degraded, but you have built complex "stratagems" (tachbulot) to prevent them from doing so. You hide the cancellation button behind three layers of UI, require a live phone call with a high-pressure retention agent during narrow business hours, or refuse to release their historical data in a usable format.
The Arukh HaShulchan teaches us that if a creature is already naturally aligned with you, further coercive trapping is entirely unnecessary and changes nothing about the fundamental state of possession. Conversely, if you must resort to complex, artificial traps to keep your customer, you are admitting that they are not naturally aligned with you. You are using coercion to simulate loyalty.
From an ROI perspective, the resources you spend building and maintaining these artificial "traps" (dark patterns, legal threats, complex contractual lock-ins) are capital-allocative waste. They do not improve your Net Promoter Score (NPS), they do not drive product-led growth, and they do not increase your expansion revenue.
In fact, they do the opposite: they destroy your brand equity. In a highly connected B2B software market, buyers talk. If your platform becomes known as a "roach motel"—easy to check into, impossible to check out of—your customer acquisition cost (CAC) will skyrocket as prospect trust plummets.
The Decision Rule: If your retention metrics rely on artificial friction rather than product value, you are executing a redundant and predatory trap. True market capture is achieved when the customer is so well-served that they are "considered as if they are already captured in your hand" without the need for contractual or technical cages.
Insight 2: The Fallacy of Exploiting the Vulnerable — Trapping the "Sick and Blind" is Not a Win
In Arukh HaShulchan, Orach Chaim 316:6, the text outlines an important exemption: trapping a sick, old, or blind animal that is incapable of fleeing does not violate the biblical prohibition of trapping. The reasoning is clear: "שכבר הוא ניצוד ועומד" — it is already considered captured and standing. Because the animal lacks the physical capacity or agency to escape, the act of "trapping" it requires no skill, overcomes no resistance, and represents no true victory of capture.
This halachic category maps perfectly onto a common, yet highly unethical, startup growth strategy: targeting and exploiting captive, highly vulnerable, or low-agency customer segments.
We see this frequently in several sectors:
- FinTech: High-interest payday lending apps or predatory fee structures targeting financially illiterate or desperate demographics who cannot qualify for traditional banking.
- EdTech / GovTech: Selling outdated, overpriced software to municipal governments or public school districts that are locked into slow, bureaucratic procurement cycles and lack the technological expertise to evaluate alternative solutions.
- B2C Subscriptions: Targeting elderly populations with recurring billing models for services they do not understand, do not use, and do not know how to cancel.
When you boast to your board about high customer retention or high margins in these segments, you are celebrating a false victory. You have not built a superior product; you have simply trapped a "sick, old, or blind" customer who lacks the mobility, agency, or market awareness to run away from you.
This is a highly fragile business model. It carries massive regulatory, legal, and reputational risks:
- Regulatory Retribution: Government bodies like the FTC, CFPB, and state attorneys general actively hunt for companies whose business models rely on exploiting vulnerable populations. A single regulatory investigation can wipe out your entire enterprise value overnight.
- Platform Risk: If you distribute your product through major app stores (Apple App Store, Google Play), a sudden change in their developer guidelines regarding dark patterns or predatory pricing can instantly de-platform your business.
- Talent Drain: High-performing engineers, product managers, and executives do not want to work for a company that exploits the defenseless. Over time, your talent pool will degrade, leaving you with mediocre staff who cannot innovate, accelerating your company’s decline.
The Decision Rule: Do not build a business model around capturing customers who cannot run away. If your primary source of profitability comes from exploiting market asymmetries, low technological literacy, or regulatory blind spots, you are renting a temporary cash flow, not building an enduring enterprise. Compete for the "healthy, fast-running" customers who have choices; if they choose you, you have a real business.
Insight 3: Defensive Shielding vs. Offensive Sabotage — Trapping to Prevent Harm
In Arukh HaShulchan, Orach Chaim 316:10, the text introduces a crucial ethical and practical distinction: trapping a dangerous creature (like a venomous snake or a scorpion) on Shabbat is permitted if your intent is defensive — i.e., "כדי שלא ישכו" (so that they do not bite or harm you). However, if your intent is offensive or commercial — i.e., trapping them for their meat, skin, or to use them for your own utility — it remains prohibited.
This distinction between defensive trapping (to prevent harm) and offensive trapping (for predatory gain) is the ultimate guide for how a founder should think about intellectual property (IP), non-compete agreements, and competitive moats.
Every startup must protect itself. You operate in a brutal, highly competitive environment where larger incumbents will gladly steal your IP, copy your features, and poach your key talent to crush you.
Building a "trap" for defensive purposes is not only ethical; it is a fiduciary duty to your shareholders.
1. Defensive Intellectual Property
Filing patents to prevent an incumbent from copying your proprietary algorithms and suing you out of existence is highly ethical. You are trapping their ability to harm you ("כדי שלא ישכו").
However, transitioning into a patent troll—where you acquire vague, broad patents solely to extort licensing fees from smaller startups who are actually innovating—is offensive trapping. It is predatory, value-destructive, and ethically bankrupt.
2. Talent Protection and Employment Agreements
Using reasonable non-disclosure agreements (NDAs) and non-solicitation clauses to prevent a departing executive from taking your proprietary codebase or poaching your entire engineering team to a direct competitor is defensive. You are protecting your business from a lethal bite.
On the other hand, forcing low-wage, non-executive employees (like customer support reps or junior QA engineers) to sign draconian, nationwide non-compete agreements that prevent them from finding any job in the tech sector is offensive trapping. You are using legal asymmetry to crush their career mobility and depress their wages, simply to maintain a minor operational convenience.
3. Competitive Moats
Building an ecosystem where your products integrate seamlessly with each other (e.g., a suite of developer tools) is a great defensive moat. You are making your platform highly cohesive so that security threats are minimized and data flow is optimized.
But intentionally breaking integrations with third-party tools or fabricating security warnings to scare your customers away from using a competitor's complementary software is offensive sabotage. You are no longer protecting your house; you are poisoning your neighbor’s field.
| Strategy Dimension | Defensive Trapping (Permitted / Ethical) | Offensive Trapping (Prohibited / Predatory) |
|---|---|---|
| Intellectual Property | Filing patents to protect your core, unique technology from being copied by giants. | Buying up broad, vague patents to sue and extort smaller innovators (Patent Trolling). |
| Talent & HR | Using NDAs and non-solicitation to protect trade secrets and core team integrity. | Enforcing broad non-competes on junior staff to lock them in and depress their wages. |
| Ecosystem & APIs | Building tight, secure integrations within your suite to maximize user performance. | Intentionally blocking third-party interoperability to freeze out competitors. |
The Decision Rule: Evaluate every legal, technical, and competitive barrier you erect. Ask yourself: "Are we building this trap defensively to prevent a competitor or bad actor from destroying our unique value, or are we building this offensively to capture and exploit market players who pose no threat to us?" If it is the latter, tear down the trap.
Policy Move: The "Open-Exit Portability Standard" (OEPS)
To transition your startup from a business built on "hostage revenue" to one built on "advocate revenue," you must implement a concrete, operational policy that guarantees customer freedom while protecting your genuine IP.
We call this the Open-Exit Portability Standard (OEPS).
+-------------------------------------------------------+
| THE OPEN-EXIT PORTABILITY FLOW |
+-------------------------------------------------------+
|
v
+-------------------------------------------------------+
| Customer Initiates Cancellation / Exit |
+-------------------------------------------------------+
|
+-------------------------+-------------------------+
| |
v v
+---------------------------------+ +---------------------------------+
| AUTOMATED SELF-SERVICE DATA | | ZERO-FRICTION CONTRACTUAL |
| PORTABILITY ENGINE | | TERMINATION |
+---------------------------------+ +---------------------------------+
| * One-click raw data export | | * Clear, visible terms |
| (JSON/CSV/SQL) within 24 hours| | * Auto-renew warnings sent |
| * Standardized schema maps | | 30 days prior via email/app |
| * No "extraction fees" or bills | | * No mandatory retention calls |
+---------------------------------+ +---------------------------------+
| |
+-------------------------+-------------------------+
|
v
+-------------------------------------------------------+
| Clean Exit Achieved -> Trust & Brand Intact |
| (Reduces Chargebacks, Shortens Future Sales Cycles) |
+-------------------------------------------------------+
1. The Operational Mechanics of OEPS
Your product and engineering teams will build and maintain a self-service "Data Portability & Account Termination" dashboard. This dashboard must adhere to three non-negotiable rules:
- One-Click Raw Data Export: Any customer, at any tier, must be able to export their entire database, media assets, and transaction history in a universally readable, non-proprietary format (e.g., structured JSON, CSV, or standard SQL dumps) with a single click. This export must be processed automatically within 24 hours.
- No "Extraction Fees": You will not charge "data migration fees," "administrative transition costs," or any other financial penalties designed to make leaving cost-prohibitive. The data belongs to the customer; charging them to access their own property is extortion.
- Zero-Friction Contractual Termination: If a customer is on a monthly or annual auto-renewing subscription, you must send an automated email and in-app notification 30 days prior to the renewal date, explicitly stating the upcoming charge and providing a direct link to cancel. The cancellation process must take no more than three clicks and cannot require a phone call or chat with a sales representative.
2. Why This is Highly ROI-Positive
On the surface, making it easy for customers to leave sounds like a recipe for immediate churn. In practice, it is one of the most powerful growth levers you can pull:
- It Shortens Enterprise Sales Cycles: Enterprise buyers are highly sophisticated. They dread vendor lock-in. During the procurement process, their security and IT teams will audit your exit options. By presenting your OEPS compliance upfront—showing them exactly how easy it is to export their data and leave if your product fails to deliver—you eliminate their biggest risk. You turn a high-friction sales conversation into a high-trust, fast-closing deal.
- It Drastically Reduces Merchant Chargebacks: When customers are forced to jump through hoops to cancel, they don't blame themselves—they blame you. Instead of calling your support team, they will call their credit card company and file a billing dispute (chargeback). High chargeback rates lead to heavy penalty fees from payment gateways (Stripe, Adyen), and can ultimately lead to the termination of your merchant processing accounts. OEPS keeps your payment processing history pristine.
- It Establishes a " boomerang" Customer Pipeline: Customers leave for many reasons—budget cuts, corporate restructuring, or a temporary pivot. If you make their exit graceful and professional, they will remember you. When their budget returns or they move to a new company, they will buy from you again. If you trap them and make their exit a nightmare, they will become toxic detractors who actively warn their network away from your brand.
3. The Metric Proxy: The Exit Friction Ratio (EFR)
To measure and report your compliance with this policy to your leadership team and board of directors, you will track a new proprietary KPI: the Exit Friction Ratio (EFR).
$$\text{EFR} = \frac{\text{Time to fully export data and terminate contract (in hours)}}{\text{Time to sign up and onboard a new account (in hours)}}$$
An ethical, high-velocity, high-trust startup should target an EFR of $\le 1.5$.
If it takes your customer 1 hour to sign up, input their credit card, and get onboarded, it should take them no more than 1.5 hours of automated, self-service effort to completely export their data and cancel their account.
If your EFR is $10.0$ or $50.0$ (meaning it takes days of back-and-forth emails, legal threats, and manual data pulls to leave compared to a 5-minute signup), you are running an illicit "trap." Your NRR is built on friction, not value.
Board-Level Question
At your next board meeting, when your investors are pressing you on customer retention, cohort expansion, and defensive moats, you need to elevate the conversation from short-term metrics to long-term enterprise value.
Ask your board and executive team the following strategic question:
"What percentage of our Net Revenue Retention (NRR) is driven by value-creation (the customer choosing to stay because of product utility) versus transaction-friction (the customer staying because they are contractually, technically, or financially trapped)—and how would our valuation hold up if a competitor launched a zero-friction migration tool tomorrow?"
To prepare your leadership team for this discussion, break down the analysis into three distinct components:
1. The "Hostage Revenue" Audit
Instruct your VP of Finance and VP of Product to audit your customer cohorts. Segment your revenue into two buckets:
- Advocate Revenue (Low Exit Friction): Customers who are out of contract (on month-to-month terms), have fully portable data, and continue to pay you because your product is a critical utility.
- Hostage Revenue (High Exit Friction): Customers who have expressed low satisfaction scores (NPS < 6) or low product usage, but remain with you because they are locked into multi-year contracts, have proprietary database structures that are highly complex to migrate, or face steep termination penalties.
If more than 30% of your recurring revenue falls into the "Hostage" bucket, your business is highly vulnerable to disruption. You do not have product-market fit; you have contract-market fit.
2. The Churn-Resistance Stress Test
Ask your engineering team to simulate a "Zero-Friction Competitor" scenario.
If a well-funded competitor entered the market tomorrow and offered:
- A free, one-click automated tool that scrapes your database and imports it into their system,
- A promise to cover any early-termination legal fees your customers incur for breaking your contract,
- A 20% discount on your current pricing,
...how many of your customers would migrate within 90 days?
If the honest answer is "a significant portion," then your platform's moat is an illusion. Your moat is not a deep river of product value; it is a shallow wall of legal and technical bureaucracy. The moment that wall is breached, your company's valuation multiple will collapse.
3. The Due Diligence Risk Profile
Remind your venture capital board members of the realities of modern M&A and late-stage growth rounds.
Sophisticated private equity buyers and strategic acquirers are no longer fooled by top-line growth and raw retention numbers. During due diligence, their technical and legal teams will explicitly audit your customer churn dynamics, contract structures, and data portability.
If they discover that your high retention is artificially manufactured through predatory lock-ins or dark patterns:
- They will write down your valuation multiple,
- They will demand massive escrow holdbacks to cover potential post-acquisition churn,
- Or they will walk away from the deal entirely, citing systemic brand and regulatory risk.
By forcing this conversation at the board level, you align your investors around a profound truth: the most valuable companies are those whose customers have the absolute freedom to leave, yet choose to stay.
Takeaway
Applying the timeless wisdom of the Arukh HaShulchan to the high-stakes world of venture-backed startups yields a powerful paradox: to secure your customers, you must set them free.
When you build artificial traps, exploit vulnerable market segments, or weaponize your legal and technical infrastructure for offensive sabotage, you are violating the fundamental ethical principles of fair competition and truth. You are trading your long-term brand equity, your team’s morale, and your company's ultimate enterprise value for a temporary, fragile bump in monthly recurring revenue.
A true Mensch founder does not build a digital prison. They build a world-class platform.
By designing your startup around value-driven retention, implementing the Open-Exit Portability Standard, and maintaining a low Exit Friction Ratio, you build an enduring, high-trust enterprise. You prove to your customers, your team, and your investors that your product is so exceptional that it requires no cages.
When you "call," your customers will "come" — not because they are trapped, but because you are the undisputed leader in delivering them value.
derekhlearning.com