Mishneh Torah, Sanctification of the New Month 9-11

Hook

The founder’s dilemma is rarely about "right vs. wrong"; it is almost always about "precision vs. utility." Every day, you face the trade-off between the perfect analytical model and the one that actually keeps the ship moving. You want the data to be perfect, but you have a product to ship, a burn rate to respect, and a team that needs a clear, if slightly simplified, North Star.

In Mishneh Torah, Sanctification of the New Month 9:11, Rambam addresses this exact friction. He acknowledges that the sages of the nations and even the greatest minds of his own tradition debated the precise length of the solar year. He admits that his own mathematical models rely on "approximations" (hilchot 11:1). He could have spent his life refining the decimals to the n-th degree, but he chose to provide a functional system that allows the community to set the calendar now.

This text speaks to the founder who is paralyzed by "analysis paralysis." You are chasing the perfect KPI, the perfect CAC/LTV ratio, or the perfect market segmentation, while your competitor is out there, moving at a "good enough" pace, capturing the market. Rambam teaches us that truth in business is not found in the vanity of infinite precision; it is found in the utility of a model that serves the objective. If your data doesn’t help you make the decision, it’s not data—it’s just noise. Are you building a system for the sake of accuracy, or are you building a system for the sake of action? Stop trying to calculate the exact millisecond of the solar cycle when you haven’t yet determined the date of your next launch.

Text Snapshot

"The method of calculating [the beginning of] the seasons can be explained as follows... If you desire to know [the time and the date of] the vernal equinox of a particular year within a given [nineteen-year] cycle, [the following procedure should be used:]... [These] are approximations, based on the mean rate of progress of the sun, and not on its actual position... [The sages] relied on this calculation... because this calculation is more accurate than the former one. It shares a greater resemblance to the data explained by the astronomers." (9:5, 9:11)

Analysis

Insight 1: The Principle of "Satisficing" (Good Enough for Growth)

Rambam is remarkably candid: "Both these calculations that we have explained are approximations" (9:11). He doesn't apologize for this. He understands that there is a diminishing return on computational effort. In startup terms, this is the transition from "v1" to "v2." Your MVP doesn't need to be perfect; it needs to be directionally accurate. If your financial projections for Q4 are based on a model that is 95% accurate, spending another 100 hours of engineering time to get to 97% is a waste of capital. Rambam’s decision rule: If the delta between the "perfect" model and the "approximated" model does not change the strategic outcome, choose the model that allows for faster execution.

Insight 2: The Truth is in the Utility

Rambam notes that when he does choose to be imprecise, it is intentional: "whenever we were not exact, it was because our mathematical calculations proved that [this inaccuracy] did not affect the knowledge of the time when the moon would become visible" (9:14). This is a masterclass in prioritization. He defines the "truth" of his model by its output, not its internal consistency. In your business, stop obsessing over the "technical debt" of your metrics if those metrics are already driving the right decisions. If you are measuring "Daily Active Users" to gauge engagement, don't waste time trying to filter out every possible bot if the trend line is clear enough to inform your product roadmap. Your KPI is a tool, not a religious relic.

Insight 3: Respect the Domain, But Master the Application

Rambam acknowledges that "Great wise men have blundered" (9:13) and that there are "mysteries" known only to the masters. He respects the depth of the field (astronomy/math), yet he creates a simplified version for the "school children" (9:13). The decision rule here is: Learn the science deeply so you can simplify it intelligently. You cannot lead an engineering team if you don't understand the constraints, but you shouldn't force your marketing team to understand the underlying architecture of your database. Master the complexity internally so you can deliver elegant simplicity externally.

Policy Move: The "Strategic Approximation" Audit

Implement a quarterly "KPI Utility Audit."

Most startups suffer from "dashboard bloat"—tracking hundreds of metrics that no one looks at.

1. The Process: For every metric on your primary dashboard, ask one question: "Does this metric, if it moved by 5% in either direction, change a decision we are making today?"
2. The Cut: If the answer is "No," delete the metric.
3. The Goal: Reduce your "Executive Dashboard" to no more than five "North Star" metrics.
4. The Rationale: Follow the Rambam approach: If the data is being tracked for "precision" rather than "visibility," it is a distraction. You want to spend your time observing the "moon" (your customers/market), not calculating the "solar year" (your internal vanity metrics).

KPI Proxy: "Data-to-Decision Ratio." Count how many reports are generated vs. how many strategic pivots or resource allocations are made based on those reports. If the ratio is > 1:1, you are doing too much math and not enough business.

Board-Level Question

"We are currently spending X% of our engineering/finance bandwidth on maintaining high-precision models for [Projection/Reporting/Inventory]. Based on our current growth stage, are we over-indexing on precision at the expense of speed, and if we were to accept a 5% margin of error, how much capital could we reallocate to customer acquisition this quarter?"

Takeaway

The Rambam was a scientist, a physician, and a legal genius. He knew exactly how the stars moved. Yet, he chose to write a simplified manual for the people. He prioritized the function of the calendar over the vanity of his own brilliance. As a founder, your job is not to be the smartest person in the room; your job is to be the most effective. If your models are more complex than your business, you are failing the Mensch test. Be precise where it matters, approximate where it doesn't, and always, always keep your eyes on the moon.