Shulchan Arukh, Orach Chayim 119:2-4

Hook

Founders, let's cut to the chase. You're building something new, something disruptive. Every decision, every dollar, every minute is scrutinized for ROI. You're wired for growth, for impact, for winning. But what happens when the pressure mounts, when the stakes are sky-high, and you feel the urge to… well, to pray for a specific outcome? This isn't about appeasing investors with a polished pitch deck; it's about navigating the ethical tightrope of personal appeals within the established structures of your business. Are those personal pleas for a sick co-founder, a critical funding round, or a competitor's stumble simply "asking for mercy" in the "Blessing of Years," or do they risk derailing the entire operation? The Shulchan Arukh grapples with this exact tension: the desire to insert personal, urgent needs into a framework designed for broader, more general supplication. It’s a founder dilemma disguised as a liturgical law. Can you afford to add your personal prayer to the company's "blessing," or does it create a problematic "interruption" that undermines the overall mission? This is where the ancient wisdom of Torah meets the modern imperative of scalable, ethical business.

Text Snapshot

"If one wanted to add in any of the middle blessings, something similar the blessing, one may add. How so? If one had a sick person, one asks for mercy for [that person] in the blessing of 'Refa'einu' ['Heal us']. If one needs a livelihood, one may ask for it in the 'Blessing of the Years'. And in [the blessing] of 'Shomeya Tefilla' ['Who hears prayers'], one may ask for any of one's needs, for it includes all the requests. [...] And according to Rabbeinu Yona, when one adds to the blessing something similar to that blessing, if one is adding it on behalf of all of Israel, one says it in plural language and not singular language, and one should only add at the end of the blessing and not the middle. And if one is asking specifically for one's own needs, for example: there is a sick person in one's home or one needs a livelihood, one can ask even in the middle of the blessing, as long as one does so in singular language and not plural language."

Analysis

The core of this passage is about integrating personal needs into a structured system without causing disruption. For a founder, this translates directly into how you handle personal appeals within the company's operational and ethical framework. We can derive three decision rules from this text, framed through the lens of fairness, truth, and competition.

Insight 1: Fairness – The "Public Need" vs. "Private Plea" Distinction

The text differentiates between adding prayers "on behalf of all of Israel" (plural, at the end) and "specifically for one's own needs" (singular, potentially in the middle). This distinction is critical for maintaining fairness within your organization.

• Decision Rule: When addressing urgent company needs that benefit the entire team or stakeholder group, frame them as collective objectives. When dealing with individual hardship or specific personal requests, ensure they are handled with discretion and don't appear to grant undue advantage.
• Application: If a key employee is facing a personal crisis that impacts their work, a company-supported leave or aid package (framed as a general policy for hardship) is "on behalf of all of Israel" in spirit – it supports the collective well-being of the team. However, if you, as a founder, are personally pushing for a specific vendor because they are a friend, that leans towards a "private plea" that could be perceived as unfair to other vendors who are equally or more qualified but lack personal connections. The Shulchan Arukh advises that if it's for one's "own needs," one can ask "even in the middle of the blessing." This implies a potential for personal intervention, but the caveat about not making it "lengthy" for individual needs suggests a need for efficiency and avoidance of undue influence. The commentary in Mishnah Berurah and Kaf HaChayim highlights that this is especially true for individual needs, as opposed to collective ones. The Ba'er Hetev even notes, "one should not make it lengthy" unless "many need his Torah," implying that individual requests should be concise and not disruptive.
• Metric Proxy: Track the number of vendor contracts awarded to entities with personal connections versus those awarded through a standard, objective procurement process. A widening gap could indicate a shift from collective benefit to private plea. Alternatively, survey employee sentiment regarding fairness in how personal hardship is addressed.

Insight 2: Truth – The Integrity of the "Blessing"

The Gloss and Rabbeinu Yona emphasize how one adds to a blessing: "one should begin the blessing and, after that, add, but one should not add and then begin the blessing." This is about maintaining the integrity and flow of the existing structure.

• Decision Rule: Ensure that any personal or urgent requests integrated into company processes are additive and supportive, not interruptive or deceptive. The underlying truth and purpose of the established process must remain intact.
• Application: Imagine your company is in a critical negotiation. A founder might be tempted to privately instruct the legal team to accept a less favorable term to close the deal quickly, driven by personal anxiety. This is akin to "adding and then beginning the blessing" – it subverts the established negotiation framework. The proper approach, according to the text, would be to first "begin the blessing" (i.e., follow the established negotiation strategy) and then, if necessary, "add" a specific, well-reasoned request within that framework (e.g., "Given the urgency, can we explore a phased approach to this clause?"). The Magen Avraham commentary, noting that a lengthy prayer is permitted for an individual if "many need his Torah," suggests that the justification for an extraordinary request matters. If the "need" is truly significant and benefits a wider group (like the "Mahril's Torah"), the "addition" is more permissible. But if the "addition" is a personal whim or an attempt to circumvent due diligence, it compromises the "truth" of the process. The commentary in Kaf HaChayim regarding "adding and then beginning" reinforces this: it's about not corrupting the established order.
• Metric Proxy: Measure the deviation of negotiated deal terms from pre-approved negotiation parameters or benchmarks. Significant deviations without clear, documented justification could signal a compromised "truth" in the process.

Insight 3: Competition – The "Shomeya Tefilla" of the Marketplace

The text states that in the "Blessing of 'Shomeya Tefilla' ['Who hears prayers'], one may ask for any of one's needs, for it includes all the requests." This is the catch-all, the final opportunity to voice any unmet need. In business, this translates to the broader market, the competitive landscape, and the ultimate "hearer" of your venture's success – the market itself.

• Decision Rule: Recognize that while dedicated channels exist for specific needs (like the "Refa'einu" for a sick team member), the overarching success of the company relies on its ability to adapt to all market demands and competitive pressures, especially in the "Shomeya Tefilla" phase of its lifecycle – its ultimate market validation.
• Application: If your startup is struggling against a dominant competitor, the "Shomeya Tefilla" of the market is where your ultimate request for success is made. You can't, ethically or practically, insert a personal plea to sabotage a competitor within your core product development or marketing strategy – that would be like trying to add a personal request into a blessing that isn't about competition. However, you can, and should, use your "Shomeya Tefilla" moment (your strategic planning, your R&D, your market positioning) to address these competitive realities. The Mishnah Berurah commentary, stating that one can ask for "any of one's needs" in "Shomeya Tefilla," implies that this is the place for broad, encompassing appeals. This means that addressing competitive threats is a valid, indeed essential, part of your company's ultimate "prayer" for success. The Kaf HaChayim commentary even discusses how in times of fasting and prayer (analogous to intense market pressure), congregations would ask for forgiveness and make requests, implying that collective appeals for survival and success are permissible and even expected during challenging periods. The key is that these are addressed within the "Shomeya Tefilla" – the overarching plea for divine or market favor – rather than trying to force a specific, potentially unethical, intervention into another "blessing" (e.g., product integrity).
• Metric Proxy: Track your market share growth relative to key competitors. A consistent decline could indicate that your "Shomeya Tefilla" – your strategic response to the market – is insufficient.

Policy Move

Policy: Implement a "Needs Integration Protocol" for urgent and personal company-related requests.

Process Change:

1. Establish Designated Channels: Clearly define the official channels for addressing specific company needs. For instance:

   • Employee Hardship Fund: For personal crises impacting employees (analogous to "Refa'einu"). This fund should have a clear application process and be managed by HR, ensuring fairness and avoiding individual founder discretion.
   • Strategic Initiative Review Board: For requests related to significant market opportunities or competitive threats that might require deviating from standard operating procedures (analogous to "Blessing of the Years" for livelihood, or "Shomeya Tefilla" for broader needs). This board would include cross-functional leaders.
   • Ethical Review Committee: For any proposal that involves potentially sensitive competitive tactics or unique market plays, ensuring alignment with the "truth" and fairness principles derived from the text.

2. Founder's Role as Gatekeeper (with guardrails): Founders, as per the text's allowance for personal needs, can initiate requests. However, they must do so through the established protocol. Instead of directly instructing a team member to change a process for a personal reason, the founder would submit a formal request to the relevant committee or board. This request must clearly articulate the need, the desired outcome, and how it aligns with or supports the broader company goals. The protocol will stipulate that personal requests, while acknowledged, should not be "lengthy" in their impact or disruptive to the established processes, aligning with the Shulchan Arukh's caution about individual needs not becoming an undue burden.

3. Documentation and Transparency: All requests and their resolutions must be documented. This ensures accountability and provides a record for future ethical reviews. The documentation should explicitly reference which "blessing" or company function the request relates to, thereby maintaining the integrity of the original framework. This aligns with the Gloss's emphasis on not adding before beginning the blessing; the established process is the starting point.

This protocol ensures that urgent and personal needs are addressed, but within a structured, fair, and transparent framework, preventing the "addition" from becoming a disruptive interruption to the company's core mission and ethical operations. It operationalizes the principle of integrating personal needs without compromising the integrity of the established "blessings" of business.

Board-Level Question

"Considering the Shulchan Arukh's guidance that one may add personal needs to prayers similar to the blessing, but with caveats about not disrupting the flow or making it lengthy for individual requests, how are we ensuring our strategic decision-making processes allow for urgent, founder-initiated needs – such as a critical competitive response or a unique market opportunity – to be integrated effectively and ethically, without creating undue bias or compromising the integrity of our established operational frameworks? Specifically, what mechanisms do we have in place to differentiate between a legitimate, mission-critical 'personal need' that benefits the collective, and a mere personal preference that could introduce unfairness or inefficiency, akin to adding a personal plea that interrupts a communal blessing?"

Takeaway

Founders, your drive to succeed is a powerful force. But unchecked, even good intentions can lead to ethical shortcuts. The Shulchan Arukh teaches us that personal needs can be integrated into established systems, but only with careful attention to fairness, truth, and the overall integrity of the process. Treat your company's operations like those sacred blessings: allow for necessary additions that support the whole, but never at the expense of the fundamental structure. Your ROI isn't just financial; it's also in the ethical capital you build.