Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 312:1-7
Hook
The silent killer of scaling startups is not market risk; it is operational drag. In the early stages, survival depends on speed, agility, and high-agency execution. Yet, as venture capital flows and teams expand, founders almost invariably fall into the trap of "carrying" unnecessary weight. You hire for future capacity that hasn’t materialized, accumulate a bloated SaaS tech stack, and tolerate underperforming team members because "firing them looks bad to investors" or "we need the headcount to look credible for our next valuation round."
This is the classic founder's dilemma: How do you scale without accumulating ruinous organizational drag?
[Active Value (High Agency)] ---> Carries itself (Zero drag)
[Overhead (Tech/Admin)] ---> Justified ONLY if secondary to Active Value
[Dead Weight (Low Agency)] ---> Requires constant carrying (Ruinous burn)
You have a team of 50. Ten of them are rockstars who generate 90% of your progress. Twenty are competent but require constant managerial oversight. The remaining twenty are "dead weight"—passive executors who wait to be told what to do, generating negative net value when you factor in the management hours required to keep them aligned. Simultaneously, your balance sheet is littered with enterprise software licenses that only a fraction of your team uses, but migrating away feels too painful. You are carrying an immense load, and your runway is evaporating.
This is not merely a modern corporate governance issue; it is a profound ethical and operational hazard addressed directly by Jewish law. In the laws of Shabbat, the Torah restricts carrying objects in a public domain. However, the Rabbinic codifiers, culminating in the late 19th-century masterpiece of Rabbi Yechiel Michel Epstein, the Arukh HaShulchan, articulated a brilliant psychological and physical distinction: "The living carries itself" (Chai nosei et atzmo).
When you carry a living, self-sustaining entity, the nature of the burden changes. But when you carry "dead weight" or unnecessary accessories, you violate the core operational parameters of the system.
By applying the halachic principles of carrying, secondary accessories (tafeil), and the ethical handling of distressed assets (kikar o tinok), we can construct a rigorous, ROI-minded framework for modern startup design. This framework ensures that every dollar of burn and every ounce of founder energy is leveraged toward active growth, rather than subsidizing structural decay.
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
"כלל גדול אמרו בשבת שהחי נושא את עצמו... ואפילו המוציאו במטה פטור אף על המטה שהמטה טפילה לו..."
"A great rule they said concerning Shabbat: a living being carries itself... and even one who carries him on a bed is exempt even for the bed, because the bed is secondary to him." — Arukh HaShulchan, Orach Chaim 312:1
"אבל אם יש על המטה בגדים שאינם צריכים להחי... חייב עליהם..."
"But if there are clothes on the bed that are not needed for the living person... he is liable for them..." — Arukh HaShulchan, Orach Chaim 312:3
"מת שמוטל בחמה... מניח עליו ככר או תינוק ומטלטלו..."
"A corpse lying in the sun... one places upon it a loaf of bread or a child and moves it..." — Arukh HaShulchan, Orach Chaim 312:4
Analysis
Insight 1: The Principle of Self-Sustaining Assets (Fairness & Talent Density)
In the laws of Shabbat, carrying an object in a public domain is a biblically prohibited labor (Melacha). Yet, the Talmud and subsequent halachic codes establish a fascinating exception: carrying a living human being who is capable of walking does not violate the biblical prohibition of carrying. The Arukh HaShulchan codifies this:
"כלל גדול אמרו בשבת שהחי נושא את עצמו..." (A great rule they said concerning Shabbat: a living being carries itself...) Arukh HaShulchan, Orach Chaim 312:1.
Why? Because a living person, through their own muscular tension, balance, and consciousness, actively facilitates their own movement. They are not passive mass; they are an active partner in the kinetic action. They "carry themselves."
In the context of startup talent density, this is the ultimate decision rule for hiring and retention. High-agency talent consists of "living" assets. They do not require you to carry them; they align themselves with the company’s trajectory, solve problems autonomously, and generate momentum. They carry their own weight—and then some.
Conversely, low-agency employees are "passive mass." They do not carry themselves; they must be dragged. Every task requires micro-management, explicit instructions, and constant emotional and operational "carrying" by leadership.
The halachic distinction is sharp: if you carry a living person who cannot walk (like an infant), or if you carry a corpse, you do not enjoy this exemption. You are fully carrying.
From an ethical standpoint, tolerating low-agency, underperforming team members is not "kindness"—it is a profound act of unfairness to your high-performing, self-carrying talent. When a founder tolerates mediocrity, they force their A-players to subsidize the drag of the underperformers. The A-players must write the code, close the deals, and fix the mistakes of those who cannot carry themselves.
This dilutes your talent density, breeds resentment, and burns out your most valuable assets. The ethical founder must apply the rule of Chai nosei et atzmo: every node in the organizational chart must be self-carrying. If an employee requires continuous, active carrying to perform basic functions, they are structurally incompatible with a high-growth startup.
[A-Player (Self-Carrying)] ---> Generates own kinetic energy ---> Elevates team
[C-Player (Requires Carrying)] ---> Absorbs management energy ---> Drags down team
Insight 2: The Law of Auxiliary Drag (Truth & Overhead Rationalization)
A common justification for startup bloat is that "we need these tools/managers to support our core talent." The Arukh HaShulchan addresses this exact dynamic through the concept of tafeil (secondary or auxiliary components):
"...ואפילו המוציאו במטה פטור אף על המטה שהמטה טפילה לו..." (...and even one who carries him on a bed is exempt even for the bed, because the bed is secondary to him...) Arukh HaShulchan, Orach Chaim 312:1.
If you are carrying a living person on a bed, you are exempt from liability for carrying the bed itself. Why? Because the bed is strictly auxiliary to the living person. It is a necessary vehicle to facilitate the movement of the primary, self-carrying asset. The bed has no independent status in this scenario; its utility is entirely derived from its service to the living.
However, the Arukh HaShulchan immediately introduces a critical boundary:
"אבל אם יש על המטה בגדים שאינם צריכים להחי... חייב עליהם..." (But if there are clothes on the bed that are not needed for the living person... he is liable for them...) Arukh HaShulchan, Orach Chaim 312:3.
If you pile extra clothes, items, or software on that bed that are not strictly necessary for the living person, the exemption evaporates. You are now liable for carrying those unnecessary items.
This is a powerful decision rule for startup overhead, SaaS spend, and middle management. Your core engineers, sales reps, and product designers are the "living assets." Your tech stack, office space, project management software, and HR platforms are the "bed." They are only ethically and operationally justified if they are strictly auxiliary (tafeil) to the productivity of the living assets.
The moment you add "clothes that are not needed"—such as enterprise software licenses that sit idle, vanity PR agencies, over-engineered reporting frameworks, or redundant layers of middle management—you are no longer carrying a secondary asset. You are carrying independent, dead weight. You have violated operational truth.
Is the expense/process directly enabling a "living" asset to move faster?
├── YES: It is "Tafeil" (Justified, integrated overhead).
└── NO: It is "Unnecessary Clothing" (Liable, immediate drag to be cut).
In the venture-backed world, founders often accumulate these "unnecessary clothes" to signal maturity to future investors. They buy expensive enterprise tools because "that's what Series B companies do." But the Arukh HaShulchan warns us: the moment you add unnecessary weight to the bed, you bear full, liable drag for it. Every dollar of burn that does not directly leverage a self-carrying asset is a betrayal of your fiduciary duty and a threat to your company’s survival.
Insight 3: The Ethical Transition of Distressed Assets (Competition & Human Dignity)
What happens when an asset is truly dead? In a startup, this represents a failed product line, a legacy codebase that must be retired, or an employee who must be let go. Leaving these assets in place is disastrous, but how we transition them is a measure of our ethical integrity.
The Arukh HaShulchan deals with a highly sensitive case: a corpse (which is muktzeh—forbidden to be moved on Shabbat) that is left exposed to the elements:
"מת שמוטל בחמה... מניח עליו ככר או תינוק ומטלטלו..." (A corpse lying in the sun... one places upon it a loaf of bread or a child and moves it...) Arukh HaShulchan, Orach Chaim 312:4.
Leaving a human corpse to rot in the sun violates the supreme Jewish value of Kevod HaBriyot (human dignity). Yet, the laws of Shabbat strictly forbid moving a corpse. To resolve this tension, the Sages developed a brilliant, ethical workaround: you place a permitted item—a loaf of bread (kikar) or a living child (tinok)—on top of the corpse. You then move the entire bundle. Because you are carrying the bundle for the sake of the permitted item (the bread or the child), you are permitted to move the corpse, thereby preserving human dignity without violating the structural integrity of the Shabbat laws.
This provides an extraordinary model for modern corporate restructuring and offboarding.
When a product line fails, or when an employee is no longer viable in their role, many founders engage in "quiet firing" or allow failed projects to linger in obscurity. This is the corporate equivalent of leaving a "corpse in the sun." It is degrading to the employee, confusing to the market, and toxic to company culture. It drags down the morale of the entire organization.
The ethical founder does not leave the corpse in the sun. Instead, they utilize the "loaf or child" strategy: constructive bundling.
For a failed product or legacy system, you do not let it rot and alienate customers. You bundle its IP or transition its users to a viable partner or a new, active product line (the "loaf"). You make the transition value-additive.
For an employee who must be let go, you do not cast them out brutally or make their life miserable so they quit. You bundle their departure with active, dignity-preserving support: generous severance, warm introductions to companies where their skills can be a "living," self-carrying asset, and career coaching (the "child"). You transition them in a way that preserves their professional dignity (Kevod HaBriyot) while maintaining the operational hygiene of your startup.
This is not soft-hearted philanthropy; it is high-ROI risk mitigation. A company that offboards people with genuine dignity preserves its employer brand, avoids costly litigation, and signals to the remaining team members that they are working for a highly ethical organization. You clear the dead weight, but you do so with profound respect.
Policy Move
The "Self-Carrying" Operational Audit & Offboarding Protocol (S-COAP)
To operationalize these three insights, your company will implement a bi-annual structural audit designed to eliminate organizational drag, ruthlessly prune unnecessary overhead, and transition distressed assets with maximum dignity.
[S-COAP BI-ANNUAL AUDIT]
│
┌────────────────────┼────────────────────┐
▼ ▼ ▼
[Talent Audit] [Overhead Audit] [Transition Protocol]
"Does the living "Is the bed truly "No corpses left in
carry itself?" secondary?" the sun: bundle it."
Step 1: The Talent Agency Classification (Applying "Chai Nosei Et Atzmo")
Every manager must evaluate their direct reports on a quadrant mapping Agency (Self-Carrying capability) against Value Delivery.
- Category A (Self-Carrying): High agency, high value. These individuals require minimal management overhead. They define their own tasks based on high-level company goals. Policy: Maximize autonomy, increase equity compensation, and remove administrative barriers.
- Category B (Supported Living): High agency, developing value (e.g., junior engineers). They are self-motivated but need technical guidance. Policy: Pair with Category A mentors.
- Category C (Static Mass): Low agency, moderate value. They only move when pushed. They require extensive managerial "carrying." Policy: Place on an immediate 30-day "Agency Improvement Plan" (AIP) focused entirely on self-directed execution, not just task completion. If they cannot learn to carry themselves, they transition to Step 3.
Step 2: The Infrastructure & SaaS Rationalization (Applying "Meteh Tefilah")
Every department head must audit their software, consulting, and operational expenses. Every line item must be categorized as either:
- Direct Enabler (Tafiel): Software or infrastructure that is directly and actively used by a Category A or B employee to deliver value (e.g., GitHub for developers, Salesforce for active AEs).
- Excess Clothing (Bgadir She'eino Tzrichim): Software licenses that have not been accessed in 30 days, redundant project management tools, or vanity services.
- Policy: Immediately cancel all "Excess Clothing." No tool is kept because "we might need it next quarter." If an asset is not actively serving a living, value-generating process, it is a liability.
Step 3: The Dignified Transition Protocol (Applying "Kikar O Tinok")
When a product line is sunsetted or an employee is terminated under Step 1, the transition must follow the "Loaf or Child" protocol to ensure no corporate "corpse" is left to degrade in the sun.
- Product Sunsetting: Customers must be given a 60-day migration path to a competitor or partner, bundled with a discount or data-export tool (the "loaf"), ensuring the company’s reputation remains pristine.
- Employee Separation: Terminations must never occur via automated email or sudden, cold lockouts (unless security risks dictate otherwise). Every departed employee is provided with:
- A minimum of 4 weeks of severance to bridge the gap.
- An opt-in "Alumni Directory" shared with friendly VCs and recruiters.
- A designated transition coach to help them package their skills for their next role.
The KPI Proxy: The Structural Leverage Ratio (SLR)
To measure the success of this policy, the finance team will track the Structural Leverage Ratio (SLR) on a monthly basis:
$$\text{SLR} = \frac{\text{ARR (Annual Recurring Revenue)} \times \text{Talent Density %}}{\text{Total Non-Talent Overhead} + \text{Cost of Low-Agency Management Hours}}$$
Where:
- Talent Density % = $\frac{\text{Number of Category A & B Employees}}{\text{Total Headcount}}$
- Cost of Low-Agency Management Hours = Estimated hours managers spend micro-managing Category C employees multiplied by their hourly loaded cost.
Target: Your SLR must remain above 4.0x. A falling SLR indicates you are accumulating "unnecessary clothes" on your bed and carrying too much passive mass.
Board-Level Question
"Are we carrying 'dead weight' on our balance sheet under the guise of future capacity, and are we forcing our 'living' assets to bear the moral and operational friction of this bloat?"
[BOARD-LEVEL EVALUATION]
│
┌──────────────────┴──────────────────┐
▼ ▼
[Is headcount growing [Is management overhead
faster than revenue?] increasing per capita?]
│ │
▼ ▼
Indicates accumulation of Indicates accumulation of
"Unnecessary Clothes" "Passive Mass" (Non-Self-Carrying)
The Context and Strategic Risk
In board meetings, the default metric for "scale" is often headcount growth. When a company raises a Series A or B, the immediate pressure from investors is to "hire, hire, hire." This is a highly dangerous proxy for success. Headcount growth without strict adherence to talent density creates a massive carrying liability.
If your headcount is growing faster than your revenue or product velocity, you are not scaling; you are bloating. You are piling "clothes on the bed" Arukh HaShulchan, Orach Chaim 312:3.
The strategic risk is twofold:
- Capital Efficiency: You burn through runway funding administrative drag rather than product-market fit.
- Cultural Degradation: Your highest-performing, self-carrying talent will eventually realize they are carrying the entire organization. They will look at the low-agency team members receiving the same equity upside or salary, and they will leave. You will be left with an organization of "corpses" that require constant carrying.
How to Interpret the Executive Team’s Response
When you ask this question at the board level, look for these red flags in the leadership team's answers:
- Defensive Answer: "We need this headcount because our competitors have 100 people and we only have 50. We are building infrastructure for the future."
- Interpretation: The founders are insecure. They are using headcount as a vanity metric to soothe their ego. They are ignoring the halachic truth that "the living carries itself." If their 50 people were truly high-agency, they wouldn't need to match competitor headcount.
- Process-Oriented Answer: "We are implementing more management layers and Jira tracking workflows to make sure everyone is executing."
- Interpretation: They are trying to build a heavier "bed" to carry passive mass. Instead of raising talent density, they are increasing management overhead. They are compounding the liability.
- The Right Answer: "We have identified that 15% of our team is low-agency and requires too much carrying. We are actively transitioning them out using our Dignified Transition Protocol, and we have canceled $20k/month in unused SaaS tools. We are focusing our capital on compounding our Category A talent."
- Interpretation: The founders understand operational truth. They are committed to high talent density and capital efficiency. They are keeping the bed secondary and ensuring their assets are self-carrying.
Takeaway
A startup is not a family; it is a high-performance sports team. Your job as a founder is not to build a welfare state for mediocre talent or to accumulate vanity software licenses. Your job is to win.
The Arukh HaShulchan provides the ultimate blueprint for this lean, high-velocity execution:
- Keep your team self-carrying: Only hire and retain high-agency talent who generate their own kinetic energy Arukh HaShulchan, Orach Chaim 312:1.
- Ruthlessly prune your bed: Ensure that every dollar of overhead is strictly auxiliary to the productivity of your living assets Arukh HaShulchan, Orach Chaim 312:3.
- Never leave a corpse in the sun: When an asset or employee is no longer viable, transition them immediately, cleanly, and with profound professional dignity Arukh HaShulchan, Orach Chaim 312:4.
By aligning your operations with these timeless halachic parameters, you eliminate organizational drag, extend your runway, and build a culture of high-agency excellence that can out-execute any competitor. Stop carrying dead weight. Build a living organization that carries itself.
derekhlearning.com