I need access to the following:

• Git repository (E.g. GitHub or BitBucket)

• Access to server management software (E.g. Ploi or Forge)

• Access to hosting provider control panel

• SFTP access

• SSH access

I can help you pull this information together and liaise with your in-house team, web developer, or hosting provider to get access to what I need to manage your website and server seamlessly.

Startup Core, Corporate Plus and Enterprise Max

Annual billing is used for these plans. Invoices cover a full year of support and maintenance, with payment due on receipt. Once I have access to your website and servers, your first update will begin.

Annual invoicing ensures consistent, reliable maintenance throughout the year while keeping administrative costs low. Each invoice clearly states your chosen plan and includes the maintenance schedule for the year ahead.

Essential Fix

This option is a one-off service with a single payment due on receipt. As soon as I have access to your website and servers, I’ll begin your update.

Critical Fix

A minimum upfront payment of 6 hours is required. Once payment is received and I have access to your website and servers, I’ll begin resolving your website issues.

All maintenance plans (Startup Core, Corporate Plus, and Enterprise Max) have a 12-month minimum contract period. This ensures continuity of service and allows me to plan and deliver proactive maintenance throughout the year.

Yes. Before every maintenance update, I take a fresh backup of your production site and store a local copy of your website and its assets. This copy is regularly refreshed by pulling from the production site.

All updates are version-controlled using Git. After testing locally and on a staging environment, if an update still causes an issue on production, I can quickly roll back to the previous working version.

The backup process is a standard part of maintenance - no request or action is needed on your end.

All updates are tested in two stages before reaching your live site:

1. Local testing – Updates are applied in a local environment first.

2. Staging testing – They are then pushed to a staging server, which mirrors your production hosting environment.

On staging, I run automated crawls across every page to check for errors (such as 5XX or 404s). I also test site functionality manually—for example, contact forms and interactive features—to ensure everything works as expected.

Only when both automated and manual tests confirm stability do I apply updates to your production site, timed for low-traffic periods.

Maintaining both staging and production environments ensures issues are caught early, reducing risk and protecting your business operations.

Although problems are rare thanks to thorough testing, I follow a defined recovery process if an issue arises:

1. Immediate restoration – Your site is restored within minutes using the fresh backup taken before maintenance began.

2. Root cause analysis – I investigate the issue on the local copy and staging environment to identify what went wrong.

3. Fix and retest – A solution is developed and thoroughly tested on staging before reapplying the update to your live site.

4. Clear communication – You receive regular updates and an estimated timeline until the issue is resolved.

This approach ensures downtime is kept to a minimum while maintaining the safety and stability of your website.

Yes. I’ll always notify you in advance of any scheduled maintenance.

• Timing agreed in advance: Maintenance is planned for low-traffic periods and the exact window is confirmed with you beforehand.

• Coordination with your activity: I avoid maintenance during marketing campaigns or when your team is making in-house updates.

• No action needed: You’ll receive clear notice so you can plan accordingly if needed.

If you’d like, I can add your preferred maintenance windows (days/times to avoid) to your account notes.

The length of a maintenance window depends on what’s being updated. It can range from around 30 minutes to a few hours, depending on the scope and complexity of the updates.

All updates are fully tested locally and on staging before being deployed to production. The actual push to production only takes a few minutes, but the scheduled window allows time for thorough testing and verification.

You’ll always be notified in advance of the expected timeframe, and maintenance is carried out during low-traffic periods to minimise disruption.

Update frequency depends on your chosen plan:

• Startup Core – 4 scheduled updates per year (staging + production)

• Corporate Plus – 6 scheduled updates per year (staging + production)

• Enterprise Max – Monthly updates for both website and servers, ideal for mission-critical sites

Every update is fully tested on staging before being deployed to your live site.

Backups and testing

• Full site backup taken before any changes

• Updates tested on a staging environment first

• Automated and manual checks run across your site’s functionality

• Changes deployed during low-traffic periods to minimise disruption

System updates

• Statamic CMS and Laravel framework upgraded to the latest stable versions

• Ubuntu server security patches and system updates applied

• PHP configuration updated

• SSL certificates checked and renewed if needed

Troubleshooting & support

• Each plan includes a set number of troubleshooting hours

• Can be used for CMS support, resolving technical issues, content management assistance, or general maintenance queries

I only offer three standard maintenance plans—Startup Core, Corporate Plus, and Enterprise Max. These cover the most common maintenance needs for Statamic websites at different business scales.

By standardising plans, I can provide a consistent, reliable service while keeping costs predictable and processes efficient.

If you’re unsure which plan best fits your needs, I’ll recommend the most suitable option based on your site’s size, complexity, and business priorities.

Not as part of the maintenance service. Maintenance is focused solely on keeping your Statamic CMS and hosting environment secure, updated, and running smoothly.

If you’d like new functionality, design changes, or other custom development work, I can provide a separate quote. This way, maintenance remains streamlined for essential updates, while enhancements are handled through the standard project process.

Feel free to get in touch anytime to discuss improvements - I'm always happy to provide a tailored quote for development work.

While I don’t provide 24/7 emergency cover, I’ll always do my best to help if a critical issue arises between scheduled updates. I can assess the situation and apply emergency fixes where possible, based on my availability.

Any unused troubleshooting hours in your plan will be used first, and if more time is required, I’ll provide a clear estimate before proceeding.

The regular maintenance schedule itself is designed to minimise the chance of emergencies by keeping your site secure and up to date.

If you use up all the troubleshooting hours included in your plan, you can purchase additional blocks of 6 hours for £500. These hours are added to your account and can be used as needed for support, fixes, or technical assistance.

In practice, most clients never need extra hours, the included allowance usually covers typical support and maintenance needs.

The maintenance service is focused only on keeping your Statamic CMS and Ubuntu servers secure, stable, and up to date.

It does not include:

• New development or added functionality

• Design changes or content updates

• Search engine optimisation (SEO)

Any of these can be arranged separately with a tailored quote. This keeps the maintenance service streamlined and dedicated to essential system updates, security patches, and smooth performance.

No. Your site will stay online and accessible to visitors throughout the maintenance process. All testing and preparation happen on the staging environment first, and updates are deployed to your live site in a way that keeps it operational.

The maintenance process is designed for continuous availability, so your customers won’t experience downtime while the underlying systems are updated.