Most support agreements are written by the supplier, and they tend to describe what the supplier is willing to do. An agreement that protects you describes what your business needs when something goes wrong, in terms you could check afterwards. This guide sets out what to ask for. It is a practical checklist from the engineering side and does not replace legal advice, so have your lawyer review the final wording.
Name What Is Covered
List every system, integration and service the agreement applies to, including the hosting, the connections to other software and any AI features. Loose wording such as "the platform" leaves room for an argument about whether the part that failed was included, and that argument always happens at the worst moment.
Define Severity by What It Does to Your Business
| Level | What it means for you | An example | What to have written down |
|---|---|---|---|
| Critical | The business cannot trade | Orders cannot be taken, or customer data is exposed | A response time, cover at all hours and updates at set intervals |
| Serious | A main function is failing, but there is a way round it | Invoices will not send, although orders still arrive | A response time in working hours and a target for the fix |
| Minor | An inconvenience | A report shows the wrong heading | A place in the next planned release |
Ask for Response and Fix Times Separately
A response time tells you how quickly someone will acknowledge a fault, and says nothing about when the system will be working again. Ask for both at each level, together with a commitment to provide a temporary way round a critical fault while the full fix is made. Check also when the clock starts, since some agreements count from the moment a ticket is accepted and others from the moment you reported it.
Find Out Who Answers
Ask whether a call reaches an engineer who knows your system or a desk that will pass it on, and whether the same people cover nights and weekends. If cover outside working hours matters to you, the agreement should say which levels of fault justify waking somebody and how you reach them.
Include the Work That Prevents Faults
- Security updates applied within a stated period of their release.
- Backups taken on a stated schedule, with a restore tested at stated intervals.
- Monitoring that alerts a person, with a note of who that person is.
- Checks on the services, integrations and AI models the platform depends on.
- A regular report of incidents, work done and anything coming up.
Say How New Work Is Handled
Support keeps a system running, and sooner or later you will want it changed. Decide in the agreement whether small changes are included, how larger pieces of work are quoted and who has the authority to approve them. Without that, every request becomes a negotiation, and the people who use the system learn to stop asking.
Decide What Happens When a Promise Is Missed
A commitment with no consequence is only a hope. Agree what follows if a response or fix time is missed, whether that is a credit against the next invoice, a review meeting or the right to leave without notice. You are unlikely to rely on it often, and its presence changes how seriously the times are taken.
Keep Everything in Your Name
The code, the hosting account, the domain and every third-party account should belong to your company, with the supplier given access to do the work. An agreement that leaves any of those with the supplier makes leaving difficult, whatever the notice period says.
Agree How It Ends
Write the exit while relations are good. The agreement should state the notice either side must give, what is handed over, how long the supplier will help a successor and what that help costs. Documentation kept up to date throughout is worth asking for here, because it is what makes a handover possible in practice.
Three Warning Signs
A response time with no fix time
You are promised an acknowledgement and nothing beyond it.
Hosting in the supplier's name
Your platform can be held while a dispute is settled.
No mention of exit
The terms of leaving will be set at the moment you have the least bargaining power.
BY BANKS provides support and managed hosting on a monthly retainer, with everything in the client's name and the engineers who built the platform on call. If you have been sent a support agreement and would like an engineer's view of it before you sign, get in touch.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation