← All articles

How to build your Service Level Agreements

Every SaaS customer asks for service commitments. Which ones to grant, which ones to refuse, and how to write an SLA that protects both sides.

Every customer buying a SaaS solution asks for service commitments when signing the contract. This is the norm. It is healthy both for the customer and for the provider, as it sets a framework for decisions in case of problems.

These commitments are written directly in the contract, usually in an appendix called Service Level Agreements (SLAs). Those are critical and protect both parties. They should not be neglected. But how should you build, write and use an SLA? Let's dive into this topic.

Definition of a Service Level Agreement

An SLA is a legal document that defines the services you will deliver to your customers. It includes the responsiveness that can be expected to meet client expectations, and how you will measure performance.

In other words, an SLA is a roadmap to success: it sets expectations for performance. This level of clarity helps to improve communication and trust between two parties. It also helps avoid misunderstandings and build a productive business relationship, which is key to Customer Success.

Key components of a service level agreement are:

  • Service description and scope of work
  • Performance metrics and standards
  • Service level objectives (SLOs)
  • Responsibilities of each party
  • Review and update procedures

In this article, we'll see the different commitments, mandatory or optional, to include in your SLA.

Warning: use only standard SLAs

This is the main mistake to avoid: never customize SLAs for a client. Propose only generic and standardized SLAs. It's easy to say, harder to do, as clients always ask for adjustments, but it's essential if you want to scale.

Managing a multitude of specific contracts will quickly become impossible for your Support, Success, Product, and Infrastructure teams. SLAs are the last piece of your contract on which to make adjustments for your customers.

Project commitments

This part is optional, as it only comes if your product needs implementation, and it's the only one on which you can accept client specificities if necessary. The project phase is not recurring, so it's more manageable for the project manager to handle specific requests.

I would advise to avoid any commitments on the project part, especially if you charge your subscription at the customer go-live.

Things are slightly different if you charge the subscription to the customer at contract signature: the customer will ask for guarantees to avoid paying additional subscription fees because of project delays. In this case, take the time to clearly define the project scope with your customer before signing the contract, estimate the workload and especially the duration of the project. Once the go-live date is set and shared with the client, with some margin, you can estimate penalties related to project delays: take a penalty amount corresponding to the cost of the subscription the customer pays, to compensate for this delay.

Finally, don't forget to write in the contract that these delay penalties will not apply if the delay is due to the customer and not your teams.

One last thing: project commitments will impose on your teams a very rigorous follow-up at each project step that should not be neglected. This will add complexity and may increase your workload. It's not always easy to prove who is responsible for a project delay.

Platform availability commitment

This one cannot be negotiated: a SaaS platform is by definition shared and mutualized, or multi-tenant. Proposing a 99% availability rate to client A and 99.5% to client B makes no sense. On the market, a 99% availability commitment is quite low; 99.5% is in the standards.

Keep in mind that, by offering a 99.5% availability rate, you're providing a minimum rate, but the reality will of course be higher. SaaS solutions often aim at reaching at least a 99.99% availability rate.

Do not forget to exclude scheduled maintenance periods from this availability rate calculation. The periods you exclude should only concern unplanned downtimes. Of course, your customers may ask to limit the duration of scheduled maintenance.

Here is an example of availability rate calculation:

((Total time of the period − Unavailability time on the period − Scheduled maintenance time on the period) / (Total time of the period − Scheduled maintenance time on the period)) × 100

Also, make sure to exclude all causes of downtime that are external to your responsibility, such as network downtimes or downtimes caused by the client infrastructure.

Support commitments

Support commitments usually concern response times. Depending on the criticality of the incident, your support team will commit to sending a first response to the customer in less than a given number of hours. Avoid considering an automatic response from your support tool as an official first response to the customer. A message saying the ticket has been received and an agent will respond as soon as possible will tend to irritate the customer more than satisfy him.

A second commitment can be made on updating tickets. Once again, depending on the criticality of the ticket, you can offer your customers an update every few hours regarding the resolution of their ticket.

Be sure to anticipate all the impacts related to response time commitments: the easiest is to take commitments only during the support team's business hours. However, some customers may ask for replies outside of your business hours, for the most critical tickets for example, or when you start selling your solution internationally. What about a ticket opened by a user with a 9-hour time difference from your support function? Implementing 24/7 support can be very costly and you will need to include these costs in your subscription model.

Product commitments

This one is very sensitive. Almost all of your customers will ask for commitments on product incident resolution times. Yet, this makes no sense. It is impossible to know how long resolving an incident will take before doing a proper diagnosis. Try asking your mechanic how long it will take to fix your car without knowing the cause of the breakdown.

Never take any commitment on the resolution of a bug or an outage. If it is a major bug affecting a critical function of your application, include this in the downtime calculation of your service and manage it through your product availability rate.

Take no other commitment than doing your best effort and working around the clock on the resolution of the incident. You can also regularly update the customer about the progress of the resolution.

Finally, never take any contractual commitments on the development of a new feature in the product. You never know how your roadmap will evolve and what product requirements you will have. You will just create frustration and lose your customer.

Building an efficient SLA: three last steps

  1. Be careful with penalties. While it is essential to have a Service Level Agreement policy towards your customers, it is also important to protect yourself. You will set financial penalties in your SLAs. Make sure to cap them to avoid putting yourself at risk. Set a maximum percentage of the ARR paid by the customer, for example.
  2. Crisis management should be included in the contract, not in the SLAs. Some customers may ask you to include crisis management in your SLAs. While a crisis can lead to penalties based on your availability rate calculations, it is better to include the details of the process you implement to face a crisis directly in the body of your contract. You can detail the crisis identification process, the communication, the stakeholders on your side and on your customer's side, and the governance. It's very important to mention it, but not in your SLAs.
  3. Ask for help if you have any question. Writing or rewriting an SLA is one of those exercises where an outside, experienced view saves a lot of time and avoids commitments you will regret.

← All articles

Want to chat?

Reach out on LinkedIn or by email to talk about scaling your Customer Success.

LinkedIn flerays.pro@gmail.com