The Outage
A critical SaaS app went down for nearly two full days. Work stopped, the team built workarounds in spreadsheets, someone asked for updates every few hours. Outages happen. Every B2B company that runs long enough will have a bad day.
What didn't happen: the vendor never offered a service-level credit. Not during the outage, not after, not in the postmortem email. That absence is what customers remember at renewal.
The Math on Credit
Two days of downtime on a $60,000 annual contract equals roughly $330. Credit a full week and it is about $1,150. Credit a month and it is $5,000 against a $60,000 renewal. For most vendors, that is less than one field marketing dinner and less than the CSM hours that will go into defending the account nine months later.
The dollar amount is not the point. The credit tells the customer you know it hurt them and you took responsibility without being asked.
When the Customer Has to Ask
Making the customer request compensation turns an engineering failure into a relationship failure. The outage is technical. Customers understand those. After the outage, though, the customer is stuck: dig up the SLA, file a ticket, email the rep, feel petty doing it. Most won't. They will quietly note it. That note comes back when someone suggests looking at alternatives and nobody pushes back.
If the vendor offers first, the customer sees accountability. If the customer has to request it, they see that nobody was paying attention. If it never comes, they assume nobody cared.
What It Signals About Uptime Ownership
If you have an SLA, you had a two-day outage, and no credit went out automatically, then either you don't track uptime against the SLA, nobody is responsible for acting on it, or someone decided not to bother. The second is most common.
For critical systems (CRM, billing, ERP), buyers ask about this in contract review: Who declares an outage? How long before credits activate? Are they automatic, or does the customer claim them? Vague answers cost you before you ever go down.
Your Champion Has to Defend You
The outage happens, the team is annoyed, things go back to normal. The champion remembers. At renewal, or when a competitor's AE sends a well-timed email, or when a new exec asks why we use this tool, the champion does not say "they had an outage." They say "they had a two-day outage and didn't offer us anything."
That is much harder to defend internally. Vendors who skip a $330 credit often spend 10x to 100x that later on save campaigns, renewal discounts, and executive escalations.
What to Do After a Major Outage
- Don't make the customer ask. Calculate the credit, apply it, tell them it is done. If the SLA math produces a tiny number, round up.
- Do it within 24 hours, with an honest root cause. Send the credit and the explanation in the same email. Say what broke, why, and what you changed.
- Thank them and say you'll do better. For a multi-day outage on a critical system, this should come from a VP or the CEO.
Then automate it. Connect uptime monitoring to billing so credits go out automatically when a threshold is crossed. Nobody has to remember, no customer has to ask.
For a typical customer, all of this costs a few hundred dollars and 30 minutes of an executive's time. One email within 24 hours: a credit, an honest explanation, a thank you. Instead, the missing credit is the first thing the customer thinks of when your name comes up.
The ANZ Angle
Australian and New Zealand enterprise buyers are particularly sensitive to vendor accountability. The market is smaller, references travel faster, and champions who feel unsupported at renewal talk. SLA enforcement is table stakes in enterprise contracts, and vendors who treat it as optional lose deals they never knew were at risk.