IT Support and Services Agreement

What a good one includes

• A detailed description of the specific systems, hardware, and software supported, along with an explicit list of excluded tasks like hardware purchases or physical cabling.
• Clear Service Level Agreements (SLAs) defining response and resolution timeframes categorized by severity level, specifying what constitutes a critical emergency versus a routine request.
• Transparent pricing terms detailing the recurring monthly retainer, hourly rates for out-of-scope work, and exact billing schedules.
• A clause affirming that the client retains ownership of their proprietary data while the IT provider retains ownership of their custom scripts, tools, and methodologies.
• A robust limitation of liability cap that limits the IT provider’s financial exposure to a specific dollar amount or a multiple of the fees paid over a set period.
• Detailed protocols for terminating the contract, including how client data will be safely returned and how the transition to a new provider will be managed.

Common mistakes to avoid

• Failing to explicitly define what is out of scope, which inevitably leads to scope creep and unpaid labor for complex edge-case tasks.
• Setting unrealistic SLA response times that your team cannot consistently meet during peak hours or holidays, exposing you to breach of contract claims.
• Using a generic internet contract template that fails to address modern cybersecurity liabilities, data breach notification duties, or local privacy laws.
• Neglecting to outline the specific responsibilities of the client, such as maintaining active software licenses or providing physical access to server rooms.

Frequently asked questions