Daf Yomi · Startup Mensch · Standard

Menachot 70

StandardStartup MenschMarch 22, 2026

Hook

Every founder faces the “Pivot vs. Persistence” paradox. You build a product, you ship it, you get traction, and then you decide to iterate. But here is the silent killer: How much of your previous success carries over, and how much is now subject to a new set of rules?

In Menachot 70, the Gemara wrestles with a farmer who tithes his grain, replants it, and watches it grow further. Does the original tithe cover the new growth? Or is the new growth a "new asset" that requires a fresh tax?

This isn't just about agriculture; it’s about the integrity of your revenue streams. When you take a successful feature or a proven business model and "replant" it into a new market or a new version, do you treat it as an extension of the old, or as a distinct entity? Founders constantly try to "grandfather in" old rules to save time, avoid compliance, or bypass new obligations. The Torah demands we stop and ask: Has the nature of this asset changed?

When you scale a product, you are "planting" your original effort into a different soil—a new cohort, a different geography, or a more mature regulatory environment. If you act as if the old "tithe"—the old cost structure, the old customer agreement, or the old ethical standard—still applies, you might be building on a foundation that has legally and ethically "disintegrated."

The text asks: "Does the subsequent growth require the separation of tithes?" The danger for a startup is assuming that because you "tithed" (vetted, secured, or legalized) your initial MVP, your scaled-up version is automatically covered. This is the Founder’s Fallacy of Continuous Coverage. If you don’t distinguish between your original investment and the incremental growth, you aren't just cutting corners; you are losing your status as a Mensch. You are treating a new, distinct value-add as if it were still the initial, already-processed seed. You need to know when your business has outgrown its previous compliance shell.

Analysis

Insight 1: The "Disintegration" Principle (Integrity of Assets)

Rabba distinguishes between seeds that disintegrate and those that do not: “I do not raise the dilemma with regard to a substance whose seed disintegrates in the ground... In such a case it is clear that the new growth requires a new tithe.”

In business, you must audit your "seeds." If your core intellectual property or original business model has been fundamentally transformed, destroyed, or "disintegrated" during a pivot, it is no longer the same asset. Trying to apply the same governance, the same legal protections, or the same customer promises to a fundamentally different output is a failure of logic.

Decision Rule: Identify your "disintegrated assets." If the value proposition of your current iteration no longer relies on the original mechanism, stop pretending it does. If you’ve pivoted, your compliance and ethical framework must be re-baselined. You cannot claim the "tax exemption" of your past success if your current product is a different biological entity.

Insight 2: The "Normal Way" (Market Norms vs. Innovation)

The Gemara notes: “There, in the case of the field sowed with the tithed onions, the entire field must be tithed because that is the normal way in which a field is sowed... Here, in the case of grain, this is not the normal way.”

Context dictates the obligation. The law treats your actions differently based on whether you are following industry standards or acting in an "abnormal" (innovative) way. When you operate within established industry norms (the "normal way"), expectations for compliance and ethics are predictable. When you innovate (the "abnormal way"), you are often operating in a gray area that the law hasn't caught up to yet.

Decision Rule: If you are disrupting, you are not exempt from the "tithe." In fact, you are more obligated. Innovation does not grant you a waiver from basic ethical duties. The "abnormal" nature of your growth means you must define your own clear, transparent rules because standard industry norms no longer apply to your specific, unique process.

Insight 3: The "Attached to the Ground" Fallacy (Liability)

The Sages argue: “We do not find a case of teruma attached to the ground.” Abaye clarifies this by noting that even if one eats in an "abnormal" way, it doesn't change the underlying reality of the obligation.

Founders often try to hide behind the status of "in-development" or "beta." They argue that because the product is "attached to the ground" (not yet fully launched, in testing, or internal), they aren't liable for the same ethical or legal standards as a public product. The Gemara rejects this. Your intent, or the "abnormal" state of your development, does not absolve you from the responsibility of your actions.

Decision Rule: Liability starts at the root, not the harvest. If you are building it, you are responsible for it. Do not wait for the "official launch" (the detachment of the crop) to apply ethical rigor. If your product is "growing," it is already subject to the rules of the ecosystem.

Policy Move

The "Re-Baselining Audit" Process

To operationalize the logic of Menachot 70, every startup should implement a "Re-Baselining Audit" (RBA) during every major product pivot or market expansion.

The Policy: Any time the core product architecture or primary revenue model changes by more than 30% (measured by code churn, revenue attribution, or user base shift), the executive team must pause and issue an "Asset Integrity Report."

The Execution:

  1. The Disintegration Check: Did the original "seed" (the core IP or initial value proposition) survive this change? If not, the previous compliance and ethical certifications are void.
  2. The Tithe Reset: If the asset has changed, all new "growth" (revenue/user data) must be treated as untithed. This means a fresh review of data privacy, user consent, and ethical impact for the new growth, separate from the legacy product.
  3. The "Non-Perforated" Test: Are we operating in a "non-perforated pot" (a walled garden or private beta)? If so, we must acknowledge that our standards are currently "rabbinic" (internal/voluntary) but must be prepared to move to "Torah-level" (full regulatory compliance) the moment we "perforate the pot" (open to the public).

Metric for Success: Compliance Debt Ratio. Calculate the percentage of your product's "growth" (new features/revenue) that is covered by legacy compliance documents versus the percentage that has been audited under your new RBA process. Your goal is a 0% delta between "new growth" and "new audit."

Board-Level Question

“We are currently treating our new market expansion as an extension of our existing compliance and ethical framework. Given that our product has fundamentally changed from the 'seed' we started with, are we unintentionally claiming a 'tax exemption' on our new growth that we are no longer entitled to, and what happens to our firm if a regulator or a customer decides that our legacy compliance does not cover this new, 're-planted' iteration?”

This forces the Board to look at the scale-risk. If they answer that "it's basically the same thing," they are failing to recognize the "disintegration" of the original asset. If they acknowledge the difference, they are forced to approve the budget and time for the RBA. It shifts the conversation from "Are we moving fast enough?" to "Is our foundation still holding the weight of our current growth?"

Takeaway

You are not a farmer who can rely on a one-time blessing for a lifetime of growth. Your business is a living, changing entity. When you scale, you don’t just get more grain; you get more responsibility. The Mensch founder knows that growth requires constant re-evaluation. If you are not tithing your new growth, you are not scaling—you are merely accumulating untithed produce. And in the long run, untithed growth is just debt waiting to be collected.

Be a Mensch: Own the new reality of your product. If it’s different, it’s new. If it’s new, it’s yours to secure, to vet, and to tithe. Don't let your success become your liability.