SaaS Tips by Sapna | Tip No. 5 – Ancillary Services

In addition to the primary services, as a SaaS supplier, you are responsible for hosting the software and the ancillary obligations that come with it. These include securing and safeguarding your customer’s information, backing up the data and providing disaster recovery and business continuity to ensure your customers continued access to the software application and their data. Keep these ancillary obligations in mind when developing your SaaS and the supporting documentation and contracts.

What ancillary obligations does your SaaS supplier provide?

In the traditional on-prem model, the software is installed on a server you controls. While you may be dependent on the software provider to provide upgrades and fixes to the software, you are in control of when the software is available and how the data is safeguarded.

By moving to the SaaS model, you are giving up control of your application in return for reduced infrastructure and management costs.

However, you still need to be able to access your software and be sure that the data you provide is adequately protected and backed up. Here’s where the ancillary obligations come in. While these are not the main services provided by the supplier, these are necessary to ensure you have a compliant, workable, secure SaaS application.

When entering into the SaaS arrangement, consider how the supplier provides the following:

  • Security controls and safeguards for the information you provide and process through the application
  • Backups of the data with corresponding restoration services
  • Disaster recovery and business continuity with adequate RPOs and RTOs.

Depending on the type of information processed and the criticality of the SaaS to your business, your contract will address these issues to varying degrees.

To learn more and join in the discussion, check out my LinkedIn post.

About the Author

More Articles

About the Author

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Articles

SaaS Tips by Sapna | Tip No. 14 – Subcontractors

Your SaaS supplier will almost always subcontract part of the services to a third party so the SaaS

SaaS Tips by Sapna | Tip No. 13 – Pilots

There are similarities and differences between a pilot and a proof of concept in a SaaS agreement.

SaaS Tips by Sapna | Tip No. 12 – Proof of Concept

Before engaging a new SaaS system into your company, you will almost always start with a proof of

SaaS Tips by Sapna | Tip No. 11 – Open-Source and Third-Party Software

If the SaaS system includes open-source software, your SaaS contract should contain the appropriate provisions to ensure the

Most Recent

The Contracts Queen’s Guide to Creating a Practical Contract Playbook

Contract playbooks can be used to improve relationships, empower stakeholders, speed up the contracting process, and save time

Acceptance Terms in SaaS Agreements

Acceptance is an important commercial concept to understand as it pertains to implementation services in SaaS agreements.

Nine Financial Terms Every SaaS Negotiator Should Know

By having a strong grasp of finance aspects of SaaS agreements, you are helping the business win new

Elevating Your GC Brand: 3 Contract-Centric Strategies

A strong GC brand doesn't just bring more influence, compensation, and respect; it also opens doors to the

Subscribe to Contract Nerds weekly newsletter

* indicates required
Professional Role
Generic filters