On this page
You have found an IT company you would like to work with. The conversations went well, the price fits, and now there is an agreement to sign. Before you do, make sure you can explain what your business is committing to: the work, the payments, the length of the agreement and the way out if things do not work out.
Read the IT support contract alongside the proposal and any attached schedules. Pay particular attention to start dates, renewal notice, additional charges, software subscriptions and access to your accounts. These details matter long after you have forgotten the sales presentation.
Get all the documents that make up the agreement
The signature page may refer to several other documents. A master services agreement, or MSA, generally sets out the business terms. A statement of work, or SOW, describes the particular services being purchased. A service-level agreement, or SLA, may define support commitments. Pricing schedules, acceptable-use policies and industry-specific addendums can add further terms. Providers use these names differently, so check what each document actually says.
Ask for every document mentioned, including terms linked from a website. Check which version applies, how later changes would be communicated and which document takes priority if two provisions disagree. Save the final set together. If a promise helped you choose the provider, ask where it appears in those documents.
The scope should describe the work you expect to buy. For example, does support for your accounting software mean helping staff use it, keeping the server available, contacting the software vendor, or some combination? You should be able to identify the included service and who pays when another specialist is needed.
Separate signing, service start and the first payment
Signing the agreement, beginning onboarding and taking over everyday support are different events. Check when each happens and which one starts the initial contract term. If service begins only after onboarding is ready, the agreement should explain how that date will be confirmed and what happens if access or another dependency delays it.
Read the payment schedule just as closely. Find the setup charge, first recurring invoice, regular billing date and payment due date. Check whether fees are collected in advance, whether a partial first month is charged and which charges can start before ongoing support begins. A quoted monthly amount tells you little about the cash needed at the start unless these dates are clear.
If you are replacing a provider, compare those dates with the end of your current agreement. A planned overlap can help with the handoff; an accidental overlap leaves you paying two companies longer than expected.
Read the renewal rules before focusing on contract length
A twelve-month agreement may renew for another twelve months unless notice arrives by a stated deadline. A month-to-month arrangement can still require advance notice. Look for the initial term, renewal period, notice deadline, delivery method and recipient. Ask whether notice must be received by the deadline or merely sent. Put a review reminder comfortably ahead of that date.
Separate the decision not to renew from ending the agreement early. Find out whether early termination is available, what it would cost and what happens if either side fails to meet its obligations. Some agreements require written notice of a problem and time to put it right before further action can be taken. Ask the provider to explain that process in ordinary language.
Check price changes too: when they can happen, how you are notified, whether a formula or limit applies and what options you have before the change takes effect. Keep routine rate increases separate from increases caused by adding people, equipment or services.
Find out how additions and software commitments are charged
Ask what happens to the bill when you hire someone, replace a computer, add a server or close an office. A replacement computer should be distinguishable from an additional computer. The agreement should explain who reports changes, who can approve them and when the new quantity affects billing. Look for minimum quantities and the rules for reducing them as well.
Pay attention to the first charge for an addition. Is it a partial month, a full month or the next billing period? Ask the same question when something is removed. Support charges and software charges may follow different rules, so a departing employee may not immediately remove every related cost.
Monthly billing does not necessarily mean a monthly commitment. Microsoft, for example, distinguishes a subscription's commitment term from its billing frequency in its subscription billing guidance. An annual subscription can be billed monthly. Ask for the term, renewal date, reduction rules and remaining payment obligation for each separately committed subscription. Also ask what happens to that subscription if you leave the IT provider before it ends.
Check what the support commitments actually promise
Find the hours and time zone for staffed support, the way to report an emergency, and the charges or limits for onsite and after-hours work. If the agreement advertises a response target, check what starts the clock, what counts as a response and when the clock can pause. A response target is not automatically a promise that the problem will be fixed within that time.
Read what happens when a commitment is missed: escalation, a service credit, a review or another stated remedy. Check any conditions for requesting it. Our guide to reading an IT support report explains the measurements in more detail; the contract should establish which commitments actually apply to your service.
Agree who can authorize spending and urgent action
An employee asking for help should not accidentally authorize an expensive project. Check who can approve extra work, what form that approval takes and whether an estimate or spending limit is required. If extra work is billed hourly, find the rates, minimum charges and any travel costs.
Security incidents need their own discussion. Ask what the provider can do immediately, such as temporarily disabling an account, and when it needs your approval. Name a backup business contact for urgent decisions. Clarify who contacts your insurer or outside incident specialists and how additional investigation and recovery work would be authorized and charged.
The agreement should also explain the provider's security responsibilities, how it handles your data and how it will notify you of an incident affecting your business. The FTC's vendor-security guidance recommends putting security expectations in contracts and checking that vendors follow them. If your business has privacy, insurance or industry requirements, have the relevant adviser check the proposed terms and any required addendum before you sign.
Understand what happens to your accounts and records when you leave
Ask what your business will receive at the end: its data, account access, configuration records and other agreed documentation. The agreement should distinguish business-owned accounts and records from the provider's own tools and licenses. Some services may need replacement rather than transfer. Find out who arranges that work, how much help is included and what additional handoff assistance costs.
Check how long backups and other copies of your data remain available, how you can obtain an export and when deletion happens. Ask how an unpaid invoice or billing dispute would affect ongoing service and the handoff. You want these answers while both parties are planning a good relationship. Our provider-switching guide covers the later task of carrying out a transition.
Liability limits, indemnity, suspension rights, personal guarantees and dispute provisions also deserve attention. A liability cap can limit recovery; an indemnity may require one party to cover certain claims or costs. This guide covers buying questions, not the legal effect of your particular agreement. Have a lawyer review those provisions and any significant financial exposure, especially where they may differ from the risks your insurance covers.
Leave the final meeting with written answers
Ask the provider to point you to the clause or schedule answering each unresolved question. If a change is needed, get the agreed wording into the final documents before signing. A short written summary can help your own team keep track, but it should match the agreement.
| Confirm | What you should be able to explain |
|---|---|
| The documents | Which versions apply, what work is included and which terms take priority. |
| Dates and payments | When support and the term start, what is due first and when regular payments are due. |
| Renewal and leaving | How to give notice, what early departure costs and what you receive at the end. |
| Changes to the bill | How additions, removals, rate increases and separate license commitments are handled. |
| Authority and responsibility | Who approves extra spending, what urgent action is allowed and how problems escalate. |
| Legal and insurance review | Which risk provisions need your lawyer or insurance adviser to review before you commit. |
Still choosing between companies? Use our ten questions for interviewing an IT provider. If you have competing prices, the quote comparison guide helps you compare their scope and cost. This final contract review is where you check that the agreement reflects the decision you have made.
If you are considering managed IT services for your Suffolk County business, talk with Charles about the work you need and any questions about DreamMSP's proposed agreement.