Mishneh Torah, Sabbath 18-20

Hook

Every founder faces the "Minimum Viable Product" (MVP) dilemma. How small can you go before it’s not a product? How much do you need to ship before you’ve actually delivered value? We obsess over feature sets, market entry thresholds, and "traction" metrics. We live in a world of infinite growth, where the temptation is to ship early, ship often, and ignore the "small stuff." But in the architecture of business, as in the architecture of the Sabbath, the measure matters.

In the Mishneh Torah, Maimonides outlines the precise, granular minimums required to be liable for transferring an object on the Sabbath. If you carry a fig’s worth of food, you are liable. If you carry a fragment of metal, you are liable. If you carry a single seed, you might be liable, depending on your intent. The dilemma for the modern founder is this: Are you building a business that creates real value, or are you just moving "stuff" from one domain to another? If your business activities don’t meet the "measure of benefit"—if they don’t actually solve a problem for the user—you are effectively carrying nothing.

Founders often confuse activity with productivity. We send the emails, attend the syncs, and push the code. But if those actions don’t reach the shiur (measure) of impact, they are functionally zero. Maimonides teaches us that the law cares about the purpose behind the movement. If you are moving a product into the market without a clear, beneficial purpose that aligns with the customer's reality, you aren't building—you’re just wasting Sabbath-level energy on noise. This text is a masterclass in operational precision. It demands that we define exactly what "beneficial" looks like for our users, and it warns us that if we don't hit the threshold of usefulness, our efforts—no matter how frantic—are legally and ethically weightless.

Text Snapshot

"A person who transfers an article from a private domain into the public domain... is not liable unless he transfers an amount that will be beneficial [to accomplish a purpose]. The following are the minimum amounts for which one is liable for transferring: Human food, the size of a dried fig... For oil, enough to anoint the small toe of a newborn infant." (Mishneh Torah, Sabbath 18:1-2)

Analysis

Insight 1: The Law of Materiality (The "Shiur" Principle)

Maimonides establishes that liability—the threshold where an action moves from "inconsequential" to "significant"—is defined by the measure of benefit. In business, this is your unit economics. You can move a million units of a product, but if those units are below the "measure of benefit" for your customer, you have failed. The Rambam explains that "a person is not liable until he transfers an amount of a substance large enough to be of benefit to a person." For a founder, this is the ultimate KPI proxy. If your feature, update, or service is smaller than the "size of a dried fig" in terms of actual customer value, you are not generating liability—you are generating waste. You must define the minimum viable threshold for every interaction. If you are shipping features that don't reach the "size of a dried fig" in utility, you are burning your company's "Sabbath"—your precious, limited time—on activities that don't register as work in the eyes of the market.

Insight 2: Intent Defines the Measure

The Rambam makes a fascinating distinction: "When a person has an individual desire for an object that makes it beneficial for him, he is liable even though most people would not use that object for that purpose." This is the core of product-market fit. A feature that looks useless to the general market may be a "must-have" for a specific power user. If you target your product to the specific intent of a niche segment, your "minimum measure" for success drops significantly. You don't need to be everything to everyone; you only need to be the "size of a dried fig" to your specific, high-intent user. This is the strategic justification for pivoting to a niche: you change the definition of "beneficial" to match the actual needs of your most valuable customers.

Insight 3: The Danger of "Secondary" Assets

Maimonides notes: "When a person transfers two articles, one of primary importance and one of secondary importance... the article of secondary importance is of no significance whatsoever." In startups, we often bundle "secondary" features with our core value proposition. We think, "If I add this extra button, or this extra report, it’ll be more valuable." But the law of the Sabbath teaches that unless the secondary item is essential to the primary, it is just noise. If it doesn't serve the primary purpose, it’s a burden. This is the "feature creep" trap. If your product’s core value is the "fig," stop carrying around the "bran" and the "chaff." They don't count toward your success, and in a competitive market, they actually drag down your efficiency.

Policy Move

The "Shiur" Audit Protocol: Every quarter, leadership must conduct a "Shiur Audit." Every feature, service level agreement, or internal project must be measured against the "Dried Fig Standard."

The Process:

1. Define the Fig: For every product module, define the absolute minimum output required to trigger a "beneficial" outcome for a user (e.g., "The user must be able to export a report in under 3 seconds").
2. Eliminate the Chaff: If a feature or process cannot be articulated as contributing to this "Fig," it is categorized as "Chaff."
3. The Sunset Clause: Any "Chaff" identified in the audit that is not a direct, essential dependency for the primary value must be sunsetted or moved to a "Low-Priority" backlog.
4. Metric: Measure "Utility Density"—the ratio of core-value features to total features shipped. If your Utility Density drops, you are becoming a "carrier of burdens" rather than a "creator of value."

This forces your team to stop building for the sake of building and start shipping for the sake of benefit. If you aren't hitting the measure of benefit, you aren't doing the work.

Board-Level Question

"If we were to strip away every feature and process that currently falls below our defined 'Minimum Measure of Benefit'—the threshold that actually solves a customer's core problem—how much of our current engineering and operational spend would be revealed as 'carrying burdens' rather than 'performing purposeful work'?"

Takeaway

You are not paid for the amount of effort you exert; you are paid for the significance of your output. Maimonides teaches that in the economy of the Sabbath, the universe cares about whether your actions hit the mark. In your business, stop measuring activity and start measuring benefit. If your product, your code, and your team’s daily output don't meet the "Dried Fig Standard," you aren't building a company—you’re just moving empty containers across the public domain. Stop carrying the noise. Focus on the measure.