Preventive maintenance, one-off repair, or takeover
Website maintenance for small businesses
We first establish what system is running, who has access, whether a usable backup exists, and which existing faults require separate recovery work. Only then can one-off work and ongoing maintenance be separated.
Who is this for?
A small business with an existing WordPress or Next.js website that lacks clear ownership for updates, backups, smaller faults, or technical takeover.
What differs by platform?
WordPress work may involve core, themes, plugins, and the database. Next.js work involves dependencies, builds, deployment, hosting, and integrations. The scope names the layers that will actually be managed.
When is maintenance not enough?
A complete redesign, platform migration, or new feature system is a separate development project. Maintenance also does not imply continuous incident standby.
What can the maintenance scope contain?
Recurring work, one-off repairs, and earlier technical debt are listed separately so the checks and responsibilities are clear.
- an initial technology, hosting, and access inventory
- agreed WordPress or Next.js update tasks
- a backup and return-point check when included in scope
- separate lists for existing faults and new maintenance work
- a record of changes and checks performed
- identified technical SEO or performance risks
What happens after the first email?
- 1You send the URL, platform, and whether the need is maintenance, a fault, or takeover.
- 2The required access, hosting, source code, backups, and external services are reviewed.
- 3Urgent recovery, existing faults, and future recurring work are separated.
- 4Permitted changes, review schedule, responsibilities, and exclusions are recorded in writing.
- 5After a change, the functions named in the scope are checked and the result is documented.
Frequently asked questions
How often does a business website need maintenance?
There is no single interval for every site. WordPress depends on core, theme, plugin, and backup changes. Next.js depends on dependencies, builds, hosting, and external services. The review schedule is defined after the condition assessment.
What is the difference between maintenance and a one-off repair?
Maintenance covers agreed recurring checks and changes. A repair or rescue addresses a specific problem. Existing faults found during takeover are separated from future maintenance work.
What is required for a safe takeover?
An overview of the platform, hosting, source code, external services, access, and a usable backup. If there is no return point, creating one or recovering data may be a separate first task.
Can you take over an existing website?
Yes, when the initial review shows it can be managed safely. Access, dependencies, backups, and existing faults are documented before the takeover scope is agreed.
Share the URL, platform, and whether this is preventive work, a specific fault, or a takeover. Access is requested only in the agreed next step.