Small company website
from €99/mo
For stable brochure sites that need updates, backups, and uptime alerts.
- Core, plugin, and theme update cycle
- Daily backups with restore path
- Uptime monitoring and email alerts
- Email support for routine issues
Choose a published maintenance plan for your current website. Active includes staging-tested updates and a four-hour response window for critical incidents.

Essential covers routine maintenance for a stable company website. Active adds staging-tested updates and four-hour critical response. On-call adds the shortest response window and weekly reporting. Prices exclude VAT.
Small company website
from €99/mo
Recommended for commercial websites
from €499/mo
Business-critical website or shop
from €999/mo
Monthly price per website, excluding VAT. Before onboarding, we check WordPress, hosting, plugins, and existing damage. Cleanup or migration is quoted separately. Minimum term is 3 months, then monthly cancellation.
| Coverage | Essential | Active | On-call |
|---|---|---|---|
| WordPress, plugin, and theme updates | Regular | Weekly | Prioritised |
| Backups | Daily | Daily | Daily |
| Restore test | Quarterly | Monthly | Monthly |
| Staging test before production | Risk-based | Included | Included |
| Uptime monitoring | Included | Included | Included |
| Critical response | Next business day | Within 4 hours | Under 1 hour |
| Report | Monthly | Monthly | Weekly |
An automatic update can conflict with the theme, checkout, form, or another plugin. A backup also needs a known restoration path before it becomes useful.
Every plan includes daily backups, uptime monitoring, updates, support, and a scheduled restore test. Active and On-call test updates on a staging copy before they reach the live website.
The comparison table shows update frequency, restore-test frequency, reporting, and the response window for a critical incident.
| Generic maintenance plan | Some Tech Work maintenance |
|---|---|
| Plugin updates | Staged updates |
| Backup plugin | Rollback-ready releases |
| Ticket queue | <1h critical response on On-call plan |
| Monthly report | Performance and security monitoring |
| Reactive fixes | Rollback-ready incident response |
| Unknown engineer | Small controlled improvements |
| No pattern review | Strategic review when patterns appear |
The exact coverage depends on the plan. The recurring work includes updates, backups, monitoring, support, reporting, and defined checks after changes.
We review WordPress core, plugin, and theme updates on the schedule in your plan. Active and On-call test them on staging before release and record what changed.
Known vulnerabilities are assessed, prioritized, and patched with a tested path to production. Security updates are handled with urgency and context.
Monitoring tracks uptime, errors, and service behavior continuously. Incidents are escalated with defined response windows by plan.
Every plan includes daily backups. Restore tests run quarterly on Essential and monthly on Active and On-call, so recovery does not depend on an unchecked archive.
Maintenance work is tested in staging first, including dependencies and key flows. Production releases follow controlled deployment steps.
We track load behavior and key speed indicators so changes do not quietly degrade user experience. See our website performance monitoring approach.
Editor workflows, governance rules, and handover training are documented so teams can ship routine changes without introducing release risk.
Reports cover incidents, updates, performance patterns, and upcoming risks. Recommendations focus on risk reduction and practical gains.
Uptime monitoring, anomaly detection, and performance regression alerts before small issues become business problems.
We review core, plugin, and theme updates. Active and On-call use staging before production, while urgent security patches are prioritised.
Daily backups are included. We test the restoration path quarterly on Essential and monthly on Active and On-call.
Active and On-call include staging tests before production. Essential uses staging when the update risk requires it.
Essential responds by the next business day, Active within four hours, and On-call within one hour. Response time confirms work has started; resolution depends on the cause.
Copy updates, content changes, minor UX improvements, and low-risk feature work happen without bypassing release discipline.
The plan covers the services listed in its package and comparison table. Existing malware, a broken site inherited at onboarding, hosting migration, redesigns, and new features are reviewed and quoted separately.
Before the contract starts, we check WordPress, hosting, plugins, access, backups, and existing damage. You see any required cleanup before committing to the monthly plan.
If your team needs this operating model, start with a request a maintenance audit.
Essential runs routine updates and quarterly restore tests for a stable company website.
Active adds staging tests, weekly updates, performance monitoring, and a four-hour critical response window.
On-call adds an under-one-hour critical response window, faster security work, and weekly reporting.
Maintenance works best when aligned with WordPress consulting and implementation for architecture and release quality. For a fixed-price rebuild path, see WordPress site upgrade packages.
Ongoing exposure control requires website security (malware & hardening) with a 1–4 hour first response for accepted critical incidents.
Reliability includes speed. We apply website performance monitoring to catch regressions early.
Organic visibility and speed are connected through technical SEO and performance.
Support should protect business outcomes through conversion-focused website improvements.
See the operating context in our selected work for Vegconomist and Leverage Edu.
Weekly, monthly, and quarterly maintenance tasks before small issues become incidents.
How vulnerabilities appear, why updates need testing, and what safe patching looks like.
Why production should not be the place where updates are tested.
How to stop websites getting slower after launch.
Published provider prices, contract scope, and the difference between response, recovery, and resolution.
Yes. WordPress maintenance is a core part of this service, including core, plugin, and theme updates, staged testing, security updates, and incident response.
No. We support WordPress, headless builds, ecommerce systems, and other business-critical websites where reliability and response speed matter.
Active and On-call include staging tests before production. Essential uses staging when the change risk requires it. Every plan has a backup and restore path; the comparison table shows the exact testing and response coverage.
Yes. Backups and rollback readiness are included. Recovery paths are documented as part of release discipline from the start.
Yes. Accepted critical incidents target a first response within 1–4 hours via our website security service. The clock starts after scope, availability, and safe access are confirmed.
Yes. Maintenance includes performance monitoring and targeted remediation work when regressions appear. Serious website support includes speed as an operating concern.
Yes. Controlled change capacity is built into plans so copy, UX, and minor technical updates can ship safely through staging.
Yes, for teams where WooCommerce failures affect orders, operations, or customer trust. The approach is risk-led and release-disciplined.
Cheap maintenance plans optimize for task volume. We optimize for operational risk reduction with staged updates, rollback readiness, and incident accountability.
Every plan is led by someone who understands your stack and release history. You are not routed through a generic ticket queue.
Ready to stabilize your support model? Request a maintenance audit.
Tell us what needs fixing
We read every brief and reply within one business day.
Prefer to talk first?or request a tech stack audit →or email us directly →
Not sure where to start? Send the stuck decision, workflow, or page. We will say whether you need a diagnostic call, a tech stack audit, or a different first step.