01Why a routine and not a patch
Maintenance is not installing updates when something breaks. It is a routine: copy first, update, review, verify, and leave a record. What is not reviewed, no one knows if it works.
The promise is concrete: updates, backups, security review, and an alert when something fails, with the scope written and out-of-scope work quoted before it is touched.
It is not insurance against everything or a bank of hours. It is continuity with limits: if the hosting, a plugin, or a third party fails, it is coordinated and reported; it does not become a promise that cannot be kept.
Maintenance covers the agreed routine. A design change, a new functionality, or a migration is a different engagement and is quoted separately.
02What it covers and what it does not
Includes
- Updates of WordPress, theme, and plugins, reviewed before and after.
- Backups and verification that they can be restored.
- Periodic security review and alerts.
- An alert when something fails or requires a decision.
- A brief record of what was done and what is pending.
- Handling of incidents within the agreed scope.
Does not include
- Unlimited design, development, or content changes.
- New functionality, integrations, or migrations.
- Hosting, domain, and plugin or theme licenses.
- Campaigns, content SEO, or social media management.
- 24/7 urgencies or an SLA that is not agreed.
- Data recovery without a backup or forensic analysis.
03How we do it
-
01
Backup and check
Before updating, a backup is taken and it is checked that it can be restored. A backup that is not tested is not a backup.
What is needed Access, hosting, and someone to validate the result.
-
02
Update and review
Core, theme, and plugins are updated, and what the client uses is checked. If something breaks, it is reverted.
What is needed An agreed window and access to the environment.
-
03
Review access and security
Users, plugins, alerts, and surface are reviewed. Whatever is removed or changed is explained beforehand.
What is needed Access and decisions on what stays and what gets removed.
-
04
Verify the site
The homepage, forms, and checkout are checked if there is one. It is not taken as good just because the dashboard opens.
What is needed Someone to validate the real flow: content, forms, and sales.
-
05
Record and alert
A summary of what was done and what is pending is delivered; whatever falls outside the scope is quoted before it is touched.
What is needed An agreed contact channel for alerts and decisions.
04Price and scope
From €50/month. The scope is closed in writing: what gets updated, what gets backed up, what gets reviewed, and what gets handled. There are no unlimited changes and no single price for every case.
What determines the costNumber of sites and environments: one site does not cost the same as several, or a staging environment. · Plugins, theme, and builders: more surface to review and more risk of incompatibility. · Hosting, cache, and backups: what can be checked and what depends on the provider. · Criticality and hours: a store with checkout is not handled the same as an informational site. · Volume of changes: maintenance is not a bank of hours; changes are quoted separately. · Urgencies: outside the agreed scope and hours they cost differently.
- Number of sites and environments: one site does not cost the same as several, or a staging environment.
- Plugins, theme, and builders: more surface to review and more risk of incompatibility.
- Hosting, cache, and backups: what can be checked and what depends on the provider.
- Criticality and hours: a store with checkout is not handled the same as an informational site.
- Volume of changes: maintenance is not a bank of hours; changes are quoted separately.
- Urgencies: outside the agreed scope and hours they cost differently.
05Timelines and response
We do not publish a response time that is not confirmed. If it is agreed, it is written in the proposal with the scope and the hours; there is no implicit SLA behind this page.
What is committed: a backup before updating, a review after, and an alert when something fails. That is the routine, not a promise of total availability.
Urgencies are handled according to availability and scope. Outside the agreed hours they cost differently and are quoted before being executed.
If the hosting or a third party fails, it is coordinated and reported. The provider's responsibility does not become our own SLA.
Response policy: First response within 1 business day, Monday to Friday, Colombia and Spain time.
06Compatibility and access
We work on what you already have: WordPress, PHP, MySQL, hosting, theme, plugins, builders, and WooCommerce. The installed stack is part of the maintenance.
To start we need: the URL, WordPress admin access, hosting or SFTP access, backups, cache or CDN access if they exist, and someone who can validate.
Before touching anything: backup and rollback plan. If an update breaks something, it is reverted and what happened is explained.
The hosting is not changed and the theme is not rebuilt within maintenance. If the limit is there, it is justified in writing and quoted separately.
07What evidence we deliver
We do not publish client metrics without permission. There are no figures of incidents, times, or published cases: the evidence is the record of your site.
- Backups: when they were taken and when they were tested.
- Updates: what was updated and what was reverted.
- Reviews: access, security, and function.
- Incidents: what happened, what was done, and what is pending.
The record is the deliverable. If there are cases with permission later, they will appear with source and date; until then, nothing is invented.
08What you receive
| Deliverable | When |
|---|---|
| Monthly maintenance record | Each cycle |
| Backup and restore test | Before updating |
| Incident and decision alerts | As they occur |
| Summary of pending items and next step | At the close of the cycle |
| Proposal for out-of-scope work | Before it is executed |
09What happens next
Maintenance is not a project: it is an ongoing relationship. The scope is reviewed when the site, the hosting, or the workload change.
If you need a one-off intervention, it is quoted separately. If the problem is a rescue, a malware cleanup, or a speed improvement, those have their own service.
There is no published lock-in and no invented cancellation terms: they are agreed in the proposal and delivered in writing before starting.
See support and maintenance10Frequently asked questions
What does maintenance include?
Updates, backups, security review, verification, and an alert when something fails. It does not include unlimited changes or new development; that is quoted separately.
How much does it cost?
From €50/month. The final amount depends on the number of sites, plugins, hosting, criticality, and workload. The scope is closed in writing before starting.
Is there a response time?
We do not publish one that is not confirmed. If it is agreed, it is written in the proposal with the scope and the hours. There is no 24/7 and no implicit SLA.
Can I request changes?
Yes, but they do not enter the routine as unlimited changes. They are quoted before being executed and kept separate from maintenance.
What happens if an update breaks the site?
Before updating there is a backup and a rollback. If something breaks, it is reverted, diagnosed, and explained. If the fix is new work, it is quoted.
Do you work with my hosting, theme, and plugins?
Yes. We work on what you already have and document any exception, missing license, or hosting limit. If the hosting is the problem, it is proposed separately.