A managed IT services agreement should clearly define what the provider is responsible for, what the client is responsible for, what is included in the monthly fee, and what will be billed separately.
For a 10- to 50-user professional services firm, a strong agreement should cover five areas:
- Proactive IT management
- Reactive support
- Cybersecurity, backup, and business continuity
- Projects, exclusions, and third-party costs
- Service expectations, agreement terms, and transition requirements
The most important point is clarity.
A low monthly price is not necessarily a good value if normal support, projects, onsite service, security, or recovery services are excluded. Likewise, a broad all-inclusive agreement is not automatically the best fit if your firm rarely uses some of the services built into the price.
The agreement should make it easy to understand what you are buying and how the relationship will work.
-
Proactive IT Management
The first section of the agreement should define the services the MSP performs before something breaks.
That may include:
- Device monitoring
- Patch management
- Server monitoring
- Network monitoring
- Microsoft 365 administration
- User account management
- Backup monitoring
- Documentation
- Hardware lifecycle planning
- Vendor coordination
The agreement should go beyond vague terms like “proactive support” or “monitoring.”
Ask:
- Which devices are covered?
- Which systems are monitored?
- How often are patches applied?
- Who handles onboarding and offboarding?
- Who manages Microsoft 365?
- Who reviews hardware age and replacement needs?
- Who is responsible for third-party vendor coordination?
If the agreement does not clearly define those responsibilities, it can create confusion later.
-
Reactive Support
Reactive support is what happens when an employee needs help.
Examples include:
- A user cannot log in
- Email is not working
- A printer stops working
- A business application will not open
- A laptop becomes unstable
- A remote employee cannot connect
- A new employee needs setup assistance
The agreement should explain exactly how this labor is handled.
Common models include:
Fully Included Support
Most routine reactive support is included in the monthly fee.
This can provide predictable billing, especially for firms with frequent support needs.
Block-Based Support
The agreement includes a defined amount of reactive labor each month.
This can provide a balance between predictability and visibility into actual support usage.
Separately Billed Support
The monthly agreement covers proactive management, while reactive support is billed separately.
This may be a good fit for firms with stable environments and relatively low support usage.
At ANAX, we use all three approaches depending on the client.
Our Comprehensive Service Agreement (CSA) provides broad proactive and reactive coverage.
Our Business Service Agreement (BSA) combines proactive management with a defined block of reactive support hours and is our most commonly selected model.
Our Essential Service Agreement (ESA) focuses on proactive management, with reactive support billed separately.
The key point is not that one model is better.
It is that the agreement should match how the firm actually uses IT support.
-
Cybersecurity, Backup, and Business Continuity
Security and recovery responsibilities should be clearly defined in the agreement.
Depending on the provider and the environment, that may include:
- Endpoint security
- Email security
- Multi-factor authentication
- Security awareness training
- Identity protection
- Backup monitoring
- Microsoft 365 backup
- Server backup
- Recovery testing
- Business continuity planning
The agreement should also explain which security services are included in the monthly fee and which are separate.
For example, an MSP may manage endpoint protection as part of the agreement but charge separately for advanced email security, backup storage, or security awareness training.
Neither approach is inherently wrong.
The problem is when the client assumes something is included and discovers later that it is not.
The same is true for backup.
Ask:
- What is being backed up?
- How often?
- Where is the data stored?
- Who monitors the backups?
- How often is recovery tested?
- What happens if a critical system becomes unavailable?
A managed IT agreement should make those responsibilities clear before a disruption occurs.
-
Projects, Exclusions, and Third-Party Costs
One of the most important parts of a managed IT agreement is the section that explains what is not included.
Common exclusions may include:
- Office moves
- Cabling
- Server replacements
- Cloud migrations
- Major Microsoft 365 projects
- New office buildouts
- Large software implementations
- Hardware purchases
- Software licensing
- After-hours work
- Certain cybersecurity services
- Third-party vendor fees
These exclusions are not necessarily a problem.
The problem is when they are not clearly defined.
For example, if your monthly agreement includes routine support but a major network replacement is considered a separate project, that should be easy to understand before the work begins.
Ask:
- What qualifies as a project?
- How are projects quoted?
- Are projects billed hourly or at a fixed fee?
- Is after-hours work billed differently?
- Are travel or onsite fees additional?
- Are Microsoft 365 and software licenses included or separate?
- Are third-party vendor charges passed through?
The goal is to avoid surprises.
A well-written agreement should make it clear which costs are predictable and which may vary.
-
Response Expectations and Escalation
The agreement should also explain what happens when your team needs support.
That includes:
- How support requests are submitted
- Normal business hours
- How urgent issues are classified
- Expected response times
- How onsite support is handled
- How after-hours emergencies are handled
- Who manages escalations
It is important to distinguish response time from resolution time.
A provider may commit to responding quickly without promising that every issue will be completely resolved within the same timeframe.
That is reasonable.
Some problems can be solved in minutes.
Others depend on hardware replacement, internet providers, software vendors, or third-party systems outside the MSP's direct control.
The agreement should set realistic expectations without making promises that cannot reasonably be guaranteed.
Ask How Escalations Work
Not every support issue should remain with the first technician who receives it.
Ask:
- When is an issue escalated?
- Who becomes responsible?
- Is there a senior technical resource available?
- Who communicates with leadership during a major issue?
- What happens if a ticket remains unresolved?
A clear escalation process is especially important when the problem affects multiple employees or a critical business system.
Agreement Length, Renewals, and Cancellation
Before signing, understand how long the agreement lasts and how it renews.
Review:
- Initial agreement term
- Automatic renewal provisions
- Cancellation notice requirements
- Early termination provisions
- Price adjustment language
- Renewal timing
The exact agreement length matters less than understanding what you are committing to.
A 12-month, 24-month, or 36-month term can all be reasonable depending on the circumstances.
What matters is that the business understands how to exit the agreement if the relationship no longer works.
Who Owns the Documentation and Administrative Access?
This is an area businesses often overlook.
Your company should understand who controls:
- Microsoft 365 administrative accounts
- Domain registration
- DNS
- Cloud platforms
- Firewall credentials
- Network documentation
- Backup systems
- Software administrator accounts
- Hardware documentation
- Vendor contact information
The MSP may manage many of these systems on your behalf.
But the business should not become dependent on a provider simply because it does not have access to its own technology environment.
Ask how administrative credentials are stored, how ownership is documented, and what happens to that information when the relationship ends.
What Happens When You Change IT Providers?
A good managed IT agreement should address the transition process.
That may include:
- Returning documentation
- Transferring administrative credentials
- Providing network information
- Coordinating with the incoming provider
- Removing the outgoing provider's access
- Transferring software or service relationships
- Returning client-owned equipment
The goal should be an orderly transition, not a difficult separation.
Your agreement should make it clear that your business retains ownership of its data, accounts, and appropriate documentation.
You should also understand whether transition assistance is included or billed separately.
Use This Managed IT Agreement Checklist
Before signing, confirm that you can answer these questions:
- What proactive services are included?
- How is reactive support billed?
- What cybersecurity services are included?
- How are backups monitored and tested?
- What work is considered a project?
- What is specifically excluded?
- How are after-hours and onsite services handled?
- What are the response expectations?
- How are issues escalated?
- How long is the agreement?
- How does renewal work?
- How can we cancel?
- Who owns our accounts, data, and documentation?
- What happens if we switch providers?
If those answers are clear, you are much less likely to encounter billing or service surprises later.
Why ANAX Uses More Than One Agreement Model
After 15 years in business—and with our founder bringing 25 years of MSP experience—we have learned that not every professional services firm uses IT support the same way.
Some businesses want the predictability of broad proactive and reactive coverage.
Others prefer to keep proactive management fixed while paying separately for some support activity.
That is why ANAX offers multiple agreement structures:
- CSA for broad proactive and reactive coverage
- BSA for proactive management plus a defined block of reactive support
- ESA for proactive management with reactive support billed separately
Our Block Labor & Services Agreement (BSA) is the most commonly selected model because it gives clients predictable proactive services while still providing visibility into actual reactive support usage.
The important point is not the acronym.
It is that the agreement should fit the way the business actually consumes IT support.
Comparing ANAX Managed IT Agreement Options
ANAX offers three agreement structures because different businesses consume IT support differently.
| CSA | BSA | ESA | |
| Agreement Type | Comprehensive Service Agreement | Block Labor & Services Agreement | Essential Service Agreement |
| Proactive IT Management | Included | Included | Included |
| Reactive Support | Broadly included | Defined block of support hours | Billed separately |
| Monthly Cost Predictability | Highest | Balanced | Lower fixed cost, more variable |
| Visibility Into Reactive Usage | Lower because support is broadly bundled | High because support hours are tracked | High because support is billed as used |
| Best Fit | Firms that want broad coverage and predictable monthly costs | Firms that want proactive coverage plus visibility and control over support usage | Stable firms with relatively limited reactive support needs |
| ANAX Client Adoption | Available based on client needs | Most commonly selected model | Available based on client needs |
The CSA can make sense for organizations that value maximum predictability and expect regular reactive support.
The BSA provides the same focus on proactive management while including a defined block of reactive support hours. It is ANAX's most commonly selected model because it gives businesses predictable recurring services while still providing visibility into how much reactive support they actually consume.
The ESA focuses recurring spending on proactive management, while reactive support is billed separately. For a stable environment with relatively few support requests, this structure may provide a better fit than paying for broadly bundled support.
The important point is not to choose an agreement based on which column contains the most services.
Choose the structure that best matches how your organization actually uses IT support.
A firm that regularly consumes significant reactive support may value the predictability of a CSA. A firm with moderate support needs may find the BSA provides a useful balance between predictability and transparency. A stable organization that requires relatively little reactive assistance may prefer an ESA.
That is why comparing managed IT agreements requires looking at both what is included and how your business actually consumes those services.
Why Local Support Can Matter
ANAX takes a local-first approach to hiring and service delivery.
Our staff is 100% U.S.-based, and our team primarily lives and works in the Las Vegas Valley.
For professional services firms in Las Vegas and Southern Nevada, that can matter when support requires:
- Onsite assistance
- Office network troubleshooting
- Hardware replacement
- Vendor coordination
- New office setup
- Escalation beyond remote support
Before signing with any MSP, ask who will actually be supporting your team and where those people are located.
Frequently Asked Questions
Should everything be included in a managed IT agreement?
Not necessarily.
A good agreement should clearly define what is included, what is excluded, and what is billed separately.
Clarity is more important than having the longest possible list of included services.
Are projects usually included?
Often, major projects are billed separately.
Examples include migrations, office moves, major network upgrades, and server replacements.
The agreement should define where normal support ends and project work begins.
Should cybersecurity be included?
Some security services may be included, while others may be separate.
The important point is to understand exactly which services are covered and who is responsible for them.
Should the MSP have access to all of our systems?
The MSP may need administrative access to manage the environment effectively.
However, the business should retain ownership of its accounts, data, and appropriate administrative access.
What is the most important part of the agreement?
For most businesses, it is clarity around:
- Scope
- Support
- Security
- Billing
- Ownership
- Exit terms
If those areas are well defined, the relationship is much easier to manage.
Final Takeaway
A good managed IT services agreement should answer three basic questions:
What are you responsible for?
What is your MSP responsible for?
What will you pay for separately?
For a 10- to 50-user professional services firm, the agreement should clearly define proactive management, reactive support, cybersecurity, backup, projects, exclusions, response expectations, ownership, and transition terms.
The best agreement is not necessarily the most comprehensive.
It is the one that gives both sides a clear understanding of how the relationship will work.
Want a Second Opinion on Your Managed IT Agreement?
If you run a 10- to 50-user professional services firm in Las Vegas or Southern Nevada and are reviewing a new MSP agreement—or wondering whether your current one still makes sense—ANAX can help.
We can review the structure, scope, exclusions, support model, and technology responsibilities with you so you can better understand what you are actually paying for.
Click here to schedule an initial consultation with ANAX.
There is no obligation to change providers. The goal is simply to help you evaluate the agreement with clearer expectations before you sign or renew.
