Mishneh Torah, Blessings 8

Hook

The founder’s dilemma is rarely about "what to do." It is almost always about "what to prioritize." You are buried in a deluge of incoming data—feature requests, pivot signals, investor emails, and team friction. In this state of perpetual noise, you lose the ability to categorize the essential from the incidental. You treat every fire as a five-alarm blaze, and every minor update as a foundational shift. You are, in effect, blessing everything equally, which means you are valuing nothing.

Maimonides, in Mishneh Torah, Blessings 8, offers a masterclass in taxonomy. He isn’t just teaching you how to say grace; he is teaching you how to build a mental framework for resource allocation. He distinguishes between fruit that grows from the tree, fruit from the earth, and things that provide no benefit at all. He demands that you pause, identify the nature of what you are consuming, and act accordingly.

In business, if you cannot distinguish between a core product (the "tree") and an auxiliary service (the "vegetable"), or between an actual strategic win and mere "sugared water" that offers no long-term sustenance, you are operationally illiterate. Founders who fail to apply this level of precision to their business model—who fail to define which tasks deserve a "full blessing" (deep focus/capital) and which deserve a shehakol (a quick, generic acknowledgment)—eventually burn out because they are giving 100% of their energy to 100% of their inputs.

This text forces us to ask: What are you actually building? Is your current activity a "seven species" priority—something that builds the land, the core infrastructure of your enterprise—or is it a byproduct that should be handled with a cursory glance and a quick move to the next item? If you are treating everything as equally important, you are lying to yourself. Precision in categorization is not just a religious exercise; it is a competitive advantage. It is the difference between a founder who is perpetually busy and a founder who is ruthlessly effective. It is time to audit your operations against the logic of the Blessings.

Analysis

Insight 1: The Principle of Categorization (The "Tree vs. Earth" Rule)

Maimonides dictates that different sources require different responses: “When partaking of all fruit that grows on trees, we recite the blessing borey pri ha'etz... [When partaking of] fruit that grows from the earth and vegetables, we recite the blessing borey pri ha'adamah” (8:1).

In organizational terms, this is the imperative to correctly identify the "root" of your revenue and value. A "tree" is a long-term asset—it yields fruit season after season. A "vegetable" is often a seasonal, fleeting gain. The error many founders make is misclassifying a short-term, high-maintenance vegetable as a tree. They invest massive overhead into a project that doesn't have the structural longevity to support it.

Decision Rule: Before you commit a single dollar of burn, classify the activity. Is it a core, perennial asset (Tree)? Is it a project-based, seasonal requirement (Earth)? Or is it a generic, non-essential transaction (Shehakol)? If you treat a shehakol project with the time investment of an ha'etz project, you are destroying your ROI.

Insight 2: The Utility Test (The "Thirst" Criterion)

The text notes: “When a person drinks water for an intention other than fulfilling his thirst, it is not necessary for him to recite a blessing” (8:4). This is the "Utility Test." If the action does not provide the primary, intended benefit, it does not require a formal, dedicated investment of energy.

Founders suffer from "feature creep" and "meeting bloat." They hold meetings for information that could be an email; they build features that nobody asked for. If an action does not directly serve your mission (thirst), stop formalizing it. Don't waste "blessings"—your focused energy—on things that provide no real, measurable value.

Decision Rule: If an activity doesn't move the needle on your primary KPI, do not treat it with the same ceremony as your core product development. If it doesn't quench your company's "thirst," it shouldn't consume your time.

Insight 3: The Hierarchy of Importance (Precedence)

Maimonides outlines a strict hierarchy: “The order of precedence depends on one's desires... If among the foods there are foods from the seven species... the blessing should be recited over them first” (8:12).

This is about ruthless prioritization. You cannot address every problem at once. You must have a "Seven Species" list for your company—the five or seven key metrics or strategic initiatives that actually define your success. When you start your week, you don't start with the "vegetables." You start with the "wheat, barley, vines, figs, and pomegranates." You prioritize the core. Everything else is secondary, and the system is designed to reward that focus.

Decision Rule: Your "Seven Species" are your company’s North Star metrics. If it isn't in your top-tier list, it waits. You must consciously structure your calendar to address these items before the generic, low-impact tasks.

Policy Move

The "Blessing Audit" Protocol

Implement a mandatory "Blessing Audit" for every new project or feature launch. Before a team can begin development, they must fill out a one-page "Source Classification" document.

The Process:

1. Source Identification: Identify the "Source" of the activity. Is it a Tree (Core Business), Earth (Secondary/Market-Driven), or Shehakol (Utility/Maintenance)?
2. Utility Check: Does this satisfy a "thirst" (Market Need) or is it for "another intention" (Vanity/Internal Preference)? If the latter, it is marked for immediate de-prioritization.
3. Precedence Ranking: Where does this sit on our Seven Species list? If it does not rank, it is delegated or discarded.

KPI Proxy: The "Utility Ratio." Measure the percentage of engineering hours spent on "Tree" projects vs. "Shehakol" maintenance tasks. A healthy startup should see this ratio shift toward the "Tree" as the company matures. If your "Shehakol" overhead is growing faster than your "Tree" output, you are losing your competitive edge to administrative bloat.

Board-Level Question

The "Core vs. Byproduct" Challenge

"We are currently spending [X]% of our burn on initiatives that, by our own definition, are shehakol—generic, non-foundational activities. Looking at our current roadmap, which of our 'fruits' are actually 'trees' that justify our current level of capital investment, and which are simply 'spoiled food' that we are continuing to bless out of habit rather than necessity?"

This question forces the leadership team to confront the reality that they are likely over-investing in low-impact areas. It shifts the conversation from "Are we working hard?" to "Are we focusing on the right source of value?" It creates a culture of accountability where every project must justify its existence relative to the core mission.

Takeaway

You are not paid to be busy; you are paid to distinguish. The Mishneh Torah isn't a list of rules for dinner; it's a manual for clarity. By categorizing your tasks, testing their utility, and strictly prioritizing your "Seven Species," you stop the bleeding of focus that kills most startups. Precision is the ultimate founder hack. Stop blessing everything, and start investing only in what actually sustains your enterprise.