Daily Rambam · Startup Mensch · Standard
Mishneh Torah, Sabbath 28
Hook
As a founder, you are constantly fighting a war on two fronts: scope creep and metric elasticity.
On one front, you have the operational boundary of your business. Where does your core product end, and where do custom, non-scalable client requests begin? If you draw your boundaries too narrowly, you starve your startup of growth and fail to capture adjacent market opportunities. If you draw them too loosely—treating every bespoke integration or temporary service contract as a permanent expansion of your platform—your operational complexity explodes, your margins collapse, and you sink under the weight of technical debt. You have allowed temporary "huts" to dictate the borders of your permanent "city."
On the other front, you have the integrity of your measurement. When you report your traction to the board, your team, and your investors, what kind of measuring tape are you using? Is it a rigid, unyielding metric that tells the brutal truth of your unit economics, or is it an elastic, stretchy vanity metric that expands when you pull it (like "Registered Users" or "Gross Merchandise Value") and sags when you let go?
This is not a modern software dilemma. It is an ancient architectural and halachic challenge. In Mishneh Torah, Hilchot Shabbat, Chapter 28, Maimonides (the Rambam) lays down the geometric and operational laws of the Tehum Shabbat—the physical boundary of a city within which a person may walk on the Sabbath.
The text provides an incredibly sophisticated framework for:
- Determining what constitutes a permanent extension of a city’s boundary versus a temporary, isolated structure.
- Standardizing the physical tools of measurement to prevent manipulation and mathematical drift.
- Resolving discrepancies between conflicting expert valuations.
As a founder, applying these laws to your startup isn't just a lesson in ethics; it is a blueprint for scaling with absolute operational rigor. Let's look at the text.
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
Whenever there is a home that is outside a city, but seventy and two thirds cubits... or less from the city, it is considered to be part of the city and joined to it... If one house is within seventy cubits of a city, another house is within seventy cubits of the first, and a third within seventy cubits of the second [and so on], they are all considered to be one city, although the chain extends for a distance of several days walk...
— Mishneh Torah, Sabbath 28:1
[The following laws apply to] the dwellers of huts: [The Sabbath limits] should be measured from the entrance to their homes... If [in that area] there are three courtyards with two houses in each, [the entire area] is established [as a unit]. A square is constructed around it, and two thousand cubits are measured [from its borders]...
— Mishneh Torah, Sabbath 28:10
The [Sabbath limits] should be measured only by using a rope of fifty cubits, but not a shorter or a longer one. The rope should be made of flax, so that it will not stretch beyond [that length]...
— Mishneh Torah, Sabbath 28:11
We rely only on the measurement by an expert who is proficient in the measuring of land. If the Sabbath limits [of a city] had been established and an expert came and measured [them again], increasing them in some places and decreasing them in others, we accept his ruling regarding the limits that he increased...
— Mishneh Torah, Sabbath 28:17
Analysis
To build an enduring enterprise, you must master the geometry of your operations. Rambam’s rules for defining a city’s boundary offer three profound strategic insights that translate directly into modern business decision rules.
Insight 1: The Integrity of the Core (Fairness) — Defining the Core vs. the Edge
The first dilemma Rambam addresses is how outlying structures affect the boundary of the collective city. If a permanent house is within seventy and two-thirds cubits (the length of a side of a square of 5,000 square cubits, or a beit satayim) of the city, it is consolidated into the city’s boundaries Mishneh Torah, Sabbath 28:1. This creates a chain: as long as each subsequent house is within seventy cubits of the previous one, the city's boundary extends indefinitely, "although the chain extends for a distance of several days walk" Mishneh Torah, Sabbath 28:1.
However, this consolidation rule changes dramatically when dealing with "huts" (tzarifin). Rambam rules:
"[The Sabbath limits] should be measured from the entrance to their homes." Mishneh Torah, Sabbath 28:10
They do not consolidate the city's boundaries.
To understand why, we look to the Steinsaltz commentary on this passage. Steinsaltz on Mishneh Torah, Sabbath 28:10:1 defines tzarifin as "structures made of braided branches" (mivnim ha'asuyim me'anafim klu'im). Because these structures are temporary and flimsy, Steinsaltz on Mishneh Torah, Sabbath 28:10:2 notes that "we do not group the huts together to be considered as a city and square them off" (ve'ein metzarfim et hatzarifin yahad leheiacheshev ke'ir ulerabe'a otam). They lack the structural permanence to redefine the collective boundary.
Yet, there is an exception: if there are "three courtyards with two houses in each" within that area, the entire settlement—including the temporary huts—is "established [as a unit]" and squared off Mishneh Torah, Sabbath 28:10. Steinsaltz on Mishneh Torah, Sabbath 28:10:4 explains that once a permanent core is established, "even the huts are considered as part of the permanent settlement" (af hatzarifin nechshavim kechelek mehayishuv hakeva).
The Business Translation
In your startup, "permanent houses" are your scalable, core product features, standard operating procedures (SOPs), and repeating revenue lines. "Temporary huts" (tzarifin) are the bespoke, hand-crafted integrations, manual workarounds, and temporary consulting services you spin up to appease a single high-paying customer.
Fairness to your team, your cap table, and your future buyers demands that you do not allow these temporary "huts" to redefine your operational boundary. If you treat every custom enterprise integration as a core product extension, your product roadmap will warp, your engineering team will burn out maintaining legacy code, and your gross margins will collapse.
However, Rambam offers a brilliant architectural compromise: the "Three Courtyards" rule. If a temporary workaround or custom feature request is validated by a permanent core—defined as being utilized by at least three distinct customer cohorts (courtyards) with at least two active, paying accounts in each (houses)—it is officially consolidated into the core product.
The Ohr Sameach's Geometric Rigor
To understand how this consolidation is executed, we must look at the Ohr Sameach on Mishneh Torah, Sabbath 28:1:1. The Ohr Sameach analyzes the Talmudic debate regarding the squaring off of a city (ibbur). He explains that the seventy and two-thirds cubits are not merely measured as a straight line; rather, they are calculated to form a "square table" (tavla meruba'at) at the corners (keranot) of the city:
"...שעושין אותה כמין טבלא מרובעת לכל צד." "...that they make it like a square table on every side."
This geometric squaring ensures that the city's boundaries are clean, predictable, and structurally sound, preventing irregular "points" from creating chaotic, jagged boundaries.
In business, when you consolidate a new business unit or product line, you must "square it off." You cannot leave it as a jagged, irregular appendage. You must build the supporting infrastructure—billing, customer success, compliance, and documentation—so that the new offering integrates seamlessly into your standard operating model.
Decision Rule 1 (Fairness)
Never allow temporary, bespoke client solutions (huts) to alter your core product roadmap or operational boundaries unless they meet a strict threshold of repeatable market demand (the "Three Courtyards" rule). When you do consolidate an outlier into your core, fully square it off by investing in the necessary operational and compliance infrastructure to keep your business boundaries clean and predictable.
Insight 2: Non-Elastic Metrics (Truth) — The Flax Rope Rule
Once the boundaries of the city are defined, how do we measure the outward limit of two thousand cubits? Rambam is uncompromisingly specific about the physical properties of the measuring instrument:
"The [Sabbath limits] should be measured only by using a rope of fifty cubits, but not a shorter or a longer one. The rope should be made of flax, so that it will not stretch beyond [that length]." Mishneh Torah, Sabbath 28:11
Why flax? Why exactly fifty cubits?
If the rope is shorter than fifty cubits, the measurers must lift and lay it down more frequently. In doing so, they are highly likely to pull it too tightly, stretching the rope and artificially expanding the boundary. If the rope is longer than fifty cubits, the physical weight of the rope will cause it to sag in the middle, shortening the measurement and unfairly restricting the city's inhabitants. Furthermore, flax is selected because it is a highly stable, non-elastic plant fiber. Unlike wool or hemp, which expand and contract based on humidity, tension, and weather, flax maintains its physical integrity under pressure.
The Business Translation
In the startup world, founders are constantly tempted to measure their progress with "elastic ropes."
Consider these common elastic metrics vs. their non-elastic, "flax" equivalents:
| Elastic Metric (Wool/Hemp) | Non-Elastic Metric (Flax Rope) |
|---|---|
| Registered Users / Sign-ups (Stretches with marketing spend; sags when bot traffic is cleared) | Cohort-Based Daily Active Users (DAU/MAU) (Uncompromising engagement) |
| Gross Merchandise Value (GMV) (Padded by low-margin, pass-through transactions) | Net Revenue / Gross Profit (The actual cash retained by the business) |
| Contract Value (TCV) (Includes soft options and uncommitted professional services) | Annual Recurring Revenue (ARR) (Strictly defined by committed, repeating software fees) |
| Bookings (Stretches when you sign non-binding Letters of Intent) | Cash Collected from Operations (Non-elastic bank reality) |
When you use elastic metrics, you are lying to yourself, your board, and your market. Under the tension of a fundraising round or a missed quarter, you will naturally "pull the rope tighter" to make your boundaries look larger. But when the market cools, the rope sags, and the sudden contraction can kill your company.
To run an ethical, high-performing business, you must establish a set of "Flax Rope KPIs"—metrics that are mathematically incapable of being stretched or manipulated by optimistic assumptions, seasonal fluctuations, or accounting parlor tricks.
Decision Rule 2 (Truth)
Establish a "Flax Rope" standard for all board-level and investor-facing metrics. Any metric that can be artificially inflated by changing definitions, pulling forward revenue, or ignoring churn must be banned from official reporting. Measure your operational boundaries with tools that do not stretch under pressure.
Insight 3: Navigating Irregular Terrain and Valuation Discrepancies (Competition) — Step-by-Step Approximations and Expert Tolerances
How do you measure boundaries when the physical terrain is chaotic? Rambam dedicates a massive portion of Chapter 28 to the problem of geography: steep cliffs, deep crevices, high mountains, and obstructing walls Mishneh Torah, Sabbath 28:12-16.
If the measurers encounter a steep mountain or valley that cannot be spanned by a fifty-cubit rope, they cannot simply guess, nor can they measure along the jagged incline (which would shorten the horizontal distance). Instead, they must perform a highly disciplined, step-by-step horizontal approximation:
"Two people hold a rope four cubits long. The person above should hold the upper end at the level of his feet, while the person below should hold the lower end at the level of his heart... [The entire process should be repeated and] continued until the entire area has been measured." Mishneh Torah, Sabbath 28:15
This is a physical execution of trigonometric leveling. It is slow, painstaking, and requires absolute coordination between two people.
Furthermore, Rambam addresses what happens when experts disagree on the final measurement:
"If two experts came and measured the Sabbath limits, one giving a larger measure and the other giving a smaller measure, we accept the ruling of the one who gives the larger measure, provided that the inconsistency is not greater than the difference between the diagonal [and the border of] a city... if the latter measure is less than 580 cubits more than the original measure, it is accepted." Mishneh Torah, Sabbath 28:18-19
Because the Sabbath limit is a Rabbinic decree (Derabanan), we apply the principle of leniency (safek derabanan lekula), as noted in Mishneh Torah, Sabbath 28:19: "since our Sages stated that the lenient approach should be accepted in these rulings... because the measure of two thousand cubits is a Rabbinic institution."
However, this leniency is not a license for arbitrary inflation. The difference between the two experts' measurements cannot exceed 580 cubits. Why 580 cubits? This is the precise mathematical difference between measuring the city's boundary straight out versus measuring it diagonally from the corner of a squared-off city. If the discrepancy is within this 580-cubit limit, we can logically attribute the variance to a known, systematic difference in geometric methodology (one expert measured from the flat edge, the other from the diagonal corner). If the discrepancy is larger than 580 cubits, it is no longer a methodological variance; it is an egregious error, and the larger measurement must be rejected.
The Business Translation
Your startup will inevitably encounter "irregular terrain." This represents market volatility, regulatory shifts, technical debt, and pivot points.
When navigating a massive technical debt migration (a "mountain") or an unmapped market opportunity (a "valley"), you cannot measure your progress with a straight-line projection. You cannot simply say, "We will complete this migration in Q3." You must apply the "Four-Cubit Horizontal Rope" rule: break the massive, irregular mountain down into tiny, highly coordinated, step-by-step increments (Agile sprints, micro-milestones). Two people—your VP of Product and your VP of Engineering—must hold the ends of the rope, keeping their measurements perfectly level and aligned, moving step-by-step until the terrain is conquered.
Handling Valuation and Market Size (TAM) Discrepancies
When competing for venture capital or positioning your company for an acquisition, you will face conflicting valuations and market size (TAM) calculations. Your internal model might show a $5B TAM, while a conservative third-party market research firm puts it at $3.5B.
Rambam’s "Expert Discrepancy" rule provides a masterclass in ethical positioning:
- The Leniency Principle: You are permitted to present the more optimistic, larger market valuation to investors, provided it serves your strategic growth.
- The Methodological Boundary: This optimism is only ethical if the variance can be entirely explained by a transparent, systematic difference in methodology (e.g., Top-Down vs. Bottom-Up calculation, or inclusion of adjacent software markets). This is the equivalent of the 580-cubit diagonal variance.
- The Rejection of Fabricated Scale: If your optimistic valuation is so bloated that it cannot be mathematically traced back to a specific methodological variance, it is a lie. It violates the boundary of truth, and using it will destroy your credibility in the market.
Decision Rule 3 (Competition)
When tackling highly complex, non-linear business challenges, reject high-level guesswork. Break the execution down into short, coordinated, step-by-step sprints (the four-cubit horizontal rope). When presenting optimistic market sizes or financial valuations, ensure that the variance between your optimistic model and a conservative model can be completely and transparently justified by a specific, logical formula (such as a known model variance), rather than arbitrary speculation.
Policy Move
The "Permanent Dwelling" Registry & "Flax-Rope" Metric Audit
To operationalize Hilchot Shabbat Chapter 28 within your company, you must implement a formal policy that governs how your business defines its product boundaries and measures its performance. This policy is divided into two distinct operational protocols.
+----------------------------------------------+
| New Feature / Custom Integration Request |
+----------------------------------------------+
|
v
+----------------------------------------------+
| Is it used by >= 3 Customer Cohorts? |
+----------------------------------------------+
/ \
YES / \ NO
/ \
v v
+---------------------------+ +---------------------------+
| Is it used by >= 2 | | Classified as "Hut" |
| Paying Accounts/Cohort? | | (Temporary/Bespoke) |
+---------------------------+ +---------------------------+
/ \ |
YES / \ NO v
/ \ +---------------------------+
v v | Keep isolated; charge |
+-----------+ +-----------+ | custom service fees; |
| CORE | | "Hut" | | enforce sunset date. |
| (Stone) | +-----------+ +---------------------------+
+-----------+
|
v
+---------------------------+
| "Square it off" (Billing, |
| CS, Docs, Ops Support) |
+---------------------------+
Protocol 1: The "Three-Courtyards, Two-Houses" Product Boundary Rule
No custom feature, bespoke integration, or client-specific codebase modification may be merged into the core platform or classified as a "scalable product asset" unless it meets the 3-Courtyard, 2-House (3C2H) Threshold:
- The Threshold: The feature must be actively utilized and paid for by at least three distinct customer cohorts/verticals (the three courtyards), with at least two active enterprise accounts in each cohort (the two houses).
- The "Hut" Isolation: Any feature request that does not meet the 3C2H threshold is officially designated as a "Temporary Hut". It must be kept strictly isolated from the core codebase via APIs or custom microservices. It must be funded entirely by the requesting client's professional services fees, and it must carry a mandatory sunset clause (e.g., 12 months) unless it graduates to the 3C2H threshold.
- The "Squaring Off" Process: Once a feature graduates to the 3C2H threshold, it cannot simply be left as a raw piece of engineering. It must be "squared off" under the oversight of a cross-functional team (Product, Engineering, Customer Success, and Finance). This requires updating standard pricing models, creating public product documentation, training the support team, and establishing automated automated testing protocols.
Protocol 2: The Non-Elastic Metric Charter
Your finance and data teams must audit every KPI reported to the board and external stakeholders, grading them on an Elasticity Index of KPIs (EIK).
$$\text{EIK} = \frac{\text{Worst-case Metric Value under Strict Auditing (Flax Rope)}}{\text{Reported Metric Value under Optimistic Assumptions (Wool/Hemp)}}$$
- The Rule: Every board-level KPI must maintain an $\text{EIK} \ge 0.95$.
- The Execution: If you report "Monthly Active Users" (MAU), the denominator must exclude any user who has not completed a core, value-producing action within the platform (e.g., running a query, exporting a report) within the last 30 days. You cannot include idle sessions, automated system pings, or users who merely landed on a login page. This is your "flax rope" metric.
Action Item for the Executive Team
Publish this policy in your internal wiki as the "Sabbath 28 Operational Architecture Framework." Mandate that the VP of Product and the CFO present a quarterly audit of all "Hut" codebase exceptions and the EIK scores of all reported metrics.
Board-Level Question
How elastic are our operational boundaries, and are we measuring our progress with a flax rope or a stretchy string?
To initiate a high-level strategic discussion with your board of directors, present the following prompt during your next meeting.
Context for the Board
In Mishneh Torah, Hilchot Shabbat 28, Maimonides outlines the physical and mathematical laws of boundary-setting. He argues that temporary, flimsy structures ("huts") cannot be used to extend the boundaries of a permanent city unless they are anchored by a robust, repeatable core of permanent dwellings. Furthermore, he mandates that the boundaries of the city must only be measured using a highly stable, non-elastic rope made of flax, ensuring that the measurement cannot be stretched or manipulated under pressure.
As we scale this enterprise, we face the constant temptation to expand our operational boundaries based on temporary, non-scalable revenue streams—such as highly customized enterprise contracts, consulting services, and bespoke integrations. If we treat these "huts" as part of our core product, we risk distorting our true margins, bloating our engineering organization, and misleading ourselves about our true product-market fit.
Simultaneously, we must ensure that our growth metrics are completely inelastic. If our key performance indicators (KPIs) can be stretched to fit a favorable narrative during fundraising or board meetings, we are building our company on an unstable foundation.
Strategic Questions for Board Discussion
- Our "Huts" vs. "Houses": What percentage of our current Annual Recurring Revenue (ARR) is dependent on highly customized, bespoke integrations or manual workarounds (temporary huts)? If we stripped away these custom elements, what is the exact, unyielding boundary of our truly scalable, high-margin software product?
- Our Metric Elasticity: If we applied a brutal, "flax-rope" audit to our current North Star metrics—such as Net Revenue Retention, Customer Acquisition Cost (CAC), and Daily Active Users—how much would they contract? Are we currently reporting any metrics to our investors that contain "stretchy" definitions?
- Our "Squaring Off" Execution: When we do identify a highly successful, custom client solution and decide to bring it into our core product, are we properly "squaring it off"? Or are we leaving it as a jagged, irregular appendage that drains our engineering resources and creates operational chaos?
Takeaway
SABBATH 28
STARTUP OPERATIONAL LAW
|
+----------------------------+----------------------------+
| |
v v
CORE INTEGRITY METRIC TRUTH
(Houses vs. Huts) (Flax Rope)
| |
v v
Build with stone, not branches. Never measure your
Isolate custom requests ("huts") growth with a stretchy,
unless validated by a 3C2H elastic metric. Use rigid,
permanent core. uncompromising KPIs.
Do not build your startup's kingdom with braided branches, and do not measure your boundaries with a stretchy rope.
To build an enterprise that endures, you must have the courage to tell the brutal truth about your operations. Isolate your custom, non-scalable features so they do not drain your core resources. Establish non-elastic, "flax-rope" metrics that refuse to warp under market pressure or investor expectations. And when you face the irregular, chaotic terrain of scaling a business, tackle it step-by-step, with the disciplined, coordinated precision of the ancient sages.
Build with stone, measure with flax, and run your startup with the geometric integrity of the Mishneh Torah.
derekhlearning.com