Menachot 61

Hook

The founder’s dilemma in Menachot 61 isn’t about ritual; it’s about taxonomy of value. Every startup faces the same question: "Which of our activities are 'core' and which are 'adjunct'?"

In the text, the Sages agonize over whether a meal offering requires "bringing near" (hagashah) to the altar. They aren’t debating busywork; they are defining the essential proximity required for a contribution to count. They exclude the meal offering of the priest or the one brought with libations because those are secondary—they are attached to something else. They include the "stand-alone" offerings because those carry their own weight.

Founders suffer from "Libation Syndrome." You launch features, services, and partnerships that are technically functional but exist only to support a larger, often bloated, legacy product. You spend your capital and your team’s cognitive bandwidth "bringing near" these secondary offerings, treating them with the same ritual importance as your core value proposition.

The baraita asks, "What did you see that led you to include [this] and exclude [that]?" It demands a rigorous logical framework for prioritization. If you cannot explain why a feature deserves the investment of your "handful" (your best resources), you are merely cluttering the altar.

In business, as in the Temple, if you treat everything as a high-stakes ritual, nothing is. When everything is a priority, nothing is a priority. This text is a masterclass in stripping away the "libations"—the noise—to find the core of the business. Are you building a standalone entity that holds its own weight, or are you just a side-dish to your own past decisions? The Talmud teaches that before you wave your offering, you must first define if it even belongs on the altar. If it doesn't stand on its own, stop wasting your "handful" on it.

Analysis

Insight 1: The Principle of Independent Viability (Fairness)

The Sages distinguish between offerings that come "due to themselves" (ba'ot biglal atzman) and those that are "attached" (nilvit). In a startup context, this is the Unit Economics Test.

The text notes: "I include the other meal offerings, as they come due to themselves... and I exclude the meal offering brought with libations."

Decision Rule: If a feature or business line requires an "animal offering" (a massive, separate subsidy of capital or engineering time) just to justify its existence, it is a libation. A product that is not independently viable, or at least on a clear path to being so, is a drag on the ecosystem. Fairness, in the eyes of the baraita, is giving your limited resources (the "handful") only to that which can stand independently. If your secondary product lines are not contributing their own "pleasing aroma" to the bottom line, they are parasitic, not synergetic.

Insight 2: Precision in Execution (Truth)

The Gemara is obsessive about the how of the ritual: "Just as the taking off... is performed specifically with the priest’s handful and not with a vessel."

They reject the use of a tool (the vessel) in favor of the direct human touch (the handful).

Decision Rule: Stop automating your core value. Many founders try to scale too early using "vessels"—abstracted processes, outsourced teams, or bloated software layers—to perform tasks that require the "handful," the direct, human judgment of the founder. When you are establishing your core value, you must use your own hands. If you are outsourcing the "taking off" of your core metrics or your customer discovery, you are losing the kavanah (intention) that makes the product viable. Truth in business is found where the founder’s hand meets the customer’s need. If you can’t describe the "handful" of your business—your specific, non-delegatable competitive advantage—you have no business.

Insight 3: The Synergy of Ownership (Competition)

The discussion of the log of oil and the guilt offering being waved together reveals a profound truth about bundling: "The plural form 'them' teaches that the log of oil and the offering require waving, and that this should be performed with both of them together."

Decision Rule: Bundling must be intentional, not accidental. The Sages allow the oil and the guilt offering to be waved together, but they forbid multiple, redundant wavings. They seek one efficient, unified action.

In your competitive strategy, do not bundle features just because they are "related." Bundle them only if they function as a single, stronger offering. If your product roadmap is a jumble of disparate features, you are wasting the "waving" motion. Effective competition requires that your product feels like one cohesive unit—the "breast and thigh" brought together—rather than a collection of broken parts. If you are waiving your features to the market, make sure the bundle makes the offering stronger, not just more complicated.

Policy Move

The "Independent Viability" Audit (The 20% Rule)

To operationalize the wisdom of Menachot 61, I propose a quarterly "Altar Audit" for every product line and internal initiative.

Policy: Any initiative that consumes more than 20% of a team's capacity but does not produce at least 10% of the unit’s direct revenue (or equivalent KPI, such as active user growth) must be flagged as a "Libation."

The Process:

1. Categorization: Every project must be designated as a "Standalone" (must stand on its own revenue/KPIs) or a "Supportive" (a libation).
2. The "Handful" Review: If a project is "Supportive," the team must produce a "Justification of Attachment." Why does this specific feature exist only to support the core? If it could be spun out or cut without killing the core, it is failing the test of "coming due to itself."
3. The Sunset Clause: If an initiative is deemed a "Libation" and cannot demonstrate its necessity to the core product within one quarter, it is sunsetted immediately.

Metric/KPI Proxy: "Contribution Margin per Feature." Track the direct cost of development and maintenance of a feature versus the direct revenue or retention lift it drives. If the margin is negative or strictly dependent on the existence of another, larger product, it is a Libation. This forces the leadership team to stop hiding inefficient products inside the "bundle" of the overall company performance. You are not running a temple; you are running a business. Efficiency is your only path to growth.

Board-Level Question

The Strategic Question:

"Looking at our current product roadmap, which of our initiatives are 'standalone' offerings that justify their own existence, and which are merely 'libations'—features we are subsidizing with our core resources because we are too afraid to admit they don't hold their own weight?"

Context for the Board: Founders often cling to legacy features because they represent "sunk costs" or historical sentiment. By framing the conversation around the distinction between independent value and subsidized noise, you shift the board’s perspective from "What are we building?" to "What is actually creating value?" This question forces a pivot from a mindset of accumulation (adding more) to a mindset of distillation (refining the essence). It challenges the leadership to prove that every dollar spent is on an offering worthy of being "brought near" the altar of the market. If they cannot answer, they are not strategizing; they are just busy.

Takeaway

The Talmudic baraita in Menachot 61 is a stark reminder that scale does not excuse complexity. The priests were not allowed to treat every offering the same; they had to categorize, evaluate, and act with precision. As a founder, your resources—your time, your capital, your team's energy—are your "handful." If you are using that handful to wave offerings that do not deserve to be there, you are not building a business; you are performing a hollow ritual. Be ruthless in your taxonomy. If it doesn't stand alone, cut it. If it doesn't require your direct, expert hand, delegate it or drop it. Efficiency is the ultimate form of respect for your mission.