Legal documents / Employment & HR / Contractor Agreement (individual)
First document free, no credit card
Rating
★★★★★ {{RATING}} from {{N}} reviews
Built by
Australian lawyers
Signing
E-sign included
Storage
Saved to your account
Lawpath Atlas · the AI editor
Single-tap answers, each explained in plain English.
Type it or use voice input — names, fees, dates and scope.
Every change Atlas makes shows as a tracked suggestion.
First document free, no credit card
| Document | What it covers | Who signs | Use it when | |
|---|---|---|---|---|
| SaaS Agreement (Software as a Service) | Access to software as an online subscription | The provider and the customer | You provide software as a service | Create now |
| Licensing Agreement (IP) | Permission to use intellectual property | The licensor and the licensee | You’re licensing IP rather than providing a service | Create now |
| Website Terms and Conditions of Use (Services) | The rules for people using your website | The website owner’s terms apply to users | You need rules for visitors, not a contract with business customers | Create now |
Here’s what’s in Lawpath’s SaaS Agreement (Software as a Service), clause by clause.
Names the provider and the customer and describes the software and services being provided.
Sets out the right to access and use the software and what the customer can’t do with it.
Sets goals for the service, such as minimum uptime and support response times.
Covers the subscription fee, when it is charged and how it can change.
Sets out how customer data is handled and protected.
Confirms the provider keeps ownership of the software and sets who owns what the customer puts into it.
Stops each side sharing the other’s confidential information.
Records what the provider promises about the service and what it doesn’t.
Allocates risk if something goes wrong, including limits on liability.
Explains how the agreement can end or be suspended, and which state’s law applies.
| Document | What it covers | Who signs | Use it when | |
|---|---|---|---|---|
| SaaS Agreement (Software as a Service) | Access to software as an online subscription | The provider and the customer | You provide software as a service | Create now |
| Licensing Agreement (IP) | Permission to use intellectual property | The licensor and the licensee | You’re licensing IP rather than providing a service | Create now |
| Website Terms and Conditions of Use (Services) | The rules for people using your website | The website owner’s terms apply to users | You need rules for visitors, not a contract with business customers | Create now |
| Lawpath Atlas | Online form LAWPATH | Bespoke lawyer | |
|---|---|---|---|
| How you describe the deal | A few quick questions, then plain English (typed or voice) | Answer form questions | A conversation with your lawyer |
| Time to complete | 10 to 15 minutes | Varies by provider | {{SOURCED_TIME}} |
| Changes shown as redlines | Yes, accept or reject each one | Not checked | Depends on the firm |
| Lawyer access | Through Lawpath’s Legal Advice plan | Not checked | Yes |
| E-sign | Included | Not checked | Depends on the firm |
| Price | First document free (no credit card required) | Price varies by provider | {{SOURCED_COST}} |
“Not checked” means we haven’t verified that feature.
Lawpath members get unlimited lawyer and accountant consults on the Legal Advice plan.
Everything founders ask before they offer software as a service.
A SaaS agreement is a contract between a software provider and a customer for using cloud-based software on subscription, rather than installing or owning it.
It sets out the service levels, fees, support, data rights, and each party’s responsibilities, so both sides know what the service covers and what happens if something goes wrong.
It suits any business that provides software online for a subscription, from startups to established providers, and the customers who subscribe.
Lawpath’s template is written mainly from the provider’s side, setting the terms of access. If you’re the customer being asked to sign one, read it closely, because the terms are designed to protect the provider.
A SaaS agreement gives subscription access to software hosted in the cloud, so the customer never downloads or owns it and pays an ongoing fee to keep access.
A licence orEnd User Licence Agreement grants rights to install software on a device. If you offer a mobile app version, you may need both.
It sets the service levels the provider commits to, protects the provider’s intellectual property in the software, imposes confidentiality, and limits the provider’s liability where the law allows.
For the customer, clear service levels and support response times give something to hold the provider to if the service underperforms.
The template lets the provider change fees and add charges, which can create unexpected costs. In a standard form contract with a consumer or small business, a term letting one side vary prices or terms unilaterally can be challenged as unfair, and unfair terms are void with penalties.
The ACCC’s guidance is to let customers exit without penalty when terms change.
The template places the burden of complying with all applicable laws on the user, so check what you’re agreeing to carry.
As a customer, you may be responsible for how you use the software and the data you put into it. As a provider, that clause doesn’t remove your own obligations under privacy and consumer law.
The template gives the provider extensive rights to use and disclose aggregate data derived from the user’s data, which can raise privacy and confidentiality concerns.
Check who owns the data, what the provider can do with it, and whether it’s de-identified. Agree what happens to your data when the agreement ends, including return or deletion.
It should set out how personal information is handled, but it doesn’t replace your privacy obligations. The Privacy Act applies to businesses with turnover above $3 million and some others regardless of turnover, such as health service providers.
If data is hosted or accessed overseas, you stay accountable for it, so pair the agreement with aPrivacy Policy.
Not entirely. A SaaS agreement can include service levels and data terms, but many providers also use a separateService Level Agreement, a Privacy Policy, and sometimes a data processing agreement where sensitive data is involved.
Keep the documents consistent, and use the one that fits how detailed your commitments need to be.
Click-to-accept at sign-up or checkout can be binding if the terms are clearly presented and the customer has a genuine chance to read them before agreeing.
Keep a record of who accepted which version and when. Flag material changes to existing customers rather than relying on silent updates, which can be challenged.
It can limit liability, but not below the consumer guarantees under the Australian Consumer Law, which can’t be excluded and apply to many software services. A term trying to exclude them is void.
You can cap liability and exclude indirect loss where it’s fair and reasonable, so have the liability clause checked rather than assuming it holds.
Yes to both. The template is built to be tailored to your service, so you can adjust the maintenance, support, service level and setup provisions to fit what you offer.
It’s designed for use in every state and territory, because the key laws, such as privacy and consumer law, are federal. Tailor it before you rely on it.
The cost depends on whether you tailor the template yourself or have a lawyer draft or review it against your pricing, data and service commitments. Your first SaaS agreement is free on Lawpath, with unlimited documents from $45 a month on the Essentials plan.
For complex products, enterprise customers, sensitive data or overseas hosting, Lawpath lawyers can review or draft the agreement. Pricing may range depending on the complexity of your service, so it’s worth getting a quote based on your circumstances.