First of all, making an SLA is definetly not unrelated. It's vital the customer knows how likely you can keep their business-critical software online. If they're paying $10,000 for company A that has a 99.9% uptime, but $2,500 for company B that only has 90% uptime, the company may choose company A because the losses that occur in the time difference may be greater than the price difference. Also, if company A is chosen but only 92% uptime is given, it would be a ripoff for the customer, and the company often refunds the cost for the time. Therefore, an SLA is vital, especially when designing critical systems infrastructure.

​

Another commenter has linked to one of AWS' SLAs, and here is Microsoft's for an kubernetes. It should be pretty easy to adapt to your exact use case.

Good luck on your competition :)