SaaS contract terms to check before you sign

A SaaS agreement is rarely one page. It is usually an order form with the price, term and quantity, a master agreement or terms of service, and attachments by reference: a service level page, a data processing agreement, an acceptable-use policy. If the order form says the other documents are "incorporated by reference", they bind you in the version they have on the day the clause says, which may be a web page the vendor can edit.

Before you read a clause, collect every document and save a dated copy (PDF or a screenshot with the URL and date) in the same folder as the order form. When a dispute or a renewal comes, the version you accepted is the one that counts, and a changed web page will not show you it.

Read in this order. The first four decide how much cash is committed and for how long; the rest decide what you can do about it. For each clause write down the answer, the page it came from and the date, in your vendor register.

The renewal date is when you are charged. The notice deadline is when you lose the choice. They can be months apart, and the deadline is the number that belongs in your calendar. If a contract renews for a full year, the cost of missing the deadline is the whole year, not the month you noticed.

Read the mechanics as carefully as the dates. Does notice have to come from a named contact? Does it have to be in writing to a postal or email address, or is there an in-app cancel? Is a reminder from the vendor promised? Does cancelling stop renewal, or only turn off auto-renewal and leave the term to run out? Settle these on the order form, because a support chat does not change a contract.

Whether any law overrides a contract's renewal terms for a business buyer depends on where you and the vendor are, and it is a question for counsel. Do not rely on a statute to rescue a missed deadline. See cancelling without penalties for what to do if you are already inside the window.

• Write the notice deadline, the notice method and the address in one line next to the vendor in your register.
• Set reminders ahead of the deadline, not the renewal date.
• After you send notice, ask for written confirmation that renewal is stopped and the date service ends.

A discount in year one is a cost in year two if nothing limits the renewal price. The clause to look for is a cap on increases, written as a percentage, tied to an index, or a fixed price for the renewal term. If there is none, the contract is silent on the biggest unknown in your software budget.

Ask for the cap on the order form. If the vendor will not cap the increase, ask for the renewal price to be stated in writing a set number of days before the notice deadline, so you learn the number while you can still act on it.

• Sample arithmetic, with invented numbers: a plan costs $10,000 for the first term. With a 5% cap the renewal can be at most $10,500; with no cap the contract does not say. The point is the check, not the percentage.
• Check whether the cap applies to the unit price, the total, or only to the list price. A cap on unit price does nothing if the seat count you must buy rises.
• Check whether add-ons, support tiers or usage rates sit outside the cap.

The quantity on the order form is usually a commitment. If it is a floor for the term, a seat you remove next month is still on the invoice until the term ends. A true-down is a right to lower the count, often only at renewal; a true-up is the bill for seats you add during the term. If neither appears, assume you pay for the committed count until the end.

Measure before you sign. Estimate the seats you need on day one and the seats you will need at renewal, and sign for the first number, not the second. Ask for the right to add seats at the same rate and for a reduction right at renewal. If you buy for the team you expect to hire into, you pay for empty seats while you hire.

Exit terms look irrelevant on the day you sign and decide your options on the day you leave. Three questions settle it: can you leave before the term ends and what does it cost; what can you take with you, in what format, and for how long after the contract ends; and when does the vendor delete your data.

A clause promising return of your data is a promise on paper. Test it. During the first months, run an export of the data you would need to run the business without the tool, open the files and check them against the screen. If the export leaves out attachments, history or relationships, you want to know now, not at the end of the notice window. See offboarding SaaS accounts for what to collect on the way out.

• Ask what formats export in, whether you can export without the vendor's help, and whether the export is included in the price.
• Ask how long you have after termination to retrieve data, and to be told in writing before deletion.
• Ask for early termination to be priced as the unused part of the term, if early exit is allowed at all.
• Ask for the right to end the contract for cause if the vendor misses a service level repeatedly or has a security incident, with a refund of the prepaid unused portion.

A service level commitment has four parts: the target, how it is measured, what you get when it is missed, and how you claim it. A number without a remedy is a marketing line. A remedy that requires a claim within a short window is one you will miss unless someone owns it.

Vendors differ. Slack's service level page, as read on the checked date, says the vendor uses commercially reasonable efforts to keep the service available around the clock and lists exclusions for planned downtime, with notice, and for events outside its reasonable control such as internet provider failure or denial-of-service attacks. The page, as read, states no uptime percentage and no credit. That is one vendor's page for one product on one day; other vendors and plans differ and your order form may point to a different document.

Decide how much the tool matters. For a chat tool you can live without it for a day. For billing, payments or your ledger, an outage costs money, and the question is whether the contract lets you leave or recover anything when it happens.

If the vendor handles personal data for you, privacy rules in many places expect a contract that spells out what the vendor may do with it. Under the GDPR, Article 28 lists what a processor contract must contain, as read on the checked date: processing only on the controller's documented instructions, confidentiality for the people involved, security measures, conditions for engaging sub-processors, help answering data subject requests and meeting security and breach obligations, deleting or returning the data at the controller's choice when the services end, and information and audit rights to show compliance.

Whether the GDPR applies to you depends on whose data you hold and where they are. If it does, use Article 28 as a checklist against the vendor's data processing agreement. If it does not, other laws or customer contracts may ask for similar terms. Counsel decides which apply.

• Ask for the vendor's data processing agreement and its list of sub-processors, and how you are told when it changes.
• Ask where your data is stored and processed, and whether it can be fixed to a region. Do not assume a region from where the vendor is based.
• Ask what happens to your data at the end: return, deletion, and how deletion is confirmed.
• Ask whether your data may be used to improve the vendor's products, and get the answer in the contract, not a blog post.

Asking works best when it is specific, in writing and tied to what you can show. Pick the three clauses that move the most money for your contract (usually renewal notice, price at renewal and seat reduction) and ask for those; a long list gets a short answer.

Ask in this order, because each costs the vendor less than the next: a written reminder before the notice deadline; the renewal price stated in advance or capped; a right to lower seats at renewal; a shorter term or lighter commitment; a clearer exit and data return clause; a service level with a remedy.

Not every tool needs a full read. A tool at a small monthly price on a monthly plan needs the term, the cancel method and the price-change clause. A tool you run the company on, or one that holds sensitive data, deserves the whole checklist and an hour of counsel. The deciding factors are what leaving costs, what the data is and how long you commit, not the logo.

Put the rule in a software approval policy so the check happens before the card is entered. Compare monthly and annual terms with annual vs monthly billing, and see what you already owe with the browser audit, which runs in your browser and sends nothing out of it.

A contract term is also an accounting fact. An annual prepayment is held as an asset and released into expense as the service is delivered under accrual basis accounting, while the cash leaves at once. A committed minimum that you cannot reduce is a payment you owe, whether or not you use the seats, and the invoice will arrive in accounts payable. Tell your bookkeeper the term, the commitment and the notice deadline when you sign.

This is general information, not legal advice. Contract terms are enforced differently in different places, and the wording of your clause matters more than any rule of thumb here. Have counsel read anything binding before you sign it, especially terms on liability, data protection and early termination. We give no typical notice period, cap or discount, because none of the sources we read gives one that would hold for your contract.