- A licence agreement gives you permission to use software under specific conditions.
- - Vague scope of use that leaves it unclear whether growing your team or adding a location breaches the licence - Unlimited or one-sided liability exposure, especially if the software…
Whether you're buying an off-the-shelf accounting package, licensing an industry-specific platform, or commissioning custom software, the contract you sign rarely transfers ownership of anything. It grants a software licence agreement that defines exactly what you're allowed to do, and for how long. Businesses that skim past these terms often find out the hard way what wasn't included.
This article walks through the terms that actually matter, in roughly the order they tend to cause problems.
What a Software Licence Agreement Actually Grants
A licence agreement gives you permission to use software under specific conditions. It does not, on its own, transfer copyright or ownership of the underlying code to you — even for custom-built software — unless the agreement explicitly says so. This distinction matters most when the relationship with the vendor or developer ends: without an ownership transfer or a durable licence, your right to keep using the software may be far more limited than you assumed.
Key Terms to Read Before You Sign
| Term | Why It Matters |
|---|---|
| Scope of use | Defines who can use the software, how many users or devices, and for what purpose — exceeding this can itself be a breach |
| Term and renewal | How long the licence lasts, whether it renews automatically, and what happens at expiry |
| Fees and escalation | Not just the current price, but whether and how the vendor can raise it over time |
| Ownership and IP | Confirms who owns the underlying code — a licence is not the same as ownership |
| Warranties and disclaimers | What the vendor promises about the software's performance, and what it explicitly disclaims |
| Limitation of liability | Caps on what you can recover if the software fails and causes you a loss |
| Indemnification | Who covers the cost if a third party claims the software infringes their IP |
| Support and maintenance | What's included, what costs extra, and how quickly issues get addressed |
| Termination rights | What triggers termination, and what happens to your data and access afterward |
| Assignment / change of control | Whether the licence survives if either business is sold or restructured |
Red Flags to Watch For
- Vague scope of use that leaves it unclear whether growing your team or adding a location breaches the licence
- Unlimited or one-sided liability exposure, especially if the software touches customer data or business-critical operations
- No clear data export or transition process if you need to leave the platform
- Automatic renewal with a short cancellation window you're likely to miss
- Silence on IP ownership for custom-developed software — this should never be left implied
- A "we can change these terms at any time" clause with no meaningful notice to you
Are Clickwrap and Browsewrap Terms Actually Enforceable?
Many software agreements today are accepted by clicking "I agree" rather than signing a physical document. These "clickwrap" agreements are generally enforceable in Ontario, provided the terms were reasonably presented and the user had a genuine opportunity to review them before accepting. Enforceability tends to be weaker for "browsewrap" terms that are merely linked somewhere on a page without requiring active acceptance. If a software vendor's terms matter to your business, don't assume a click made them binding without at least glancing at what you agreed to.
Negotiating as a Small Business
Small businesses often assume vendor terms are non-negotiable, especially with larger software providers, and sometimes that's true for standard consumer-facing terms. But for anything involving meaningful contract value, custom development, or business-critical software, it's worth asking about:
- Caps on price increases
- A trial or pilot period before full commitment
- Data export rights that are usable in practice, not just in theory
- A liability cap that's proportionate to what you're actually paying
Frequently asked questions
If we pay for custom-built software, don't we own it?
Not automatically. Unless the agreement explicitly assigns ownership of the code to you, the developer generally retains copyright, and you hold a licence to use it, even though you paid for the development work.
What happens to our data if we cancel a software subscription?
This depends entirely on what the agreement says. Some vendors provide a defined export window; others don't guarantee anything beyond immediate loss of access. This term is worth checking before you sign, not after you need it.
Can a vendor change the licence terms after we've already signed?
Many agreements include a clause allowing the vendor to update terms, sometimes with limited notice. Whether an update is enforceable against you can depend on how the clause is worded and how the change was communicated.
Do we need a lawyer to review a standard subscription agreement?
For low-cost, low-risk software, probably not. For anything business-critical, holding sensitive data, or involving meaningful annual spend, a quick legal review before signing is usually inexpensive relative to the risk of discovering a bad term later.
This is a corporate question
Start a file online — flat, published fees, reviewed by a licensed Ontario lawyer before a dollar is owed.