Corporate PC Maintenance Agreement: A Practical Guide

A PC maintenance agreement turns IT support from unpredictable break-fix invoicing to a predictable monthly service. For SMBs without a full internal IT team, it’s the natural model for keeping endpoints, servers, network and basic software running. This guide covers what’s typically included, how SLAs are structured, what’s not included (and shouldn’t be), and what to look for in a contract.

What a PC maintenance agreement typically includes

Endpoint coverage.

• Hardware troubleshooting for company-owned PCs and laptops.
• Operating system support (Windows, macOS).
• Standard application support (Office, Outlook, Teams, browsers).
• User account issues, password resets, profile problems.

Network & connectivity.

• Router and switch monitoring.
• Wi-Fi access point management.
• Internet connectivity troubleshooting (with ISP coordination).

Server & infrastructure.

• Server health monitoring.
• Patch management (Windows / Linux updates).
• Backup verification.

End-user support.

• Helpdesk via phone, email, ticket portal.
• Remote support sessions.
• On-site visits per SLA (typically Tier 2+).

Periodic maintenance.

• Quarterly health checks.
• Annual hardware inventory.
• Documentation updates.

How SLAs are structured

A useful SLA defines response time (when work starts) and resolution time (when issue is fixed) by severity:

Severity	Example	Response	Resolution
Critical	Server down, network outage	30 min	4 hours
High	Department blocked	1 hour	8 hours
Medium	Single user blocked	4 hours	1 business day
Low	New request, training	1 business day	5 business days

Business hours definition matters. “9–18 Mon-Fri” is the SMB standard. 24/7 is meaningful for organisations with off-hours operations but adds cost.

What’s typically NOT included (and shouldn’t be)

Hardware replacement cost. The maintenance agreement covers labour to diagnose and replace; the hardware itself is invoiced separately or comes from an inventory you own.

Software licences. Microsoft 365, Adobe, line-of-business software — you own those subscriptions. The maintenance covers troubleshooting, not licensing.

Project work. Office relocations, new server deployment, migration projects — these are scoped as separate engagements.

End-user training. “How do I use Excel” isn’t break-fix. Some agreements include light training; serious training is a separate engagement.

Major upgrades. Windows 11 migration, server consolidation, Microsoft 365 migration — project work.

The honest test: anything that’s predictable and ongoing should be in the agreement; anything that’s a one-time project should be scoped separately.

What to look for in a contract

1. Clear severity matrix. Specific examples for each severity level. If the contract just says “response time will be reasonable,” that’s not a real SLA.

2. Defined business hours. When does the SLA apply? After-hours premium charge structure (or 24/7 inclusion).

3. Number of devices covered. Per-device pricing or all-inclusive? Onboarding new devices process.

4. Escalation path. Tier 1 → Tier 2 → engineer with named contacts. Critical incident contact (phone, not just email).

5. Reporting cadence. Monthly ticket summary, quarterly business review, annual strategic planning.

6. Termination clauses. 30 or 60 days notice; what happens with documentation; data return.

7. Documentation ownership. The runbooks for your environment belong to you. If you change provider, the new one inherits the knowledge.

8. Change management process. How does the MSP request approval before making changes to your environment?

Pricing posture

Typical SMB PC maintenance pricing:

Scope	Approximate range
Per-device flat (helpdesk + basic monitoring)	30–60 USD/device/month
Per-user comprehensive (with security)	60–150 USD/user/month
Mid-market full-stack (with security + 24/7)	100–250 USD/user/month

Significantly cheaper than ranges typically signals corners cut on security or response time.

When a maintenance agreement isn’t enough

Some scenarios need more than a basic maintenance agreement:

• Compliance environments (KVKK strict scope, ISO 27001) — need full managed IT with documented controls, not just break-fix.
• 24/7 operations — need 24/7 SLA, not 9–18 business hours.
• Multi-site — need on-site coverage where users are.
• High-stakes data — need MDR (managed detection and response) on top of basic maintenance.

Frequently asked questions

Should the agreement include security? Basic maintenance includes AV / EDR monitoring. Advanced security (MDR, threat hunting, security operations) is typically an add-on or separate contract.

Are on-site visits included or extra? Depends. Many SMB-focused MSPs include 2–4 hours/month on-site as part of the agreement, with additional hours billed separately. Confirm in the contract.

What about new employees? Onboarding new users is typically included up to a defined volume (e.g., 5 per month). High-turnover environments need to discuss this.

Can we move to a different MSP later? Yes — with proper documentation transfer. The 30/60-day notice + transition plan should be in the contract.

Bottom line

A well-structured PC maintenance agreement converts unpredictable break-fix costs into a predictable, manageable monthly service. The discipline is in the SLA structure and contract clauses, not just the price. To draft or evaluate a maintenance agreement that fits your environment, contact us for a free initial review.