Customer-Facing vs Internal SLOs: When to Use Each

Customer SLOs are legal-adjacent; internal SLOs are diagnostic. Pick on audience; both have a place.

Customer-facing SLOs

Customer-facing SLOs are commitments. They live on pricing pages, in contracts, and in legal language; their primary job is being defensible.

• Outcome-shaped. 'Login works', 'checkout completes'; expressed in user-visible verbs, not internal metrics.
• Committed publicly. Marketing pages, MSAs, status page; once written, the number is hard to retract.
• Audience. External users, legal, sales; the SLO survives every conversation those audiences have.
• Conservatism. Set lower than internal targets; the buffer is what survives a bad month without breach.

Internal SLOs

• Internal: process (‘auth-svc latency p99’); used by engineering teams.
• Audience: own team; platform team; on-call.

Cascade pattern

Customer SLOs depend on chains of internal SLOs. The math compounds; the right cascade design makes internal breaches predict customer breaches.

• Compounding math. Three internal SLOs at 99.95% chain to a customer SLO at roughly 99.85%; the multiplication is unforgiving.
• Predictive value. Internal-tier breaches almost always precede customer-tier breaches; the cascade is the early-warning system.
• Diagnostic depth. When customer SLO drops, the internal cascade tells you which service is responsible.
• Tighter inside. Internal SLOs must be tighter than the customer-facing target or the math will not work.

Ownership

Customer-facing and internal SLOs have different owners and different decision rights. Confusing the two is how SLO programmes lose credibility.

• Customer SLO. Joint ownership: product owns the user-facing promise, engineering owns delivery.
• Internal SLO. Owned by the team running the service; they set, track, and tune their own targets.
• Decision rights. Engineering cannot unilaterally relax a customer SLO; teams can adjust their own internal SLOs at their discretion.
• Reporting line. Customer SLO attainment goes to product reviews; internal SLO attainment goes to engineering retros.

Antipatterns

• Customer SLO without internal SLO support. Cannot diagnose breaches.
• Internal SLO never rolled up to customer view. Loses business context.
• One SLO type only. Missing half the picture.

What to do this week

Three moves. (1) Apply the pattern to your most-impactful service. (2) Measure adherence for 30 days. (3) Rewrite the policy or the SLO if the gap is durable.