Website AMC
An annual maintenance contract that keeps a live site patched, monitored and reported on, priced against your actual stack rather than a flat retainer.
Scope is agreed per engagement once we understand what you need.
How it works
Audit
Existing site reviewed for uptime history, outstanding security patches and content drift.
Plan
Maintenance scope and response times agreed against the client's own stack and risk tolerance.
Monitor
Uptime and error monitoring runs continuously against the live site.
Patch
Framework, dependency and security updates applied on an agreed cadence.
Report
A monthly summary of what changed, what was patched and why.
What's included
- Uptime and error monitoring
- Framework and dependency updates
- Security patching on an agreed cadence
- Monthly change report
- Agreed response times for reported issues
Questions
What does a website AMC include?
It covers the ongoing work a live site needs after launch: uptime and error monitoring, framework and dependency updates, security patching on an agreed cadence, and a monthly report summarising what changed and why. Because this is priced as a custom quote, the exact scope is agreed against your stack first, not sold as a fixed package. A Next.js site on Vercel needs different upkeep than a site on other infrastructure, and the AMC scope reflects that rather than assuming one shape fits every client. What it does not include, unless agreed separately, is new pages, new copywriting or a redesign; those are treated as project work, quoted on their own. The point of an AMC is that the site keeps working quietly, with someone watching it, rather than surfacing problems only when a client notices something is broken.
How fast do you respond to an issue?
Response times are set during the planning step and written into the agreement, because a checkout flow going down and a broken footer link carry different urgency and we scope for that difference upfront rather than promising one blanket number for every issue type. Monitoring runs continuously, so most problems are caught before a client even notices or reports them, which is the main value of an AMC over ad hoc fixes booked after something breaks. When something is reported, it is triaged against the agreed severity levels and worked in that order, not first-come first-served. This is a quote-based service precisely because response commitments vary by stack, hosting and how much of the surrounding infrastructure is under our control, so we agree the numbers with you before the contract starts, not after something has already gone wrong.
What happens if we don't have an AMC?
The site keeps running, but nobody is watching it. Dependencies go unpatched, which is how most small sites eventually get compromised, and framework updates pile up until a routine change becomes a risky one. Nothing about launch requires an AMC. It is optional, and we hand over full ownership and credentials at launch either way, so you are never locked into taking one. What an AMC buys is the difference between a problem being caught by monitoring at 2am and a problem being caught by a customer the next morning. For a site that is quote-led with no live checkout, like a catalogue or corporate build, the risk of going without is lower than for a site handling live transactions, and we say so plainly when a client asks whether they need one.