+7 993 408-61-15

Blog — article

What Website Maintenance Costs and What It Includes

Your site launched successfully, but a month later it stopped loading. Three months in, it got hacked and started sending spam. Or the contact form broke after an update and you lost leads for three weeks without knowing. Website maintenance is insurance against these scenarios - a set of tasks that keep your project alive.

August 31, 2026 · EFIMOV DEV

What's Included in Technical Website Support

The basic package covers CMS updates, plugin updates, and server PHP upgrades. WordPress, Bitrix, custom platforms - they all receive security patches, and if you don't install them, your site becomes vulnerable. Exploits get published openly, and bots scan the internet looking for outdated versions.

Uptime monitoring means automatic checks that your site loads, forms send emails, and checkout works. If something breaks, the contractor gets notified and fixes it before you learn about it from an angry client call.

Backups are copies of your site and database. They run daily or weekly and get stored on a separate server. If your site breaks after an update or gets hacked, you roll back to yesterday's version in ten minutes instead of rebuilding from scratch.

Minor content edits - changing a phone number, uploading a news item, fixing text in a block. Usually included in the package with a limit, say up to two hours of work per month. More than that and you pay hourly.

When Support Isn't Necessary

If you have a landing page on Tilda or WordPress with a page builder that you edit yourself, and there's no payment processing - technical support is overkill. The hosting platform updates PHP automatically, Tilda patches vulnerabilities on their end, and backups are handled by the platform.

If your site is static (coded without a CMS, unchanged for years) and sits on decent hosting - you can also skip monthly maintenance. Just check quarterly that it loads and keep a copy of the files yourself.

Support starts paying for itself when the site generates revenue or leads, when it has integrations (CRM, payments, user accounts), when you don't understand code and don't have time to troubleshoot a technical failure on Friday evening.

Website Support Costs: What Determines the Price

Subscription model - a fixed monthly fee for a package of services. Market prices start around $40-70 for a minimal set (updates, backups, monitoring) and go up to $400-700 for complex projects with integrations, high traffic, and SLA guarantees.

At EFIMOV DEV we publish a starting price range for support on our site - the exact amount depends on technology stack, volume of edits, and response time requirements. For an online store with a dozen plugins and weekly edits, the package costs more than for a React corporate site that updates quarterly.

Hourly billing is an alternative to subscription. You pay only when you need something: something broke - they fix it, need an edit - they do it. Convenient if edits are rare, but risky: when an emergency hits, the developer might be busy and you join a queue. With a subscription you're buying priority.

Hosting and domain usually aren't included in support costs - those are separate payments. Hosting for a small site runs $3-7 per month, a domain around $10-15 per year. If the contractor bundles this into the package, verify who controls the access: domain and hosting should be registered under your name, otherwise you might lose your site if the contract ends.

What to Check in a Maintenance Contract

SLA - response time and resolution time. A good contract has numbers: 'critical error - 2 hour response, 4 hour resolution during business hours.' A bad one has vague promises like 'we'll fix it promptly.' Without SLA, you can't demand compensation for downtime.

What counts as a minor edit versus a separate task. Changing a phone number is an edit. Adding a new site section is a separate task requiring an estimate. Without this boundary, disputes happen.

Who handles backups and where they're stored. Hosting might do automatic backups but store them on the same server - that's not a backup, that's a copy in the same house that can burn down. Normal practice is copies on separate storage or in your hands.

Exit terms. What happens if you decide to change contractors: will you get source code, access credentials, site archive. If this isn't in the contract, problems transferring the project can arise.

How Website Support Differs from Development Work

Support means preserving what exists. Updates, monitoring, backups, fixing bugs that appeared on their own (after updates, due to incompatibility). Development means adding new functionality: a form, filter, service integration, new page block.

The line blurs, and unscrupulous contractors exploit this: they might present a minor enhancement as complex work and bill accordingly. Or the opposite - drag out a major edit within the subscription package, delaying deadlines.

A good contractor clearly separates: if it fits within the package hour limit - they do it immediately, if not - they provide an estimate and get approval. Ask at the start of the relationship for a couple examples of what counts as an edit versus development work to remove ambiguity.

How to Tell You're Getting Good Service

You learn about problems from the contractor, not from clients. If a form broke and you heard about it three days later from support - there's no monitoring, they're faking it.

They send reports: what was updated, how much time spent on edits, what issues were found. Doesn't have to be weekly, but monthly is normal practice. Without reports, you don't understand what you're paying for.

Questions get answered same day, minor edits done within two or three days. If every phone number change turns into a week-long email chain - that's not support, that's theater.

They explain causes of problems and propose solutions. 'Site went down due to outdated plugin, updated it, won't happen again' - good. 'Fixed it, everything works' with no explanation - bad, means they didn't dig into the cause and it will repeat.

What to Do If Budget Is Tight

Minimum package means updates, backups, and availability monitoring. Costs $40-70 per month and covers the main risks: hacking and data loss. Handle content edits yourself through the admin panel or pay hourly when several tasks accumulate.

If even that's expensive, arrange with the developer for one-off work as needed. But then you need to monitor yourself: log into the admin monthly and check for available updates, check weekly that the site loads and forms work. And keep a fresh backup - ask the contractor to show you how to download it.

You can economize on support if the site isn't critical to the business. But if leads, sales, or bookings come through the site - an hour of downtime can cost more than a month of maintenance.

In short

Website maintenance isn't a luxury, it's basic hygiene if the project makes money. A minimal package covers the main risks and costs less than one day of downtime. The key is a clear contract with understood boundaries and a contractor who explains what they're doing.

Frequently asked

Can I maintain the site with my own employee?

You can, if they know how to work with your CMS, understand how to update plugins and PHP, and can quickly roll back changes if something breaks. In practice this rarely pays off: paying a programmer on staff costs more than a subscription, and a generalist without experience on your stack will create more problems than they solve.

What happens if I don't update the site?

Sooner or later it gets hacked. Vulnerabilities in popular CMS platforms get exploited at scale - bots scan sites automatically. After a hack, spam, viruses, or miners get uploaded to your site, Google blacklists the domain, and visitors see a warning. Recovery costs more than a year of maintenance.

Does support include SEO and content management?

No, those are separate services. Support means technical site health. SEO, social media management, article writing, catalog population - those are different specialists and different contracts. Some studios offer bundled packages, but the price reflects that.

How often should backups run?

Depends on how often the site changes. An online store with daily orders - daily backup. A corporate site that updates monthly - weekly backup is sufficient. The key is that copies get stored somewhere other than the same server as the site, otherwise when equipment fails you lose both site and backup.

Need a website or automation?

Tell us what you need - we come back with an estimate and a timeline within a day. No long approval chains.

Message us on Telegram