Customer Contract

A customer contract is the binding legal agreement between a startup as seller and its customer as buyer. The agreement defines the scope of products or services delivered, the fees and payment terms, duration and renewal, intellectual-property ownership, warranties, indemnification, limitation of liability, and dispute resolution. It is the document that converts a sales handshake into an enforceable revenue contract, and the negotiation of its terms is where most enterprise sales cycles actually live.

The three dominant structures: Terms of Service plus order form (the default for self-serve SaaS and product-led companies; the customer clicks "I agree" to a standardized ToS and provides payment, with no negotiation; used by Slack's free and SMB tiers, Notion, Linear, most subscription tools at the SMB level); Master Services Agreement plus order form or statement of work (the enterprise default; MSA captures the long-term governing terms that survive multiple engagements, while each specific deal sits on a separate order form or SOW; used by virtually every B2B SaaS company selling to F2000); and fully custom negotiated agreement (used at the largest enterprise deals where the customer requires their own template, which is common with banks, healthcare systems, governments, and any deal over roughly $250K ACV). Key provisions that get negotiated: limitation of liability cap (typical: 12 months of fees, sometimes 1-2x annual fees for higher-risk deals); indemnification (mutual versus one-way, scope, exclusions); auto-renew (whether the contract rolls automatically and the notice window required to terminate); data ownership and portability (who owns customer data, what format it can be exported in, retention after termination); SLA commitments (uptime guarantees with credits for breach, typically 99.5-99.99%); termination for convenience (whether the customer can exit early, and with what penalty); confidentiality and IP assignment for any custom development. Negotiation reality: enterprise customers (especially regulated industries) routinely require their paper, which can add 60-120 days to the sales cycle and demand provisions a startup cannot accept (uncapped liability, broad IP indemnification, US-state-specific governing law). Companies that grow into enterprise without legal preparation hit a wall at exactly the deal size where contract review consumes more time than the deal generates revenue.

What founders get wrong: Confusing the MSA with the order form, and signing customer-supplied paper without an experienced startup lawyer reviewing it. The MSA is the governing framework; the order form is what dollars per quarter flow through. Customer-supplied templates are written by procurement to maximize the customer's protections and minimize the vendor's, and routinely include provisions (uncapped liability, broad indemnification, US data-residency, auto-renew with 90-day notice windows) that destroy startup-side economics if accepted unmodified.

Related: Master Services Agreement · Terms of Service · Indemnification Clause · Vendor Contract · Subscription Agreement

FAQ

What is the difference between a customer contract and an MSA?
The MSA (Master Services Agreement) is the umbrella framework that governs the long-term relationship between vendor and customer. The customer contract is the actual binding agreement for a specific engagement, which is usually structured as an order form or statement of work sitting under the MSA. For SaaS, the equivalent pattern is Terms of Service plus order form.

What's the difference between a customer contract and Terms of Service?
Terms of Service is one form of customer contract used for self-serve, click-to-accept agreements at scale. It is non-negotiable and standardized. A "customer contract" more broadly includes any binding agreement, from a $20-per-month click-through ToS to a $5M custom negotiated enterprise deal.

What are the most-negotiated provisions in a customer contract?
Limitation of liability cap, indemnification scope (especially IP indemnification), data ownership and portability, SLA commitments and credits, auto-renew and termination notice windows, and confidentiality. Enterprise customers also negotiate governing law, dispute resolution venue, and audit rights.

How long does a typical enterprise customer contract take to negotiate?
For mid-market SaaS, typically 2-6 weeks. For F500 enterprise on the customer's paper, 60-120 days is common and 6 months is not unusual for first-time-in deals. Companies with a well-prepared vendor-side template and an experienced legal partner can compress this materially.