Arukh HaShulchan Yomi · Startup Mensch · On-Ramp

Arukh HaShulchan, Orach Chaim 263:16-22

On-RampStartup MenschFebruary 27, 2026

Hook

You’re staring at a spreadsheet, red ink everywhere. Your runway is shrinking faster than a penny stock in a bear market. Every line item feels like a luxury, every feature request a frivolous indulgence. Sound familiar? Every founder hits this wall. You’ve got a product roadmap longer than your arm, a backlog of bugs, and a team running on fumes and instant coffee. The question isn’t if you cut, but what you cut. What’s truly essential? What’s a "nice-to-have" that suddenly feels like a "can't-afford-to-have"?

This isn't just about features; it’s about the very soul of your operation. Do you prioritize customer delight, or fundamental decency? Do you build a flashy new module, or invest in shoring up a critical, but unsexy, piece of infrastructure? The Rambam, a towering figure in Jewish thought, grapples with a similar dilemma, albeit with Shabbos candles. He states unequivocally, "Lighting Shabbos candles is not (some ordinary) optional act, where you may or may not light them according to your desire." This isn't a suggestion; it's a non-negotiable. Even more strikingly, he insists, "Even if you do not have your own food to eat, you must go door to door begging for oil and kindle the light." Think about that: you’re starving, but you must find a way to light that candle. This isn't just a religious dictate; it's a radical principle of prioritizing foundational obligations over even personal survival, because those obligations define the essence of the experience. It forces us to ask: what are your "Shabbos candles" – those core, non-negotiable elements of your business that must be maintained, even when you're "begging for oil"?

Text Snapshot

The Rambam declares lighting Shabbos candles an absolute "obligation for both men and women," not an option. He emphasizes its critical importance, stating one "must go door to door begging for oil" even without food, as it's part of "Shabbos Pleasure" (Oneg Shabbos). The text then clarifies that a blessing is recited, akin to other Rabbinical requirements. Rashi offers a nuanced perspective, explaining the reason as "Honoring Shabbos" (Kavod Shabbos), since "you can only hold an important feast in a well lit place," rather than purely for pleasure. This highlights a tension between immediate satisfaction and foundational respect.

Analysis

This short passage from Arukh HaShulchan, dissecting the reason behind a seemingly simple act like lighting a candle, unearths profound insights for founders navigating the brutal realities of building a business. It forces a re-evaluation of what constitutes a "must-have" versus a "nice-to-have," especially when resources are scarce.

Insight 1: The Non-Negotiable Core – Obligation Over Option (Fairness)

The Rambam doesn’t mince words: "Lighting Shabbos candles is not (some ordinary) optional act, where you may or may not light them according to your desire... rather it is an obligation." This is a foundational truth for any venture. What are the absolute, non-negotiable core functions or values of your business? These aren't features you add if you have spare cycles; they are the bedrock that, if absent, renders your entire offering moot.

In business, this translates to fairness. Fairness means delivering on fundamental promises. For a SaaS product, this might be uptime, data security, or core functionality that simply works without glitches. For a service business, it’s delivering the agreed-upon output on time and to standard. Many founders get distracted by shiny new features, chasing "delight" before nailing down "dependability." The Rambam’s decree is a stark reminder: you must fulfill the obligation first. It’s not about what makes your customer happy in the moment, but what they are fundamentally owed. Neglecting these core obligations isn't just bad business; it's a breach of trust, an unfair transaction. A user who experiences frequent crashes or data breaches doesn't care about your new AI-powered chatbot; they care that the fundamental "light" of your service is extinguished. This foundational delivery is a prerequisite for any meaningful relationship with your customers.

Insight 2: Pleasure vs. Honor – Beyond Satisfaction to Respect (Truth)

The text presents a fascinating divergence in reasoning: the Rambam links the candle to "Shabbos Pleasure" (Oneg Shabbos), while Rashi attributes it to "Honoring Shabbos" (Kavod Shabbos), explaining, "you can only hold an important feast in a well lit place." This isn't semantic hair-splitting; it's a critical distinction for your business model and customer relationship. Are you optimizing for transient "pleasure" or enduring "honor" (i.e., respect and perceived value)?

"Pleasure" might equate to immediate customer satisfaction: a slick UI, a fun onboarding flow, a clever Easter egg. These are important, but they often mask deeper issues if the "honor" isn't present. "Honor," as Rashi defines it, is about creating an environment where an "important feast" – or in your case, an important transaction, relationship, or experience – can genuinely take place. It’s about truth in advertising and delivery. It's the robust backend, the transparent pricing, the ethical data handling, the respectful customer support. These elements might not always elicit a "wow" moment, but they build profound trust and perceived value over time. They signal that you respect your customer's intelligence, their time, and their investment.

Many businesses chase "delight" (pleasure) as a differentiator, only to find customers leaving because of a lack of "respect" (honor). They might enjoy the superficial aspects but feel fundamentally undervalued or even exploited. A "well-lit place" for your customers means clarity, security, and a sense of dignity in their interaction with your brand. This distinction is crucial for authentic branding and long-term customer loyalty. Are you building a fleeting moment of joy or a lasting relationship built on mutual respect? The truth in your offering lies in whether you can truly hold an "important feast" in the "place" you've provided.

Insight 3: The "Begging for Oil" Principle – Investing in Non-Negotiables (Competition)

Perhaps the most potent business lesson here is the Rambam's radical instruction: "Even if you do not have your own food to eat, you must go door to door begging for oil and kindle the light." This is not about prioritizing; it's about identifying an absolute, non-negotiable investment that must be made, even at personal sacrifice. It's about recognizing what is so fundamental to your purpose that its absence would invalidate everything else.

For a startup, this translates directly to competitive strategy and resource allocation. What are the "oil" investments you must make, even if it means foregoing "food" (i.e., other opportunities, personal comfort, or even short-term survival)? This isn't about profit maximization in the immediate term, but about preserving the very essence of your value proposition. Is it a critical cybersecurity upgrade? Is it retaining a key talent even when cash is tight? Is it investing in a compliance framework that ensures your long-term viability? These are the investments that keep your "light" burning, ensuring you're even in the game.

Many founders, when faced with limited resources, cut corners on these foundational elements, hoping to catch up later. But the Rambam's point is that some "lights" cannot be allowed to go out, even if it means extreme measures. Competitively, this means understanding what minimum standard of operation, ethics, or product quality you must uphold to retain any legitimacy. If you don't "beg for oil" for these essentials, your customers will migrate to competitors who do. This isn't just about survival; it's about defining your non-negotiable commitment to quality and integrity, a commitment that, over time, becomes an unassailable competitive advantage.

Policy Move

Based on the distinction between "pleasure" and "honor," and the "begging for oil" imperative, implement a "Core Dignity Standard" (CDS) Policy.

This policy mandates that all product development, customer service interactions, and marketing communications prioritize fundamental respect and transparency over superficial delight or aggressive sales tactics. Before any new feature is greenlit or marketing campaign launched, it must pass a CDS review, answering:

  1. Does this uphold our users' fundamental right to privacy, data security, and clear communication? (Aligns with "Honoring Shabbos" as a "well lit place" – no dark patterns, no hidden fees, clear TOS).
  2. Does this deliver on our core promise reliably and fairly, even under stress? (Aligns with "obligation," not "optional act" – focusing on bug fixes, system stability, and core functionality before "delight" features).
  3. Are we investing sufficient resources into maintaining this foundational respect, even if it means sacrificing short-term gains or other "food" (features)? (Aligns with "begging for oil" – ensuring critical infrastructure, compliance, and essential support staff are never deprioritized).

Every quarter, a dedicated "Dignity Audit" team (cross-functional: product, legal, customer success) will review a sample of customer interactions, feature releases, and communications against the CDS. Failures trigger immediate remediation and a root cause analysis to prevent recurrence.

KPI Proxy: We will track a "Core Respect Index" (CRI). This index will be a composite score derived from:

  • Customer feedback on trust, transparency, and data security (e.g., specific survey questions).
  • Incidents of data breaches, major outages, or regulatory compliance violations.
  • Customer Service resolution rates for foundational issues vs. "delight" issues.
  • Net Promoter Score (NPS) specifically segmented for customers who highlight "reliability" and "trust" as key drivers.

The goal is to ensure CRI never falls below a predefined threshold (e.g., 85%), recognizing that while delight is good, foundational respect is non-negotiable.

Board-Level Question

Considering the Rambam's emphasis on "obligation" and Rashi's distinction between "Shabbos Pleasure" and "Honoring Shabbos," and the extreme measure of "begging for oil": How do we, as a leadership team, strategically differentiate between investments that foster short-term customer delight ("Shabbos Pleasure") versus those that build long-term trust and fundamental respect ("Honoring Shabbos"), particularly when facing resource constraints? Furthermore, what are our "begging for oil" investments – those non-negotiable core elements that we must fund, even at the expense of other strategic priorities, because their absence would fundamentally undermine our integrity and long-term viability? How are these specifically ring-fenced in our budget and product roadmap?

Takeaway

Stop chasing fleeting "pleasure" if you haven't mastered "honor." Your customers don't just want to be delighted; they demand to be respected. Identify your non-negotiable core obligations, and commit to them with the ferocity of one "begging for oil." That unwavering commitment to foundational respect and reliability isn't just an ethical stance; it’s a brutal, ROI-positive strategy for sustainable growth.