Ask any operations engineer about the worst outage they lived through and, sooner or later, the story turns to a contract. Somebody assumed the vendor would cover the loss, or that support would answer in an hour, or that the plan could be cancelled whenever. Then someone finally opened the agreement. The stories differ, but the shape is the same: a belief that felt safe, a clause that said otherwise. Here are six myths worth retiring, with the quieter truth behind each.
Myth one: “Ninety-nine point nine percent uptime means we are covered”
The number sounds like protection. What it usually describes is a target, measured in a way the vendor defines, with a remedy that may be a small credit on next month’s bill. Look at three things: how downtime is measured, which kinds of outage are excluded, such as planned maintenance, and what you receive when the target is missed.
A team I know of kept a shelf of printed incident reports and was fond of saying that an uptime promise without a remedy is a mood, not a safeguard. It is a fair way to put it. The paragraph that matters is the one that says what happens next.
Myth two: “It is a standard contract, so nobody reads it”
Standard means standard for the vendor. It describes the terms the company prefers, written by its own lawyers to protect its own position. That does not make them unreasonable, but it does make them a first offer. Notice periods, credit mechanics and data export terms are often negotiable, especially for customers who ask politely and early.
Teams who treat the draft as fixed leave value on the table. Teams who read it can usually trade a long commitment for a better exit clause.
Myth three: “The salesperson said we could cancel anytime”
Verbal assurances have a short shelf life. People change roles, memories blur and agreements often contain a clause saying the written document is the whole deal. If something matters, it needs to exist in the paper you sign, or in an order form that the contract recognises.
The practical habit is simple. When a promise is made in a meeting, send a short message the same day saying what you understood, and ask for the contract wording that reflects it. If the wording never appears, you have learned something important.
Myth four: “Support means someone will fix it”
Support terms describe response, not resolution. A four-hour response target means somebody acknowledges you within four hours, not that the incident is solved. Read the severity definitions: what the vendor counts as critical may differ from what your team would. Check which channels are covered and whether the hours include weekends.
For anyone responsible for incidents, the surrounding practice is covered well in an article on incident management with AIOps for faster resolution. The contract just decides how much of that speed depends on the vendor.
Myth five: “If we leave, we simply take our data”
Exit is where many agreements get specific in ways customers did not expect. Check the export format, the time allowed, whether there is a fee and how long the vendor keeps your data afterwards. A platform that holds years of operational history can become a very expensive thing to leave if exporting requires a paid service.
Plan for the exit when you plan for the entrance. A rough roadmap, such as the one in a hands-on AIOps plan for operations and reliability teams, is easier to follow when you know the tools in it can be replaced.
Myth six: “Legal will catch anything that matters”
Lawyers are essential for reading liability, indemnity and licensing clauses, and they do a great deal of good. But they usually review what is placed in front of them, and they do not know your operations the way you do. They will not know that your batch window ends at four, or that your busiest week is in March, unless someone tells them.
The best results come from a pairing. Engineers read for operational fit: dates, limits, response times and exit mechanics. A lawyer reads for meaning and risk. If your team in India does not have a legal contact yet, WakilSahab is a site with a lawyers directory, forum discussions, legal news and a blog that you can browse to learn and begin looking. What the clauses mean for your case remains for a professional to say.
What the myths have in common
In every case an assumption stood where a question belonged. Uptime, standard terms, verbal promises, support, exit and legal review all feel like settled matters, and each deserves a minute of reading.
A short routine puts that into practice.
- Find the uptime remedy and write it in one sentence.
- Mark anything that looks fixed and ask whether it can move.
- Move every promise made in a call into the document or an order form.
- Read the severity table and compare it to your own.
- Test the exit on paper before you sign.
- Give legal the operational context along with the draft.
A closing story
The same engineer with the shelf of incident reports once showed me a dog-eared contract with three yellow tabs. “Renewal, remedy, exit,” he said. “Everything else is detail.” He admits it is a simplification. Still, on a Friday afternoon, with a renewal notice in the inbox and a vendor on the phone, those three tabs did more good than any dashboard.
Read the fine print first. The myths survive because the paragraphs go unread.

