Deuteronomy 15

Hook

The founder’s dilemma is rarely about "if" to scale, but "when" to cut losses. We live in a culture of "never give up," a toxic hyper-fixation on growth that confuses persistence with martyrdom. You hold onto that failing product line because of the sunk cost fallacy. You keep that underperforming executive because you’re afraid of the optics of a firing. You chase a failing pivot because you’re terrified of the "failure" label.

Deuteronomy 15 isn’t just a religious text; it’s a masterclass in cycle management. It introduces the Shmita (remission) and the release of slaves. It forces a hard stop. It demands that you acknowledge that your grip on assets, debts, and labor is not infinite. If you are a founder who refuses to build "off-ramps" into your business model, you aren’t being "determined"—you are being undisciplined. The text forces a transition from an ego-driven, hoarding mentality to a system-driven, sustainable one. It challenges you: are you running a business that creates value, or are you running a cult of personal attachment? If you cannot release, you cannot lead.

Text Snapshot

"Every seventh year you shall practice remission of debts. This shall be the nature of the remission: all creditors shall remit the due that they claim from their fellow Israelites... There shall be no needy among you... do not harden your heart and shut your hand against your needy kindred. Rather, you must open your hand and lend whatever is sufficient to meet the need." (Deuteronomy 15:1-8)

Analysis

Insight 1: The ROI of the Hard Stop

The text specifies that remission is not a whim; it is a structural mandate: "Every seventh year you shall practice remission of debts" (15:1). Ramban clarifies that this is a "cessation," a complete pause. In startup terms, this is your annual audit, your quarterly reset, or your product end-of-life (EOL) schedule. If your business model lacks a mechanism to periodically "zero out" legacy debt—be it technical, emotional, or financial—you are accumulating rot.

Decision Rule: If an initiative or debt hasn't yielded returns within a predetermined cycle, it must be cleared. This prevents "zombie projects" from draining resources. The "remission" forces you to confront the reality of your balance sheet rather than hiding behind a spreadsheet of "expected future value."

Insight 2: The "Base Thought" and Cognitive Bias

The text warns against a specific psychological trap: "Beware lest you harbor the base thought, ‘The seventh year... is approaching,’ so that you are mean and give nothing" (15:9). This is a direct hit on the "Founder’s Loss Aversion." When you know a deadline is coming—an investor exit, a contract renewal, a pivot point—you instinctively tighten your grip. You stop investing in talent or customer success because you’re hoarding for the "winter."

Decision Rule: Never let the "end of the cycle" dictate your generosity or your operational integrity. If your business model relies on withholding resources from stakeholders (employees, partners, users) simply because you are approaching a fiscal cliff, your business model is fundamentally broken. You don't solve a cash crunch by being "mean"; you solve it by being better at value creation.

Insight 3: Hardship is a System, Not a Bug

The text admits a brutal reality: "For there will never cease to be needy ones in your land" (15:11). This is the ultimate refutation of utopian, "we’ll fix everything" founder-speak. You will always have churn. You will always have bugs. You will always have market volatility.

Decision Rule: Stop building as if you are aiming for a frictionless, perfect state. Design your organization for resilience in the face of inevitable hardship. If your strategy assumes that "needy" market segments or internal failures will disappear once you hit a certain ARR, you are delusional. Build the "open hand" (15:8)—a culture of support and liquidity—into your baseline operating expense.

Policy Move

The "Zero-Base Innovation" Policy: Every 18 months, implement a formal "Remission Period." For one sprint, all teams must justify their current projects as if they were starting from scratch. Any project that would not be started today if it didn't already exist is subject to "remission"—it is either cut, significantly restructured, or spun off.

This forces you to stop the "dunning" of your own team—the constant grinding for output on legacy systems that no longer serve the mission. By institutionalizing this "release," you force the company to shed "technical and operational debt."

• KPI Proxy: "Project Retirement Velocity"—the ratio of projects deprecated to new projects launched. A healthy ratio should be at least 0.3. If you’re only adding and never subtracting, you are building an empire of complexity, not a business of value.

Board-Level Question

"If we were to lose our current access to all 'legacy' revenue streams and codebases tomorrow, what would we build today with the resources we have left?"

This question forces leadership to detach from the "sunk cost" of their past labor. It shifts the conversation from "how do we protect what we have" (the hoarding mentality) to "how do we build what matters" (the growth mentality). If they can’t answer this, they are too attached to the past to navigate the future.

Takeaway

The Torah demands that you be a mensch by knowing when to let go. You are not the owner of your business; you are a steward of its mission. By forcing a periodic release of debts and ego-attachments, you ensure that your organization remains dynamic. A founder who cannot "remit" is a founder who eventually becomes a hostage to their own history. Open your hand, cut the dead weight, and stop fearing the end of the cycle—it’s the only way to ensure a new one begins.