Skip to content

Services

Maintenance & support

We review and maintain existing websites, online stores and applications, including systems developed elsewhere. The initial review identifies the first priorities and what ongoing support can cover.

When this service helps

Maintaining an existing system starts with ownership, access and a way to recover it. The initial review creates a working record of its dependencies and the issues to address first.

Your website has custom code or integrations, but no clear maintenance responsibility.

Updates, failed imports, performance problems or small changes are accumulating without a plan.

A silver key with a blue head beside an open document folio and blank sheets

What you receive

Initial system review

An inventory of the code, hosting, dependencies, access, integrations and available documentation, with a prioritised list of issues.

Update and release checks

A process for applying updates and checking the affected pages, purchasing flows or application tasks before changes reach the live system.

Backup and recovery checks

A record of what is backed up, where copies are stored and who controls access. Restore testing can be included to check the recovery process.

Support responsibilities and change log

Defined contact and review arrangements, the systems covered, and a record of fixes and further changes. Monitoring can be included for selected failures or services.

Example workflow

Taking over an existing website

The first maintenance work establishes how the system operates and how changes can be recovered.

  1. Establish access

    Confirm ownership, accounts and available documentation.

  2. Review and prioritise

    Inspect dependencies, current failures and important user journeys.

  3. Check recovery

    Review backups and the process for restoring the system.

  4. Maintain and record

    Apply the planned changes, verify the affected tasks and log the work.

Questions about this service

Can support cover a website Lennos did not build?

Yes, following an initial review. Available access, the code and dependencies, documentation and the condition of the system determine what can be taken on and what needs attention first.

Does maintenance include new features?

Fixes, routine updates and further development are identified separately in the support arrangement. New features can be estimated and scheduled alongside the maintenance work.

How are support availability and response times defined?

The support arrangement records the contact method, availability, priorities and response expectations. These are agreed for the work being covered rather than assumed to be continuous or immediate.

Related reading

Practical notes on the decisions behind this work.

What needs to change?

Share the current website or tools, what needs to work differently and any deadline you already have.