What website support is
Website support (or website maintenance) is the work a development team does after launch. A site isn’t finished on release day: the CMS and modules get updates, new services and products appear, marketing asks for new pages, and the business needs new integrations. Someone has to do all of this quickly and carefully, without breaking what already works.
“Support” usually covers two different things, and it pays to keep them apart:
- Technical support keeps the site running: updates, security, backups, the server.
- Development work keeps the site growing: new pages, features, integrations, design.
The first part is regular and predictable, so it’s convenient to pay for it monthly. The second depends on the business’s plans, so it’s billed in hours or per task.
Signs your site needs regular support
- The CMS and modules haven’t been updated in a while, and the admin panel keeps showing new-version notices.
- The site loads slower than a year ago, especially on mobile.
- Page or indexing errors are piling up in Google Search Console.
- Marketing waits weeks for new pages and banners.
- Nobody in the company knows exactly where the access details are or when the last backup was made.
If two or more of these sound familiar, it’s time to agree on regular support with a team.
Technical support: what’s included
| What we do | Why |
|---|---|
| CMS, module and library updates | Vulnerabilities get closed, and the site stays compatible with new browser and server versions |
| Backups | Files and the database are stored separately from the site, and restores are tested regularly |
| SSL certificate | Renewed on time, so the site always opens over https |
| 24/7 monitoring | Uptime, speed, form and payment errors — the team sees a problem before your customers do |
| Security | Admin protection, password and access rotation, bot and spam filtering |
| Server | OS updates, disk space, load, email and domain |
| Integrations | Enquiries reach the CRM, payments and delivery work, analytics counts conversions |
If the site runs on a managed server, part of this — OS updates, backups, server monitoring — is already covered by the server service.
Website development work: what’s typical
- New pages and sections: services, landing pages for ads, case studies, articles.
- New features: a calculator, catalog filters, a customer account, multiple languages.
- Integrations: CRM, telephony, payment systems, delivery services, accounting software.
- Speed and technical errors: image and code optimization, redirects, fixing issues from Google Search Console.
- Design and copy: updated blocks, banners, promotions, content edits.
- Analytics: Google Tag Manager and GA4 setup, goals and events to count enquiries.
Supporting sites on WordPress, OpenCart, Laravel and more
The scope of work is the same on any platform; the details differ:
- WordPress: core, theme and plugin updates with compatibility checks, admin protection, removing plugins that slow the site down.
- OpenCart and other store platforms: payment and delivery modules, product import and export, catalog speed, updates without losing orders.
- Laravel and other frameworks: dependency updates, new features and integrations, tests before each release.
- Custom-built sites: first a code audit and documentation, so every task after that is predictable.
Website support pricing models
| Model | How it works | Best for |
|---|---|---|
| Monthly maintenance | A fixed fee for the technical part: updates, backups, monitoring, security | Every site that brings in enquiries or sales |
| Block of hours | A block of developer hours is paid in advance, and tasks are deducted from it against a report | When development is needed regularly but the volume varies month to month |
| Hourly, pay as you go | You pay only for hours worked, after the task is done | When tasks are rare and small |
| Fixed price per task | A separate quote for a specific piece of work | Large, clearly defined tasks: a new section, an integration, a redesign |
In practice the most convenient combination is monthly maintenance plus a block of hours for development. The site runs reliably, and the team always has time for new tasks without a separate budget approval each time.
Need a team to support your site?
Tell us what the site is built on and what you plan to change — we’ll suggest the right format.
How developer hours are billed
Hourly work is transparent when four rules are followed:
- Estimate up front. Before a task starts, the developer says how many hours it will take. You approve, and only then does work begin.
- A report for every hour. Afterwards you see the list of tasks and the time spent on each, not one lump sum for the month.
- Approval before overruns. If a task turns out to be harder, the team warns you before spending more time than estimated.
- Testing before release. Changes are tested on a copy of the site first and only then go live.
Here’s what a monthly report looks like:
| Task | Estimate | Actual | Status |
|---|---|---|---|
| New service page with an enquiry form | 3 h | 3 h | Live |
| Sending enquiries from the new form to the CRM | 1.5 h | 1.5 h | Live |
| Image optimization on the home page | 2 h | 1.5 h | Live |
| Copy edits on the About page | 0.5 h | 0.5 h | Live |
| Total | 7 h | 6.5 h | Last backup: daily |
An example of the report format, not a report for a specific client.
An hour covers analysis, development, testing, release and a check afterwards. Small edits are best grouped into one task — that saves time on context switching.
Urgent vs planned tasks
| Urgent | Planned | |
|---|---|---|
| Examples | The site is down, payments fail, enquiries don’t arrive | New pages, features, integrations, design changes |
| Response | The team starts right after you report it | Estimate and timing are agreed with you |
| Priority | Jumps the queue | By the priorities you set |
Agree with your provider in advance on what counts as urgent. Then there’s nothing to negotiate at a critical moment.
How many hours a month you need
We count hours not per site but for the project as a whole. Any project task is deducted from the plan:
- the website, landing pages and online store;
- the server: setup, updates, migration, new services;
- integrations with the CRM, telephony, payments and delivery;
- process automation.
| Plan | Hours a month | Best for |
|---|---|---|
| Start | 20 | The site runs smoothly, development is needed from time to time |
| Business | 35 | New pages, features and integrations every month. The most popular choice |
| Maximum | 50 | A store, portal or service with a constant flow of tasks |
That way you don’t negotiate the site, the server and each integration separately: one team does everything from one plan. The reports from the first one or two months show whether the plan fits.
If another team built the site
This is a common situation: the company has grown, and the developer who built the site has moved on to other projects. The handover to support takes three steps:
- Access. Hosting or server, domain, admin panel, code repository, Google Search Console, Tag Manager and Analytics. All of them should be registered to the company.
- Backup. A full copy of the files and database is made before any changes.
- Technical audit. CMS and module versions, speed, security, Search Console errors, forms and integrations. The result is a task list with priorities and hour estimates.
After the audit it’s clear what to do right away and what can be planned for the coming months. If the site is moving to a new server as part of the handover, we explain how to do it without downtime in “How to migrate a website to new hosting or a VPS”.
Support team vs an in-house developer
Once the site matters for sales, the question comes up: hire an in-house developer or work with a support team? Both options work; the difference is the scale of the work:
| In-house developer | Support team | |
|---|---|---|
| Skills | One person with their own stack | Frontend, backend, servers, integrations and automation in one team |
| Cost | A monthly salary regardless of workload | A block of hours, a report for every task |
| Vacation, sick leave | Needs cover | The team works without breaks |
| Server and security | Separate, or on top of the main work | Included in the same plan |
| Best for | A large product with daily development | A site, store or service that keeps growing |
We compared both models in detail — with a calculator of the real cost of an in-house developer, a quiz and a checklist for when a developer leaves — in “In-house developer or project support: which pays off for your business”.
How to choose a website support provider
Here are the questions to ask before you sign a contract:
- How fast do you respond? Separately for urgent issues (site down, payments failing) and planned work.
- How do you estimate and report? Will there be an estimate up front and a report for every task?
- Where are backups stored, and how often are restores tested? A backup that has never been restored is only an assumption.
- Do you test changes before release? A staging copy of the site is the sign of a mature team.
- Who owns the access and the code? The right answer: the company that owns the site.
- Do you support the server too? When one team handles both the site and the server, every question is solved in one chat, without hunting for who’s responsible between the host and the developer.
Checklist: what an owner can check every month
5 minutes a month
- Send a test enquiry from the site and make sure it reaches a manager or the CRM.
- Open the site on your phone: home page, a key service or product, the form.
- Check the Pages report in Google Search Console for new errors.
- Check the home page speed in PageSpeed Insights.
- Get a report from your provider: what was done, how many hours, the date of the last backup.
How we support websites
At WebCode.Agency, support is handled by the same team that builds websites and runs servers. Here’s how our dev support works:
- Response within 1 hour. We often reply in 5–10 minutes, and urgent issues are picked up immediately.
- Any stack. WordPress, OpenCart, Laravel, custom-built sites — including those built by another team.
- Estimates up front and a report for every hour. You approve each task before it starts and see where every hour went.
- Changes go to a staging copy first. Only tested work reaches the live site.
- Site and server under one roof. Updates, backups with regular restore tests, SSL and 24/7 monitoring — together with a managed server. If something stops working, fixing it is part of support.
- A dedicated account manager. One person takes your tasks, tracks deadlines and sends reports.
- Official contract and invoicing. We work under a contract and provide monthly invoices and a report.
- Your access, your data. The server, admin panel, code and data belong to your company, and you get full access.
- Plans of 20, 35 and 50 hours a month per project. They cover everything: websites, servers, integrations and automation. Plan details are on the Project support page.
How the start works:
- You send tasks wherever it suits you: Telegram, Viber, email. We move them into our CRM, where we track time and build reports.
- We get access, make a full backup and run a free express audit.
- We send a task plan with priorities and hour estimates.
- We start on the first tasks and send a report at the end of the month.
More on what we do for websites: Corporate websites and Online stores.
A site that runs reliably and keeps growing
We’ll take your site on support, even if another team built it. We start with a free express audit.
FAQ
What does website support include?
The technical part: CMS and module updates, backups, SSL, 24/7 monitoring, security and the server. And development: new pages, features, integrations, design and copy changes, speed.
What’s the difference between technical support and development work?
Technical support keeps what already exists running and is usually paid monthly. Development adds something new — pages, features, integrations — and is billed in hours or as a separate quote.
How are developer hours billed?
Before a task starts, it’s estimated in hours and approved by you. Afterwards you get a report: which tasks were done and how long each took. If a task is harder than expected, the team warns you in advance.
How many support hours do I need a month?
We offer three plans per project: Start — 20 hours, Business — 35, Maximum — 50 a month. They cover any task: websites, servers, integrations and automation. Business is the most popular choice.
Do you support sites built by other teams?
Yes. First we get access, make a full backup and run a technical audit, then send a task plan with priorities and hour estimates.
How fast do you respond?
Within 1 hour, often in 5–10 minutes. Urgent issues — the site is down, payments or enquiries fail — are picked up immediately.
Which CMSs do you support?
Any: WordPress, OpenCart, Laravel, other platforms and frameworks, and custom-built sites.
Which is better: a support team or an in-house developer?
An in-house developer suits a large product with daily development. For a site, store or service, a support team is more convenient: frontend, backend, servers and integrations in one block of hours, no breaks for vacations, and a report for every task.
Who owns the site and the access during support?
The company that owns the site. Access to the server, admin panel, code and analytics should be registered to you, and the provider works with it under your permission.
Updated November 12, 2026 · Data current as of the update date