Menachot 70

Hook

The founder’s dilemma is rarely about starting from zero; it is about scaling what already exists. You have a product, a process, or a codebase—the "main growth"—that you have already vetted, compliance-checked, and launched. Then, you decide to pivot or expand, effectively "replanting" that core asset into a new market or a new feature set. The dilemma hits when the new growth begins to sprout.

Do you treat this iteration as a fresh entity that requires a full compliance audit, or do you rely on the "tithing" you already performed on the original version? In Menachot 70, the sages debate whether the initial "tithing" (the compliance or validation of your MVP) covers the subsequent growth.

If you treat the new growth as exempt, you risk cutting corners on quality and regulatory requirements. If you treat it as a new entity, you risk over-engineering and burning resources on processes you’ve already mastered. The Talmud doesn't just offer a theological debate; it offers a framework for technical debt and product governance. How do you distinguish between a legitimate iteration of an existing asset and a new venture that demands a fresh "separation" of resources?

Text Snapshot

"One estimated the amount of tithe necessary, and then he separated those tithes, and then he planted the grain again and it added to its growth... I do not raise the dilemma with regard to a substance whose seed disintegrates in the ground... Rather, when I raise the dilemma it is with regard to a substance whose original seed does not disintegrate." (Menachot 70a)

Analysis

Insight 1: The Distinction Between Disintegration and Evolution

The Talmud makes a sharp distinction between a seed that "disintegrates" and one that remains intact. In business terms, this is the difference between a pivot and an iteration. If your product "disintegrates"—meaning the original value proposition is entirely consumed or replaced by the new version—you are obligated to perform a new round of "tithing" (compliance, testing, and validation).

If the seed remains intact—meaning you are scaling the same core engine into a new market—the dilemma is whether the old compliance regime holds. The decision rule here is Functional Continuity: If your expansion requires a fundamental change in the "DNA" of the product, treat it as a new product. Do not hide behind the "tithe" of a previous iteration to justify lack of oversight in a new context.

Insight 2: The "Normal Path" of Scaling

The Gemara rejects a resolution from onions because "that is the normal way in which a field is sowed." In scaling your business, you must ask: Is this expansion following the "normal" growth pattern of my industry, or is it an anomaly?

When you scale, you often assume that because the method of growth is standard, the rules of the original state apply. The Sages challenge this. Just because you are using an established, "normal" process to grow your business does not exempt you from the obligation to re-verify your outcomes. If you are using an established, "normal" channel (like a proven sales funnel) to push a new product, you cannot simply assume the previous compliance and quality standards are sufficient. The growth dictates the status, not the process.

Insight 3: The Myth of "Attached" Compliance

The Sages discuss teruma (tithe) that is "attached to the ground," noting that "we do not find a case of teruma attached to the ground." This is a crucial lesson for founders: Compliance cannot be "attached" to an ongoing, unfinished process.

Many founders believe that because their product is "live" and "in the market," it is inherently compliant. The Talmudic logic here is that you cannot sanctify or validate something that hasn't been detached from the chaotic, unrefined state of raw growth. You must "detach" your features—bring them to a point of completion—before you can truly certify them. You cannot "tithe" (validate) a feature that is still in a state of rapid, uncontrolled flux.

KPI Proxy: Validation Velocity vs. Release Velocity. If your release velocity exceeds your validation velocity (the rate at which you perform formal quality and compliance checks), you are effectively eating "untithed" growth. Aim for a 1:1 ratio.

Policy Move: The "Compliance Detachment" Protocol

To avoid the trap of "attached" compliance, implement the "Feature Detachment" Policy.

Currently, many engineering teams treat "scaling" as a continuous, unbroken line from R&D to production. Under the Menachot model, this is a mistake.

The Policy:

1. The Harvest Point: No feature or market expansion can rely on the compliance certification of the "seed" (the previous iteration) if the new growth exceeds the original scope by more than 20%.
2. Mandatory Detachment: Before any "tithe" (security audit, data privacy review, or quality assurance sign-off) is considered valid for a new iteration, the feature must be "detached" from the primary branch. This means moving it into a hardened, static state where it is no longer being actively modified by the core development team.
3. Re-Tithing: Once "detached," the feature must undergo a specific, documented validation audit. This prevents the "it worked before, so it works now" mentality that leads to technical and ethical debt.

Metric: Delta-Compliance Score. Measure the percentage of new code/features that have undergone a "Detachment Audit" vs. those that are riding on the legacy compliance of the original "seed."

Board-Level Question

"We are currently scaling our core product into [New Market/New Feature]. Based on our analysis of the 'seed'—the original product's compliance and value—have we fundamentally changed the nature of the 'grain'? In other words, are we relying on the 'tithe' of our past success to cover the risks of our current expansion, and if so, what specific 'new growth' risks have we failed to measure?"

Takeaway

You are responsible for the crop you currently harvest, not the crop you planted three versions ago. Do not confuse the "normalcy" of your growth process with the "validity" of your output. When you scale, you must "detach" your new work from your old successes, audit it as a distinct entity, and ensure that your compliance is as robust as your ambition. Be a mensch in your product lifecycle: don't sell "untithed" growth to your customers.