Nobody is watching the site
Plugins, certificates, or dependencies age until something breaks in public.
Platforms
A team to call after the launch.
Maintenance is how a site stays secure, fast, and editable. We cover updates, small fixes, monitoring, and the surrounding technical work: hosting, DNS, cloud deployment, and performance. Support is scoped. A care plan is not an unlimited rebuild, and we will say when a request belongs in a new project.
Problems we help with
Small fixes have nowhere to go
A broken form or a content issue waits because there is no support path.
Hosting and DNS are a mystery
The person who set up the domain has left, and the logins are unclear.
Services and deliverables
What this engagement can include. The final scope is agreed per project.
Website maintenance
Updates, backups checks, and small content or layout fixes.
Application support
Bug fixes and dependency care for apps we or another team built.
Website security hardening
Practical hardening: updates, headers, admin access, and backups.
Performance optimisation
Follow-up work when a live site has become slow.
Hosting configuration
The environment the site actually runs on, documented.
Domain and DNS configuration
Records for the site, email, and verification, changed carefully.
Cloud deployment
A repeatable way to ship the current application.
Cloud migration
A planned move between hosts, with a rollback idea.
Database optimisation
Queries and indexes when an application has grown.
Technical consulting
A written recommendation when you need a decision more than a build.
CRM implementation
Setup support when the CRM is part of the maintained system.
Third-party integrations
Keeping connections working when an API changes.
Product prototyping
A short technical prototype to test an approach.
MVP development
A small build under a support-to-product path when that is the right next step.
Key benefits
A known response path
You know how to report an issue and what the plan covers.
Fewer emergency rebuilds
Updates happen before they become outages.
Accounts in your name
Hosting and domains should be owned by the business, with us as users.
A line back to the original build
If we built it, the people supporting it understand the stack.
Tools and technologies
- Hosting panels
- Cloudflare
- AWS
- Vercel
- GitHub Actions
- Docker
Our process
01
Inventory
Domains, hosts, repositories, and who has access.
02
Stabilise
Backups, updates, and the issues that are already open.
03
Agree the plan
What is included each month, and what is quoted separately.
04
Review
A short note of what changed and what is coming due.
Relevant use cases
After a launch
The team who built the site stays on for the first months.
An inherited website
We take stock of hosting, plugins, and access, then propose a plan.
A move of host or domain
DNS and deployment changed with a checklist, not a hopeful click.
Questions
Related services
- Website DevelopmentBusiness websites, landing pages, and web applications built to explain the offer and collect the right enquiries.
- Custom SoftwareInternal tools, SaaS products, and integrations for workflows that spreadsheets and off-the-shelf apps no longer cover.
- CMS and E-commerceWordPress, Shopify, WooCommerce, and HubSpot builds that your team can edit after launch.
- Analytics and TrackingGA4, Tag Manager, Search Console, and event tracking set up so reports describe real behaviour.
Discuss Your Project
Tell us about your maintenance and support needs and we will suggest a sensible starting scope.