Contract Negotiation Template for PMs

Product managers should be involved when the deal includes any of these: feature commitments (roadmap implications), custom SLAs (engineering implications), pricing below standard (margin and precedent implications), or custom integrations (product scope implications). For standard-priced, standard-terms deals, PM involvement is not needed. Establish clear trigger criteria with sales leadership so PMs are not pulled into every deal. The [Product Strategy Handbook](/strategy-guide) covers how to set these thresholds.

Reframe from "no" to "here is what we can do." Options: (1) Commit to the outcome, not the specific feature ("We will provide a way to achieve X" rather than "We will build feature Y"). (2) Offer professional services to build a custom solution. (3) Commit to a discovery process ("We will research this need and include it in our Q3 planning cycle"). (4) Offer early access to a beta that partially addresses the need. Never commit to a feature you are not confident you can deliver.

Industry benchmarks for B2B SaaS: 5-10% for 2-year commitment, 10-20% for 3-year commitment. Anything above 20% should require exceptional strategic justification (top-100 logo, competitive displacement, new market entry). Always pair discounts with value exchanges: longer commitment, annual prepay, reference agreement, case study participation.

Document every custom term with an explicit "exception" flag in your deal records. Include the business rationale for the exception. Set a review trigger: if more than 3 deals in a quarter request the same exception, evaluate whether it should become standard (and re-price accordingly). Never tell a new customer "we did this for [CustomerX]" without sales leadership approval. Use the [TAM Calculator](/tools/tam-calculator) to assess whether standardizing a custom term would open a meaningful market segment.

Always use "commercially reasonable efforts" rather than hard commitments. Specify the outcome, not the implementation. Include a timeline with buffer (2x engineering estimate). Add a clause that allows the customer to terminate (or receive credit) if the feature is not delivered within a reasonable extension period. Never commit to a specific UI, API endpoint, or implementation detail in a contract. ---