SaaS contracts, licensing and pricing, answered
111 questions on SaaS agreements, MSAs and SLAs, pricing models, and software licensing, answered in plain English for technology and SaaS businesses.
SaaS agreements, MSAs and SLAs, pricing models, and software licensing, answered directly, drawn from what technology and SaaS businesses actually search for.
SaaS contracts, licences, MSAs and SLAs
The agreement is where your product promise becomes an enforceable obligation.
A SaaS agreement is not a software licence. A licence grants rights to a copy of software; a SaaS agreement grants access to a service you continue to run. That difference drives everything downstream: uptime rather than delivery, subscription rather than perpetual fee, your infrastructure rather than the customer’s, and data that lives with you rather than with them.
The common structure is a master agreement plus order forms. The master carries the legal terms that rarely change, and each order form carries the commercial specifics: users, tier, term, price, start date. That structure is worth building early, because it is what lets you close the second and third deal with a customer without a fresh negotiation each time.
Service levels deserve more care than they usually get. An SLA with a 99.9 percent target, service credits as the sole remedy, and no exclusion for scheduled maintenance is a very different commitment from one with maintenance windows, a measurement method, and a chronic failure termination right. Both look similar on a page. Only one of them is survivable at scale.
What are SaaS agreements?
Contracts for access to hosted software on a subscription basis. They cover subscription scope, fees and renewal, service levels, support, customer data rights, security, IP, liability and termination, and they usually sit alongside a DPA and an acceptable use policy.
What are the legal risks in a SaaS contract?
Uncapped or carved-out liability, service credits that do not limit your exposure, uptime you cannot measure, indemnities with no cap or control of defence, unilateral audit rights, data deletion obligations that conflict with your backups, unrestricted assignment, and auto-renewal terms that a customer can later argue were not brought to their attention.
What is the difference between a SaaS agreement and a software licence agreement?
A software licence grants permission to install and use a copy, often perpetually, with the customer running it. A SaaS agreement grants access to a service you host and operate, on subscription, with availability obligations attached. Using licence drafting for a SaaS product leaves gaps around uptime, data and termination.
What should a SaaS contract review checklist include?
Scope of the subscription and permitted users, fee and uplift mechanics, renewal and notice periods, uptime and credits, support response times, security commitments, data ownership and return, sub-processor rights, liability cap and carve-outs, indemnities, termination triggers, and the DPA’s interaction with the cap.
How do I negotiate an enterprise SaaS contract?
Decide in advance which three points you will hold and which you will trade, and get them agreed internally before the call. The usual holds are the liability cap, the data deletion timescale and the audit right. The usual trades are payment terms, notice periods and a narrow security addendum. Going into a negotiation without that list is how deals drift for months.
Do I need a service level agreement?
If you sell to businesses, you will be asked for one, and the version you write is better than the version they impose. Define availability, exclusions, the measurement window, the credit mechanism, how a customer claims, and whether credits are the sole remedy.
Is a free SaaS agreement template a reasonable starting point?
As a structure, yes. As the contract you sign with your largest customer, no. Templates carry generic caps and silent schedules, and they will not reflect your architecture, sub-processors or support model.
Who can draft SaaS contract templates for a startup?
A commercial lawyer who will build a set rather than a single document: master agreement, order form, DPA, acceptable use policy and SLA, plus a short internal playbook saying what your sales team can agree without asking. Eliga builds these as a package so the second and third deal do not go back to legal.
Pricing models and what they do to your contract
Every pricing decision creates a drafting obligation. Most pricing pages are silently unenforceable.
Pricing is a commercial decision, but it lands in the contract. Per-seat pricing needs a definition of user and a rule for what happens when the count changes mid-term. Usage-based pricing needs a metering definition, a source of truth for the count, and a dispute process for when the customer’s number differs from yours. Tiered pricing needs to say what happens when a customer exceeds a tier: automatic upgrade, overage rate, or throttle.
Renewals are the other half. If you want to raise prices, the contract has to give you the mechanism: a defined uplift, a notice period, and a renewal that does not silently lock last year’s rate in perpetuity. Auto-renewal clauses are useful but need to be clearly presented, especially in any consumer or small business context where fairness rules bite.
None of this requires a lawyer to design your pricing. It requires someone to read the pricing page and the contract in the same sitting, and to notice where the page promises something the contract does not deliver, or the contract charges for something the page said was included.
What are the main SaaS pricing models?
Flat rate, per user or per seat, tiered packages, usage or consumption based, per feature, and hybrid models that combine a platform fee with usage. Freemium and free trial sit on top of any of them as acquisition mechanics rather than pricing models in their own right.
What is a subscription pricing model?
Recurring payment for continued access, usually monthly or annually, rather than a one-off purchase. The contract implications are renewal mechanics, price change rights, minimum terms, cancellation notice and what happens to data when payment stops.
How does usage-based pricing change the contract?
You need a defined billable unit, a stated source of truth for measurement, a billing cycle, an invoice dispute window and a rule for what happens if metering fails. Without those, every anomalous month becomes a negotiation.
What is the difference between SaaS pricing and SaaS cost?
Pricing is what you charge and how you package it. Cost is what it takes to serve the customer, including infrastructure, support and onboarding. Contract terms sit in between: unlimited support and aggressive SLAs can turn a healthy price into an unprofitable one.
Can I raise prices at renewal?
Only if your contract lets you, and only in the way it describes. The workable pattern is a stated uplift mechanism, for example CPI plus a fixed percentage, with a defined notice period before the renewal date and a customer right to terminate if they will not accept it.
How should tiered pricing be handled contractually?
State what each tier includes, what happens on exceeding it, and how a mid-term upgrade is priced and invoiced. Ambiguity about overage is one of the most common sources of unpaid invoices in SaaS.
How do I negotiate on price without discounting?
Trade on terms rather than rate. Longer commitment, annual upfront payment, a case study, a reference call or a narrower support commitment are all worth real money and none of them reset your price expectations for the next renewal.
IP and software licensing
Ownership, licence scope and what happens at the end. Everything else is detail.
A software licence agreement grants permission to use software on stated terms. The core is the grant: what may be used, by whom, how many, where, for how long, and for what purpose. Then the restrictions, then the ownership statement making clear that a licence is not a transfer, then support and maintenance if any, then warranties and liability.
Perpetual, subscription and open source licences behave differently. Perpetual grants ongoing use rights for a one-off fee, usually with paid maintenance separate. Subscription rights end when payment ends. Open source licences carry obligations, and permissive licences such as MIT and Apache 2.0 behave very differently from copyleft licences such as the GPL, which can force disclosure of your own source in some distribution scenarios.
For a services or development business, the IP question is simpler and more urgent: who owns what you built. In the UK, work created by an employee in the course of employment generally belongs to the employer, but work created by a contractor belongs to the contractor unless assigned in writing. If you have never checked your contractor agreements for an assignment clause, check them this week.
What is a software licence agreement?
A contract granting rights to use software, defining the scope of that use, restricting what the licensee may not do, confirming that ownership stays with the licensor, and setting out warranties, support and liability.
What software licensing terms should I understand?
Grant and scope, named user versus concurrent user, seat and device limits, territory, term, sublicensing and affiliate use, restrictions on reverse engineering and benchmarking, audit rights, maintenance and support, and end of term rights.
Who owns work produced by a contractor?
In the UK, the contractor, unless the contract assigns the IP to you in writing. This is different from employees, whose work in the course of employment generally vests in the employer. Assignment clauses in contractor agreements are not optional if you intend to own the output.
Do we need to worry about open source licences in our product?
Yes, if you distribute software or ship components. Permissive licences require attribution; copyleft licences can require you to make your own source available in certain distribution scenarios. Enterprise buyers and acquirers ask for a component inventory, so knowing what is in your product is worth doing before someone asks.
Still the wrong answer for your situation?
General answers only go so far. If you have a SaaS contract on your desk, a pricing model that has outgrown your terms, or a licence question specific to your product, the useful conversation is about your facts.
Book a call: calendly.com/dhruve-eligaconsultancy
This page is general information about UK and EU commercial practice. It is not legal advice and it does not create a solicitor-client relationship.