The problem it solves
Outdated components, a broken form, an expired SSL certificate or a missing backup can go unnoticed for months — until the site breaks or enquiries stop arriving. Routine checks surface problems early and make recovery predictable.
Who it is for
Owners of existing websites, WordPress projects, online stores and business systems — including sites built by other developers, after an initial review.
What maintenance includes
- Updates — core, plugins and libraries updated in staging first, then live
- Backups and recovery — automatic copies, storage location and periodic recovery tests
- Security — SSL expiry, access review, monitoring of suspicious activity
- Functional checks — forms, links, payment and key actions tested
- Speed and Google — monitoring of load time, Core Web Vitals and Search Console errors
- Small changes — text, images, prices and pages updated within an agreed limit
One-off task or recurring service
Both formats are possible. One-off — fixing a specific problem, a single audit or update. Recurring — monthly or quarterly checks with an agreed task list, response times and a report of work done. If a site rarely changes and has no CMS, quarterly checks are often enough; WordPress and stores need monthly attention.
A site built by another developer
We are often approached with a site whose author is no longer available. We first review it: code, hosting and domain access, technology used, outdated components, existence of backups. Then we say whether support is possible and what it costs — sometimes rebuilding is more rational than maintaining an outdated system.
What the service includes
- Agreed updates verified in staging first
- Regular testing of forms, links and core journeys
- Backup and recovery planning and testing
- SSL, domain and hosting expiry control
- Speed, availability and Search Console error monitoring
- Small changes within an agreed limit
- Issue prioritisation and work reports
- Advice on when to extend or rebuild
How we work
1. Discover
Define the goal, audience and essential functions.
2. Design
Agree on structure, visual direction and user journeys.
3. Build
Develop and test the agreed functionality.
4. Launch
Prepare publication, access and ongoing maintenance.
Choosing the technology
The final technology is selected after reviewing your requirements. These are possible directions.
What affects the timeline
Response times depend on severity and the agreed terms. A critical outage (site down, payment failing) and a text update are different priorities and are stated separately in the agreement. Continuous or emergency support needs a separate arrangement.
What affects the price
The price is defined by a one-off task or the scope of recurring work — how many components, how often they are checked and how many small changes are included. Substantial new features are a separate project. A concrete offer follows an initial review; see the pricing page.
Pricing ↗Why webandapp
We document the task, agree on stages and define the deliverables before development. You can see what is included and what needs a separate decision.
FAQ
Do you support sites built by other developers?
Yes, after an initial review. We need access to the code, hosting and required licences, then we say what is possible and what it costs.
Is a backup enough?
Besides having a copy, recovery must be tested — a backup that cannot restore the site is useless. The plan defines frequency, storage and the responsible person.
Is adding a new page included?
The limit for small changes is written into the agreement. A new section, functionality or design change is priced separately.
Why is a staging environment needed?
Updates are checked in staging first so a form, payment or design does not break unexpectedly on the live site. This matters most for WordPress and stores.
Is 24/7 support automatically included?
No. Service hours, channels and response times are agreed explicitly.