Software Licences: What Small Businesses Need To Know

Whether you build software, resell it, or simply use tools to run your operations, software licences sit at the heart of your business. They decide who can use the software, how, for how long, and on what terms.

Get them wrong, and you risk compliance headaches, unexpected costs, or disputes with customers and suppliers. Get them right, and you’ll protect your IP, keep your data safe, and scale with confidence.

In this guide, we break down software licences in straightforward terms, highlight UK legal requirements, and share practical steps to stay compliant from day one.

What Is A Software Licence And Why It Matters For Your Business?

A software licence is a legal permission to use software under certain conditions. It doesn’t transfer ownership of the code - it sets out the terms under which you (or your customers) can use it. For small businesses, licences appear in three common scenarios:

• You license software in to run your business (for example, your accounting platform or CRM).
• You license software out to customers (for example, your app, platform, or embedded tooling).
• You use third-party components (including open source) inside your own product.

Clear licensing keeps expectations aligned, controls costs, and reduces legal risk. If you’re supplying software, a well-drafted Software Licence Agreement also signals professionalism and builds trust with customers.

Under UK law, software is protected primarily by copyright (Copyright, Designs and Patents Act 1988). The default position is “all rights reserved” - meaning no one can use, copy, adapt, or distribute your code without permission. Your licence provides that permission on your terms.

Which Type Of Software Licence Do You Need?

The “right” licence depends on how your business will use or supply software. Here are the main options you’ll encounter and how they differ.

Perpetual Licence

A one-off fee in exchange for the right to use a specific version indefinitely. Often paired with optional annual support/maintenance. Useful for on-premises deployments, but can be costlier to support and doesn’t naturally cover updates or new features unless specified.

Subscription Or SaaS Licence

Recurring payments (monthly/annual) for hosted access to software. This model is flexible, easier to budget for, and allows you to bundle support, updates, and uptime commitments. If you’re providing cloud software, your terms will usually be set out in your SaaS Terms.

User-Based, Device-Based, Or Capacity-Based

Licences can be limited by named users, concurrent users, devices, cores, API calls, or other usage metrics. Choose a metric that aligns with how value is delivered. Be clear on how usage is measured and audited to avoid disputes.

Site Or Enterprise Licence

A broader grant allowing a defined location or an entire organisation to use the software. Pricing is typically tiered by headcount or revenue. These can simplify administration for larger customers, but they require careful drafting around scope and exclusions.

Trial, Beta, And Freemium

Limited-term or feature-limited access at no or low cost. If you offer trials, make sure the licence restricts production use and addresses feedback, confidentiality, and any data retention after the trial ends.

Open Source Licences

Open source components are licensed under public terms (for example, MIT, Apache 2.0, GPL). Some are permissive (few obligations), while others are “copyleft” (they may require you to share derivative code on the same terms). If you embed open source into your product, you must comply with the relevant licence obligations (attribution, notices, disclosure of modifications, and - in some cases - source code availability).

If you’re commercialising a product that includes third-party or open source code, it’s smart to pair your commercial terms with a robust Software Licence Agreement so your rights and obligations are crystal clear.

Key Clauses To Include In Your Software Licence Agreement

Licences vary by business model, but certain clauses show up time and again. Getting these right reduces risk and helps prevent disputes.

1) Scope Of Licence

• Type: non-exclusive/non-transferable vs exclusive; sub-licensable or not.
• Permitted uses: internal business use only? Production vs development? Territory limitations?
• Usage caps: users, devices, API calls, storage, transactions, or other metrics.

2) Restrictions

• No reverse engineering, decompiling, or altering code (save as allowed by law).
• Limits on unauthorised sharing, renting, or reselling.
• Security obligations (for example, no credential sharing; reasonable steps to prevent misuse).

3) Intellectual Property

• Ownership: the licensor retains all IP in the software.
• Customisations: clarify who owns bug fixes, configurations, integrations, or new features.
• Background vs foreground IP: define each clearly.

If a customer funds bespoke development, you’ll need a separate Software Development Agreement and potentially an IP Assignment where appropriate.

4) Data Protection And Privacy

• If you process personal data for customers, UK GDPR and the Data Protection Act 2018 require a written data processing contract. Include a Data Processing Agreement (or a detailed schedule) covering purpose, security, sub-processors, international transfers, and deletion.
• If you collect personal data on your own account (for example, users of your platform), publish a compliant Privacy Policy explaining how you handle that data.

5) Service Levels And Support

• Uptime commitments and exclusions (maintenance windows, force majeure).
• Response and resolution targets by severity level.
• Support hours and channels.
• Service credits for breaches. You can house these in a standalone Service Level Agreement or in your main terms.

6) Fees, Billing, And Changes

• How and when fees are charged; renewal terms; indexation or price review mechanisms.
• Overage charging for exceeded usage limits.
• Payment terms, late fees, and consequences for non-payment (for example, suspension).

7) Warranties, Liability, And Indemnities

• Warranties: virus-free on delivery; material conformity with documentation; professional services provided with reasonable skill and care.
• Exclusions: clarify that you don’t warrant uninterrupted or error-free operation.
• Liability caps: reasonable limits under the Unfair Contract Terms Act 1977 for B2B contracts; carve-outs for death/personal injury, fraud, deliberate default, and IP infringement indemnity.
• IP indemnity: if a third party claims the software infringes their rights, set out your remedies (for example, modify, replace, or refund) and customer obligations to notify and cooperate.

8) Audits And Compliance

• Reasonable audit rights to verify usage, with notice and confidentiality safeguards.
• Underpayment consequences and back-pay calculations.

9) Term, Renewal, And Termination

• Initial term and auto-renewal mechanics (be clear on notice periods).
• Termination for cause (material breach, insolvency) and for convenience (if offered).
• Exit assistance: data export, deletion, and ongoing access to backups or logs.

10) Security And Acceptable Use

• Security standards (for example, encryption in transit/at rest, vulnerability management, incident response).
• Prohibited activities (for example, uploading malware, spamming, scraping beyond agreed APIs).

How UK Law Affects Software Licences

Licences don’t exist in a vacuum - they sit alongside general UK laws that you’ll need to consider.

Copyright Law

Under the Copyright, Designs and Patents Act 1988, software is protected as a literary work. Your licence should make it clear that you retain ownership and are granting limited rights to use. If you use third-party libraries, ensure your licence terms don’t conflict with those upstream obligations.

Data Protection And Privacy

If your software collects or processes personal data, UK GDPR and the Data Protection Act 2018 apply. You must have a lawful basis for processing, provide transparent notices, and implement appropriate security. Where you act as a processor for a customer, you need a compliant Data Processing Agreement that sets out mandatory controller–processor terms.

Consumer Law (If You Sell To Consumers)

If you license software to consumers (B2C), the Consumer Rights Act 2015 implies certain rights in digital content - it must be of satisfactory quality, fit for purpose, and as described. Consumers may be entitled to repair, replacement, or refund if those standards aren’t met. Your terms can’t contract out of core statutory rights.

Contract Law And Unfair Terms

In B2B contracts, the Unfair Contract Terms Act 1977 and common law controls apply to exclusions and limitations of liability. Clauses must be reasonable in all the circumstances (including bargaining positions and availability of insurance). Clear, balanced drafting is key.

Computer Misuse And Export Controls

It’s good practice for licences to prohibit unlawful use, including misuse offences (Computer Misuse Act 1990). If you provide encryption or make your software available internationally, consider whether export control rules apply and restrict certain territories accordingly.

VAT And Invoicing

Licensing software is typically a supply of services for VAT. Make sure your invoices are compliant and that pricing terms clarify whether VAT is included or added.

Managing Open Source And Third-Party Components

Most modern software stacks rely on open source. That’s fine - as long as you manage your obligations. A few practical tips:

• Keep a software bill of materials (SBOM) listing all third-party packages and versions.
• Record each licence type (for example, MIT, Apache 2.0, GPL) and the obligations it carries.
• Include attribution and licence notices where required (for example, in your documentation or “About” section).
• Be cautious with strong copyleft licences (for example, GPL) in proprietary products - get legal advice if you’re unsure how your distribution model interacts with copyleft.
• Review updates promptly to patch security vulnerabilities and maintain compliance.

Your outbound terms should also clarify that your product may contain third-party components and that you’ll comply with any attribution obligations - without giving away more rights than necessary.

Practical Steps To Stay Compliant And Avoid Audit Surprises

Small businesses often stumble on the practical side of licence compliance. These steps help you stay in control.

1) Centralise Purchasing And Approval

Pick a single owner (or small team) to approve new software purchases and keep records of licence keys, user counts, and renewal dates. This prevents shadow IT and over-subscription.

2) Track Usage

Use device management tools and SSO to monitor who has access, revoke leavers promptly, and map real usage against your licence entitlements.

3) Set Clear Policies

Adopt an acceptable use and onboarding/offboarding process. If your team uses personal devices, make sure your BYOD and access controls enforce your licence terms.

4) Prepare For Audits

Many licences allow reasonable audits. Keep accurate logs, store purchase records, and respond within the timeframes in your contract. If an audit is triggered, engage your legal team early.

5) Plan Renewals And Price Changes

Calendar renewal dates and notice periods, especially where terms auto-renew or allow price adjustments. Build in time to re-negotiate terms or switch vendors if needed.

6) Protect Your Commercial Interests

If you supply software, decide how you’ll handle common requests (for example, additional indemnities, security questionnaires, penetration tests, or escrow). Standardising your responses saves time and reduces risk.

Essential Documents When You Sell Or Buy Software

Depending on your role, these documents are commonly needed to protect your business.

If You’re Supplying Software

• Software Licence Agreement: core terms for on-premise or downloadable software.
• SaaS Terms: your hosted/subscription terms, often paired with an order form.
• Service Level Agreement: uptime, support, and service credits.
• Data Processing Agreement: mandatory controller–processor terms under UK GDPR.
• Privacy Policy: how you collect, use, and store personal data.
• Software Development Agreement and IP Assignment: for bespoke builds or funded features.

If You’re Buying Software

• Master terms or end user terms: review the licence scope, restrictions, and termination rights.
• Security and data protection schedules: ensure security controls and data handling match your risk profile.
• Implementation or SOWs: capture deliverables, timelines, acceptance testing, and milestones.
• Commercial protections: liability caps, indemnities, audit procedures, and exit assistance obligations.

As a rule of thumb, avoid generic templates or DIY drafting - these documents work best when tailored to your product, data flows, and risk tolerance. A short conversation upfront can prevent bigger costs later.

Key Takeaways

• Software licences control how software is used - for your business and your customers. Choose a model (perpetual, subscription/SaaS, usage-based, or enterprise) that mirrors how value is delivered.
• Well-drafted terms should cover scope, restrictions, IP ownership, data protection, service levels, fees, and fair risk allocation (warranties, liability caps, and indemnities).
• UK laws sit around your licences: copyright protection for code, UK GDPR for personal data, Consumer Rights Act 2015 for B2C digital content, and reasonableness tests for exclusions in B2B contracts.
• Open source is powerful, but manage it with an SBOM, correct attribution, and awareness of copyleft obligations - especially in proprietary products.
• Operational compliance matters: centralise purchasing, track usage, set policies, and prepare for audits to avoid surprises at renewal or during vendor checks.
• If you’re supplying software, anchor your legals with a Software Licence Agreement or SaaS Terms, supported by a Data Processing Agreement, Service Level Agreement, and a clear Privacy Policy.

If you’d like help putting robust software licences in place - or you want a quick review of your current terms - you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.