Bespoke service

Maintenance that keeps the website ready for business.

Launch is not the end of the work. I define what is monitored, how backups are created and verified, and how content or technical changes reach production.

Discuss your project

What is included

What you receive

  • 01

    Hosting environment suited to the technology and traffic

  • 02

    Backups with agreed retention and verification

  • 03

    Security and compatibility updates

  • 04

    Monitoring of availability, errors and important expiry dates

  • 05

    Controlled content and functional changes

  • 06

    Change records and an incident procedure

Who it is for

This service is for a website or application owner who needs a clear responsible contact after launch. The scope may be light for a static business website or more detailed for a store or application with a database, accounts and background jobs.

What it covers

We define hosting, domains and certificates, the update schedule, backups, monitoring and the route for requesting a change. I document dependencies and recovery steps that match the actual architecture of each system.

The problem we solve

Without ownership of maintenance, a small error remains unnoticed until a customer reports it. Another common problem is a backup that exists but has never been tested for recovery. Maintenance turns those responsibilities into agreed and verifiable procedures.

How I work

Before taking over, I review the code, hosting, access, databases, DNS and existing backups. We then define regular checks and what counts as a separate change. Larger functions receive their own scope and test version first.

What shapes the proposal

Scope depends on technology, traffic, system criticality, integrations, the frequency of content changes and the required recovery time. The proposal lists concrete responsibilities and reporting channels without unlimited items that can later be interpreted differently.

FAQ

Frequently asked questions

Do you maintain websites you did not build?

Yes, following a technical review. I first establish the condition of the code, hosting, access, licences and backups, then propose a scope.

Are content changes included?

They can be included in an agreed quantity or scoped separately. The proposal states exactly what enters regular maintenance.

Can backups be stored away from the main server?

Where the scope requires it, a copy is stored in a separate location. Location, frequency and retention are agreed for the specific system.

What happens when a larger new feature is needed?

Scope, risks and testing are defined first. A feature is not introduced as an unverified change directly in production.

Next step

Have a project that needs to work better?

Send me your goal and current situation. I will reply with a concrete scope proposal.

Start a project