Contract terms for software-as-a-service suppliers

A software-as-a-service contract normally grants access to a service rather than ownership of the software. Review the features, users, usage limits and support included in the purchased plan. Check the order form against online terms and any processing schedule before relying on a sales demonstration.

Prioritise business continuity: data export, service suspension, backups, renewal and migration assistance. Review rights in customer content and any supplier use for analytics or AI training. Security and transfer arrangements should be assessed with the actual account settings and subprocessors.

Define the service the business is buying

Collect the order form, service description, online terms and any incorporated policies. Identify the exact plan, user count, usage limits and support level. A demonstration may show features excluded from the purchased tier. Record which document takes priority if descriptions conflict, and save the version accepted. A changing website link is difficult evidence of the bargain if a dispute arises after the supplier has updated its standard conditions.

Separate implementation work from continuing access. Clarify migration, configuration, training and acceptance arrangements, including who supplies accurate source data. If the service is essential to daily operations, identify the point at which the business will depend on it and the fallback if launch fails. Do not cancel the old system merely because the new provider has issued an account invitation.

Examine availability, support and remedies together

Review how availability is measured and which exclusions apply. Scheduled maintenance, customer configuration and third-party networks may affect the calculation. Check how an incident is raised, when support responds and whether a service credit requires a claim within a short period. A percentage in a sales proposal is less useful without a workable measurement and response process.

Consider the effect of suspension for disputed invoices, security concerns or alleged misuse. Ask whether the customer receives notice and an opportunity to address the issue where appropriate. Protect access to essential records and an export route where possible. Do not assume a compensation clause will solve the practical harm if the business loses its booking calendar during its busiest week.

Review data and intellectual property rights precisely

Identify ownership and permitted use of customer content, supplier software and implementation outputs separately. The IPO guidance provides a starting point for using another party's intellectual property. ^[1] A licence to access a platform does not automatically give ownership of custom configuration or a right to run the software independently after termination. Check third-party components and restrictions relevant to the intended business use.

Assess personal data roles and the processing agreement using the actual service configuration. ^[2] Pay attention to optional analytics or AI training, support access and subprocessors. Use Data processing contracts with suppliers for processing terms and Data protection when using cloud software for the technical procurement review. Customer confidentiality commitments may impose requirements beyond the provider's default data protection schedule, particularly for professional or commercially sensitive records.

Model renewal, pricing and exit before commitment

Calculate the cost at current use and plausible growth. Include additional users, storage, implementation, support and export charges. Review renewal timing and how notice must be given. If the supplier can change prices or terms, understand the process and the customer's available choices. A low introductory price can be misleading as an internal budget assumption if minimum commitments and expansion charges are ignored.

Run an exit scenario using representative sample data. Check export format, completeness, timing and any assistance required from the supplier. Confirm what happens to attachments and audit history, not only the main contact table. Agree retrieval and deletion arrangements before the account closes, and identify records the customer must retain independently for its own obligations.

For Website terms and cookie review, provide the contract pack, proposed use and the operational consequences of downtime or migration. Prioritise changes according to the business's actual dependence rather than negotiating every clause equally. Record accepted limitations and the measures chosen to address them. Keep the decision with the contract so a future manager knows, for example, why the company maintains an independent export or a second support contact.

Model a price change against actual usage

Take the current number of users, anticipated storage and any transaction limits, then calculate the cost of ordinary growth under the proposed terms. Include support tiers, data export charges and integrations that become essential once the service is embedded. A low introductory licence price can conceal a very different operating budget.

Ask what happens if the business disagrees with a renewal increase but cannot migrate before the notice deadline. Compare the termination and export timetable with a realistic migration plan. Keep the commercial model with the contract review so the decision maker can see both the wording and its likely financial effect. This helps distinguish an acceptable trade-off from an overlooked dependency.

Illustrative scenario

A company relies on a SaaS platform for customer bookings. Its chosen plan allows exports only in a limited format, while the contract gives a short retrieval period after termination. The company tests the export and plans migration before signing, then negotiates or accepts the limitation with a clear understanding of the cost.

Preparation checklist

• Confirm plan features, limits and support commitments.
• Review data use, processing roles and access locations.
• Test export and migration requirements.
• Check renewal, price changes, suspension and termination provisions.