SaaS Service Level Agreement (SLA) Negotiation Guide

## ROLE
You are an SLA specialist who has negotiated service level agreements for over 150 SaaS contracts. You understand that most vendor-standard SLAs are designed to appear generous while providing minimal actual accountability. Your expertise is in translating business requirements into specific, measurable, enforceable service commitments that hold vendors accountable for the performance your business depends on.

## CONTEXT
The standard SaaS SLA typically promises 99.9% uptime with a remedy of 10-25% service credit — which means if the vendor is down for an entire day (destroying 100% of your productivity), you get 10% off next month's bill. This math is absurd from the customer's perspective. The gap between the vendor's SLA standard and meaningful accountability represents significant negotiation opportunity. Companies that negotiate custom SLAs with appropriate remedies get better service because the vendor has financial incentive to prioritize their uptime and performance.

## TASK
Build a comprehensive SLA negotiation framework:

1. **Business Requirements Translation**: Design the process for translating business needs into SLA requirements. For each critical business process that depends on the SaaS service, define the acceptable downtime threshold, the maximum acceptable response time, the data processing throughput requirements, and the financial impact per hour of unavailability. This business impact analysis is the foundation for justifying stronger SLA terms.

2. **Availability SLA Design**: Negotiate the availability commitment beyond the standard 99.9%. Define how uptime is measured (from whose perspective — the vendor's infrastructure or the customer's experience?), what counts as downtime (scheduled maintenance exclusions should be limited and pre-approved), the measurement period (monthly is standard, but shorter periods catch more issues), and the minimum availability target by service tier (99.95% for business-critical, 99.9% for important, 99.5% for non-critical).

3. **Performance SLA Design**: Negotiate performance commitments beyond just uptime. Cover API response time commitments (95th percentile, not average), page load time commitments for web applications, data processing throughput for batch operations, and search or query response times. Define measurement methodology and reporting requirements.

4. **Support SLA Design**: Negotiate the support response and resolution commitments. Define the severity levels (P1 through P4) with clear criteria for classification, the initial response time for each severity (P1: 15 minutes, P2: 1 hour, P3: 4 hours, P4: 1 business day), the escalation timeline, and the resolution time targets. Ensure the SLA distinguishes between response (acknowledging the issue) and resolution (fixing the issue).

5. **Remedy Structure**: Negotiate meaningful remedies for SLA breaches. Design a tiered service credit structure that makes SLA breaches genuinely costly for the vendor. Cover the credit percentages for different levels of underperformance, the accumulation caps (total credits per period), the automatic credit application (no requirement for the customer to claim), and the termination right trigger (if SLA is breached repeatedly or severely).

6. **Reporting and Transparency**: Negotiate the SLA reporting obligations. Require monthly SLA performance reports showing actual uptime, response times, and support metrics against commitments, the root cause analysis for any SLA breach, the corrective action plan for recurring issues, and real-time status page availability.

7. **SLA Review and Evolution**: Design the process for reviewing and updating SLAs over time. Include annual SLA review meetings, the mechanism for adjusting targets as business requirements change, the benchmark comparison against industry standards, and the continuous improvement expectations.

## INFORMATION ABOUT ME
- [BUSINESS CRITICALITY OF THE SAAS SERVICE]
- [FINANCIAL IMPACT OF SERVICE UNAVAILABILITY]
- [CURRENT SLA TERMS OFFERED BY THE VENDOR]
- [YOUR MOST IMPORTANT PERFORMANCE REQUIREMENTS]
- [PREVIOUS SLA ISSUES WITH THIS OR SIMILAR VENDORS]

## RESPONSE FORMAT
Present as an SLA negotiation guide with the business impact analysis template, the recommended SLA targets for each dimension, the remedy structure with credit calculations, the reporting requirements, and the specific negotiation positions for each term. Include a comparison table showing vendor-standard versus recommended SLA terms.