Halakhah Yomit · Startup Mensch · Standard
Shulchan Arukh, Orach Chayim 120:1-121:2
Hook
Every founder lives and dies by acceptance. Not just once, but constantly. You pour your blood, sweat, and equity into a product, a service, a vision. You launch, you iterate, you pivot. But beneath all the hustle, there's a primal question: Will it be accepted? Will the market embrace it? Will investors fund it? Will your team believe in it? Will your customers keep coming back?
This isn't a one-and-done deal. It's a continuous, often agonizing, quest for validation. You might have a killer product that nails market fit today, but what about tomorrow? What if a competitor emerges? What if customer preferences shift? What if your internal processes, once sharp, become dulled by "customs" that slowly erode efficiency and quality?
The Torah, through the lens of the Shulchan Arukh, confronts this exact founder dilemma head-on. It's not talking about SaaS or Series A, but about prayer – humanity’s most fundamental "offering" to the Divine. Yet, its insights are brutally relevant. The text grapples with the imperative of consistent, unwavering acceptance for our "offerings." It dissects what it means for something to be "accepted with favor" (בְּרָצוֹן), and the severe consequences of deviation from established, proven practices, even when local "customs" emerge. It challenges us to look beyond the superficial transaction to the deeper "soul" of our work, and to understand that true acceptance isn't a passive hope, but an active, consistent, and deeply intentional pursuit.
When you’re fighting for market share, battling for talent, and striving for profitability, the last thing you need is an offering that’s only sometimes accepted, or a process that’s undermined by unexamined habits. This isn't just about spiritual adherence; it's about operational excellence, market resilience, and the very survival of your venture. The question isn't if your offering needs acceptance, but how you consistently ensure it.
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
The Shulchan Arukh, Orach Chayim 120:1-121:2, lays down precise rules for key parts of the Amidah prayer. It mandates, "We say 'R'tzei' in all the [Amidah] prayers; and this is not like those who have a custom to not say it in the afternoon [Amidah] prayer." It then clarifies that during "Modim" (thanksgiving), "We bow... at the beginning and at the end," adding, "One who says 'Modim Modim', we silence [that person]." Finally, it states, "An individual does not say 'Birkat Kohanim' ["The Priestly Blessing"]", explicitly dismissing a widespread custom to the contrary as incorrect.
Analysis
Insight 1: Acceptance Isn't Assumed; It's Earned Through Consistent "Offering" (Fairness)
In the startup world, "acceptance" is the holy grail. Market acceptance, investor acceptance, user acceptance. Founders often assume that if they build it, "they" will come, or that a stellar initial launch will guarantee perpetual success. The Shulchan Arukh, however, shatters this complacency by demanding unwavering consistency in our "offerings." It states unequivocally, "We say 'R'tzei' in all the [Amidah] prayers; and this is not like those who have a custom to not say it in the afternoon [Amidah] prayer." This isn't a suggestion; it's a non-negotiable directive. The blessing of "R'tzei" is a plea for Divine acceptance, and the text insists this plea must be part of every offering, at all times.
The commentary deepens this, explaining that "even though there is no service now [i.e., no Temple sacrifices], we pray for the prayer, which is in place of the offering, that it be accepted with favor before God." (Tur on 120:1, quoted by Mishnah Berurah and Kaf HaChayim). Our prayers, our efforts, our products – these are our "offerings" in the modern context. The expectation is that they must always be presented with the intention and structure that seeks "favor."
Consider the Spanish custom mentioned by the Tur, "And the custom in Spain is not to say 'R'tzei' in Mincha, but rather they begin 'Ve'ishei Yisrael'. And so wrote Rav Sherira Gaon... and one who says it always does not do well." This shows a historical precedent for deviation, where a regional custom sought to alter a fundamental practice. Yet, the Shulchan Arukh, as codified law, rejects this custom, stating, "and this is not like those who have a custom to not say it in the afternoon [Amidah] prayer." Why? Because consistency in seeking acceptance is paramount. The Kaf HaChayim on 120:3:1 elaborates, quoting the Pri Megadim, that "according to what is now customary everywhere to say 'R'tzei', one who omits it is considered to be deviating from the 'minted coin' established by the Sages, and his law is as the author wrote in Siman 119 Sif 3 regarding one who erred in a blessing." This is a stark warning: deviating from established, effective practices – even if a "custom" has emerged – is not merely a preference; it's an error with significant consequences, akin to invalidating the entire "offering."
For a founder, this translates directly to product and service delivery. Your customers don't care if your "A-team" built the initial MVP but your "B-team" is now handling maintenance. They don't differentiate between your flagship product and a minor feature. Every interaction, every update, every customer support ticket is an "offering." If your core product experience is exceptional but your onboarding process is clunky, or your customer service is inconsistent, you're essentially saying "R'tzei" sometimes but not always. You're exhibiting the "custom" the Shulchan Arukh rejects.
Fairness demands consistency. Customers expect a consistently high level of quality, reliability, and value. Employees expect consistent leadership, communication, and opportunities. Investors expect consistent performance and transparency. Any deviation, any "custom" that creeps into your operational standards, undermines the trust and loyalty you've worked so hard to build. It's not enough to sometimes strive for acceptance; you must always do so, in every facet of your business. The "minted coin" of your brand reputation, your product quality, and your customer experience must remain undiluted, always reflecting the highest standard.
Metric/KPI Proxy: Customer Retention Rate (CRR) Consistency by Product Line or Feature. This tracks whether customer stickiness and satisfaction remain high across all offerings, not just the most popular or recently updated ones. A dip in CRR for a specific product or feature indicates an inconsistency in "offering" quality or acceptance, signaling a deviation from the "minted coin."
Insight 2: Your "Offerings" Are More Than Just Output – They Are a Reflection of Your Soul (Truth)
Founders are often driven by passion, a vision that transcends mere profit. But in the relentless pursuit of growth, it’s easy to lose sight of that deeper purpose, to view products as just commodities, and services as mere transactions. The Shulchan Arukh, through its profound interpretations of "Ve'ishei Yisrael U'tefilatam" (the fire-offerings of Israel and their prayer), reminds us that our "offerings" are imbued with a sacred essence, a reflection of our "soul."
The Tur explains, "And in the Midrash, there is Michael, the great angel, offering the souls of the righteous upon the heavenly altar. And for this, they instituted 'Ve'ishei Yisrael'." (Tur on 120:1, quoted by Mishnah Berurah and Kaf HaChayim). This is a breathtaking insight. Our "offerings" – our prayers, our work, our creations – are not just external acts. They are so profound that they are likened to the "souls of the righteous" being offered. The Kaf HaChayim further clarifies, "the meaning is 'Ve'ishei Yisrael' – meaning the people of Israel who are offered by Michael, or it could be from the word 'Isheh' (fire-offering), meaning the sacrifices of Israel, i.e., their souls, which are themselves offered by Michael." This means our work, at its highest level, is a conduit for our very essence, our being, to be presented for "favor."
This isn't about spiritualizing every spreadsheet; it's about understanding the profound impact of truth and authenticity in your business. When your product or service genuinely solves a problem, is built with integrity, and reflects a deep understanding of customer needs, it carries a different weight. It has "soul." This "soul" is what resonates with users, builds authentic brand loyalty, and attracts dedicated talent. It’s the truth embedded in your offering.
The Chokhmat Shlomo adds another layer, linking prayer (our "offering") to the concept of "Avodah sheb'lev" (service of the heart), stating, "the intention is all about prayer... 'Which service is in the heart? This is prayer.'" (Chokhmat Shlomo on 120:1). This implies that true "service" – and thus, true "offering" – originates from the heart, from a place of genuine intention and purpose. When a founder builds a company with a clear, authentic mission and vision, and imbues that mission into every product decision, every hiring choice, and every customer interaction, that "service of the heart" becomes the soul of the business.
Conversely, when a company pursues profit at all costs, cuts corners, misleads customers, or exploits employees, it offers a product without a soul. It's an empty "offering," lacking the truth and authenticity that command genuine "favor." The debate around adding "bimeheirah" (speedily) to the prayer "U'tefilatam... tekabel bimeheirah" (and their prayer... speedily accept) further highlights this. Some argued against "bimeheirah" because it might imply praying for the speedy death of the righteous whose souls are being offered (Kaf HaChayim on 120:2:1, quoting Kasha LeHashiv). While ultimately rejected as a misinterpretation, the concern itself underscores the deep reverence for the "souls" associated with the offering. You don't want to rush an outcome in a way that disrespects the inherent value or integrity of the "soul" of the offering.
For a founder, this means constantly asking: Is my offering merely functional, or does it embody the true purpose and values of my company? Am I building with integrity, transparency, and a genuine desire to serve, or am I prioritizing short-term gains over long-term truth? The "soul" of your product, rooted in its truth and authenticity, is what allows it to be "accepted with favor" not just superficially, but deeply and sustainably.
Metric/KPI Proxy: Employee Engagement Score (EES) & eNPS (Employee Net Promoter Score) linked to Mission Alignment. This measures how deeply employees connect with the company's mission and feel their work has purpose. A high EES and eNPS, especially when tied to understanding and believing in the company's mission, indicates that the "soul" of the organization is vibrant and genuinely reflected in its internal "offerings" (culture, work environment), which inevitably translates to external offerings.
Insight 3: Gratitude Is a Collective Act, Not an Individual Spectacle (Competition)
In the high-pressure, often ego-driven startup environment, individual recognition and competition can easily overshadow collective achievement. Founders, executives, and star employees often seek validation, and while healthy, an excessive focus on individual glory can be detrimental to team cohesion and overall company success. The Shulchan Arukh offers a sharp corrective, emphasizing the collective nature of certain expressions and the dangers of individualistic excess.
The text states, "One who says 'Modim Modim', we silence [that person]." (Shulchan Arukh, Orach Chayim 121:1). "Modim" means "We are thankful." Repeating it excessively, "Modim Modim," is seen as a disruptive, inappropriate individualistic display. It's not about prohibiting gratitude, but about regulating its expression within a collective context. In a startup, this translates to how we recognize success and express gratitude. While individual contributions are vital, over-the-top, self-aggrandizing displays of gratitude or achievement can be counterproductive. It disrupts the harmony of the "team prayer." When one person is constantly "Modim Modim"-ing themselves, it can diminish the collective spirit and make others feel unheard or undervalued.
Even more pointed is the ruling regarding the Priestly Blessing: "An individual does not say 'Birkat Kohanim' ["The Priestly Blessing"]." (Shulchan Arukh, Orach Chayim 121:2). This blessing, a powerful invocation of Divine blessing, is reserved for specific individuals (Kohanim) acting in a specific, collective context (a minyan). The text even notes a "widespread custom" for individuals to say it, but explicitly dismisses it, stating "but this does not appear [correct to me]" (Gloss on 121:2, Beit Yosef in the name of Manhig). This is a powerful rejection of individualism in matters designed for the collective. Certain blessings, certain expressions of power or authority, are not for individuals acting alone or outside their designated role.
In a startup, this principle is critical for managing internal competition and fostering collaboration. It teaches that certain "blessings" – credit for major successes, strategic decisions, public representation of the company – are not for every individual to claim or perform unilaterally. When a single founder or executive constantly hogs the limelight, claims all credit, or makes unilateral decisions that should be collective, they are akin to an individual saying "Birkat Kohanim." Even if done with good intentions, or if it's a "widespread custom" within certain startup cultures (e.g., the "hero founder" narrative), the Shulchan Arukh warns that "this does not appear correct." It undermines the collective strength and disempowers the team.
True gratitude and recognition in a business should uplift the entire team, not just a few "stars." While individual performance should be acknowledged, the ultimate "blessing" of success is a collective outcome. Encouraging excessive internal competition where individuals prioritize their own glory over the team's success is a recipe for dysfunction. It's about empowering the collective, understanding that the greatest "blessings" come when everyone plays their designated role in harmony, rather than each trying to be the "Priest" for themselves.
Metric/KPI Proxy: Peer Recognition Program Participation Rate & Cross-Functional Project Success Rate. A high participation rate in peer recognition indicates a culture where gratitude is shared and celebrated collectively, rather than just top-down. A high cross-functional project success rate (measured by on-time, on-budget, and goal achievement) indicates effective collaboration and a minimization of individualistic "Modim Modim" or "Birkat Kohanim" behaviors that disrupt collective effort.
Policy Move
Policy Name: The "Consistent Offering Acceptance & Iteration" (COAI) Framework
Problem: Many startups excel at launching new products or features, but struggle with consistent quality, customer satisfaction, and feature maintenance over time. "Customs" of neglecting older products, inconsistent customer support, or ad-hoc iteration processes creep in, leading to a decline in overall market acceptance and brand trust. This directly violates the principle of "We say 'R'tzei' in all the [Amidah] prayers," where every "offering" must consistently strive for acceptance.
Policy Objective: To ensure every product, service, or major feature offered by the company consistently seeks and maintains "favor" (acceptance) from its target audience, treating all "offerings" with equal diligence and commitment to quality. This policy aims to eliminate the "custom" of inconsistent attention and ensure the "minted coin" of our brand's quality remains undiluted.
Policy Description: The COAI Framework mandates a structured, recurring review and iteration process for all active company offerings, not just new launches or those currently underperforming. This framework is designed to institutionalize the consistent pursuit of "favor" and prevent "customs" of neglect or inconsistent quality.
- Categorization of Offerings: All company products, services, and significant features will be categorized into tiers (e.g., Core, Growth, Legacy) based on strategic importance and user base.
- Mandatory "Acceptance Reviews":
- Core Offerings: Quarterly "Acceptance Reviews" for all core products/services.
- Growth Offerings: Bi-annual "Acceptance Reviews."
- Legacy Offerings: Annual "Acceptance Reviews."
- Each review will be led by a cross-functional "Acceptance Squad" comprising representatives from Product, Engineering, Marketing, Sales, and Customer Success.
- Review Components: Each "Acceptance Review" must include:
- Customer Feedback Aggregation: Synthesis of quantitative data (e.g., NPS, CSAT, churn rates, usage analytics) and qualitative data (e.g., support tickets, user interviews, social media sentiment) related to the specific offering. This is our direct measure of "favor."
- Performance Metrics Analysis: Review of key business metrics (e.g., revenue, user engagement, cost-to-serve) to evaluate the offering's health and contribution.
- Competitive Landscape Scan: Assessment of how the offering stands against competitors and evolving market trends.
- Technical Health Check: Review of system performance, stability, and security for the offering.
- "R'tzei" Gap Analysis: A specific component asking: "Where is this offering not being accepted with favor? What are the 'customs' or inconsistencies that are eroding its value?" This directly links to the Shulchan Arukh's critique of inconsistent "R'tzei."
- Actionable Iteration Plan: Based on the review, the Acceptance Squad must propose a concise, prioritized iteration plan (e.g., bug fixes, minor feature enhancements, documentation improvements, marketing adjustments) to address identified "acceptance gaps." This plan must include clear owners, timelines, and success metrics.
- Reporting & Accountability: Review findings and iteration plans will be presented to relevant departmental heads and, for Core Offerings, to the executive leadership. Progress on iteration plans will be tracked and reported in subsequent reviews.
Rationale Connection: This policy directly operationalizes the Shulchan Arukh's dictum, "We say 'R'tzei' in all the [Amidah] prayers." It ensures that our business "offerings" are not just released and forgotten, but are continuously presented with a conscious effort to ensure their acceptance "with favor." By institutionalizing regular, structured reviews, we prevent the emergence of "customs" that lead to inconsistent quality or neglect of certain products, which the Kaf HaChayim warns is "deviating from the 'minted coin' established by the Sages." Just as one who "errs and begins 'Ve'ishei Yisrael' in Mincha... must return" (Kaf HaChayim on 120:3:1), this framework forces us to "return" to the standard of consistent pursuit of acceptance for all our offerings, maintaining the integrity and value of our brand's "minted coin." It's a proactive measure to ensure fairness to customers who expect consistent value across our portfolio.
KPI Proxy for Policy Effectiveness: Weighted Average Customer Satisfaction Score (CSAT) across all active products/features. This KPI will track the average CSAT, weighted by user count or revenue contribution, across our entire portfolio. The goal is to minimize variance and maintain a consistently high score, demonstrating that all our "offerings" are being "accepted with favor" without significant dips in specific areas.
Board-Level Question
"Given the profound insight from the Tur that our 'offerings' (our products, services, and efforts) are analogous to 'Michael, the great angel, offering the souls of the righteous upon the heavenly altar,' how are we strategically investing in the authenticity, purpose, and long-term 'favorability' of our core value proposition, ensuring we don't succumb to short-term gains that dilute our brand's 'soul' or lead to 'unaccepted' offerings?"
This question cuts to the core of long-term strategic resilience and brand integrity, drawing directly from the deep theological interpretation of our "offerings." The Tur, quoted by Mishnah Berurah and Kaf HaChayim (on 120:1), elevates our work from mere transaction to a sacred act, where "Michael, the great angel, offers the souls of the righteous upon the heavenly altar. And for this, they instituted 'Ve'ishei Yisrael'." This isn't just about what we sell; it's about what we put of ourselves into what we sell. The "soul" of the righteous is the ultimate offering – pure, intentional, and truthful.
At the board level, this translates to scrutinizing whether our strategic decisions truly reflect the "soul" of our company. Are we chasing fleeting trends or superficial metrics that compromise the fundamental purpose and authenticity that initially attracted customers and talent? Are we so focused on immediate revenue spikes that we risk diluting the deeper value proposition that makes our "offering" genuinely "accepted with favor" (בְּרָצוֹן) in the long run?
This question forces a reflection on our company's mission and values. If our product is merely a means to an end (e.g., solely to extract data or monetize attention without genuine value creation), then it lacks "soul." Such an offering might achieve short-term gains, but it will eventually be perceived as inauthentic, leading to a loss of customer trust and market "favor." Just as the debate around "bimeheirah" (speedily) in the prayer highlighted a concern for inadvertently wishing for the death of the righteous, a rapid pursuit of profit without regard for the "soul" of the offering can similarly lead to a "death" of brand equity or genuine market acceptance.
By asking this, the board probes whether leadership is prioritizing ephemeral tactical wins over the enduring strategic investment in the company's core identity and ethical foundation. It challenges leadership to articulate how their strategic roadmap ensures the "truth" of the offering, as conceptualized by the "service of the heart" (Avodah sheb'lev) that the Chokhmat Shlomo (on 120:1) connects to prayer. It's about ensuring that our company's "offering" remains worthy of the deepest form of acceptance, not just from the market, but from a place of intrinsic value and purpose. This isn't just an ethics question; it's a profound strategic imperative for building a resilient, trusted, and truly impactful enterprise that is "accepted with favor" for generations.
Takeaway
Your startup's survival hinges on consistently earning "favor" – acceptance from customers, investors, and your team. This isn't a passive hope, but an active, ethical commitment. Deviating from proven practices for inconsistent "offerings" is a critical error, undermining your "minted coin." Your product is more than just output; it's a reflection of your company's "soul," demanding truth and authenticity. Finally, foster a culture where gratitude and recognition uplift the collective, not just individual stars, ensuring shared "blessings" and preventing disruptive ego. Consistent, authentic, and collaborative striving for acceptance: that's the Torah-driven ROI for enduring success.
derekhlearning.com