Maintenance and support clause for freelancers
A maintenance and support clause: what ongoing support covers after launch, how many hours, and what's billed on top.
Maintenance and support clause: copy and adapt
After delivery, the Provider will provide maintenance and support for [amount] per month, covering up to [4] hours of: software and plugin updates, security patches, backups and minor content changes. Unused hours do not roll over. New features, redesigns and work beyond the monthly hours are billed separately at [rate]. Either party may end the support arrangement with [30] days' notice.
When to use it
After any website, app or system launch. It turns 'can you just fix this quickly' after handover into recurring, paid work.
Variants by trade
Bug fixes only
For [60] days after launch the Provider will fix, at no charge, defects where the delivered work does not match the agreed specification. Support after that period is billed at [rate].
Priority support
Critical issues (site down, checkout broken) receive a response within [4] business hours; other requests within [2] business days.
Frequently asked questions
Should maintenance be in the same contract as the build?
It can be a clause in the build contract or a separate retainer. Either way, decide it before launch, not after the first emergency.
Do unused support hours roll over?
Usually not. Rollover turns a quiet month into an unexpectedly heavy one later; if you allow it, cap it.
Put this clause in a contract they sign today.
Clinch drafts the full contract with AI from a template, your client signs from their phone without an account, and the deposit is requested the moment they sign.
Start the contract with ClinchRelated clauses
These clauses are general templates, not legal advice. Laws vary by country and state; for high-value or unusual deals, have a lawyer review your contract.
Also available in: Español · Deutsch · Français · Italiano · Português (Brasil)