Menachot 87

Hook

The founder’s dilemma is rarely about "good vs. evil." It’s almost always about "good enough vs. excellent." In the early days of a startup, you are perpetually tempted to ship the "flour-like white scum"—the impurities, the technical debt, the "just-good-enough" features—because you are desperate for momentum. You tell yourself, "We’ll fix it in the next release," or "The customer won't notice the sediment at the bottom of the cask."

But the Mishna in Menachot 87a presents a brutal reality check for the builder: the Temple treasurer didn’t just look at the wine; he actively inspected the integrity of the supply. When he saw the hagir (the chalk-like scum), he didn't adjust his expectations; he immediately knocked the reed to halt the flow. He knew that the quality of the offering defined the sanctity of the entire operation. As a founder, your product is your offering. When you normalize "scum" in your process—whether it’s sloppy code, half-baked customer support, or a "good enough" culture—you aren't just cutting corners; you are diluting the value of the entire enterprise. The question is: Do you have a "treasurer" in your org—a process or a person—who is empowered to "knock with the reed" the moment the quality dips below the "middle third" of the cask?

Text Snapshot

"The treasurer sits alongside the cask and has the measuring reed in his hand. The spigot is opened and the wine begins to flow. When he sees that the wine emerging draws with it chalk-like scum, he immediately knocks with the reed to indicate that the spigot should be closed." (Menachot 87a)

Analysis

Insight 1: The "Middle Third" Principle of Fairness and Quality

The Gemara insists that we don't take from the top (the scum) or the bottom (the sediment), but from the "middle third." In business, this is a radical rejection of extremes. Taking from the top is selling "hype"—features that don't exist yet or marketing that promises the world but delivers only surface-level vapor. Taking from the bottom is selling "legacy debt"—shipping the dregs of your R&D because you’re too lazy to clean the process.

Decision Rule: True quality exists in the "middle." It is the consistent, repeatable core of your value proposition. If your product requires constant "dilution" (compensating with excessive customer support or marketing spin), you are operating in the sediment. If your product is all "scum" (buzzwords, no substance), you are operating on the surface. Aim for the center of the cask: consistent, dense, and pure.

Insight 2: The High Cost of "Noise"

The Talmud notes that "just as speech is beneficial to the incense spices, so is speech detrimental to wine." The treasurer avoids speaking while inspecting the wine because vibration and agitation can disturb the purity of the pour.

Decision Rule: There is a "physics of operations." Sometimes, the sheer noise of a startup—the constant pivoting, the loud Slack channels, the frantic meetings—is what causes the "scum" to float to the surface. Effective quality control requires silence and focus. When you are inspecting your product for "sediment" (bugs, churn-inducing UX), do it in an environment that isn't agitated by the noise of panic. Silence is a competitive advantage in quality assurance.

Insight 3: Cultivation is the ROI Driver

The Gemara highlights Rav Yosef’s orchard, which was hoed twice (refik la-tei) and produced wine so potent it could be diluted with twice the water of normal wine. This isn’t just a farming tip; it’s a growth strategy.

Decision Rule: The quality of your "output" is a direct result of the intensity of your "cultivation." You cannot expect premium results from an under-tilled market or a neglected product stack. If you want to scale—to "dilute" your product for a mass market without losing its essence—you must have put in the "extra hoeing" during the R&D and team-building phase. Quality isn't found; it’s cultivated through repetitive, disciplined investment in the fundamentals.

Policy Move

The "Reed-Knock" Quality Gate: Implement a "Stop-the-Line" policy for your engineering and product teams, modeled after the treasurer’s reed.

Every sprint, designate a "Treasurer" (a rotating role, not necessarily the CTO) whose sole authority is to halt any deployment that shows signs of "white scum"—technical debt masquerading as features, or customer-facing bugs that degrade the core experience. This person does not need permission from the CEO to "knock the reed."

KPI Proxy: "Days Since Last Stop-the-Line." If this number is too high, you are likely ignoring sediment. If it’s too frequent, your cultivation (training and standards) is failing. Target a "Goldilocks" frequency where the team is empowered to self-correct before the "cask" (the market) is contaminated.

Board-Level Question

"Looking at our current product roadmap, which features are we shipping because they are ‘pure wine’ from the middle of the cask, and which are we shipping because they are the ‘chalk-like scum’ floating on top? Specifically, what are we currently ‘diluting’ with excessive marketing or support overhead, and how much would our long-term ROI increase if we simply chose to discard that sediment today rather than forcing our customers to consume it?"

Takeaway

The treasurer didn't try to filter the scum; he refused to serve it. In a world of "move fast and break things," the Mensch founder understands that "moving fast" is useless if you are shipping tainted goods. True scale comes from the "middle third"—the pure, intentional, and well-cultivated core of your product. Stop trying to polish the scum. Knock the reed, close the spigot, and demand the quality that makes your offering worthy of the table.