Mishneh Torah, Sales 25-27

Hook

You just closed a monster deal. Champagne corks popped, the team celebrated, projections are up. Then, the integration call. Your customer, beaming, asks, "So, when do we get access to those legacy data pipelines? They're crucial for the analytics package we bought." Your stomach drops. Legacy data pipelines? That was a separate, enterprise-level add-on, not part of the standard analytics package. Your sales rep swore they were clear, but the customer heard "analytics package" and assumed "everything necessary for robust analytics." Now you're facing a choice: nickel-and-dime a crucial new client, eroding trust and future upsell potential, or absorb a significant, unbudgeted cost, hitting your margin hard.

This isn't just a hypothetical. It’s the silent killer of startup growth, the hidden liability lurking in every ambiguous contract: the "What's Included?" dilemma. Founders, we spend countless hours perfecting our product, nailing our pitch, and closing deals. But how much time do we dedicate to meticulously defining the boundaries of what we sell? What comes standard? What’s an add-on? What's implied versus explicit? This isn't nitpicking legal jargon; it's the bedrock of sustainable business relationships and predictable revenue.

Ambiguity isn't "flexibility"; it's a ticking time bomb. It leads to customer churn, scope creep, legal battles, and a reputation for being unreliable. In a world of SaaS subscriptions, bundled services, and complex B2B offerings, the default assumption often favors the buyer, especially if your marketing language is broad or your contracts are vague. You promise a "solution," they expect a complete solution, even if your definition differs. This gap between expectation and reality is where deals unravel, where customer lifetime value plummets, and where your early-stage company can bleed cash and credibility. The question isn't if this will happen, but when – and how prepared you are to navigate it. Are you building on solid ground or a foundation of unspoken assumptions?

Text Snapshot

The Mishneh Torah's "Sales" chapters methodically delineate what is automatically included or excluded when selling various properties and assets (houses, fields, ships, animals), emphasizing that appurtenances or distinct components are generally not included unless explicitly stated. It highlights the power of local custom in defining terms and the differing generosity between gifts and sales, while consistently asserting that the price paid is not proof of seller's intent.

Analysis

This isn't ancient real estate law; it's a masterclass in contractual clarity and managing expectations in commerce. For founders, these principles are gold, distilling complex human interactions into actionable decision rules that protect your downside and build your upside.

Insight 1: Truth & Transparency – Explicit Over Implicit

The most striking and frequently repeated principle in these chapters is the absolute primacy of explicit statements over implicit assumptions. Time and again, the text details what is not included in a sale "unless that is explicitly stated."

Consider the sale of a house: "If a person sold a house, he did not sell the patio around the house... Nor does the sale include the roof if it is four cubits wide... Nor does it include a water receptacle hollowed out in the ground or a cistern... This applies even when he sold him the height and the depth of the property." This isn't just about patios; it's about features. Your SaaS "dashboard" might imply reporting, but does it imply custom reporting? Your "onboarding service" might imply setup, but does it imply data migration? The text forces us to define the boundaries of our core offering. Even when selling something as comprehensive as a "town," the text is meticulous: "Not included in the sale is the movable property the town contains."

This principle extends to what might seem "obvious" inclusions. When selling a house, "he also sells the oven, the range, the door frames... but not the key." Why not the key? Because it's a small, distinct item, easily forgotten but critical for functionality. This teaches us that even seemingly minor components, essential for the use of the primary asset, are not automatically transferred. Similarly, for a ship, "Not included in the sale is the beitzit – the small boat in which one sails to land, the dugit – the small boat with which the sailors fish – the servants who work on the ship, or the sacks and the merchandise that it contains." These are all accessories to a ship, vital for its operation or utility, yet they are distinct enough to require explicit mention.

The wisdom here is profound: ambiguity breeds conflict. As founders, we often err on the side of brevity, assuming our customers understand the scope of our "platform" or "solution." But the text teaches us that unless you say it, it’s not included. This isn't about being stingy; it's about being honest and setting clear expectations. Every "feature" or "service" you don't explicitly list as included risks becoming an uncompensated expectation.

KPI Proxy: Contract Scope Clarity Score (CSCS). This could be a quarterly internal metric: (Number of post-sale customer inquiries/disputes regarding included features/services ÷ Total number of active contracts) * 100. A lower CSCS indicates better clarity. The goal is to drive CSCS to zero by proactively defining scope upfront.

Insight 2: Fairness – Context-Dependent Generosity

The Torah's legal framework often distinguishes between different types of transactions. Here, a critical distinction is drawn between a sale and a gift. "When, however, a person gives a present, the recipient acquires all the entities mentioned above – whether a field, a house, a courtyard or an olive press – that are being transferred. The general principle is that when a person gives landed property as a present, the recipient acquires everything that is attached to it unless the giver specifies otherwise." This is immediately followed by a powerful rationale: "The rationale is that a person is more generous when he gives than when he sells."

This isn't just an observation; it's a legal principle dictating the default interpretation of intent. In a sale, the presumption is a narrower transfer, requiring explicit inclusion of extras. In a gift, the presumption is a broader transfer, requiring explicit exclusion of certain items. This highlights a fundamental truth about human motivation and transaction types: the intent to profit (sale) naturally leads to a more guarded, specific transfer, while the intent to benefit another (gift) leads to a more expansive, encompassing transfer.

For founders, this insight illuminates the different "fairness" frameworks that apply to different business contexts.

• Sales: When you're selling, your default stance should be one of meticulous specificity. You are exchanging value for value, and fairness dictates that both parties understand the precise boundaries of that exchange. Hidden costs for you (due to assumed inclusions) or hidden disappointments for the customer (due to assumed exclusions) are both unfair. This is where the strict rules of "he is not including the appurtenances in the sale unless that is explicitly stated" come into play.
• Partnerships/Strategic Alliances/Free Tiers: When you're engaging in strategic partnerships, offering "freemium" models, or even granting equity to early employees, the "generosity" principle applies. These are often less about direct monetary exchange and more about building relationships, fostering ecosystems, or attracting talent. Here, a more expansive, inclusive approach to what's "given" or "shared" can build immense goodwill and long-term value. If you're "giving" access to a beta product, are you also generously including support, training, or early feature requests by default? Or are you applying a "sales" mindset, which might be perceived as ungenerous or transactional in a "gift" context?

The text even addresses access rights, showing another facet of fairness. If a seller retains a cistern within a sold property, "The seller must purchase a path from the purchaser in order to gain access to the water receptacle or the cistern that he retained. For when a person sells property, he sells generously." This seems counter-intuitive given the strictness of sales. However, the generosity here is on the part of the seller who sold the property, implying that the buyer acquires maximum utility unless explicitly restricted. If the seller wants to retain use of something within the sold property, they must compensate the buyer for the inconvenience or loss of exclusivity. This ensures the buyer's acquisition is truly valuable and unencumbered, unless otherwise agreed.

KPI Proxy: Customer Value Perception Score (CVPS). This could be derived from post-purchase surveys asking customers to rate "Value for Money" and "Fulfillment of Expectations." A higher score indicates that customers feel they received at least what they paid for, and often more, aligning with fair exchange. It's about ensuring the perception of value meets or exceeds the price, fostering trust.

Insight 3: Competition & Market Standards – Custom as King

Perhaps the most commercially relevant and empowering principle for modern business is the overriding power of local custom and commonly accepted terms. After pages of meticulously detailed rules about what's in and out, the text delivers a decisive blow to rigid interpretation:

"Even with regard to a seller and a purchaser, all the above concepts apply with regard to these matters only when there is not a fixed custom or known terms commonly used with regard to every individual article. In a place where it is customary that a person who sells a particular entity includes in the sale other particular entities, those entities are included in the sale even if they are not mentioned explicitly, for we rely on the custom."

And then, the "fundamental principle": "This is a fundamental principle: With regard to all matters of commerce and trade, we follow the commonly accepted meanings of the terms used by people of that place, and the local business customs." This is a game-changer. It means that while the Sages provide default rules for when clarity is absent, the market itself (local custom, commonly accepted meanings) dictates the true meaning of a transaction.

For startups operating in competitive markets, this is critical. You don't just sell a "SaaS platform"; you sell "enterprise SaaS," "AI-powered analytics," or "cloud infrastructure." Each of these terms carries implicit expectations within its respective industry and locale. If your competitors bundle certain features as standard, and you don't, but you use the same term, you're creating a disconnect that custom will resolve against you. Your customers will expect what the market defines, not necessarily what your internal product spec dictates.

This principle forces founders to:

• Understand market expectations: What do buyers in your niche expect when they purchase a "CRM solution" or "dev ops tool"? What features are considered standard?
• Benchmark against competitors: If everyone else includes Feature X with "Premium Tier," you ignore that custom at your peril. It sets the baseline for competitive offerings.
• Articulate your unique value proposition clearly: If you deviate from custom (e.g., you don't include something standard, or you include something extra), you must make it explicit. Otherwise, custom will fill the void, potentially to your detriment.
• Develop your own "custom": As a startup, you can shape the custom in your emerging niche, but you must do so consciously and consistently. Your consistent bundling, naming conventions, and service level agreements will, over time, become your custom, which then influences the broader market.

The text even gives examples: "Similarly, in a place where the term 'house' refers to the house alone, or the term 'house' refers not only to the house but to all of its surroundings and everything that is upon it, we follow the meaning common in that locale." This illustrates that even basic terms are defined by local context.

KPI Proxy: Market-Fit Feature Gap (MFFG). This metric tracks the percentage of features/services that customers expect to be included based on market norms (competitor offerings, industry standards) but are not included in your standard offering for a given product or tier. (Number of expected but excluded features ÷ Total expected features based on market custom) * 100. A high MFFG indicates a misalignment with market expectations, potentially leading to competitive disadvantage or customer dissatisfaction unless explicitly communicated.

Policy Move

Policy: "The Explicit Scope Mandate" – Standardized Deal Desks with Mandatory Inclusions/Exclusions Checklists.

Problem: Founders often rely on individual sales reps to verbally communicate what's included in a deal. This leads to inconsistency, assumptions, and post-sale disputes—precisely the ambiguity the Mishneh Torah warns against. The text repeatedly states that items are "not included in the sale unless that is explicitly stated."

Solution: Implement a mandatory "Deal Desk" process for all sales contracts above a certain threshold (e.g., $10K ACV). This Deal Desk will utilize a dynamic, product-specific checklist that explicitly lists:

1. Standard Inclusions: Every core feature, service, and support level that is always part of the named product/tier.
2. Standard Exclusions: Key features or services that might be assumed to be included but are not (e.g., "The analytics package includes standard reports but does not include custom dashboard development or direct API access to raw data unless purchased separately"). These should be common "gotchas" identified from past customer disputes or competitive analysis.
3. Optional Add-ons: A clear list of modules, services, or premium features that can be added at an additional cost, with their respective pricing.
4. Dependencies & Prerequisites: Any required third-party integrations, data formats, or customer responsibilities necessary for the product's full functionality.

Process:

• Before any contract is sent, the sales rep must complete this checklist, selecting the specific product/tier and any add-ons.
• The checklist dynamically generates a "Scope of Work" (SOW) or "Included Features" addendum that is automatically attached to the main contract.
• The Deal Desk lead (e.g., Head of Sales Ops, Legal Counsel, or even the Founder for early-stage) reviews and approves this SOW before the contract is sent.
• Crucially, a clause in the main contract will state: "This Agreement, including the attached Scope of Work (SOW), constitutes the entire agreement between the parties regarding the services provided. Any features, services, or deliverables not explicitly listed in the SOW are hereby excluded."

Why this works (Torah Principles in Action):

• Explicit Over Implicit (Truth & Transparency): This policy directly addresses the core teaching: "he is not including the appurtenances in the sale unless that is explicitly stated." By forcing explicit documentation of both inclusions and exclusions, we eliminate ambiguity. It prevents the customer from assuming the "patio around the house" is included when only the "house" was sold. It compels the seller (your sales rep) to articulate precisely what is being delivered, leaving no room for "one person will have this intent and another, another intent."
• Custom as King (Competition & Market Standards): The creation of these checklists must be informed by market research and competitive analysis. What do your competitors offer as standard for a "house" (your product)? What are common industry expectations? "In a place where it is customary that a person who sells a particular entity includes in the sale other particular entities, those entities are included in the sale even if they are not mentioned explicitly." This policy helps you proactively define and communicate your offering in relation to market custom. If you deviate from custom, you explicitly call it out as an exclusion, managing expectations. If you match custom, you confirm it as an inclusion.
• Fairness (Context-Dependent Generosity): While sales are inherently less "generous" than gifts, this policy ensures fairness by establishing a clear, agreed-upon baseline. It protects the customer from feeling shortchanged by unstated exclusions and protects the company from scope creep due to unstated inclusions. The "seller must purchase a path" concept implies that if you retain rights or exclude what might be expected, you bear the burden of clarifying that or compensating for it. This policy clarifies that "path" upfront, avoiding post-sale negotiations.

ROI:

• Reduced Scope Creep: Fewer uncompensated hours spent on features customers "thought" were included.
• Improved Customer Satisfaction & Retention: Customers know exactly what they're getting, leading to fewer disappointments and a higher Net Promoter Score (NPS) related to product functionality.
• Faster Sales Cycles: Clear definitions reduce back-and-forth on scope during negotiations.
• Stronger Legal Position: A clear SOW minimizes legal disputes over contractual obligations.
• Predictable Revenue & Margins: Accurate forecasting based on defined deliverables, protecting profitability.

This isn't just a legalistic exercise; it's a strategic move to build trust, predictability, and a reputation for clarity in the market. It costs less to be explicit upfront than to resolve disputes later.

Board-Level Question

Strategic Question: "Given the fundamental principle that 'With regard to all matters of commerce and trade, we follow the commonly accepted meanings of the terms used by people of that place, and the local business customs,' how are we actively monitoring, adapting to, and influencing market custom in our product bundling, feature definitions, and service level agreements to ensure our offerings are competitively aligned and clearly understood?"

Rationale & Impact:

This question cuts to the core of market strategy and competitive positioning, directly leveraging the Mishneh Torah's profound insight into the power of "custom." The text makes it unequivocally clear that, despite all the detailed legal definitions, "in a place where it is customary that a person who sells a particular entity includes in the sale other particular entities, those entities are included in the sale even if they are not mentioned explicitly, for we rely on the custom." This isn't just a nuance; it's declared a "fundamental principle."

For a startup, this means your product's value and scope are not solely defined by your internal engineering specifications or your legal team's contract language. They are fundamentally shaped by the collective expectations of your target market—the "local business customs."

Why this is a Board-level question:

1. Competitive Strategy: If your competitors consistently bundle certain features with a given product tier (e.g., "Enterprise CRM" includes advanced analytics and 24/7 support), that becomes the custom. If your "Enterprise CRM" doesn't, your customers will expect it, and you'll either have to provide it for free (margin hit) or explain its absence (sales friction, customer dissatisfaction). The Board needs to ensure the company isn't operating in a vacuum, defining its products purely internally, but is actively measuring itself against what the market expects. This directly impacts market share, pricing power, and competitive differentiation.
2. Product Roadmap & Pricing: Understanding market custom informs what features are "table stakes" versus true differentiators. If a feature becomes custom-expected, it might need to be moved from an add-on to a standard inclusion, impacting your pricing model and product roadmap. The Board needs to validate that product development and pricing strategies are aligned with market realities, not just internal capabilities.
3. Brand & Reputation: A company that consistently disappoints customers by failing to meet customary expectations will quickly develop a poor reputation. Conversely, a company that clearly understands and either meets or transparently deviates from custom builds trust and loyalty. "The price paid for an article is not considered to be proof of the seller's intent." Similarly, your stated intent in a contract might be superseded by market custom in the customer's mind. The Board is the ultimate steward of the company's brand and long-term value.
4. Risk Management (Legal & Financial): Misalignment with market custom can lead to costly customer disputes, contract renegotiations, and even legal challenges (if a customer can argue common understanding was violated). Financially, it can lead to unbudgeted fulfillment costs (scope creep) and revenue leakage. The Board must ensure these risks are being proactively managed.

How to address it (Board's expectation):

The Board would expect management to present:

• Market Custom Analysis: Regular competitive landscaping reports detailing competitor product bundles, feature inclusions, and service levels for comparable offerings.
• Customer Expectation Surveys: Data from NPS, CSAT, or specific feature expectation surveys that gauge what customers assume comes with various product tiers or service packages.
• "Custom Gap" Analysis: A clear articulation of where the company's offerings align with, or diverge from, established market custom, and the strategic rationale for any divergence.
• Actionable Plans: Specific initiatives to either adapt product definitions to align with custom, or to explicitly educate the market and differentiate where divergence is strategic.
• KPIs: Metrics like the Market-Fit Feature Gap (MFFG) and Contract Scope Clarity Score (CSCS) (as suggested in the Analysis section) to track progress.

This isn't about blindly following the pack. It's about being acutely aware of the "rules of the game" as defined by the market, and then making informed, strategic decisions to either play by those rules or consciously redefine them with absolute clarity. The Board needs assurance that leadership understands that market custom is a powerful, implicit contract that can either be your greatest ally or your most formidable adversary.

Takeaway

Clarity isn't a cost center; it's a revenue protector. Define your boundaries, respect market custom, and build trust explicitly.