SLA Definition Template for Product Managers

Start with 99.9% (43 minutes of allowed downtime per month). This is achievable for most well-architected SaaS products and meets the expectations of mid-market enterprise buyers. Move to 99.95% when your infrastructure maturity supports it and your largest customers require it. 99.99% is rarely necessary outside of financial services and healthcare, and it requires significant investment in redundancy. Use the [RICE calculator](/tools/rice-calculator) to evaluate the ROI of infrastructure investments needed to reach higher availability targets.

Your SLA covers what you can control. If a third-party service (AWS, Stripe, Twilio) causes an outage, you have two options: exclude third-party outages from your SLA (simpler, but customers may object), or include them but build redundancy so a single third-party failure does not take you down. The second approach is more expensive but creates a stronger competitive position. Document your third-party dependencies and their SLAs transparently.

Yes. Enterprise customers paying $50K+/year expect better uptime, faster response times, and dedicated support. Tiered SLAs also create a natural upsell path: "Upgrade to Enterprise for 99.95% uptime and 15-minute incident response." The [custom pricing template](/templates) covers how to structure enterprise pricing with SLA tiers as a pricing lever.

First, communicate proactively. Do not wait for the customer to notice. Second, issue the credit promptly (within the next billing cycle). Third, conduct a post-incident review and share the root cause analysis with affected customers. Fourth, implement improvements and communicate what changed. How you handle a breach matters more than the breach itself. The [stakeholder management guide](/stakeholder-guide) covers crisis communication techniques that apply directly to SLA breaches.

Review SLA compliance monthly (internal) and share reports with enterprise customers quarterly. Review SLA targets annually. As your product scales and your infrastructure matures, you should be able to tighten SLAs over time. If you consistently exceed your SLA by a wide margin, consider tightening it and using the improved SLA as a competitive differentiator. ---