What website support includes and what it costs

Website support covers two kinds of work. Technical maintenance keeps the system alive: CMS and plugin updates, backups, protection against break-ins, checks on uptime and speed. Ongoing edits handle everything you ask us to change, from a new product to updated prices, a promo page or a repaired lead form. Both go into one contract, because on a live website they run side by side anyway.

Now about money. One-off requests are billed hourly, from $20 an hour, and you pay only for approved tasks. The technical plan starts at $400 a month. When you also need regular improvements, you take a block of hours: 40 hours a month from $800, or 80 hours a month from $1,600 with a dedicated manager. Below we break each format into its parts, so you can see what you pay for.

What happens to a website nobody looks after

A website lives in an environment that changes without your involvement. New CMS and plugin versions come out, the hosting company moves the server to a newer PHP release. A site untouched for half a year usually still works. A site untouched for two years returns an error on the payment page one morning, and the owner learns about it from a customer over the phone.

The awkward part is that a failure is rarely visible. The site opens, the catalog is in place, the buttons respond. Only the lead form stays silent, because the host tightened its rules for sending mail. Ads keep running, the budget keeps draining, and inquiries stop arriving.

• A break-in through an outdated plugin. Most infections we have cleaned up started with a known hole whose fix had been published long before the incident. The site then sends spam and the host suspends the account.
• Lost inquiries. The form shows a success message while the emails reach nobody. It can run for months until somebody opens the mailbox and checks by hand.
• Sliding search positions. Errors in the code, slow loading and broken pages push a site down in results. Winning positions back takes longer than holding them.
• No usable backup. At the moment a copy matters most, it turns out the host keeps one for a week and the freshest already contains the problem.

The work a site needs right after release we covered in What to do with your website after launch: the first 90 days. Support begins there, when real traffic uncovers scenarios that never came up during testing.

What technical maintenance covers

None of this work shows on the site. No new blocks appear, and yet the site opens every morning, payments go through, and mail reaches the manager.

Updates to the CMS, the plugins and the PHP version

Updates go in as a batch on a schedule, and always on a staging copy first. A conflict between two plugins or with the theme is normal, and it is better met on a copy than on a live store. After the update we walk the critical paths: catalog, cart, checkout, form submission, admin login. The PHP version gets its own attention, because hosting companies switch off old releases on their own schedule.

Backups that actually restore

A backup starts to mean something once you have tested a restore from it. We take the files and the database on a schedule, keep them away from the server, and now and then raise a test site out of the archive. Retention depth matters too. If the trouble appeared three weeks ago, yesterday’s copy will not save you. Copies kept on the same server disappear together with it.

Security and response to a break-in

The baseline looks modest and still closes most of the risk: limits on login attempts, two-factor authentication for administrators, service files removed from public reach, tracking of changed files. If a site is already infected, cleanup gets quoted separately, because it means scrubbing the code, changing every password, finding the entry point and lifting search engine penalties.

Monitoring of uptime and speed

The site gets checked automatically every few minutes, and our team receives the alert before visitors notice anything. Alongside uptime we watch the expiry dates of the SSL certificate and the domain, errors in the logs, and server response time. Speed gets a separate look, because it degrades quietly under new banners, extra analytics scripts and heavy photos in the catalog. The reasons behind such delays are laid out in Why your website loads slowly and how to fix it.

Edits, improvements and growth of the site

This part of support is easy to see, since the site has to change along with the business. Tasks come from you or from your marketer, we estimate them in hours and take them into work.

• Content. New products and categories, a service description, an article for the blog, price and stock updates, seasonal banners, changed contact details.
• Small improvements. An extra field in a form, a new filter in the catalog, a review block on the home page, the wording of the order email.
• Integrations. A payment gateway, a delivery service, an email platform, product feeds for marketplaces, exchange with an accounting system.
• Analytics. Goal setup, events for forms and phone clicks, preparing pages for advertising campaigns.
• Search work. Page titles and descriptions, cleanup of duplicates, redirects after a change in structure.

When a task outgrows support, we say so openly and quote it as custom development. A customer portal, two-way sync with a CRM or a shipping calculator of your own will not fit inside a monthly block of hours.

How much website support costs

The price follows the amount of attention a site needs every month. Page count is secondary, since a brochure site and a store with a few thousand products create different loads.

The hourly format looks cheapest while there are few tasks. As soon as requests become regular, a monthly plan wins on arithmetic and on convenience, because the team knows your project and keeps a copy of the site ready. We calculate the exact figure after a review, and the full scope is on the Project support and development page.

Which support format suits your website

Brochure site and corporate website

Changes here are infrequent, and the only requirement is that the site stays available and secure. The technical plan is enough for that, and the occasional edit, such as a new service or an updated price list, is billed hourly on top. A company that publishes a blog every month has reason to look at a block of hours.

Online store

A store needs attention almost every day. The assortment changes, payment and delivery services update their APIs, and promotions follow one another. Hours of downtime during the season turn into lost revenue. For stores we recommend a block of hours, and for large catalogs with automated feeds, the extended plan.

Web applications and customer portals

On Laravel projects with user roles, personal dashboards and several integrations, support sits close to continuous development. You need a testing environment, version control and releases agreed in advance. The 80 hour plan gives a predictable pace: the team plans a sprint, you see the tasks and the dates, and incidents get handled out of turn.

A project inherited from a previous contractor

Before naming a price we run an audit of the code, the versions, the plugins, the backups and any traces of outside interference. Sometimes it becomes clear that rebuilding the site costs less than keeping the current one alive, and we say so plainly. For borderline cases, When your website needs a redesign and how to keep your traffic describes the border between improvements and a full rebuild.

What to put in the support contract

A monthly plan without written terms slides into a payment for something nobody can describe. Before you sign, get answers to a handful of questions that a reasonable contractor answers without pausing.

• Response time. How quickly the team picks up a task and what counts as an emergency. A site that is down and a button color change deserve different priority.
• Scope of work. What the fee includes and what gets quoted separately. Cleanup after a break-in, migration to a new host and a redesign of a section usually fall outside the plan.
• Reporting. A monthly report with the list of tasks and the hours spent. Without it you cannot see where the paid hours went.
• Access and ownership. Hosting, domain, admin panel, repository and analytics registered in your name. The contractor works under a separate account that you can switch off at any time.
• Exit terms. Who hands over the backups, the documentation and the credentials if you change teams. This clause gets mentioned least often and saves the most trouble.

The same criteria help while you are still choosing a team. We wrote about checking a contractor in How to choose a web agency: criteria and red flags.

Common mistakes business owners make

Across the sites we support, owners repeat the same mistakes. Here are the ones that cost the most.

• Support gets remembered after the emergency. Recovering a hacked site costs more than a calm year of maintenance and eats up a week of the owner’s time.
• Updates are forbidden out of fear of breaking what works. Two years of that quiet leave a site with so many outdated components that a safe update becomes a project of its own.
• The contractor holds all the credentials. The domain is registered to a programmer who vanished long ago, the hosting is paid from his card, and nobody remembers the admin password. Recovering your own rights can take longer than building a new site.
• The plan is paid for and never used. The hours go to waste because nobody inside the company puts tasks into words. One responsible person on the business side is enough to make the block pay off.

If you are still planning the project and counting the full budget, start with what determines the cost of website development, where support appears as part of the first-year costs.

Conclusions

Behind the word support stands a concrete list of work with a measurable result. The site stays available, updated, protected and fast, and the changes you ask for appear on it within a week. The format follows the load of the project.

• A site with infrequent changes is covered by the technical plan, from $400 a month.
• A store or a fast growing site needs a block of hours: 40 hours from $800, 80 hours from $1,600 a month.
• Isolated tasks with no commitment are billed hourly, from $20 an hour.
• Before signing, fix the response time, the scope, the reporting and the ownership of access.

Amidcode runs projects on WordPress, WooCommerce, OpenCart and Laravel. Over the years we have built more than two hundred websites, and we still look after part of them. Send us the address of your site. We will look at its condition and say which support format is enough, with no push toward a larger plan.