The Distinction Between Warranty and SLAs
Did you ever wonder what the difference is between a Warranty and an SLA?
Think of the Lemon Law for new car sales when you think about the warranty. If a product does not work; you have a chance (generally several chances) to get it resolved within a defined period of time. If the problem is still not resolved, you have an opportunity to get your money back. That is a heck of a lot different from saying that if the product doesn’t work I will respond in 2 hours and if it’s not working within x hours you will get a 5% credit on your next monthly maintenance invoice, that is an SLA. Since most software licenses are moving to a SaaS model, a careful review of the contract language is required to avoid having just an SLA rather than a warranty followed by an SLA (which is my recommended approach).
I encourage you to review your last software license to ensure it includes both a warranty and an SLA. This will assure you: 1.) the product works when you first install it; and 2.) it also includes an ongoing SLA methodology for curing potential defects that may be found months, or even years later. When a license proactively includes both a warranty and an SLA, it sends a positive message about the quality of the product, and instills a level of consumer confidence in the developer. This approach increases sales opportunities and establishes loyal customers who drive repeat business.