Skip to content

Maintenance · revamps Labs

Website maintenance that keeps your site current and working.

revamps Labs keeps the site you already have current and working: CMS, plugin and framework updates tested before release, security patches, the changes your team can't make, every form and link checked monthly, and a written report on what changed. Set hours and a reply time on every plan.

LABS / MAINTENANCE
  • Updates tested before release
  • A reply time on every plan
  • Colombo team · Sri Lanka and international

The problem

The site still loads. That doesn't mean it works.

Plugins wait for updates nobody dares to run. A form stops sending and nobody notices for weeks. The person who built the site has moved on, and every small change becomes a quote. Risk builds quietly until it breaks in public. We take over the upkeep, test every change and report monthly. Now someone owns it.

  1. 01

    Updates nobody dares run

    The CMS and plugins are versions behind because the last update broke something. Each skipped release is a known hole left open.

  2. 02

    A form that went quiet

    Enquiries go to a spam folder or a mailbox that bounces. Nobody knows until a customer calls to ask why no one replied.

  3. 03

    The builder moved on

    The freelancer or agency has gone, logins are scattered across personal emails, and nobody knows how the site was put together.

  4. 04

    Small changes cost a project

    A price, a page or a team photo waits weeks for a quote, so the site drifts away from the business it describes.

  • EXAMPLE — HOW IT WORKS
  • ORANGE HIGHLIGHTS THE ACTIVE PATH OR RESULT

How revamps maintains a site

Monitor. Fix. Verify. Report. Every month.

Every plan runs the same loop. We watch uptime, forms, links and speed; catch what has changed or broken; fix it on a staging copy; check it on the live site; and write it down. The report ends with what to improve next, and next month's checks start there.

Hover or tap a node

Illustrative system map, not client data. Uptime comes from your hosting plan. The loop repeats monthly: what node 06 changes is checked at node 01 next month. Rebuilds and new feature sets are scoped as Web Development.

The process

From the first audit to a site someone owns.

Five steps. The audit and the takeover happen once; the monthly cycle runs for as long as the plan does, and each month closes with a report.

  1. 01

    Enquiry and reply

    Tell us the site, what it runs on and what keeps breaking. We reply with the questions that matter and the access we would need.

    Within 2 business days

  2. 02

    Baseline audit

    Versions, plugins, forms, backups, speed and who holds which login, reviewed. You get a written risk list, the plan that fits, or a plain note that the site needs rebuilding.

  3. 03

    Takeover and setup

    Logins moved into your name, a staging copy built, monitoring switched on and one request route agreed.

  4. 04

    Monthly cycle

    Updates tested on staging and released, changes from your queue inside the plan's hours, and forms, links and speed checked.

    Every month

  5. 05

    Report and improve

    A written report: what changed, what broke and how fast it was fixed, hours used, and the improvements worth doing next.

    Monthly

What's included

Anyone can click Update. The job is knowing nothing broke.

Six workstreams in every plan. Tiers change the hours, the reply time and how complex the site is: environments, integrations and the vendors we coordinate with.

  • Tested updates

    CMS core, plugins, themes, frameworks and dependencies updated on a staging copy first, checked, then released, with a backup taken before each release.

  • Application security

    Security patches for the CMS, plugins and code, unused plugins and old admin accounts removed, logins reviewed. Server and network security stay with your host.

  • Content and small changes

    New pages, prices, team photos, a section or a small feature, from one request queue, inside the plan's monthly hours.

  • Forms, links and flows

    Every form submitted end to end and traced to its inbox or CRM; broken links fixed.

  • Speed and conversion review

    Core Web Vitals and the main enquiry path checked monthly against the last report. A regression becomes a ticket, not a footnote.

  • Monthly report and access

    What changed, what broke, hours used and what to do next. Logins stay in your name, so you can leave with everything.

Fit

You don't need a fixer on call. You need an owner.

Maintenance works when the site is worth keeping and someone on your side can approve changes. A short call and the baseline audit tell us both.

  • A good fit if

    The site earns enquiries or sales and has to keep working. The CMS is behind, or the builder has left. You want changes made in hours, not quoted as projects.

  • Not a fit if

    You want one emergency fix at the lowest price and nothing after. You expect unlimited changes for a flat fee. You won't share admin access or approve releases.

  • Where maintenance stops

    Hosting keeps the site up and fast; maintenance keeps it current and working. A rebuild or new feature set is Web Development. Rankings are SEO.

revamps Labs · The monthly report

Every month, a report you can check.

Every plan produces one written report a month, in plain language, that someone outside the team could audit. It is the method, not a client result.

  • What changed

    Every update and change released, with versions before and after, the date and who approved it.

  • What broke, and how fast

    Each incident: when it was found and by whom, the fix, and the time from report to fix.

  • What was checked

    Forms submitted end to end, links crawled, Core Web Vitals against Google's thresholds, uptime from your host.

  • Hours and next steps

    Hours used against the plan's allowance, what is waiting in the queue and the improvements worth doing next, ranked.

Questions

Ask what's covered. Then ask what isn't.

Can revamps maintain a website built by another team?

Yes, if the platform is maintainable. We start with a baseline audit of versions, plugins, forms, backups and logins, move every login into your name, and tell you in writing if the site needs rebuilding rather than maintaining.

What is the difference between hosting and maintenance?

Hosting keeps the site up and fast: the server, uptime, backups and the environment it runs on. Maintenance keeps it current and working: updates, security patches to the site itself, content changes, form and link checks, and a monthly report. Each has its own plan, and many sites need both.

Does maintenance include content updates?

Yes. Depending on the plan, routine content and layout updates can be handled as part of the recurring support queue.

What if the site needs larger rebuild work?

revamps will separate ongoing maintenance from larger structural work so the support plan stays clear and predictable.

Enquire

Tell us what keeps breaking. We'll come back with a plan.

Four short fields, about a minute. Include the site's address, what it runs on and what keeps breaking. We reply within 2 business days with the questions that set the plan and the access we'd need. If the site is down right now, call or WhatsApp instead.

Prefer email? [email protected]

Fields marked * are required.

The live URL, the platform (WordPress, Shopify, custom), who built it, and what has broken or keeps waiting.