Stop losing money on
Virtual Assistant projects.
Without a clear maintenance boundary, 'quick updates' quickly mutate into unpaid full-scale projects that cannibalize your profit margins. You are a strategic partner maintaining a system, not a volunteer offering an unlimited buffet of your professional time.
Pro Tip
Include a 'Project Trigger' clause that explicitly states any maintenance request requiring more than 90 minutes of continuous labor will automatically be reclassified as 'New Project Work' and requires a separate estimate.
Uncompensated Feature Creep
Routine inbox or site maintenance slowly expands into full-scale system architecture or CRM migrations without a corresponding increase in pay.
Always-On Liability
The client assumes 'maintenance' implies 24/7 technical support, leading to burnout and legal disputes over missed response times during weekends or holidays.
Third-Party Software Blame
Being held financially responsible for a native bug or outage in a third-party tool (like Kajabi or Shopify) simply because you are the one assigned to 'maintain' the account.
Built from real freelance projects
This template is based on real-world scenarios across freelance projects where unclear scope, missing payment terms, and revision creep led to lost revenue. It is designed to protect your time, define expectations, and ensure you get paid.
What is a Virtual Assistant Maintenance Agreement?
A Virtual Assistant Maintenance Agreement is a legal contract that defines the scope of ongoing support for existing systems. It distinguishes routine upkeep—like software updates and link monitoring—from new project work, setting clear limits on hours, response times, and types of services included in a recurring retainer.
Quick Summary
This content outlines the essential components of a Virtual Assistant Maintenance Agreement, focusing heavily on preventing scope creep. It provides a strategic framework for distinguishing routine upkeep from new, billable projects. Key features include service exclusions, response time protocols, and pricing structures designed to protect a VA's time and revenue. The page serves as a guide for VAs to formalize long-term client relationships while ensuring they are fairly compensated for technical support and system longevity.
Why Virtual Assistants need a clear maintenance agreement
In the Virtual Assistant industry, the line between 'keeping things running' and 'building something new' is notoriously thin. For long-term clients, familiarity often leads to boundary erosion, where they expect complex upgrades under the guise of routine upkeep. A Maintenance Agreement is the only legal fence protecting you from 'support debt'—the phenomenon where you spend so much time fixing old systems that you have no room for high-ticket new business. This document formalizes your role as the guardian of the status quo, ensuring you are paid for the 'invisible' work like link checking, software updates, and database cleaning, while providing a clear contractual path to bill separately for new features or migrations. It transforms your relationship from a reactive task-taker to a proactive, protected service provider.
Do you need an invoice or a contract?
Invoices help you get paid, but they do not define scope, revisions, or ownership. For most projects, professionals use both a contract and an invoice to protect their work and cash flow. MicroFreelanceHub bundles both into a single link.
Real-world scenario
Sarah, a technical VA, managed a client’s membership site on a $500/month maintenance retainer. Her agreement clearly defined maintenance as 'bug fixes and monthly updates.' When the client launched a new product and asked Sarah to 'just quickly' build out a 10-page sales funnel and integrate a new payment gateway, Sarah didn't have to argue. She pointed to her Maintenance Agreement's 'Excluded Services' section. She explained that while she could certainly do the work, it was 'New Project Work' and not 'Routine Maintenance.' Because the boundary was already legally established, the client immediately signed a separate $3,000 project contract for the funnel build. Without the document, Sarah would have likely spent thirty unpaid hours on the project to avoid 'ruining' the long-term relationship.
🛡️ What this maintenance agreement covers:
- ✓Defined List of Routine Maintenance Tasks (e.g., plugin updates, link checks)
- ✓Maximum Monthly Support Hours Cap
- ✓Service Level Agreement (SLA) for Response Times
- ✓Emergency Support Surcharge Rates
- ✓Data Backup and Security Protocol Responsibility
- ✓System Status Reporting Schedule
Pricing & Payment Strategy
Maintenance pricing is most effective as a recurring flat-fee retainer that covers a specific 'menu' of upkeep tasks. Most VAs price this based on a 'peace of mind' model, charging 20-30% of their standard project rate for ongoing insurance that things will stay running. It is critical to include an 'Overload Rate' (typically 1.5x your standard hourly fee) for any maintenance hours that exceed the monthly cap, ensuring you are compensated if a particular month requires heavy troubleshooting.
Best practices for Virtual Assistants
The Maintenance Log
Provide a monthly report of 'invisible' tasks completed (e.g., updates, security scans) to prove ongoing value even when nothing breaks.
Tiered Priority Levels
Define 'Critical' vs 'Non-Critical' issues in the agreement to manage client expectations during high-volume periods.
1. Included Maintenance Tasks
The Service Provider shall perform the following routine maintenance tasks to ensure the stability and security of the Client’s existing systems:
- Monthly software, plugin, and application updates.
- Weekly verification of broken links and form functionality.
- Routine database cleaning and backup verification.
- Minor bug fixes to existing workflows (defined as fixes taking under 30 minutes).
2. Excluded Services (New Project Work)
Maintenance does not include the creation of new assets or the expansion of current systems. The following are explicitly excluded and require a separate Project Agreement:
- Migration to new platforms or software integrations.
- Design of new landing pages, funnels, or email sequences.
- Development of new features not present at the time of signing.
- Major troubleshooting caused by Client-initiated changes to the system code or settings.
3. Response Times & Availability
The Service Provider will acknowledge maintenance requests within 24 business hours. Resolution times are categorized as follows:
- Critical (System Down): Resolution efforts begin within 4 business hours.
- Standard (Bug/Update): Resolution within 3-5 business days.
- Non-Essential: Scheduled for the next monthly maintenance cycle.
4. Payment for Ongoing Support
The Client agrees to pay a recurring monthly fee (the 'Maintenance Retainer') for the services defined in Section 1. This fee covers up to [X] hours of support per month. Any hours exceeding this limit, or work requested outside of the maintenance scope, will be billed at the Service Provider’s 'Overload Rate' of $[X] per hour.
5. Cancellation Policy
Either party may terminate this Maintenance Agreement with 30 days' written notice. Upon termination, the Service Provider will provide a final 'Handover Report' detailing the current status of all maintained systems, provided all outstanding invoices have been paid in full.
Legal Disclaimer: MicroFreelanceHub is a software workflow tool, not a law firm. The templates and information provided on this website are for general informational purposes only and do not constitute legal advice.
Frequently Asked Questions
How is this different from a standard VA service contract?
A standard contract covers the initial build or general tasks, whereas the Maintenance Agreement is hyper-focused on the long-term health, security, and stability of existing systems with strict boundaries on new work.
What happens if the client asks for a 'small' new feature?
Under this agreement, small features are billed at a separate 'Change Request' rate or moved to a new project quote if they fall outside the 'Included Maintenance Tasks' list.