Key takeaways
- A managed IT agreement usually covers monitoring, updates, help desk support, antivirus and email security, backups, and management of your network equipment, for a flat fee per user or per device.
- It usually does not cover projects, new hardware, software licenses, cabling, or third-party costs; those are quoted separately, and the agreement should say so plainly.
- The term and cancellation clause matters more than the price: many Dallas agreements auto-renew for a year, while mine is month-to-month and you can cancel any time.
- Read the onboarding and offboarding sections carefully; your admin passwords, documentation and licenses must belong to your business, not to the provider.
- If a clause is vague about hours, after-hours rates or what counts as a project, ask for it in writing before you sign, not after the first surprise invoice.
The short answer
A managed IT services agreement usually includes six things: monitoring of your computers, servers and network; operating system and application updates; a help desk you can call or email; antivirus and email security; managed backups with recovery; and management of your office network equipment such as the firewall, switches, Wi-Fi access points and printers. It usually excludes projects like office moves or migrations, new hardware, software subscriptions, cabling, and anything a third party charges you for. The price is a flat monthly fee per user or per device, and the agreement sets a term, a notice period, and what happens when you leave.
That is the skeleton. The details are where agreements differ, and where small businesses in Dallas get surprised a year in. This article goes clause by clause so you can read any provider's agreement, including mine, and know what you are agreeing to. I will point out where my own managed IT services agreement sits on each point, because I think it is fair for you to see that before you call.
What services are usually covered by the monthly fee?
The core of any managed agreement is the list of things the provider will do every month without a separate invoice. In a typical small-business agreement in the Dallas market, that list looks like this:
- Monitoring. A small piece of software on every computer and server reports health, disk space, failed updates and warning signs back to the provider. This is what lets problems get fixed before you notice them.
- Updates and patching. Operating system and application updates for computers and servers, applied on a schedule and checked afterwards. Missing patches are the most common way small offices get compromised, so this line matters.
- Help desk support. Someone to call or email when a person cannot print, cannot log in, or cannot open a file. Most agreements say "unlimited remote support"; read whether onsite visits are included or billed hourly. Mine includes unlimited remote support and onsite visits at no extra charge when remote cannot fix it.
- Endpoint protection and email security. Managed antivirus on every device and filtering on your email to catch phishing and malicious attachments.
- Backup and disaster recovery. Backups of servers, key computers and cloud data, with periodic test restores. Ask whether the backup storage cost is inside the fee or billed by the gigabyte.
- Network and infrastructure management. Your internet provider relationship, router, firewall, switches, access points and printers. This is the part many agreements leave vague, so ask.
- Microsoft 365 or Google Workspace administration. User setup, license changes, security settings, mailbox management. See Microsoft 365 and Google Workspace support for what that covers.
Any agreement that does not spell out each of these, or that says "IT support" without a list, is a conversation you should have before signing rather than after.
What is usually not included?
The exclusions matter as much as the inclusions, because they are where the extra invoices come from. Here is what a typical managed agreement leaves out, and what I leave out too, so that nobody is surprised:
- Projects. An office move, a server migration, a switch to a new practice management system, or a new location are quoted separately as fixed-price or hourly projects. The agreement should define what counts as a project versus routine support. A rough rule: if it is planned, has a start and an end, and changes how your office works, it is a project.
- Hardware. New laptops, servers, firewalls and access points are purchased by you. Some providers mark up hardware; some, like me, quote it at cost with the setup time as the service. Ask which.
- Software licenses. Microsoft 365, Google Workspace, your line-of-business applications, and sometimes the security and backup platforms themselves are billed as pass-through subscriptions. Ask for the per-user cost of each.
- Cabling and physical build-out. Running Cat6 to new desks, installing a rack or patch panel is a separate scope. I do this work under data cabling and IT room setup, but as its own quote.
- Third-party costs. Internet service, phone service, domain names, web hosting. The provider manages the relationship; you pay the bill.
- After-hours emergencies, sometimes. Some agreements include after-hours support, some bill it at a premium, some do not offer it at all. Mine: remote support is available 24/7 including holidays, and after-hours rates apply.
None of these exclusions are unfair. What is unfair is an agreement that hides them, or a provider who calls every second task a "project" so the flat fee never covers anything.
How is the price structured?
Almost every managed agreement for a small business is priced one of two ways: per user per month, or per device per month. Per user means every person who needs support, regardless of how many devices they use. Per device means every computer, server and sometimes every network device, regardless of who uses it. Which is better depends on your office; I wrote a separate article on per-user versus per-device IT pricing if you want the trade-offs.
As a typical market range, small-business managed IT in the Dallas area is commonly quoted somewhere around $100 to $175 per user per month, with per-device pricing lower per unit because a user often has more than one device. That range is the market, not my price; I quote per user or per device after a short conversation about what you actually have.
Beyond the headline number, look for these in the pricing section:
- Minimums. Some agreements set a minimum monthly fee or a minimum user count, which matters for a 5-person office.
- Onboarding fee. A one-time charge for documenting your setup, installing the monitoring software and fixing what the last provider left behind. Reasonable if disclosed; ask what it covers.
- Price changes. How and when the per-user rate can go up, and how much notice you get.
- Counting rules. When a new employee starts mid-month, when someone leaves, whether part-timers count. Small clauses, real money over a year.
The pricing page lists every rate I publish, including the hourly rates that apply to work outside the managed plan.
What do the term and cancellation clauses say?
This is the clause I would read before any other, because it decides whether you are a customer or a captive. Managed IT agreements in Dallas commonly come in one of three forms:
- Annual term with auto-renewal. You sign for 12 months, and unless you give written notice inside a window, often 60 or 90 days before the anniversary, it renews for another 12. Miss the window and you are locked in for a year with a provider you were trying to leave.
- Multi-year term. Two or three years, sometimes with a discount for the commitment. Common with larger providers. Early termination usually means paying out the remaining months.
- Month-to-month. You pay each month and can cancel with short notice, typically 30 days. The provider has to keep earning the business.
Mine is month-to-month. You can cancel any time, and I would rather keep you because the work is good than because a clause says so. I go into the trade-offs in month-to-month versus annual IT contracts, and I will admit that annual terms are not evil; they let a provider invest in onboarding. But for a business under 50 people, the flexibility is worth more than the discount.
Whatever the term, check the notice period, whether notice must be in writing, what early termination costs, and whether the provider can end the agreement on you with the same notice you must give them.
How are hours, response and priorities described?
Most agreements define business hours, usually Monday to Friday during the working day in Central time, and state what happens outside them. They also often list priority levels: a whole-office outage is treated differently from a single user's second monitor not working. Larger providers attach response targets to each priority level and call the section a service level agreement, or SLA.
Here is my honest view on that section. A response target on paper is only as good as the person answering. I am the owner and the person you deal with, so I do not hide behind a ticket queue or a tiered help desk. You call, I answer or I call back, my team handles the routine work behind me, and same-day onsite visits are often possible because I am based in Dallas and work across the metroplex by appointment. I do not write a numbered promise into the agreement, because I would rather be honest than impressive.
When you read another provider's SLA section, ask three questions. Does the target measure a reply or a fix? A reply can be an automated email. Does it apply to every request or only to the highest priority? And what happens if they miss it? If the answer to the last one is "nothing," the section is decoration.
Also check how after-hours work is defined and billed. Weekends and holidays should be spelled out, and the after-hours rate should be a number, not "premium rates apply." Mine are published: remote and onsite after-hours rates are on the pricing page alongside the business-hours rates.
What happens at the start and at the end?
Two sections that small businesses skip are onboarding and offboarding, and they are the ones that protect you most.
Onboarding should describe what the provider will do in the first weeks: document your network, computers, accounts and vendors; install the monitoring and security software; set up backups and confirm they run; collect and secure your admin passwords; and fix the urgent problems found along the way. Ask how long it takes and whether there is a fee. A good onboarding is also the moment you find out what your previous provider never told you.
Offboarding is what happens when the agreement ends, for any reason. This section does not need to be long, but it should state clearly that:
- All admin credentials, documentation and configuration records are handed to you or your next provider.
- Software licenses purchased in your name stay with you; licenses on the provider's own agreement are transferred or replaced with notice.
- Monitoring and remote access software is removed from your devices on a stated date.
- Backups are handed over or retained for a stated period so you are never without a copy of your data.
The principle is simple: your business owns its systems. A provider who resists putting that in writing is telling you something. If you are switching from one provider to another, I wrote up how to do it cleanly in how to switch IT companies without downtime.
Which clauses should I read twice?
Here is the checklist I give owners who send me a competitor's agreement and ask what I think. Use it on any managed IT agreement, including mine.
| Clause | What to look for | Why it matters |
|---|---|---|
| Scope of services | A written list, not "IT support" | Decides what the monthly fee actually buys |
| Exclusions and projects | A definition of "project" | Stops routine tasks becoming extra invoices |
| Pricing unit | Per user or per device, with counting rules | Small rules add up across a year |
| Term and renewal | Month-to-month, or a renewal window you can meet | Whether you can leave a bad provider |
| Notice and termination | Days of notice, early exit cost, written form | The real cost of changing your mind |
| Hours and after-hours rates | Actual numbers for nights, weekends, holidays | Emergency invoices are where surprises live |
| Onsite visits | Included, capped, or billed hourly | Biggest hidden difference between quotes |
| Ownership | Passwords, licenses, documentation belong to you | Protects you at offboarding |
| Data and confidentiality | How your data is handled, where backups live | Essential for law, dental, medical, insurance |
| Liability and insurance-related duties | What the provider commits to help you meet | Cyber-insurance applications ask about this |
If you work in a regulated field, add one more line: the agreement should describe how the provider helps you meet HIPAA or your carrier's cyber requirements, and for a covered dental or medical practice it should include a business associate agreement. I cover that in the industry pages for dental practices and law firms.
What does my own agreement look like?
Since I have asked you to read everyone else's carefully, here is mine in plain terms. It is a managed IT agreement for small businesses in Dallas and across the DFW metroplex, with remote support anywhere in Texas.
- Billed per user per month or per device per month, quoted after a short conversation about what you have.
- Month-to-month. Cancel any time.
- Includes operating system and application updates for computers and servers, unlimited remote support, onsite visits at no extra charge when remote cannot fix it, antivirus management and email security, managed backup and disaster recovery, and management of your ISP, router, firewall, switches, access points and printers.
- Remote support is available 24/7 including holidays; after-hours rates apply and are published.
- Projects, hardware, software licenses and cabling are quoted separately, in writing, before any work starts.
- Everything is documented in your name, and you get all of it if you ever leave.
The one thing I cannot write into an agreement is that you will always talk to the same person who knows your office. That is just how an owner-led company works: I am your point of contact, and my team works behind me from the same documentation. If you want to see the document itself, get in touch and I will send it over before any sales conversation, so you can read it the way this article suggests.
Questions people ask
What is typically covered in a managed IT services agreement?
A typical agreement covers monitoring of computers, servers and the network; operating system and application updates; help desk support by phone and email; managed antivirus and email security; backups with recovery; and management of network equipment such as the firewall, switches and Wi-Fi. It is priced as a flat monthly fee per user or per device. Onsite visits, after-hours support and Microsoft 365 administration are sometimes included and sometimes billed separately, so read the list.
What is usually excluded from a managed IT agreement?
Projects such as office moves, migrations and new locations are quoted separately. New hardware, software licenses, cabling and physical build-out are excluded, as are third-party bills for internet, phones and domain names. Some agreements exclude after-hours work or bill it at a premium. A fair agreement lists these exclusions plainly and defines what counts as a project, so routine tasks do not turn into surprise invoices.
Do managed IT agreements have a minimum term?
Many do. Annual agreements with automatic 12-month renewals are common in the Dallas market, and some larger providers ask for two or three years. Others, including mine, are month-to-month with short notice to cancel. Check the notice period, whether the renewal window is one you can realistically meet, what early termination costs, and whether the provider can end the agreement on you with the same notice you must give.
Should the agreement include a service level agreement or response times?
Larger providers usually attach response targets to priority levels. If yours does, check whether the target measures a reply or a fix, whether it applies to every request, and what happens if it is missed. As a small owner-led company I do not put a numbered promise in writing; you call, I answer or call back, and same-day onsite visits in Dallas are often possible. Honest availability matters more than a number on paper.
What should the agreement say about my passwords and data when I leave?
It should state that all admin credentials, documentation, configuration records and backups are handed to you or your next provider, that licenses bought in your name stay with you, and that the provider's remote access and monitoring software is removed by a set date. Your business owns its systems. A provider who resists writing that down is a provider to be cautious about.
Does a dental or medical practice need anything extra in the agreement?
Yes. A practice that handles protected health information should have a business associate agreement with its IT provider, and the managed agreement should describe how the provider helps the practice meet HIPAA duties: encryption, access control, backups, audit records and breach procedures. The same logic applies to law firms with client confidentiality duties and insurance agencies with carrier and state requirements. Ask for it in writing.
Sources and further reading
Market price ranges in this article are my own observation of quotes in the Dallas market, not a published survey. Where I state a rule or a standard, the source is linked above.
