Alex is Sprintlaw's co-founder and a legal technology leader. He holds law and media degrees from the University of Sydney and has been recognized by Australasian Lawyer, Lawyers Weekly and the Sydney Young Entrepreneur Awards for his work building Sprintlaw and improving access to business legal support.
What should you put in your SaaS master services agreement when you're selling subscription access to business customers? The practical answer is that your agreement should clearly explain what the customer gets, what they pay, what they're allowed to do, and what happens if something goes wrong.
That sounds simple, but SaaS contracts can get messy quickly. You might have subscriptions, onboarding, support, integrations, usage limits, security promises, data handling, and custom services all wrapped into one deal.
The good news is that your contract doesn't need to be intimidating. A well-drafted SaaS MSA can make your sales process smoother, protect your product, and help both sides understand the deal from day one.
What Is A SaaS Master Services Agreement?
A SaaS master services agreement is the main contract that sets the legal and commercial rules for your customer's use of your software and related services.
Think of it as the legal framework sitting behind each sale. Your MSA usually works with shorter deal documents, such as an order form, proposal, statement of work, or online subscription terms of service. The MSA covers the bigger legal terms, while the order form captures the deal details.
For a B2B SaaS company, your MSA will usually cover:
- Access rights: who can use the platform, for how long, and for what purpose.
- Subscription terms: fees, billing, taxes, user numbers, upgrades, downgrades, and renewal mechanics.
- Service commitments: support, uptime, implementation, training, and any professional services.
- Customer obligations: acceptable use, account security, cooperation, and restrictions on misuse.
- IP ownership: your rights in the software, the customer's rights in their data, and rules for feedback.
- Risk allocation: warranties, disclaimers, liability caps, indemnities, and termination rights.
US contract law is mostly governed by state law, so the exact interpretation of your SaaS customer agreement can depend on the law you choose in the contract and the state where a dispute is heard. For software subscriptions, courts often apply general contract principles. The Uniform Commercial Code can matter for some software or mixed software and goods transactions, but many SaaS arrangements are treated more like services or licenses than sales of goods.
Do You Need A Separate Order Form Or Statement Of Work?
Yes, most B2B SaaS businesses should use a separate order form or statement of work alongside the MSA, especially once deals vary from customer to customer.
Your MSA should avoid repeating commercial details that change every sale. Otherwise, you'll end up redrafting your full contract every time a customer adds users, changes modules, or buys implementation support.
A simple order form can cover:
- the customer's legal name and billing details
- the products, modules, or subscription tier being purchased
- the number of users, seats, locations, transactions, or other usage limits
- subscription start date and initial term
- fees, billing cycle, and payment due dates
- support plan, service levels, or onboarding package
- any special terms that override the standard MSA
A statement of work is useful where you also provide IT services, such as data migration, configuration, custom integrations, training, or implementation. It should be clear about deliverables, timelines, assumptions, customer responsibilities, acceptance criteria, and extra charges.
For example, Maya runs a SaaS platform that helps manufacturers track inventory. Her standard MSA covers software access, support, IP, confidentiality, warranties, liability, and termination. For a customer buying 25 admin users plus onboarding, Maya uses an order form for the subscription and a short statement of work for the onboarding milestones. This keeps the legal terms stable while letting the commercial deal change.
What Clauses Should Go In A SaaS MSA?
Your SaaS MSA should include the clauses that explain the product, protect your platform, and allocate risk in a way that matches the deal.
Here's a practical SaaS contract checklist you can use as a starting point. A lawyer should tailor it before you use it with customers, because templates often miss product-specific risks, industry rules, and sales process details.
- Parties And Contract Structure: name the contracting parties and explain how the MSA works with order forms, SOWs, online terms, and policies.
- Definitions: define key terms like platform, customer data, authorized users, subscription term, usage limits, confidential information, and documentation.
- Access To The SaaS: grant the customer a limited, non-exclusive right to access and use the platform during the subscription term.
- User Rules And Restrictions: state who can use the platform and prohibit copying, resale, reverse engineering, security testing without permission, unlawful use, and misuse.
- Fees And Payment: set out pricing, invoicing, payment timing, late payments, taxes, disputed invoices, and consequences of non-payment.
- Implementation And Services: describe onboarding, training, configuration, support, and any project work or attach these details in an SOW.
- Support And Availability: explain support channels, response targets, maintenance windows, and any service credits if you offer them.
- Customer Data: state that the customer owns its data, explain permitted use by your business, and cover backups, exports, deletion, and data return.
- Security: describe your security commitments at the right level, without overpromising beyond what your SaaS security terms actually support.
- Privacy And Data Processing: refer to your privacy notice and include a data processing agreement where the customer or applicable law requires one.
- Intellectual Property: protect your software, documentation, trademarks, workflows, APIs, and know-how, while preserving the customer's rights in its materials.
- Confidentiality: protect business, technical, financial, and product information, including information that may qualify as trade secrets under the Defend Trade Secrets Act.
- Warranties And Disclaimers: say what you promise and what you don't promise, especially around uninterrupted access, error-free operation, and customer outcomes.
- Indemnities: deal with third-party IP claims, customer misuse, unlawful data, and other agreed risk areas.
- Limitation Of Liability: cap exposure, exclude certain damages where allowed, and carve out any risks that shouldn't be capped.
- Term And Termination: explain contract length, renewal mechanics, termination for breach, suspension, data export, and post-termination obligations.
- General Legal Terms: cover governing law, notices, assignment, subcontracting, order of precedence, electronic signatures under the federal E-SIGN Act, and entire agreement wording.
You don't need to make every clause long. Clear and specific usually beats dense legal drafting.
How Should You Handle Fees, Renewals And Suspension?
You should handle fees, renewals and suspension with enough detail that there's no guesswork when an invoice is late or a customer wants to change their subscription.
Start with the commercial basics. Your MSA and order form should say whether fees are monthly, annual, usage-based, or a mix. If pricing is per user, per location, per API call, per transaction, or per data volume, define the unit clearly.
Payment Terms
Common B2B SaaS payment terms include payment upfront, payment on receipt, or payment within a set number of days after invoice. There's no single federal rule that sets the payment period for a SaaS invoice, so your contract needs to say it.
If you're offering 30-day payment terms, say exactly when the clock starts. For example, payment could be due 30 days after the invoice date. If a customer disputes part of an invoice, you can require them to pay the undisputed part on time while both sides work through the issue.
Suspension Rights
Your suspension clause should be firm but fair. If the customer doesn't pay, breaches acceptable use rules, threatens platform security, or uses the service unlawfully, you may need the right to suspend access.
A balanced clause often includes:
- written notice before suspension for ordinary non-payment
- a short cure period, such as 10 days, if that suits your billing model
- immediate suspension for serious security, legal, or platform integrity risks
- a statement that fees keep accruing during suspension, unless you agree otherwise
Be careful with automatic renewal wording. Renewal and cancellation rules can be affected by federal and state law, customer type, industry rules, and your sales process. If you use auto-renewal, get tailored advice on the exact wording and consent process.
What Should The Agreement Say About IP, Data And Confidentiality?
Your agreement should say that you own your software and related intellectual property, the customer owns its data, and both sides must protect confidential information under clear SaaS terms.
This is one of the most important parts of a master services agreement for your software company. Without it, you may end up arguing about who owns product improvements, uploaded data, analytics, or customer feedback.
Your Software And Brand
Your MSA should make clear that the customer is buying access to the platform, not ownership of the software. You can reserve rights in your code, workflows, user interface, documentation, databases, APIs, tools, product names, logos, and know-how.
Federal IP laws matter here. Copyright protection for software code and documentation comes from the Copyright Act. Trademark rights in your product name or logo may be protected under the Lanham Act, especially if you use or register them as trademarks. Your contract should support these rights by restricting copying, reverse engineering, sublicensing, resale, and unauthorized brand use.
Customer Data And Usage Data
Your customer will usually expect to own the data they upload or generate through ordinary use. Your MSA should say that clearly, then explain what rights your business needs to host, process, display, back up, transmit, analyze, and support that data.
If you use aggregated or de-identified usage data to improve your product, benchmark performance, or develop analytics, say so in a careful way. Don't promise that data is anonymous if your process doesn't truly prevent re-identification.
Confidentiality And Trade Secrets
Your confidentiality clause should cover both sides' non-public business and technical information. For SaaS companies, that often includes product roadmaps, security details, pricing, customer lists, API credentials, and implementation materials.
If information is valuable because it's secret and you've taken reasonable steps to protect it, it may also be a trade secret under the Defend Trade Secrets Act. Your contract won't create trade secret protection by itself, but it helps show that you treat sensitive information carefully.
Privacy laws may also apply if you handle personal information, especially in regulated industries. Your MSA should point to the right privacy and data processing documents, but this article doesn't go into a privacy-law deep dive.
How Do Warranties, Liability And Indemnities Work In SaaS Deals?
Warranties, liability limits and indemnities work by deciding which risks you accept, which risks the customer accepts, and where your financial exposure stops.
For SaaS businesses, this isn't just legal fine print. These clauses can affect enterprise sales, insurance coverage, investor diligence, and your ability to recover from a customer dispute.
Warranties
A warranty is a promise about your product, services, or subscription access. You might warrant that the platform will materially perform according to the documentation, that professional services will be performed in a professional manner, or that you have the right to provide the service.
You should avoid broad promises like guaranteeing uninterrupted service, error-free operation, particular business results, or that the platform will meet every customer requirement. Those promises are difficult for most SaaS companies to control, especially when outages, third-party providers, customer systems, and internet connectivity are involved.
Your disclaimers should be clear and conspicuous where needed. Many SaaS MSAs disclaim implied warranties, such as implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement, to the extent allowed by applicable law. The wording should match your product, sales claims, and the law governing the agreement.
Limitation Of Liability
A limitation of liability clause helps stop a single dispute from threatening the whole business. It usually caps each party's liability at a set amount, often the fees paid or payable under the order form during a defined period, such as the previous 12 months.
Your clause may also exclude certain types of damages, such as lost profits, loss of goodwill, business interruption, or indirect, incidental, special, consequential, exemplary, or punitive damages, where the governing law allows this. Be precise, because courts can read these clauses closely.
Some risks are often carved out of the cap or given a higher cap. Common examples include payment obligations, confidentiality breaches, IP infringement indemnities, data security obligations, fraud, willful misconduct, and claims that can't be limited by law. The right position depends on your product risk, bargaining power, insurance, and customer profile.
Indemnities
An indemnity is a promise to cover certain third-party claims or losses. In SaaS deals, customers often ask the provider to indemnify them if the platform infringes a third party's intellectual property rights. Providers often ask customers to indemnify them for claims arising from customer data, unlawful use, misuse of the platform, or breach of acceptable use rules.
Your indemnity clause should say what claims are covered, what losses are included, who controls the defense, when notice must be given, and what happens if the software needs to be modified, replaced, or withdrawn because of an IP claim.
These clauses are worth getting right early. Once your sales team starts using the MSA, they can become hard to renegotiate across existing customers.
Frequently Asked Questions
Is a SaaS MSA the same as terms of service?
Not always. Terms of service are often used for self-serve or online signups. A SaaS MSA is usually used for negotiated B2B deals and works with order forms or SOWs. Some businesses use both, with the MSA taking priority for enterprise customers.
Can I use one SaaS MSA for every customer?
You can use one standard MSA as your starting point, but you may still need different order forms, data processing terms, security exhibits, or SOWs for particular customers, industries, or deal sizes.
Should my SaaS MSA include a service level agreement?
If you offer uptime commitments, response targets, service credits, or priority support, include them in the MSA or attach a service level agreement. Avoid promising service levels your team and infrastructure can't reliably meet.
What law should govern a SaaS MSA?
Many US SaaS companies choose the law of the state where they're based, but the best choice depends on your business, customers, and sales strategy. Your governing law and venue clauses should be deliberate, not copied from another contract.
Key Takeaways
- A SaaS MSA sets the legal framework for B2B software access, services, data, IP, risk, and termination.
- Use order forms and SOWs for deal-specific details like users, fees, onboarding, timelines, and special terms.
- Your MSA should clearly cover payment, renewal, suspension, support, security, privacy, customer data, and acceptable use.
- IP, confidentiality, warranties, liability caps, and indemnities are central to protecting your SaaS business.
- Keep the drafting practical and accurate, especially around security, uptime, auto-renewals, and customer outcomes.
If you'd like help with SaaS master services agreements, order forms, statements of work, warranties, liability limits, indemnities, or customer data terms, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.








