Skip to content

Strategy

Software support agreements: ask how hard it is to leave

The exit terms to check first, the three questions every support agreement must answer, and why a warranty is not support.

Computing America. Applications, integrations, data analysis and AI/ML engineering.

Send the schedule
4 min readComputing America
A steel exit door whose push bar is chained shut with a padlock.

In short

  • Settle support terms before the last week of the deal, when both sides want to sign and arguing about what counts as a bug is hardest.
  • A support agreement has to answer three questions: who decides whether something is a defect, what response you're buying, and what you pay in a quarter when nothing goes wrong.
  • A warranty and a support agreement are different products. A warranty says the vendor fixes what they got wrong; support says someone keeps the system running while the world changes around it.
  • Ask what happens if you want to run the system yourselves in eighteen months, and get the answer in writing.

Before you sign a software support agreement, ask what it takes to leave: accounts in your name, a build someone else can run, a current runbook, and a notice period with no exit fee and a duty to help. Those four terms are cheap for a vendor to promise and easy for you to check.

A custom software deal holds two contracts. The first covers the build: scope, price, dates, acceptance. The second covers the next five years, tends to be a short exhibit at the back, and is easy to leave until the week of signature, when neither side wants to raise anything hard.

The exit is the part to read first

  • Cloud accounts, registrar, certificate authority, app store listings, repository and error tracker all in your name from day one. Check who the account owner is (on a cloud account, the root user and its email address), not who pays: a card on file doesn't make you the owner, and a vendor-owned account can bill your card. If the owner of record is the vendor, ask why.
  • Check who owns the source code. If the contract is silent, add a work-for-hire clause with an assignment fallback. Then make the build a condition of final acceptance: someone outside the vendor builds and deploys to a scratch environment from a clean checkout of the repository, using only the handed-over documents. Before you sign, ask to see that done on a past project. If it can't be done, a new team will be reconstructing the build from the source.
  • A runbook maintained as the work happens. One assembled during a notice period, by people who are leaving, from memory, is thinnest where you'll need it.
  • A stated notice period, no exit fee, and a defined obligation to help during it. Set the length against how long your team needs to take over; 60 or 90 days are examples, not a standard.

The three questions a support agreement has to answer

A template written by people thinking about the launch rarely answers these. Write the answers in.

Who decides whether something is a defect?

This clause produces the arguments. Your operations lead says the export is broken. The vendor says it does exactly what the specification described and what you want is a billable change request. Both can be sincere: the specification was written before anyone used the thing.

A usable agreement states the test in advance. There's more than one workable answer: behavior against the written specification, against the documentation as maintained, or against what a trained user would reasonably expect. Which you choose matters less than having it on paper before anyone needs it. Ask the vendor which test they work to.

What response are you buying?

Response time and resolution time are different promises. An hour to respond means someone replies within an hour. It says nothing about when the system works again. A serious agreement defines severity levels and what triggers each. It names who a severity-one issue escalates to after a set time, and what you get if it stays unresolved. You set the definitions: severity one might mean customers can't place orders, and the set time might be a day.

Ask for the coverage window in your timezone. A distribution operation's last week of the month isn't its second week, and an agreement that treats them alike hasn't been read against your calendar.

What do you pay in a quarter when nothing goes wrong?

A retainer buys availability, which has a real cost whether or not you draw on it. We charge for it, and it's defensible. An unused retainer that no one reviews isn't. After four quarters without an incident, you should hear whether the tier is wrong before you see a renewal notice. Ask what unused hours do at the end of a period. Rolling, expiring and not-a-thing are all honest answers, so find out which before you sign.

A warranty is not a support agreement

A warranty is a statement about the work: for some period after acceptance, defects against the agreed specification get fixed at no charge, because you already paid for them to be absent. It's finite and narrow, and it shouldn't be sold as support.

Support is a statement about the future: someone keeps the system working while everything around it moves. None of that movement is a defect and none of it is optional. A system no one maintains degrades slowly, and then one morning something with a certificate in it expires.

Fig. 1
  1. Before you sign

    Accounts in your name; a past project rebuilt

    • To While the work runs
  2. While the work runs

    The runbook kept as the work happens

    • To Final acceptance
  3. Final acceptance

    An outsider builds and deploys from a clean checkout

    • To Notice period
  4. Notice period

    Where the duty to help is tested; no exit fee

Each exit term is proved at a different point in the contract, and the build test counts only as a condition of final acceptance.

SourceThe exit terms in this article, placed where each can be checked; a planning figure, not data from any contract.

Ask these before you have a proposal

  1. 1.Who decides whether something is a defect, and what is the written test?
  2. 2.What is the difference between your response time and your resolution time, and what happens when the second one is missed?
  3. 3.What do I pay in a quarter with no incidents, and what happens to what I did not use?
  4. 4.If I want my own team to run this in eighteen months, what does that involve, what does it cost, and what do you hold that I'd need handed over?

Next step

Send us the support schedule.

The support, maintenance or managed-service exhibit from the contract you are weighing, ours or anybody's. We will mark what it actually obliges the vendor to do, and what it would take to leave under it.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing