What Should Be Included in a Managed IT Agreement?

You've decided your business needs ongoing IT support.

You've spoken with a few providers, compared prices, and found a company you feel comfortable working with.

Now they send over the agreement.

It's several pages long, filled with technical descriptions, legal terminology, and conditions that aren't particularly interesting to read.

You might be tempted to check the monthly price, sign it, and move on.

But before you do, there are a few things worth understanding.

A good managed IT agreement should clearly explain what your provider is responsible for, what your business is responsible for, and what happens when something doesn't go as planned.

It shouldn't take a lawyer or an IT engineer to understand the basic services you're purchasing.

1. Exactly What's Covered

Start with the most important question: What is the IT company actually agreeing to manage?

Does the agreement cover your employee computers, Microsoft 365 environment, network equipment, servers, and other business technology?

What about shared computers, employee-owned devices, or specialized industry software?

You shouldn't have to guess.

Some providers include remote support but charge separately for onsite visits. Others manage computers but exclude network infrastructure or certain applications.

There's nothing inherently wrong with having exclusions. Every provider needs to define what it can reasonably support.

But it's also important to know what happens when a problem involves something outside that scope.

A Real Example: When the Software Vendor Blamed the Network

I've dealt with plenty of situations where a software vendor blamed the network, while the people responsible for the network believed the problem was somewhere else.

In one case, a business was having trouble with a computer supplied by its software vendor.

The vendor insisted the issue was network-related. But after investigating, I found that the computer they had supplied was severely underpowered. It struggled to handle the workload, including the use of a USB network adapter.

The problem wasn't simply that the network wasn't working. The equipment running the vendor's software was inadequate for what it needed to do.

Situations like this can turn into a frustrating back-and-forth, particularly when each vendor is focused only on the part of the system it supports.

I've found that even how a problem is described can influence whether a vendor investigates it or immediately points to someone else.

That's why vendor coordination matters.

A good IT support arrangement should make it clear who helps investigate issues that cross between systems, communicates findings, and works with outside vendors toward a resolution.

Your IT provider can't force another company to fix its product. But someone should be responsible for coordinating the troubleshooting instead of leaving the business to figure out which vendor to call next.

Your business shouldn't have to become the technical referee between companies it's already paying for support.

2. Support Hours and Response Expectations

If an employee can't access their email at 9 AM on a Tuesday, how do they request help?

What happens if your entire office loses network connectivity?

And what if something breaks on Saturday?

Your agreement should explain how to request support, when support is available, and how different types of problems are prioritized.

It should also distinguish between response times and resolution times.

A provider might promise to respond to a critical issue within a certain period. That doesn't necessarily mean the problem will be completely resolved within that same period.

Some problems depend on hardware availability, software vendors, internet providers, or factors outside the IT company's control.

What matters is understanding what the provider commits to doing and how communication will work during an outage.

3. Security and Backup Responsibilities

Cybersecurity is one area where vague agreements can create serious misunderstandings.

A company might advertise that security is included, but what does that actually mean?

Are computers receiving endpoint protection? Is suspicious activity monitored? Who investigates alerts? Who manages employee access?

The same questions apply to backups.

What information is being backed up? How often? How long are recovery copies retained? Who monitors failures, and who tests whether information can be restored?

Not every managed IT agreement includes every security or backup service.

And hiring an IT provider doesn't automatically transfer all cybersecurity or regulatory responsibilities away from your business.

The agreement should establish who's responsible for which protections, rather than leaving everyone to make assumptions.

4. What's Included in the Monthly Price—and What Costs Extra

This is where businesses sometimes get surprised.

A monthly managed IT fee might cover routine support, monitoring, maintenance, and certain security services.

But replacing computers, installing new network equipment, moving offices, or implementing a new business application may be separate projects.

Software licenses and hardware purchases may also be billed independently.

For example, at The IT Guys, our Managed IT service is $125 per user per month, including security services.

Before taking responsibility for an environment, we make sure it meets our support standards. Routine onboarding is handled through our standard onboarding process, while significant issues that need correcting are addressed as a separate project.

We separate those costs because the work required to prepare an environment is different from maintaining it afterward.

Whatever provider you choose, make sure the agreement explains how additional work is proposed, approved, and billed.

5. Who Owns Your Equipment, Accounts, and Data?

This is one of the most important sections of any IT agreement.

Your business should maintain ownership and appropriate control over its domain name, business data, accounts, and equipment it has purchased.

An IT company may need administrative access to manage those systems, but that shouldn't mean the business loses control over them.

The agreement should distinguish between assets your business owns, software or services you license, and management tools that belong to the provider.

It should also explain what happens to those tools and services if the relationship ends.

You don't want to discover that your only administrative account belongs to a departing provider or that you can't access your own domain registration.

Your IT provider should manage your technology, not hold your business hostage through its accounts or access.

6. What Your Business Is Responsible For

A managed IT agreement isn't a promise that the provider can handle everything without cooperation from the business.

There are responsibilities on both sides.

Your company may need to approve recommended upgrades, report employee departures, maintain required software subscriptions, and provide appropriate access to supported systems.

Your provider needs to understand when employees are hired, change roles, or leave so access can be managed correctly.

Similarly, if an important piece of equipment is no longer supported and the business declines to replace it, that decision may affect what the provider can reasonably maintain or guarantee.

A good agreement should explain these shared responsibilities.

It's not about shifting blame. It's about making sure everyone understands what needs to happen for the service to work as intended.

7. Contract Terms, Cancellation, and Switching Providers

Most people focus on what happens when they sign an agreement.

I'd encourage business owners to pay just as much attention to what happens when they leave.

How long does the agreement last?

Does it renew automatically?

How much notice is required to cancel?

Are there early termination fees?

What assistance will the provider offer when transitioning to another IT company?

And how will your documentation, administrative access, and business information be handed over?

Some agreements contain perfectly reasonable notice periods and transition requirements.

Others may have conditions that are more restrictive than a business realizes.

You should understand those terms before committing.

Changing IT providers shouldn't mean losing access to your own systems or having to rebuild your entire environment simply because the relationship ended.

What About All the Legal Language?

Managed IT agreements also contain provisions covering payment terms, confidentiality, liability, warranties, disputes, and other legal responsibilities.

Those clauses matter, even though they aren't usually the first things a business owner thinks about when purchasing IT support.

Pay particular attention to limitations of liability, the handling of confidential information, and what happens following a serious security incident or service failure.

For healthcare businesses and others handling regulated information, additional agreements or compliance-related terms may be necessary.

If something isn't clear, ask for an explanation. And if the agreement contains obligations or risks you don't understand, consider having an attorney review it before signing.

The Bottom Line

A managed IT agreement shouldn't be a guessing game.

It should clearly establish what your provider will manage, how support works, what protections are included, what your business is responsible for, and what happens if the relationship ends.

Not every provider needs to offer identical services, and not every agreement needs to look the same.

But the responsibilities should be understandable.

For small businesses throughout Beaumont, Port Arthur, Orange, and Southeast Texas, that clarity can prevent misunderstandings that become expensive later.

At The IT Guys, we believe clear expectations and accountability are just as important as technical expertise.

You should know exactly what you're paying for, what you're responsible for, and what you can expect from the people managing your technology.

Preferably before you need them in an emergency.