What Website Maintenance Includes
Support isn't just "fix it when it breaks." It has three parts:
- Prevention: updating the CMS, plugins and libraries; monitoring backups, the SSL certificate, the domain and server disk space.
- Incident response: fixing bugs, restoring the site after outages and finding the root cause so the problem doesn't come back.
- Development: new pages, forms, features, integrations and changes for new marketing needs.
We also handle speed improvements, technical errors flagged in Search Console and redirects after structure changes. Updates are tested on a staging copy first and only then deployed to the live site.
Websites We Support
Corporate websites, service business sites, portals, online services with user accounts and landing pages. That includes sites built on WordPress, OpenCart, Laravel, Symfony, Next.js or Nuxt, as well as custom PHP or JavaScript solutions.
Large, high-traffic projects that need on-call coverage, scaling and dedicated infrastructure monitoring are handled under a separate service: support for large and high-load projects.
Who Needs Website Maintenance, and Who Doesn't Yet
It matters most for companies whose website is a key source of leads but who don't have an in-house developer. It is also for anyone whose freelancer disappeared or whose previous developer shut down, leaving no one who knows how the site works.
Ongoing support may be overkill for a simple brochure site that rarely changes and runs on a builder like Wix or Squarespace. The platform handles updates there, so occasional one-off edits are enough.
Plans and Response Times
- Block of hours. You buy a set amount of work, and we report the time spent. Purchased hours don't expire. It suits occasional tasks with a predictable budget.
- Monthly support plan. A fixed monthly fee covering availability monitoring, backups, CMS and plugin updates, and minor edits. It makes sense when the site truly matters to your business.
- Enhancements are done on a plan in sprints, with a dedicated developer or team assigned to you.
- Response times during business hours: site down, we reply within 1 hour and restore it within 1-8 hours; a key feature broken, such as payments or a form, response within 4 hours; a regular bug, within 1 business day.
- Outside business hours, we respond if we see a message or you call; terms are agreed individually.
- Communication: Jira or email.
One-off tasks are possible too: you reach out when you need something, we estimate it and get it done. When we take on support, we run a quick check of the site. A full technical audit is ordered separately.
If Another Team Built Your Site
We don't change someone else's site blindly. First, we figure out how it's built: which versions are installed, which plugins were modified, whether the CMS core was edited, and where backups are stored. You get a clear picture of what is in good shape, what threatens stability and what should be updated. Outdated PHP or CMS versions are the most common cause of hacks, and we cover them in our security, updates and technical audit service. Sometimes the honest recommendation is to stop patching an old site and rebuild it gradually, and we walk you through the options.
What You'll Need to Provide
- Access to hosting or the server, the domain, the admin panel, and the code if it is stored in a repository.
- Access to email, forms, the CRM and any third-party services connected to the site.
- A list of known issues and tasks that keep getting pushed back.
- A point of contact on your side who approves tasks and reviews results.
How We Prioritize Your Requests
We sort requests into three groups: critical (the site is down, lead forms don't work), important (a bug affects some visitors or employees) and planned (new features, improvements). Critical issues go first, even if other tasks are in the queue. We agree on the response rules for each group in advance, so nobody has to sort them out in the middle of an outage.
What Affects the Cost of Website Maintenance
- Technology and site condition: a site on a popular CMS with clean code is easier to support than an undocumented custom system.
- Scope of work: preventive maintenance only, or ongoing improvements and new features as well.
- Number of integrations: CRM, payment services, external APIs. Any of them can break on the other system's side.
- Response requirements: how quickly outages need attention, and whether you need a response outside business hours (terms are individual).
- Engagement model: one-off tasks, a block of hours or ongoing support.
Frequently asked questions
Can we switch our support to you from another contractor? Yes. We'll need access and, ideally, information from the previous team. If that isn't available, we'll still figure it out; the quick check will just take longer.
What do you do if the site goes down? First, we restore it from a backup or by rolling back recent changes. Then we find the cause and fix it so it doesn't happen again.
How do you report on your work? Every task is logged in a tracker with a description and time spent. We also send periodic summaries of completed work along with recommendations for the next period.
Can support be combined with marketing? Yes. We have SEO specialists and marketers on the team, so technical tasks for SEO get done without handoffs between different contractors.
Will you work on a site that runs on a builder like Wix or Squarespace? Usually that isn't needed, because the platform handles updates. If you want custom changes or a move to a more flexible platform, we can discuss it separately.
Do unused hours expire? No. Purchased hours don't expire, and if there are no urgent tasks, they can go toward preventive maintenance.
Why Promodex
Support is a core part of our work: Promodex has been in business since 2015 with 750+ projects completed, and we stay with clients after launch. Support projects in our portfolio include Art Bullet, Galaktyka, Europe Medicine and SteelWest. Every task is handled by our in-house team with no outsourcing, and you always know what is being done, what it costs and why.