Ongoing Website Maintenance & Support
For sites and web apps already in production — the small fixes, updates, and performance work that keep something reliable long after launch. Whether I built it or someone else did.
What's covered
- Bug fixes — things that broke, or that were quietly broken all along and someone finally noticed.
- Content and copy updates where you'd rather not touch the code yourself.
- Performance work — pages that have got slower as content and scripts accumulated.
- Dependency and security updates, so the stack doesn't quietly rot into something that can't be updated at all.
- Cross-browser and mobile QA — manual testing on real viewport sizes, not just a desktop glance.
- Uptime, hosting, and SSL issues — certificate renewals, DNS problems, deployment failures.
- Small feature additions — a form field, a new section, an extra page.
- Technical SEO upkeep — keeping sitemaps, canonicals, and structured data correct as the site changes.
Retainer or one-off
A monthly retainer suits sites that change regularly, or where you'd rather have someone on hand than scramble when something breaks. You get a predictable cost and a known person who already understands the codebase.
One-off blocks suit stable sites that need attention a few times a year. No commitment, no unused retainer sitting there.
If a retainer would mostly go unused, I'll tell you — a monthly invoice for nothing isn't a relationship worth having.
Being straight about response times
I'm one person. I reply personally within a day, and for most sites and small web apps that's the right level of cover. What I can't offer is 24/7 on-call coverage or a guaranteed one-hour response on a production outage — if your system genuinely needs that, an agency or an in-house hire will serve you better, and I'd rather say so now than let you find out during an incident.
What isn't covered
New feature development and full redesigns are separate projects, scoped and quoted on their own — see website development, web app development, or website redesign. Maintenance is about keeping what exists working well.
Common questions
I reply personally within a day. I'm a solo freelancer, not a support desk — so if you need 24/7 on-call coverage or a guaranteed one-hour response on a production outage, an agency or an in-house hire is the honest answer. For most sites and small web apps, next-day response is the right level of cover.
Yes. I'll want read access to the codebase and hosting first so I can see what I'd be taking on — that's how I scope it honestly rather than quoting blind and revising later.
Both work. A monthly retainer suits sites that change regularly or that you'd rather not think about. One-off blocks suit stable sites that need occasional attention. If a retainer would mostly go unused, I'll say so.
New feature development and full redesigns are separate projects rather than maintenance — they're scoped and quoted on their own. Maintenance covers keeping what exists working well.
You already own the source, assets, and credentials — that's true on every project I do. Ending a retainer means ending a retainer, not untangling yourself from a dependency.
Have a site that needs looking after? Tell me what it runs on and what's been going wrong, and I'll suggest the lightest arrangement that actually covers it.