Skip to main content
A SaaS sales agreement (or subscription agreement) establishes the contractual relationship between your company and business customers who subscribe to your software service. It’s essential for B2B SaaS companies to protect both parties and set clear expectations.

Why SaaS agreements matter

While consumer SaaS services typically rely on standard Terms of Service, B2B SaaS requires more comprehensive agreements that address:

Custom terms

Enterprise customers often negotiate pricing, service levels, and specific terms that don’t fit in standard ToS

Higher stakes

Business customers depend on your service for operations, creating higher expectations and potential liability

Data obligations

You’re handling business data that may be confidential, regulated, or critical to customer operations

Compliance requirements

B2B customers need assurances about security, compliance, data protection, and availability
Y Combinator open-sourced its SaaS agreement template specifically to help startups navigate B2B sales. The template balances protecting both parties while remaining startup-friendly.

Key components

Services description

Clearly define what you’re providing: Service definition - Describe the software service, features, and functionality you’ll provide Access and availability - Specify how customers access the service (web, mobile, API, etc.) Service levels - Uptime commitments, if any (be realistic—don’t promise 99.99% if you can’t deliver) Limitations - What’s explicitly not included in the service Future functionality - Disclaim any obligation to maintain specific features or add promised features
Avoid promising specific features or functionality you haven’t built yet. Sales teams love to sell “roadmap items,” but this creates legal obligations you may not be able to meet.

Subscription and fees

Define the financial terms:
Detail the plan customer is purchasing: features included, user limits, usage caps, support level, etc.
Specify fees clearly:
  • Base subscription fee
  • Per-user, per-seat, or usage-based charges
  • Setup or implementation fees
  • Overage charges
  • Professional services rates
Explain payment logistics:
  • Billing frequency (monthly, annually)
  • Payment method
  • When payment is due
  • Late payment consequences
  • Automatic renewal terms
Reserve the right to increase prices with appropriate notice (typically 30-90 days for existing customers)

License and access rights

Grant limited rights to use your software: License scope - Non-exclusive, non-transferable right to access and use the service Permitted use - Only for customer’s internal business purposes User restrictions - Limit to specified number of users or within customer’s organization No transfer - Customer can’t transfer, sublicense, or resell access Suspension rights - Your right to suspend access for non-payment or terms violations
Grant the narrowest license necessary for customer’s legitimate use. This protects your IP and prevents customers from reselling or redistributing your service.

Customer responsibilities

Define what the customer must do: Acceptable use - Comply with acceptable use policy (typically incorporated by reference) Lawful use - Only use service for lawful purposes in compliance with all applicable laws Security - Maintain security of credentials and promptly notify of any security breaches Cooperation - Provide reasonable cooperation needed for you to deliver services System requirements - Maintain compatible hardware, software, and network connectivity

Data and privacy

This section is critical for B2B SaaS: Customer data ownership - Customer owns all data they input into your system License to process - Customer grants you license to process their data as needed to provide services Data protection - Your commitments regarding data security, privacy, and compliance Data processing agreement - Reference to or incorporation of DPA for GDPR compliance Data backup - Your backup policies and customer’s responsibility to maintain their own backups Data return and deletion - What happens to customer data upon termination
For EU customers or if processing EU residents’ data, you need a Data Processing Agreement (DPA) in addition to the main SaaS agreement. The DPA establishes the customer as controller and you as processor.

Confidentiality

Protect confidential information exchanged: Mutual obligations - Both parties agree to protect each other’s confidential information Definition - What constitutes confidential information Standard of care - Protect with same care as your own confidential information (but no less than reasonable care) Permitted disclosures - To employees, contractors, advisors with need to know Exclusions - Standard exclusions for public information, independently developed, etc. Duration - How long confidentiality obligations survive (typically 3-5 years)

Service level agreement (SLA)

For enterprise customers, define commitments: Uptime commitment - Percentage uptime guaranteed (e.g., 99.9% monthly uptime) Measurement methodology - How uptime is calculated, what counts as downtime Exclusions - Scheduled maintenance, customer issues, force majeure, third-party services Service credits - What customer receives if you miss SLA (typically percentage of monthly fee) Sole remedy - Service credits are typically customer’s only remedy for availability issues
Be very careful with SLA commitments, especially in early stages. Start without formal SLAs or with modest commitments (99% is very different from 99.9%). Missing SLA can trigger credits and damage trust.

Support and maintenance

Define support obligations: Support channels - Email, ticketing system, phone (if offered) Support hours - Business hours in specified timezone, or 24/7 for premium tiers Response times - Commitments by priority level (critical, high, medium, low) Scope of support - What support covers and doesn’t cover Maintenance windows - When you can perform scheduled maintenance

Warranties and disclaimers

Balance warranties with realistic disclaimers: Limited warranties - Service will perform substantially as described, you have rights to provide the service Customer warranties - Customer has authority to enter agreement, will comply with terms Disclaimer of other warranties - Except for limited warranties above, service provided “AS IS” No warranty of results - Don’t guarantee specific business results or outcomes
B2B customers may push back on broad “AS IS” disclaimers. Be prepared to provide limited warranties about service functionality while disclaiming warranties about results, uptime (covered by SLA), or third-party services.

Limitation of liability

Critical protection for your startup: Liability cap - Total liability limited to fees paid in past 12 months (or 6 months for lower-tier plans) Excluded damages - No liability for indirect, incidental, consequential, or special damages Specific exclusions - Loss of profits, revenue, data, business interruption, reputation Exceptions - Liability limitations typically don’t apply to:
  • Your gross negligence or willful misconduct
  • Your confidentiality obligations
  • Your indemnification obligations
  • Payment obligations
Mutual caps - Consider making liability limitations mutual to make them more enforceable
Never agree to unlimited liability. Even large enterprise customers should accept reasonable liability caps. Unlimited liability could bankrupt your startup over a single incident.

Indemnification

Define who protects whom from what: Your indemnification - You indemnify customer against claims that your service infringes third-party IP rights Customer indemnification - Customer indemnifies you against claims arising from:
  • Customer’s use of the service
  • Customer data
  • Customer’s violation of terms
  • Customer’s violation of laws or third-party rights
Process - Requirements for indemnification: prompt notice, cooperation, control of defense Exceptions - Your IP indemnity shouldn’t apply to customer modifications, use with non-approved services, etc.

Term and termination

Define relationship duration and exit:
Length of initial commitment (month-to-month, 1 year, multi-year)
Whether agreement auto-renews and for what period
Whether either party can terminate without cause (typically with 30-90 days notice)
Right to terminate for material breach (usually after notice and opportunity to cure)
What happens when agreement ends:
  • Access terminates
  • Fees for full billing period remain due
  • No refunds for prepaid amounts
  • Data return/deletion procedures
  • Survival of certain provisions (confidentiality, liability, etc.)

General provisions

Standard but important: Assignment - Customer can’t assign agreement without your consent (but you can assign to acquirer) Governing law - Which state/country law governs Dispute resolution - Court jurisdiction or arbitration requirements Entire agreement - This agreement supersedes all prior agreements and discussions Amendments - How agreement can be modified Severability - If one provision is invalid, others remain enforceable Waiver - Failure to enforce one provision doesn’t waive right to enforce it later Notices - How parties provide legal notices to each other Force majeure - Neither party liable for failures due to circumstances beyond reasonable control

Order forms and statements of work

The main agreement is often a master services agreement (MSA) supplemented by: Order forms - Specify the plan, pricing, number of users, term, and other deal-specific details Statements of work (SOW) - For professional services, implementation, or custom development
Using an MSA + order form structure lets you negotiate the detailed legal terms once, then execute new orders with minimal friction. This is standard in enterprise sales.

Negotiation strategy

What to hold firm on

Liability caps - Reasonable limitations are non-negotiable for startups IP ownership - You own your platform, customer owns their data No warranties beyond what you provide - Don’t let customers add custom warranties Data security approach - Don’t agree to specific security measures you haven’t implemented

What you can negotiate

Pricing and payment terms - Volume discounts, multi-year discounts, payment schedules Service levels - Can tier SLAs by plan level Support terms - Can offer enhanced support for premium pricing Term length - Can offer better pricing for longer commitments Contract language - Can accept reasonable markup that doesn’t change substance

Red flags

Walk away from deals requiring:
  • Unlimited liability
  • Performance guarantees you can’t meet
  • Access to source code
  • On-premise deployment if you only offer SaaS
  • Exclusive relationships or non-compete clauses
  • Personal guarantees from founders

Getting started

Y Combinator SaaS agreement

Download YC’s open-source SaaS agreement template, specifically designed for SaaS startups

Common mistakes to avoid

Sales pressure leads to promises about features, uptime, or capabilities you can’t consistently deliver. Under-promise and over-deliver instead.
Using one-off agreements for each customer creates chaos. Establish an MSA + order form structure early.
The first enterprise customer asks for unlimited liability, and you accept to close the deal. This can bankrupt your company.
Don’t negotiate detailed agreements for customers paying $100/month. Use standard Terms of Service for small customers; save MSAs for material contracts.
Your first $100K+ deal deserves legal review, even if the customer uses “standard” terms. Red flags are easier to spot before signing.

When to use different agreement types

Standard Terms of Service

  • Self-service signups
  • Small businesses and individuals
  • Monthly recurring revenue < $1,000
  • No custom terms needed

Simple SaaS agreement

  • Mid-market customers
  • Annual contracts 10K10K-100K
  • Standard plans with minor customization
  • Limited negotiation

Comprehensive MSA

  • Enterprise customers
  • Deals > $100K annually
  • Significant negotiation
  • Custom SLAs, security requirements, compliance needs
  • Multi-year commitments
As you grow, you’ll develop three tiers: (1) self-service with standard ToS, (2) sales-assisted with light SaaS agreement, and (3) enterprise with full MSA. Start simple and add complexity only when deal size justifies it.

Building a scalable contracting process

As you close more deals: Create templates - MSA template, order form template, DPA template Define approval thresholds - What deal size or terms require legal review Document playbook - What terms you will/won’t accept and why Use contract management software - Track agreements, renewals, and amendments Train sales team - Ensure they understand what terms are negotiable Pre-approve common requests - Standard security questionnaires, insurance certificates, W-9 forms Effective SaaS agreements balance protecting your company with being customer-friendly enough to close deals. Start with a strong template, know which terms are negotiable, and don’t be afraid to walk away from deals requiring unacceptable terms. Your future self will thank you.

Build docs developers (and LLMs) love