There's this moment that happens in almost every vendor relationship. You're reviewing the contract. You get to the SLA section and there it is: a detailed paragraph about what happens if uptime drops below 99.5 percent or response time slips past the threshold. Usually it's a credit. Sometimes it's a percentage of next month's bill. Occasionally someone got creative and put in something about service levels for the next quarter.

You sign it. The vendor signs it. Everyone's satisfied.

Then nothing ever happens with it again.

Not because the SLA is never breached. It's breached all the time. A server goes down. A ticket takes three weeks instead of two. An email integration stops working for six hours on a Thursday morning. You notice. You're frustrated. And then you either fix it yourself, work around it, or send an email asking what happened.

What you almost never do is cite the SLA clause and demand the penalty.

It's not that people don't know it exists. It's that the moment you'd actually need to invoke it is exactly the moment when the relationship is already strained enough that pulling out the contract feels nuclear. The vendor's going to argue about how the breach didn't technically qualify under their definition. You're going to be annoyed that you even have to make the case. And by the time anyone's talking about a credit, you've already lost faith in whether they're actually going to fix the underlying problem.

So the SLA becomes this document that lives in the folder with all the other executed agreements. It gets pulled out during renewal conversations maybe, mentioned in the context of "we've had some issues with uptime" but never in the formal, contractual way it was written. It's like agreeing to a referee before the game starts and then deciding halfway through that it's easier to just keep playing and let the disagreements happen organically.

The weird part is that this setup actually serves most people fine. The vendor understands that if they're constantly breaching the SLA and customers are complaining, they'll lose business. That's incentive enough. The customer understands that the vendor is trying most of the time and that things break sometimes and that getting into a contract dispute over a three-hour outage is worse than just waiting for the next maintenance window. So there's this informal code that forms instead: we'll try to be good, you'll try to be reasonable, and if something's really wrong we'll talk about it like adults instead of like lawyers.

The SLA exists more as window dressing now. It's there because enterprise deals expect them. It's there because someone has to write something down about what good looks like. It's there because in the one percent of cases where a vendor is actually terrible and a customer actually wants out, having signed language makes that process cleaner.

But the actual enforcement mechanism? That's theater. Both sides know it. The penalties are never meant to be collected. They're meant to be so unlikely that you can almost forget they're there.

Which raises a practical question: what would actually change if we all just stopped pretending? If SLAs came with some kind of honest subtext like "we expect this to work most of the time and you should too." Probably not much. You'd lose the security blanket of having something signed, but you'd gain clarity about what the relationship actually is instead of what we're all agreeing to believe it is.

Maybe that's the real value of these things anyway. Not enforcement. Just honesty.