Tiered Customer Experience SLOs

Premium customers get tighter SLOs.

Tiered SLO model

Tiered SLOs encode the commercial bargain in operational policy: higher-paying customers get measurably tighter availability and latency commitments, backed by capacity.

• Premium. Tighter SLOs, dedicated capacity, faster on-call response, and explicit contractual numbers in MSAs.
• Standard. Default SLOs that match what published status pages and product docs promise the wider market.
• Basic / free. Best-effort with no contractual recourse beyond service credits or product feature gating.
• Differentiation. Tiered reliability is a sales lever; competitors who ship one SLO for everyone leave the lane open.

How to structure tiers

Three tiers is the sweet spot. Anything finer creates operational sprawl that on-call cannot remember at 3am.

• Tier count. Premium / standard / free is enough; more tiers fragment runbooks and dilute the contract.
• Availability targets. 99.95% / 99.9% / 99% availability per tier is the typical industry split.
• Latency targets. Tighter p99 budgets (e.g. 200ms vs 400ms vs 800ms) per tier carry the same logic.
• Capacity policy. Dedicated capacity for premium, shared pools for standard, oversubscribed for free.

Operating tiered SLOs

Tiered SLOs only matter if monitoring, paging, and reporting all flow per-tier rather than aggregated.

• Per-tier alerting. Premium SLO breach pages immediately; standard goes through normal triage; free is dashboard-only.
• Per-tier escalation. Premium tier may have a dedicated escalation rotation or a named TAM in the chain.
• Per-tier dashboards. SLI panels split by tier so trend regressions are visible before contract review.
• Per-tier customer reporting. Each premium account sees its own tier's monthly attainment in their portal.

Engineering commitment

A premium SLO without backing capacity is a broken promise. Engineering investment must match the contract or churn follows the first incident.

• Headroom budget. Premium tier carries higher utilisation headroom and queue-depth budgets than standard.
• Redundancy. Premium may run on separate clusters, dedicated regions, or pinned routing.
• Operational priority. Premium incidents preempt standard work in the on-call queue, codified in the runbook.
• Annual review. Tier attainment versus pricing reviewed yearly; adjust price or investment to keep margin honest.

Marketing tiered reliability

Tiered SLOs only convert into revenue when sales and marketing surface the numbers concretely on pricing pages, in MSAs, and in renewal conversations.

• Public commitments. Concrete per-tier numbers on pricing pages and in contract language, not vague phrases.
• Attainment reports. Quarterly or monthly delivery reports per tier; premium customers expect them.
• Sales enablement. Reps quote real attainment ('11 of 12 months in premium tier last year'), not aspirations.
• Renewal lever. Strong attainment becomes a renewal asset; weak attainment becomes a credit conversation, never a surprise.